Cost per run
Runs on our own server with no purchased data.
SeemerceA suite of proprietary diagnostic tools to monitor keyword positions, technical page health, and SERP dynamics.
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.
The days left before the certificate expires, its issuer, and whether it covers your domain.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Check before the expiry date arrives: a direct link to port 443 on your domain, a read of the certificate itself, and the dates, issuer, protocol version and names it covers. No external service in between.
Tap any step to read the details behind it.
You see how many days remain before the expiry date arrives.
Which authority issued the certificate and which protocol version.
See whether the certificate covers your domain.
A direct connection to port 443 and a read of the certificate itself.
It has not expired, a trusted authority issued it, and it covers your domain.
Per visitor. A free account raises the cap.
Every output has a job; see which one is yours.
Tap any solution to see exactly what it includes.
Expiry.
And protocol.
Which names the certificate covers.
With no middleman.
Per visitor.
Honestly.
We set the SSL Labs rating guide and MDN's guide beside this tool.
SSL Labs treats the certificate as a precondition: matching name, valid dates, trusted CA and not revoked; otherwise the score is zero.
With us The dates, the issuer and the list of covered names are shown.
Expiry is one of the certificate validity conditions.
With us The days left before expiry are visible before it arrives.
SSL Labs scores protocol support from SSL 2.0 (zero) to TLS 1.3 (full).
With us The protocol version is shown.
MDN: a Strict-Transport-Security header with a max-age of at least six months, ideally two years; SSL Labs caps invalid HSTS at A-.
With us HSTS is not part of this tool's output; it reads the certificate and protocol.
SSL Labs assesses the server with direct requests.
With us A direct connection to port 443 on your domain and a read of the certificate itself; no external service in the path.
Sources: SSL Labs (SSL Server Rating Guide); MDN — TLS (2026)
Each reference's figure comes from its own source and Seemerce's from this page.
Runs on our own server with no purchased data.
SeemerceA daily cap per visitor so no bot takes all the capacity; a free account lifts it.
SeemerceProtocol support's share of the SSL Labs score.
SSL LabsKey exchange's share.
SSL LabsCipher strength's share.
SSL LabsThe recommended minimum HSTS max-age.
MDNSources: SSL Labs (SSL Server Rating Guide); MDN — TLS (2026)
Only what each platform's page says outright is marked; a blank means the page does not say.
| Practice | SSL Labs | MDN | Seemerce |
|---|---|---|---|
| A valid certificate (dates, CA, name)1 of 2 | Dates, issuer and names | ||
| Protocol version1 of 2 | Version shown | ||
| HSTS2 of 2 | Not part of this tool's output | ||
| Redirect HTTP to HTTPS1 of 2 | Not part of this tool's output |
stated on their published page not stated there (it may still be done)
Sources: SSL Labs (SSL Server Rating Guide); MDN — TLS (2026)
The price of one run in dollars; tools with purchased data have a real cost deducted from a wallet, while tools on our own server are free.
Sources: each tool's Seemerce page
Only what this page already promises.
Validity, issuer and expiry date of a domain certificate.
The rule is simple: See joins a word to make one new word, just as See and commerce became Seemerce.
Related names
This site only needs essential cookies to work. With your permission, we also use Google Analytics to learn which pages are most useful. It is your choice, and you can change it at any time. Cookie Policy