SSL Checker
Check whether your browser can establish a trusted HTTPS connection to a domain. Browsers deliberately hide detailed certificate data from JavaScript, so this checks connectivity honestly rather than faking certificate details.
Web browsers deliberately don't expose certificate details (issuer, expiry date, etc.) to JavaScript for security reasons. This tool can honestly tell you whether your browser trusts the connection enough to complete it, but not the certificate's specific details - for that, check your browser's padlock icon or a dedicated service like SSL Labs.
Recommended Settings
Pro Tips
- •A successful connection here confirms your browser trusts the certificate enough to connect - it doesn't tell you the issuer, expiry date, or other certificate details, since browsers don't expose those to JavaScript
- •To see full certificate details, click the padlock icon in your browser's address bar while visiting the site directly, or use a dedicated service like Qualys SSL Labs
- •A failed check could mean several different things: an expired certificate, a self-signed certificate, a DNS failure, or the server being completely unreachable - this tool can't distinguish between these causes
- •This makes a real network request directly to the domain you specify - no third-party service is involved in the check itself
Most Popular
Most users use this for a fast yes/no check before digging deeper with browser dev tools or a dedicated SSL testing service
When to Use This Tool
Get a fast yes/no answer on whether a domain's HTTPS setup is trusted by your browser.
Confirm whether a certificate issue is actually preventing connections, as a first troubleshooting step.
Do a quick sanity check that HTTPS is working before directing more thorough testing tools at a new site.
Quickly compare whether several related domains or subdomains all have valid, trusted HTTPS set up.
How It Works
Attempt a direct network request to the specified domain over HTTPS, using no-cors mode so the request isn't blocked purely for cross-origin reasons
If the browser's TLS handshake fails - due to an invalid, expired, or untrusted certificate, or the server being unreachable - the request throws an error, which is reported as a failed connection
If the handshake and connection succeed, the request resolves (even though its actual response content is inaccessible due to CORS), which is reported as a successful connection
100% Private
Files never leave your device. All processing happens locally in your browser.
Lightning Fast
Powered by Browser native Fetch API with a direct connection attempt for optimal performance on modern browsers.
Open Source
Built with verified, open-source libraries. Fully transparent.
Frequently Asked Questions
Why can't this show me the certificate's expiry date or issuer?
Browsers deliberately don't expose TLS certificate metadata to JavaScript running on a web page, as a security and privacy measure. This is a hard platform limitation, not something this tool chooses to omit.
How do I see full certificate details then?
Click the padlock or site information icon in your browser's address bar while visiting the site directly - browsers show full certificate details there. Alternatively, use a dedicated tool like Qualys SSL Labs' SSL Test for an in-depth server-side analysis.
What does a failed connection actually tell me?
It tells you your browser could not complete an HTTPS connection to that domain, which could be due to an invalid certificate, a DNS problem, or the server being down - this tool can't distinguish between these specific causes.
Is my check sent through a third-party service?
No. This tool connects directly from your browser to the domain you specify - there's no proxy or third-party service involved in the connection attempt itself.
Can this test a specific port or subdomain?
Enter the exact domain or subdomain you want to check (like sub.example.com). This tool always checks the standard HTTPS port (443) and doesn't currently support testing custom ports.