SSL Certificate Checker & Expiry Monitor
Check any domain's TLS certificate in seconds — issuer, chain, validity and days left. No account, no cookies, no tracking, no stored inputs.
Checks run server-side against the public internet; results are computed per request and not stored. Monitors store only the hostname you choose.
Automatic expiry monitoring
Create a monitor without an account. You get a random manage token (shown once) and a public status page. Free monitors are checked daily. Paid plans add hourly or 5-minute checks and HMAC-signed webhook alerts — no email required.
Built privacy-first
No accounts
Monitors are controlled by a random capability token. No name, email or phone is ever collected.
No personal data
The only data stored is the public hostname you monitor, your alert preferences and webhook capability URL.
No tracking
No analytics scripts, no cookies, no fingerprinting. Access logs at the edge are disabled.
Signed alerts
Webhook deliveries carry an HMAC-SHA256 signature so your systems can verify authenticity.
Minimal footprint
Runs in a 96 MB container. Scans only public endpoints over TLS, port 443.
Verifiable design
Our privacy design documents every data flow, retention rule and deletion path.
Pricing
Free
$0/month
- Checks every 1440 minute(s)
- Public status page
- Web UI
Always free
Pro
$5/month
- Checks every 60 minute(s)
- Webhook alerts (HMAC-signed)
- Web UI
Activates when billing is configured
Business
$19/month
- Checks every 5 minute(s)
- Webhook alerts (HMAC-signed)
- API access
Activates when billing is configured
Billing is not configured yet, so paid plans cannot be purchased and no charges are possible. This notice disappears automatically once the payment provider is connected.
Frequently asked questions
What does CertPulse check?
It performs a real TLS handshake against the public endpoint on port 443 and reports the leaf certificate's subject, issuer, validity window, days remaining, SAN list, negotiated protocol, cipher and chain length.
Do I need an account?
No. Checks require no account at all. Monitors are controlled with a random token you receive once; anyone with the token manages that monitor. This is why you should store it safely.
What data do you store?
For monitors: the hostname, your alert threshold, a hash of your manage token and, if you set one, your webhook URL and its HMAC secret. Alerts and delivery statuses are stored briefly for your status page. No personal data, no IP addresses, no emails.
How do webhook alerts work?
When a certificate is about to expire, has expired, a handshake starts failing repeatedly, or recovers, we POST a JSON payload to your webhook URL, signed with HMAC-SHA256 in the X-CertPulse-Signature header. Your secret is shown in the monitor management page.
Can I delete everything?
Yes. Deleting a monitor immediately removes its row and cascades its alerts and delivery records. There is no soft-delete or hidden archive.
Is my hostname personal data?
The hostname of a public website is not personal data, and we never ask for anything else. This design removes the need for most privacy obligations while still delivering the service.