Enter a domain to see every public TLS certificate on it, which ones are renewed by hand, and how many renewals a year you'll need from March 2027.
Free. Passive: we read public Certificate Transparency logs and never contact your servers.
Searching public certificate logs…
This usually takes 10–60 seconds. Busy domains can take a couple of minutes.
| Hostnames | Issuer | Renewal | Expires | Days left | Valid for |
|---|
Each row is a set of hostnames someone has to keep renewed; repeat renewals of the same certificate are counted once. "By hand" is a best guess from the issuing CA. This shows public certificates only: firewalls, VPNs, RDP and internal servers that use private or self-signed certificates don't appear in public logs.
We're building CertScan for UK IT providers: one console for every client, renewal agents for the devices free tools don't reach, and tickets straight into your PSA.
Early-access partners get it free until launch.
The CA/Browser Forum has voted to shorten the maximum life of public TLS certificates in three steps. Every certificate will need renewing more and more often.
| From | Max life | Renewals / yr |
|---|---|---|
| 15 Mar 2026 | 200 days | ~2 |
| 15 Mar 2027 | 100 days | ~4 |
| 15 Mar 2029 | 47 days | ~8 |
Every publicly trusted certificate is recorded in public Certificate Transparency logs. CertScan reads those logs (via crt.sh and Cert Spotter) for your domain and its subdomains. It never connects to your servers.
Certificates from Let's Encrypt, Google and cloud platforms are almost always renewed automatically. Ones bought from commercial authorities like DigiCert, Sectigo or GoDaddy are often installed by hand, and those are the ones that cause outages when renewal goes from yearly to every few months.
Certificates that never appear in public logs: internal servers, firewalls and VPNs with private or self-signed certificates, and devices on private networks. Those are often the hardest to keep renewed, and the reason we're building the full product.