TapCub is live — analytics, insights and live chat, free on one platform

Free tool SSL checker: is this certificate valid, trusted and not about to expire?

Enter a domain and get the certificate a browser would receive: when it expires, who issued it, whether it covers the name you typed, whether the chain is complete, and which TLS version and HTTP version the server agrees to. Every problem comes with the fix.

  • Days left, at a glance
  • Full chain shown
  • One handshake, on click

Check an SSL certificate

Type a domain or paste a URL; only the host name is used, on port 443. The result below is a dated sample until you click Check.

Checker

For example example.com or shop.example.com. Subdomains can have their own certificate, so check the exact name visitors use.

Try a broken one:

What is sent, and to whom

  • Nothing is requested when the page opens. When you click Check, your browser sends only the host name to TapCub’s own API (a tapcub.com server).
  • Our server in the US resolves the name and opens one TLS connection to port 443, with the name as SNI. It reads the certificate and closes the connection without sending an HTTP request.
  • The domain and the result are not saved. Your IP address is counted for the limit of 10 checks a minute and 100 a day, and that is all.
  • Private, internal and IP addresses are refused, so the checker cannot be pointed at a network behind it.

Sample: tapcub.com as checked on 2026-11-17 while building this page. Click Check for a live result.

Valid

The certificate for tapcub.com is valid and trusted, with 64 days left.

Expires

2027-01-20

64 days left

Issued by

Google Trust Services

WE1

Covers this name

Yes

tapcub.com

Chain trusted

Yes

4 certificates in the chain

TLS version

TLSv1.3

TLS_AES_256_GCM_SHA384

HTTP/2

Offered (h2)

ALPN: h2

Key

EC P-256

Issued 2026-10-22

Server address

—

Handshake 436 ms

Checks and fixes

  • OKValid until 2027-01-20: 64 days left.
  • OKThe certificate lists tapcub.com.
  • OKThe chain verifies up to a trusted root.
  • OKTLSv1.3 was negotiated, the current version.
  • OKHTTP/2 is offered (ALPN “h2”).
  • OKKey: EC P-256.

Names on the certificate (3)

Subject Alternative Names: the only names browsers check. A wildcard such as *.example.com covers one level of subdomains, not the bare domain.

  • tapcub.com
  • lab.tapcub.com
  • *.lab.tapcub.com

Certificate chain

From the site’s certificate up to the root. Hover a date for the days left, or a fingerprint for the full SHA-256 value.

#RoleSubjectIssuerExpiresKeySHA-256 fingerprint
1Site certificatetapcub.comWE1 · Google Trust Services2027-01-20EC P-256F8:78:48:78:EB:89:1C:9A…
2IntermediateWE1GTS Root R4 · Google Trust Services LLC2029-02-20EC P-2561D:FC:16:05:FB:AD:35:8D…
3IntermediateGTS Root R4GlobalSign Root CA · GlobalSign nv-sa2028-01-28EC P-38476:B2:7B:80:A5:80:27:DC…
4RootGlobalSign Root CAGlobalSign Root CA · GlobalSign nv-sa2028-01-28RSA 2048EB:D4:10:40:E4:BB:3E:C7…

Share these inputs: the values go after the # in the link, so they never reach a server.

Version v1.0Updated Update history

Read the result

What each check means

A certificate passes only when all four of these hold. The version checks below them are about speed and hygiene, not the padlock.

Expiry

Certificates are short-lived on purpose. Under the CA/Browser Forum’s rules, public certificates issued from 15 March 2026 last at most 200 days, falling to 100 days in 2027 and 47 in 2029. Under 30 days left on an automated certificate usually means renewal has stalled.

Hostname match

The name in the address bar must appear in the certificate’s Subject Alternative Names. A wildcard *.example.com matches shop.example.com but not example.com or a.b.example.com.

Chain trust

Your certificate is signed by an intermediate, which is signed by a root that browsers ship with. The server has to send the intermediate. “Trusted” means the whole path verified from this server.

Key

ECDSA P-256 and RSA 2048 or larger are the norm. The key length says nothing about the encryption of the page itself, which is negotiated per connection.

TLS version and cipher

TLS 1.3 is current and TLS 1.2 is still acceptable. TLS 1.0 and 1.1 were deprecated in 2021, and browsers refuse to use them.

HTTP/2 (ALPN)

During the handshake, the client and server agree on HTTP/2 or HTTP/1.1. “h2” means HTTP/2 is available, which loads pages with many files faster.

Revocation (OCSP and CRL) is not checked here. A revoked certificate is rare and shows up only if the issuer’s chain verification reports it.

How to use it

Three steps

No sign-up, no install.

  1. 1

    Enter the exact name

    Use the name visitors type: example.com and www.example.com can have different certificates. A pasted URL is fine; only the host is used.

  2. 2

    Check

    One TLS handshake on port 443 from our server. It takes a second or two.

  3. 3

    Fix from the top

    Problems come first, each with the fix. Copy the report for your host or developer, and check again after the change.

How it works

A TLS handshake, read carefully

