Works in Chrome, fails in curl?
It’s usually the chain. See exactly what your server sends, what’s missing, and whether anything is revoked or distrusted.
What you get
sample · example.com
What we check
Browsers fetch missing intermediates on their own; curl, Java, Android and most API clients do not. If your server only sends the leaf, those clients fail with unable to get local issuer certificate or PKIX path building failed. The checker shows the gap and the intermediate to install.
The browser could not build a path to a root it trusts. Usually the certificate is self-signed, the chain is incomplete, or the CA has been distrusted. Run the check to see which.
The sequence of certificates that links your server’s certificate to a root CA that browsers and operating systems already trust: your leaf certificate, one or more intermediates, then the root.
We download the issuing CA’s certificate revocation list (CRL) and look for your certificate’s serial number. A match is what browsers report as NET::ERR_CERT_REVOKED.
The chain checker connects to a live server and checks the chain it sends. The certificate decoder reads a PEM you paste, without connecting to anything.
Yes. Add the domain as a free monitor and you are alerted before it expires, when the chain changes, or when its CA lands on an advisory.
Free plan
Get told before it breaks.
Monitoring watches this certificate for you and emails you before it expires, when the chain changes, or when its CA is distrusted.
1 monitor, checked every 10 seconds
From six locations, confirmed before we alert, so no false alarms.
Certificate expiry alerts
Email 30, 14 and 7 days before it runs out.
Security scans and change alerts
Certificate, chain, headers, DNS and email security, with an email when anything changes.
Cloudflare offline page
Visitors see a status page instead of an error while you fix it.
12 months of history
Every check, change and incident, kept for a year.
Slack, JIRA, Linear and Teams
Send alerts where your team already works.