SSL certificate checker

Check a site’s SSL certificate the way a browser meets it: whether it is valid for the name, who issued it, the days left, the chain as sent, the TLS version, old versions still let in, and whether http:// moves to https:// with HSTS.

More checksPagesDomain and email

The answer for https://www.allbirds.com/

allbirds.comValid and trusted, 66 days left

66days left, until January 7, 2027

  • ShortIt sends HSTS for 91 days. Browsers forget it after that.Raise max-age to 31536000, a year, once https is settled. The preload list asks for at least that.
  • MatchesThe certificate names www.allbirds.com.
  • TrustedThe chain verifies to a trusted root, ISRG Root X1.
  • ValidValid until January 7, 2027, 66 days from now. Issued October 9, 2026.
  • StrongThe key is ECDSA on P-256.
  • SoundIts issuer signed it with ECDSA with SHA-384.
  • TLS 1.3It agreed TLS 1.3 with TLS_AES_256_GCM_SHA384.
  • RefusedIt refuses TLS 1.0 and TLS 1.1, as it should.
  • Redirectshttp://www.allbirds.com/ moves to https:// with a 301.

The certificate

Issued to
www.allbirds.com
Issued by
YE2Let's Encrypt
Valid from
October 9, 2026
Valid until
January 7, 2027
Names it covers
www.allbirds.com
Key
ECDSA on P-256
Signature
ECDSA with SHA-384
Serial number
06379B6B940EBCB5B4A0E7CE3424EC6ECAF1
SHA-256 fingerprint
A3:DB:20:A7:D3:73:3D:87:E5:27:2D:67:00:1F:C2:F9:FB:0F:4C:A8:D9:6C:D3:C6:97:1B:EB:A5:C6:81:0A:D0

The chain as sent

The connection

Address
2620:127:f00f:e::
Version agreed
TLS 1.3
Cipher
TLS_AES_256_GCM_SHA384
TLS 1.0 alone
Refused
TLS 1.1 alone
Refused
http://
301 at http://www.allbirds.com/, then 200 at https://www.allbirds.com/
HSTS
max-age=7889238

One TLS handshake from clickd’s server on port 443, the name sent as SNI and nothing sent but the handshake; TLS 1.0 and 1.1 are tried the same way, each on its own. The chain is checked against Mozilla’s roots as Node.js ships them, close to what browsers trust. A root at the end of the chain may come from that store rather than the server, which need not send it. Then one request each to http:// and https:// for the redirect and HSTS. Valid and trusted says the connection is sound, not that the site is safe.

That was www.allbirds.com’s certificate.clickd reads the site’s first 100 pages against one rulebook and ranks every fix by what it is worth. Free, about a minute.
Read the whole site
A certificate in good orderExample
A 90 day certificate
  1. Day 0 to 60Issued, and in use
  2. Day 60 to 90Renewed here, before it expires
The chain a browser checks
  1. example.comIts own certificate, sent by the server
  2. IntermediateSent by the server with it
  3. RootAlready trusted, kept by the browser

Renewal runs on its own with a month to spare, and the server sends the intermediate, so a crawler that never fetches one still trusts the chain.

What does it check?

No rule in the rulebook covers this, so here is what it reads.

  1. Whether the certificate is valid for the name, and who issued it
  2. When it expires, and how many days are left
  3. Whether the chain is whole, so every browser and crawler trusts it
  4. The TLS version the server offers

Questions

What happens when a certificate expires?

Browsers show a warning in place of the page, and crawlers stop reading it.

Does https help a site rank?

Google counts it as a small signal. A site without it is marked not secure in every browser.

Why does my certificate work in one browser but not another?

Usually an intermediate certificate is missing from the chain. Some browsers fetch it themselves, and many crawlers do not.