Setup

No agent to install. CertWatch checks your TLS endpoints and domains from CertWatch's own servers — you just tell it what to watch.

1. Create an account

Sign up at app.certwatch.sh/signup with an email and password. Every plan, including Free, starts immediately — no credit card required. Until you verify your alert email, an info banner at the top of the app shows the address with a Resend email button that sends the verification link again. Use the link so alerts have somewhere to go; monitoring itself doesn't wait on that, but email delivery does.

To change your password later, open Settings and use the Password card on the Account tab with your current password and a new one of at least 12 characters. You stay signed in where you made the change, every other device is signed out, and CertWatch emails your sign-in address to say the password changed.

The same tab's Privacy card holds Product analytics, on by default. It sends product events for your account to PostHog under a pseudonymous ID: signing up, verifying your email, adding a monitor, connecting Slack, a test alert going through, scheduling your account's deletion, a subscription starting or ending, and each monitor's first completed check. They also carry counts and categories such as your plan and how many monitors you have, never a hostname or an address, and deleting a monitor or changing an alert channel sends those on their own. It saves as soon as you switch it, and turned off, your account sends none. A signed-in browser where PostHog runs with its cookie also stops using your account's ID: at once on the browser where you turn it off, and at the next app page on any other. The privacy policy has the details.

2. Add a TLS endpoint

On Monitors, select Add and give a hostname and, optionally, a port (defaults to 443) and a label. The endpoint must accept a direct TLS connection, as a website or API on 443 or a mail server on 465 or 993 does, except on these ports, where CertWatch first asks the server to start TLS (STARTTLS): SMTP on 587, IMAP on 143, POP3 on 110 and PostgreSQL on 5432. A database certificate from a private CA, as most managed databases use, reads Down, because no public root trusts it. CertWatch does not read MySQL, which starts TLS inside its own protocol. CertWatch dials the endpoint immediately to confirm the check works, then keeps it on your plan's check interval afterward.

A new endpoint starts in automatic renewal mode: CertWatch learns when its certificate renews and sends no renewal alert until a renewal is late. A broken certificate (an incomplete chain, a name it does not cover, an expiry) or checks that keep failing still alert whatever the mode. If the certificate is renewed by hand, or by automation that renews with a set number of days left, set that on the monitor card's Settings tab; the add form has no renewal setting. See Renewal mode.

Want to try it without an account first? The free certificate checker runs the same check CertWatch uses on a schedule, with no signup — useful for confirming a hostname resolves and presents a valid chain before you add it for ongoing monitoring.

3. Add a domain

On Monitors, select Add, choose Domain, and give a registrable domain name (e.g. example.com — no scheme, no port). CertWatch looks up its registration status via RDAP and tracks expiry, transfer lock, DNSSEC, and exposed registrant contact separately from any certificate served on that domain.

4. Configure alert delivery

Email is included on every plan. Starter and Pro accounts can connect Slack with Add to Slack, and Pro accounts a generic webhook URL, on the Alerting page for alerts to go anywhere else you already page from. Choose the channel Slack alerts post to in the Slack tab's Connection section; a private channel needs /invite @CertWatch first. The Alert channels card sets which channels get each severity. See Alerts for what actually triggers an alert.

5. Know your plan's limits

Each plan caps the number of endpoints and domains you can monitor and how often they're checked — see Billing for the current tiers. Hitting a limit while adding something new returns a clear "upgrade to continue" prompt rather than a silent failure.