Free certificate checker
Check the certificate a website serves: who issued it, which names it covers, when it expires and whether browsers trust it.
Example report
example.com- 1 High
- 5 passed
Certificate does not cover this hostnamewww.example.comHigh
The certificate served for www.example.com lists example.com only.
Next step
Issue a certificate whose subject alternative names include this hostname, or a wildcard that covers it, and install it.
example.com
- HTTPS availability
- Certificate validity
- Certificate expiry
www.example.com
- HTTPS availability
- Certificate expiry
Certificate
example.com
- Issued to
- example.com
- Issuer
- Example Issuing CA
- Names covered
- example.com, www.example.com
- Valid from
- 1 July 2026
- Expires
- 14 January 2027
- Signature
- ecdsa-with-SHA256
- Chain sent
- 2 certificates
- Serial number
04:7a:1c:9e:52
www.example.com
- Issued to
- example.com
- Issuer
- Example Issuing CA
- Names covered
- example.com
- Valid from
- 1 July 2026
- Expires
- 14 January 2027
- Signature
- ecdsa-with-SHA256
- Chain sent
- 2 certificates
- Serial number
04:7a:1c:9e:53
What the certificate check looks at
Trust
Check that the chain leads to a root in Mozilla's root store.
Names covered
Check that the name you visit is listed, directly or through a wildcard.
Validity dates
See when the certificate started and when it runs out.
Chain and details
See the issuer, signature algorithm, chain length and serial number.
Revocation is not checked, so a certificate its authority has revoked can still show as trusted.
Understand the issue and your next step
Each finding explains what we found, why it matters and what you can change. Start with the issues that need attention, then open the evidence when you want the detail.
- Enter your domain
- Review the findings
- Follow the fix guides
Certificate does not cover this hostnameHigh
The certificate presented is not valid for the hostname that was requested.
Names covered: example.com
Name visited: www.example.comBrowsers show a warning because the certificate was issued for a different name.
Issue a certificate whose subject alternative names include this hostname, or a wildcard that covers it, and install it.
Common certificate issues you can put right
Certificate does not cover this hostnameHigh
The certificate does not list the name being visited, often the www name or the bare domain. Reissue it with every name you serve.
Certificate is not trustedHigh
Browsers do not trust the chain, usually because the server leaves out its intermediate certificate. Configure the server to send the full chain.
Certificate has expiredHigh
The certificate presented has passed its expiry date.
Certificate is not yet validHigh
The certificate presented has a start date in the future.
Keep watch after you've fixed it
Ironfang Security rechecks a verified domain every week or every day and tells you what changed: new findings, fixes and certificates nearing expiry.
Free during the preview. Domain verification required.
- NewIssue detected
- FixedConfirmed by recheck
- ReopenedDetected again
How the check works
- The site's own (leaf) certificate, served on port 443 for the domain and for its
www.name, or for the one subdomain entered. - Trust: whether the certificates sent chain to a root in Mozilla's root store, the list of authorities Firefox ships with and many other systems reuse.
- Hostname coverage: whether the name is among the certificate's subject alternative names, directly or through a wildcard such as
*.example.org. - Validity: the not-before and not-after dates, compared with the current time.
- Details for the record: subject, issuer, signature algorithm, how many certificates the server sent, and the serial number.
Reading a result
A certificate binds a public key to one or more hostnames, and a certificate authority's signature vouches for that binding. Browsers accept it only when three things hold: the chain leads to a root they trust, the name being visited is listed in the certificate, and today's date falls inside its validity period.
Each of those has its own finding. Untrusted usually means a self-signed certificate, one from a private CA, or a server that leaves out the intermediate certificate. A name mismatch often shows on just one host: the www. name, or the bare domain when the certificate was issued only for www..
Use the details to compare what is served with what you expect: the issuer you chose, every name you serve, and a chain made of your certificate plus its intermediates. A chain of one usually means the intermediate is missing.
What it does not do
- Revocation is not checked, so a certificate its authority has revoked can still show as trusted here.
- Trust is judged against Mozilla's root store. Other platforms keep their own lists, which largely but not exactly match it, and a certificate from a private CA trusted inside your organisation will show as untrusted.
- The certificate is read from a TLS 1.2 or 1.3 handshake. A server that cannot complete one gets an HTTPS finding instead, and its certificate is not read.
- Certificates for other names, such as mail or API hosts, need their own run, one subdomain at a time.
What happens to the domain you enter
The check runs from Ironfang Security's published scanner address with the same low-impact limits as a scan. Nothing you enter is stored or logged. A result is reused for five minutes, and a certificate log search for an hour, so a repeat check is quick and the domain is not checked again.
Guides
A few things worth knowing
- What is an SSL certificate?
- The certificate a server presents during a TLS handshake. It lists the hostnames it is valid for and carries a public key, signed by a certificate authority. The SSL in the name is historical; the protocol in use is TLS.
- Why does my certificate work in a browser but fail elsewhere?
- Often because the server does not send its intermediate certificate. Some browsers fill the gap from their own cache, while command-line tools, apps and other servers cannot. Configure the server to send the full chain.
- Does a wildcard certificate cover the bare domain?
- No. A wildcard such as *.example.org covers names one level below, like www.example.org, but not example.org itself or a.b.example.org. Most certificates list the bare domain as a second name alongside the wildcard.

