Help Centre
Everything you need to know about using Tlscheck — from your first inspection to understanding the fine print.
Getting started
Using Tlscheck takes about ten seconds:
Go to the inspection page
Open the Inspect page. You will see a single text input and an Inspect button. No sign-up, no account — just the tool.
Type a hostname
Enter the hostname of the server you want to check — for example example.com. Do not include https://, a port number, or a trailing slash. IP addresses are not supported.
Click Inspect
Tlscheck opens a TLS connection to the hostname on port 443, reads the certificate chain the server presents, and displays a structured report in seconds.
Read the report
The report shows the expiry date and days remaining (colour-coded), the issuer and subject Distinguished Names, every Subject Alternative Name the certificate covers, and a chain completeness check. If the server did not send an intermediate certificate, the report says so.
Frequently asked questions
When a hostname is behind Cloudflare, the server you reach is Cloudflare’s edge, not your origin server. The certificate presented is Cloudflare’s universal certificate. Tlscheck connects directly to the server the DNS resolves to — it does not bypass CDNs.
This is a platform limitation of running from this environment. The tool detects Cloudflare certificates and flags them in the report. The result shown is the edge certificate, not the origin server’s certificate. This is stated clearly next to the input field on the inspection page.
It means the server sent only its leaf (end-entity) certificate during the TLS handshake and did not send the intermediate certificate that chains it to a trusted root. A browser on a desktop may still load the page because it cached the intermediate from a previous visit — but a mobile client, a fresh browser profile, or a non-browser tool (curl, a CI pipeline, an API client) will fail with an untrusted-certificate error.
The fix is on the server: configure your web server to serve the full certificate chain, including the intermediate. Most certificate authorities provide a “chain bundle” file for exactly this purpose.
No. Every inspection is ephemeral. Tlscheck does not store hostnames, inspection results, IP addresses, or any personal data. There are no accounts, no saved history, and no profiles. When you close the page or start a new inspection, the previous result is gone.
This is by design — the tool answers when you ask it, and nothing more.
No. Tlscheck inspects one hostname per request. It does not scan subdomains, IP ranges, or networks. There is no bulk mode in the Free tier.
A Professional tier with a bulk inspection API is planned but not yet built. When it ships, it will be the correct channel for programmatic or multi-hostname usage. Sending automated requests to the Free tier is a violation of the terms of service.
Tlscheck is designed to check TLS certificates as they are served by a hostname. IP addresses are not supported because:
- Certificates are issued to hostnames (via Subject Alternative Names), not to IP addresses (with rare exceptions).
- The tool validates hostname format as a guard against mistyped input.
- A hostname tells you which service you are actually reaching; an IP address is an implementation detail that may change.
If you need to check a server by IP, use openssl s_client or a dedicated network tool.
No. Tlscheck does not have an email sender. There are no alerts, reminders, digests, or scheduled re-checks of any kind. The tool answers only when you visit the page and type a hostname.
If you need expiry monitoring, consider setting up a cron job that runs openssl s_client or a dedicated monitoring service. That capability is not part of this product and is not planned in the current roadmap.
Known limitations
These are limits of the current build. Some will change as the product develops; others are by design.
- Professional tier not built. The pricing page shows a mock checkout and lists planned features. No payment processor is connected. Subscriptions do not exist yet.
- No email sender. The tool cannot send alerts, reminders, receipts, or any outbound email. Support by email is not available.
- No accounts or data storage. Every inspection is ephemeral. There is no way to save, bookmark, or revisit a past result.
- One hostname at a time. No subdomain enumeration, no bulk API, no network scanning.
- Cloudflare edge limitation. Hosts behind Cloudflare present Cloudflare's certificate, not the origin's. This is a known platform constraint.
- No compliance certifications. Tlscheck does not claim PCI, SOC2, HIPAA, or any other compliance or audit regime.
- No inferred values. If a field is absent from the server's certificate, the report says “absent” — no values are filled in or guessed.
- No legal entity. Tlscheck is not operated by a registered company. There is no registered address or jurisdiction at this time.
Contact
If your question is not answered on this page, here is how to reach us:
Email support is not yet available. Not built
Tlscheck does not have a connected email system. Sending an email to any address on this domain will not reach anyone. This is an intentional constraint of the current build — see Terms of service for the current contact arrangement.