The checker connects to the domain the way a browser starts a visit, then stops before any HTTP request. Everything shown comes from that one handshake.

  • DNS is resolved first. Private, loopback and cloud-metadata addresses are refused, and the connection goes to the address already checked
  • The host name is sent as SNI, so servers that host many sites return the certificate for this one
  • Trust is verified against a standard root store (the one Node.js ships, from Mozilla’s list); the hostname is matched per RFC 9525, which ignores the old Common Name field
  • Days left = whole days from now until the certificate’s “not after” time, rounded down
  • The chain is listed as the server sent it, completed with the root when the root is in the store
  • Not checked: other ports, revocation status, HTTP headers such as HSTS, and every address of a site with several IPs. A CDN may serve a different certificate in another region
Thresholds this checker uses
CheckOKWarningProblem
Days left30 or more14–29Under 14, or expired
HostnameListed in SANs—Not listed
ChainVerifies to a trusted root—Incomplete, self-signed or untrusted
TLS version1.3 (1.2 noted)—1.0 or 1.1
RSA key2048 bits or more—Under 2048
HTTP/2h2 offeredNote if not—
Example

tapcub.com, checked on 2026-11-17

The sample result at the top, read line by line.

TLS check of tapcub.com, 2026-11-17
ItemValueReading
Validity2026-10-22 to 2027-01-20A 90-day certificate with 64 days left: renewed automatically, well inside the 30-day margin
IssuerWE1, Google Trust ServicesCloudflare, which serves the site, obtains the certificate from Google Trust Services
Namestapcub.com, lab.tapcub.com, *.lab.tapcub.comCovers the bare domain. www.tapcub.com is not in this list, so it is answered by its own certificate and should be checked separately
ChainWE1 → GTS Root R4 → GlobalSign Root CAGTS Root R4 appears as a cross-signed certificate under GlobalSign, which helps older devices that do not have the newer root
KeyECDSA P-256Smaller and faster than RSA at the same strength
ProtocolTLS 1.3, TLS_AES_256_GCM_SHA384, h2Current TLS version, and HTTP/2 is offered

Certificates change at every renewal. Click Check for the live values; the sample keeps its date.

Common mistakes

Why HTTPS breaks after it worked

Most certificate incidents are routine changes that missed one step.

Installing the certificate without the chain

The browser on your laptop fills the gap, so the site looks fine. Then a payment provider’s webhook or a mobile app fails. Install the full-chain file.

Forgetting www or a subdomain

A certificate for example.com does not cover www.example.com. Check every name that is in your DNS and redirects.

Renewal that silently stopped

A moved server, a changed DNS record or a firewall rule breaks the validation step, and nobody sees it until the certificate expires.

Renewed, but not reloaded

The new file is on disk, but the web server still serves the old one from memory. Reload the server after renewal, and check again.

FAQ

SSL checker questions

Still have a question?

Chat with the team behind TapCub — we usually reply within a few hours on business days.

How do I check if an SSL certificate is valid?

Enter the domain above and click Check. The certificate is valid when it has not expired, lists the exact name you entered, and chains up to a trusted root. All three are shown, with the expiry date and days left.

How do I check when an SSL certificate expires?

The Expires box shows the date and the days left. In a browser you can also click the padlock and open the certificate details, but that shows one name at a time and does not check the chain the way other clients see it.

Why does my browser show a padlock when the checker says the chain is incomplete?

Browsers repair missing intermediates themselves: Firefox ships a list of known intermediates and Chrome can download them. Command-line tools, many programming libraries and other servers do not, so API calls and webhooks to your site fail while the browser looks fine.

How long are SSL certificates valid now?

Public TLS certificates issued from 15 March 2026 can be valid for at most 200 days, under the CA/Browser Forum’s ballot SC-081. The limit drops to 100 days from 15 March 2027 and 47 days from 15 March 2029, so automated renewal is becoming a requirement rather than an option.

Does the checker test TLS 1.0 and 1.1 support?

It reports the version the server chooses when offered TLS 1.2 and 1.3, which is what browsers offer. It does not probe for old versions the server might still accept. If the result shows 1.0 or 1.1, the server does not support anything newer.

Can I check a certificate on a port other than 443, or by IP address?

No. Only port 443 and domain names are allowed, so the checker cannot be used to scan other services or internal networks. Certificates are issued for names, so the name is needed anyway.

Is my check private?

The domain goes to TapCub’s API and is used for one TLS handshake from our US server; neither the domain nor the result is saved. Your IP address is counted only to enforce the limit of 10 checks a minute and 100 a day.

Changelog

Update history

New features, fixes and data refreshes for this tool, newest first.

  1. · v1.0

    LaunchedFirst release.

Data this tool relies on

  • Sample TLS check of tapcub.com — checked 2026-11-17, reviewed every 3 months (next review by 2027-02-17)

Missing something or found an error? Tell us — requests that come up often go into the next update. All tool updates

Next step

From a working padlock to the visitors behind it

TapCub shows where visitors come from, what they do and where they get stuck, and can alert you when traffic drops. No cookies in the default mode.

See your data clearly. Find your growth.

Every click, backed by data. Install one line of code and see your first numbers in a minute.

No credit card · Free plans for analytics and chat · Cookieless analytics