CertiMonitor

Check any domain's certificate, registration and email security

Free, in a few seconds, no account needed. We read the same public records a browser or mail server does.

Try github.com, stripe.com or wikipedia.org

What the check covers

SSL/TLS certificate

Connects to the domain on port 443 like a browser and reads the certificate it actually serves: when it expires, who issued it, whether it covers the name you entered, and the full chain up to the root. If browsers wouldn't trust it, it says why, including the missing intermediate certificate that browsers often hide but curl and apps fail on.

How TLS certificates work

Domain registration

Reads the registration from the registry over RDAP: the expiry date, the registrar, and whether the transfer lock is on. An expired registration takes down the site and its email, whatever the certificate says.

The domain registration lifecycle

SPF

Looks for the domain's SPF record, the list of servers allowed to send its mail. Without one, receivers have no way to tell your servers from anyone else's.

How SPF, DKIM and DMARC decide

DKIM

Looks up public keys on the selectors most mail providers use, such as google and selector1. A published key means mail can be signed as your domain, which is what DMARC relies on when mail is forwarded.

How DKIM signatures work

DMARC

Reads the DMARC policy and says whether it's enforced. A record with p=none only monitors: spoofed mail still reaches the inbox.

Why p=none doesn't stop spoofing

A one-off check tells you how things look today. To hear about it before something expires, monitor your domains free.

Questions

Is the check really free?
Yes, and it needs no account. It reads the same public records a browser or mail server does, so it works on any domain, yours or not.
Why check all five together?
They fail for different reasons and get noticed by different people. A renewed certificate doesn't help if the domain registration lapses, and a valid site doesn't mean your mail can't be spoofed. One check shows the whole picture.
Why doesn't it find my DKIM key?
DKIM keys live under a selector name each provider chooses, and there's no way to list them. The check tries the common ones. If yours uses a custom selector, the key can exist even when the check doesn't see it.
How is this different from monitoring?
This is a snapshot of today. Monitoring runs the same checks on a schedule and alerts you by email, Slack, Teams, Discord or webhook before a certificate or registration expires, or when a record changes.