An SSL Certificate Check before the expiry date arrives
A direct link to port 443 on your domain, a read of the certificate itself, and a display of the dates, the issuer, the protocol version and the list of names it covers. No external service lies in the path.
- No sign-up
- Days left to expiry
- List of covered domains
Run the tool right here on the page
The days left before the certificate expires, its issuer, and whether it covers your domain.
- What it costs Free
- Data source Our own server
- Access No sign-up
The short answer
A healthy SSL certificate has three properties: it has not expired, a trusted authority issued it, and it covers precisely the name the visitor enters in the address bar. If any one of the three is missing, the browser shows a red warning page and effectively nobody enters the site.
In most of what reaches us the fault is not expiry; the right name is not under the certificate. The certificate is set for example.com and the visitor opens www.example.com, or the other way round. The fix is simple: both forms belong in the list of covered names. This tool shows that list in full, and within seconds the fault is visible.
The second pattern makes less noise: the full chain does not arrive. The certificate is sound but the server omits the intermediate link. The page then opens fine in desktop Chrome and errors on an older Android phone or inside apps. The owner sees nothing wrong on their own device, so it can run for months.
This certificate does weigh on a Google ranking, but only slightly. The real damage happens elsewhere: with no padlock the browser marks a payment form as unsafe, and a visitor who reads about online fraud all the time closes the page at that instant. Do not count the cost of an expired certificate in ranking, count it in lost orders.
The data source and method
A direct TLS connection from our own server, with no third-party service. A point that matters for .ir domains: Let's Encrypt certificates run for three months, and we have seen their auto-renewal fail quietly on Iranian shared hosts more than once, with nobody aware until the moment of expiry. Treat the "days remaining" figure as significant.
The situations where it helps
When the browser raises a security warning, or to catch an expiry before it lands. An expired certificate means every visitor meets a red warning page and the bounce rate is effectively total.
Where it falls short
This tool reads the certificate, it does not assess the security of the site. A site can have a perfectly healthy certificate and at the same time a vulnerable plugin, a weak admin password and security headers switched off. The green padlock only says the connection is encrypted, not that the other end is trustworthy. For the wider view see our website security scan. One technical note: the result comes from our server, so if your site serves a different certificate to non-Iranian IPs, what you see here differs from what a visitor inside Iran sees.
A lesson from working with it
Let's Encrypt certificates last three months and are supposed to renew automatically. On Iranian shared hosts we have repeatedly seen that automatic renewal break silently, with no warning recorded anywhere, until the day the certificate expired and the site came up with a red page. If you are on that kind of host, look at the days-left number once a month; that single habit makes the silent failure visible.
What it costs
This tool executes on our own infrastructure with no purchased data behind it, so it costs nothing and stays that way. Its only limit is a daily cap that stops one bot from taking the whole capacity.
The daily cap is measured per visitor. If you need more, a free account lifts your limit.
Common questions about this tool
How many days before expiry should I worry?
If the certificate renews automatically, fewer than 14 days means the auto-renewal has failed and you should look at it that day. If you buy the certificate by hand, begin a month ahead so there is time to issue and install it.
Does a free certificate differ from a paid one for SEO?
None. Google makes no distinction between free and paid certificates and the browser shows the same padlock. The difference lies in insurance, support and organisation validation, not in rankings.
The certificate is healthy but the browser still warns. Why?
Usually mixed content: the page loads over https but something within it, an image or a script, loads over http. The browser treats that as reason enough to drop the padlock. Check the URLs of the resources on the page.
Validity, issuer and expiry date of a domain certificate.
One rule throughout: See fuses onto a word and makes a single new one, never two words side by side. Exactly as See and commerce became Seemerce.
Neighbouring names
- Rising trends SeeRise
- Keyword overview SeeVolume
- Keyword suggestions SeeIdeas
- Site keywords SeeTerms
- Ranked keywords SeeMatch
- SERP viewer SeeSerp
- Backlink checker SeeLinks