1. Home
  2. Developer
  3. SSL Checker

SSL Checker

Check a domain's HTTPS certificate expiry, hostname match and TLS setup.

For every format and option in one place, use Network Diagnostics →

Measured by an outside service · the address you type is sent to Globalping
The domain you type is sent to an outside measurement service (Globalping), and probes in the regions you pick connect to its HTTPS (port 443) and read the certificate. The target server will log the probe IP. Private and internal addresses are not measured, and the tool sends one request per domain, so it cannot be used for load or scanning.
Example: example.com (a scheme or path is ignored, only the domain is used)
Regions

This is one connection from one probe location. With several servers or a CDN, different locations can get different certificates, and only the server (leaf) certificate is shown, not the whole chain. Trust is judged against the probe trust store, which can differ from your browser or OS.

How to use

  1. Type a domain such as example.com under Domain to check. A scheme or path is ignored and only the domain is used.
  2. Pick the regions. South Korea is the default, and with several regions each one connects separately and the results appear side by side.
  3. Press Check certificate. A measurement probe in each region connects to the domain over HTTPS (port 443) and reads the certificate the server presents.
  4. In the summary, read the days left until expiry, trust, issuer and TLS version. The table below lists the subject (CN), SAN names, validity start and end, cipher, key type and size, and SHA-256 fingerprint.
  5. Read the problems and suggested fixes under What it means. Copy result gives you the text.

It shows the same kind of information as the padlock in your browser address bar, but it connects from probes in other regions rather than from your own browser. It is also handy to confirm that a newly installed certificate is really what the server serves.

What is checked and how it is judged

Item Rule Shown as
Days until expiry 8 to 30 days Warning
Days until expiry 7 days or less Critical (renew now)
Expired End time has passed Error
Hostname match The domain is among the SAN names (exact or wildcard) OK
Hostname match Not in the SAN Error
TLS version 1.3 good, 1.2 note, 1.1 or older error Error
Key size RSA under 2048 bits, EC under 256 bits Warning

The 30 and 7 day thresholds are this tool’s own rule of thumb. The tool compares the SAN list itself to judge the hostname, and it also shows the verification result reported by the measurement service.

The wildcard rule: *.example.com stands for exactly one leftmost label.

Domain entered Matches *.example.com
www.example.com Match
example.com No match (the bare domain needs its own name)
a.b.example.com No match (two labels)

As a real case, the certificate of the test site wrong.host.badssl.com only lists *.badssl.com and badssl.com, so that two-label subdomain does not match.

Reading the error reasons

When verification fails, the measurement service returns an error code and this tool explains it.

Error code Meaning Fix
CERT_HAS_EXPIRED The certificate (or one in the chain) has expired Renew and deploy again
DEPTH_ZERO_SELF_SIGNED_CERT Self-signed certificate Replace with a public certificate
SELF_SIGNED_CERT_IN_CHAIN The chain has a self-signed certificate that is not a public root Check whether it is a private CA
UNABLE_TO_VERIFY_LEAF_SIGNATURE Intermediate certificate missing Install the fullchain file
ERR_TLS_CERT_ALTNAME_INVALID The domain is not in the SAN Reissue with the right names
CERT_REVOKED Revoked certificate Get a new one

For instance, expired.badssl.com deliberately uses a certificate that expired on 2015-04-12, so it returns CERT_HAS_EXPIRED, while self-signed.badssl.com returns DEPTH_ZERO_SELF_SIGNED_CERT.

How often to check expiry

  • With automatic renewal (ACME, for example Let’s Encrypt) renewal happens by itself, but a common accident is the server never loading the new file and still serving the old one. Check the real days left with this tool about once a month.
  • With manual renewal, set reminders 60, 30, 14 and 7 days before expiry.
  • The maximum lifetime of public certificates keeps getting shorter. Under the schedule the CA/Browser Forum approved in 2025 it is 200 days from 15 March 2026, 100 days from 15 March 2027 and 47 days from 15 March 2029. Schedules can change, so check your issuer’s notices. Either way, it pushes toward automation.

What is sent, and the limits

  • The domain you enter is sent to the measurement service Globalping, and the probe IP is logged by the target server. See the privacy policy for details. Results are not stored.
  • Private and internal addresses are not measured, and only port 443 is checked. There is an hourly request limit.
  • This sends one request per domain as a checking tool. It is not meant for generating load or scanning, and it never repeats automatically.
  • It shows the server (leaf) certificate only, not the whole chain. To decode a certificate file itself, paste the PEM into the SSL Certificate Viewer.
  • Trust is judged against the probe trust store, which can differ from your browser.

Frequently asked questions

What happens to a site when its certificate expires?

Browsers show a full-page warning such as “Your connection is not private”, and many visitors leave on the spot. API clients and apps often refuse to connect at all.

I renewed the certificate but the expiry date did not change.

The server or load balancer probably has not loaded the new file yet. Many setups need a reload or restart. With a CDN, renewal can reach regions at different times, so pick several regions and compare.

The domain matches but it says mismatch.

Check whether your input has www and how many labels the subdomain has. If the certificate lists only example.com and not www.example.com, the www address does not match. If the address redirects elsewhere, use the Redirect Checker to see the final address and check that domain.

Is checking the certificate enough for security?

No. This tool only looks at the certificate and the TLS handshake. For response headers such as HSTS, use the HTTP Security Header Checker.

The domain does not connect at all.

First check that the domain resolves with the DNS Lookup. A connection failure message also names the cause: unresolved domain, port 443 refused, timeout, or TLS handshake failure.

The domain you enter is sent to an outside measurement service (Globalping) and is never stored on this site’s servers.

Can't find the tool you need?

Tell us what you want to do. We build the most requested tools first.