Back

SSL Checker

Check a site's certificate and which TLS and HTTP versions it supports, from TLS 1.0 to 1.3 and HTTP/1.1 to HTTP/3. It also tests post-quantum key exchange, HSTS, redirects and compression, or puts two sites side by side.

TechCompare's server connects to the site on ports 443 and 80 to run the checks. Your browser asks Cloudflare's DNS for the site's HTTPS record. See the privacy policy.

Check a site

Type a domain above, or try one of these. Nothing is sent until you press Check.

How to use this tool

  1. Enter a site

    Type a domain like example.com. You can paste a full URL too, and the tool keeps only the host. It checks ports 443 and 80, so a link with any other port is refused.

  2. Press Check

    TechCompare's server connects with each TLS version, reads the certificate, tries HTTP/2 and a real QUIC handshake for HTTP/3, and follows the redirects from plain HTTP. It takes a few seconds, and up to 15 for a slow site.

  3. Read the summary

    The top card says how many problems it found and lists every finding, problems first. The cards below show each check: HTTP versions, TLS versions and ciphers, the certificate and its chain, HSTS and ECH, the redirect chain, and the CDN and compression.

  4. Compare two sites

    Press Compare Sites and enter a second domain. Both get checked, and a table puts the same checks side by side, with every card for each site below it.

About this tool

This SSL checker connects to a site the way browsers do and reports what it finds. It tries each TLS version from 1.0 to 1.3 and notes the cipher the server picks, reads the certificate and its chain, and tests HTTP/2 and HTTP/3. HTTP/3 gets a real QUIC handshake over UDP, so the result says whether it works, not only whether the site claims it.

The checks run on TechCompare's server, so they work for any public site and don't depend on your network. Your browser only asks Cloudflare's DNS for the site's HTTPS record, which can advertise HTTP/3 and carry an ECH key.

Advertised and working HTTP/3

A site tells browsers about HTTP/3 in two places: the Alt-Svc header on its HTTPS answers, and the alpn list of its HTTPS record in DNS. Either one makes a browser try QUIC. The checker reads both and runs its own QUIC handshake, so it catches the two common mistakes. One is a site that advertises HTTP/3 while a firewall blocks UDP port 443, which makes browsers try QUIC and fall back. The other is a server that speaks QUIC without telling anyone.

TLS versions and ciphers

TLS 1.3 connects in one round trip instead of two and only allows strong ciphers. TLS 1.2 is still fine with modern ciphers, and keeping it helps older phones and apps. TLS 1.0 and 1.1 are a different story. Chrome, Edge and Firefox dropped them in 2020, so leaving them on mostly helps old scanners flag the site. For each version that works, the checker shows the cipher suite and, for TLS 1.3, the key exchange group the server picked.

Post-quantum key exchange

The checker offers X25519MLKEM768 next to X25519, the same pair current Chrome and Firefox send, and reports which one the server picks. Yes means the session keys are safe from a quantum computer that doesn't exist yet. No means the server picked a classic group like X25519, which is still secure today. If the handshake only fails when the post-quantum key is offered, the checker flags it as a problem, since real browsers send that hello every time.

What the certificate check covers

It reads who issued the certificate, when it expires and how many days that leaves, which names it covers, its key type and its signature. Then it checks the chain the server sends against trusted roots, the way a strict client like curl does. Expired, not yet valid, wrong name, untrusted and self-signed certificates are problems, since browsers show a full-page warning for each. An incomplete chain is flagged to look at, because most browsers work around it and many apps don't.

HSTS, redirects and ECH

The checker requests http:// on port 80 and follows each redirect, so you see every hop and where it ends. Then it reads the Strict-Transport-Security header, which tells browsers to use HTTPS for the site from then on, and checks it against the HSTS preload list's rules. ECH comes from the HTTPS record. With it, browsers encrypt the name of the site they connect to, so the network in between only sees the CDN.

Comparing two sites

Compare mode checks two sites at once and lines up every result in one table: TLS versions, post-quantum, HTTP/2 and HTTP/3, the certificate, HSTS, ECH, IPv6, compression and the CDN. It's handy for checking a new server against the old one before a move, or a staging site against production.

HTTPS, TLS and certificate guides

How each check works, what a failing one means and how to fix it.

Frequently asked questions

Does HTTP/3 need TLS?
Yes. HTTP/3 runs on QUIC, and QUIC has TLS 1.3 built into its own handshake, so there's no HTTP/3 without TLS 1.3. QUIC also runs over UDP instead of TCP, usually on port 443. So a site needs three things for HTTP/3: TLS 1.3, a server that speaks QUIC, and UDP port 443 open all the way through its firewall. That's why the checker runs a real QUIC handshake instead of trusting what the site says about itself.
Why does HTTP/3 work but browsers don't use it?
A browser always starts over TCP, because it can't know a site speaks QUIC until something tells it. That's the Alt-Svc header in an HTTPS answer, or the alpn list in the site's HTTPS record in DNS. Without either one, the browser stays on HTTP/2 even though the server would answer over HTTP/3. The checker shows both, next to the result of its own QUIC handshake.
What does post-quantum key exchange mean?
The key exchange is how the browser and the server agree on the keys that encrypt the connection. X25519MLKEM768 mixes the classic X25519 exchange with ML-KEM, a method NIST standardized because large quantum computers could break X25519 one day. Someone who records encrypted traffic now could decrypt it then, so sites switch early. Chrome, Edge and Firefox offer it already, and the checker tests whether the server picks it.
What does it mean when the post-quantum check fails?
It means TLS 1.3 breaks when the hello carries the post-quantum key, but works without it. That hello is bigger than one packet, and some old firewalls and load balancers drop it. Visitors on current Chrome, Edge and Firefox send exactly that hello, so they may not reach the site at all. The fix is usually a firmware update on whatever sits in front of the server.
Is it SSL or TLS?
TLS. SSL was the name of the older versions, and every one of them is broken. Browsers switched them off years ago. TLS replaced it in 1999, but people still say SSL, so SSL certificate and SSL checker stuck. The certificate itself works the same with either name.
Why does my browser show a padlock when the checker finds an incomplete chain?
The server should send its own certificate plus the intermediate certificate that links it to a trusted root. When it leaves the intermediate out, most desktop browsers fetch it themselves or have it cached from another site. curl, apps, scripts and some phones don't, so they fail with a certificate error while your browser looks fine. Configure the server with the full chain file your certificate authority gave you.
Why can't I check the same site again right away?
One check opens about 15 connections to the site, so TechCompare keeps each result for 10 minutes and shows it to everyone who asks in that time. Check again starts a new check once the last one is 30 seconds old. Each visitor can also run 10 checks in a row, and after that one more every 15 seconds. Compare mode counts as two checks.
Which sites can it check?
Public sites on ports 443 and 80. The checker refuses private and local addresses, like a router at 192.168.1.1 or a server on your own network, since TechCompare's server can't and shouldn't reach them. It also connects over IPv4, so a site with only IPv6 addresses can't be checked yet. It still lists the AAAA records of sites that have both.