CertiMonitor

Blog

Why I built CertiMonitor

Jaime Guerrero · · 3 min read

I'm Jaime, a software engineer in New York, and I build and run CertiMonitor myself. I started it for four reasons.

Certificates are about to expire much more often

Until March 2026, a TLS certificate could be valid for up to 398 days. The limit is now 200, it drops to 100 in 2027, and to 47 days in 2029. A certificate you used to renew once a year will need renewing about eight times a year.

Automation handles most of that, but automation fails without telling anyone: a token expires, DNS moves to another provider, a server never reloads the new certificate. With a year-long certificate, a broken renewal job had months before anyone noticed. With 47 days it has a couple of weeks. More renewals means more chances for one to go wrong, and less time to catch it.

An expired certificate takes everything down with it

When a certificate expires, browsers block the site with a full-page warning, and with HSTS there's no way past it. API clients refuse to connect, webhooks start failing, and mobile apps lose their backend. I wrote about what breaks in more detail.

What makes it frustrating is that the expiry date is known from the day the certificate is issued. The useful check isn't what your renewal tool says it did, but what the server is actually serving to visitors, checked from the outside, with enough warning to fix it calmly.

Email security is part of the same problem

SPF, DKIM and DMARC decide whether your mail reaches inboxes and whether someone else can send email pretending to be you. They live in DNS, they break when someone changes a mail provider or adds a new tool, and nobody notices until mail starts landing in spam. I wrote up how receivers actually evaluate them. Many domains also stop at a DMARC policy of p=none, which reports on spoofing without blocking it.

These records belong to the same domain as the certificate and the registration, so I wanted them checked in the same place.

The warnings are scattered everywhere

The certificate renewal notice comes from the certificate authority or the hosting panel. The domain renewal reminder comes from the registrar. DMARC reports arrive as XML attachments from Google and Microsoft. Each goes to whoever created that account, often a former colleague or a shared inbox that nobody reads, and each looks a little different.

With alerts spread across that many places, the important one is easy to miss. I wanted every warning about a domain in one place, sent to the channel the team already watches, whether that's Slack, Microsoft Teams, Discord, email or a webhook into your own tools, with a clear severity and a single message when the problem is fixed.

What CertiMonitor does

CertiMonitor checks each domain's TLS certificate, its registration and its SPF, DKIM and DMARC records on a schedule, from the outside, the way a browser or a mail server sees them. There's nothing to install and no credentials to share. When something is close to expiring or stops working, it alerts your team in one consistent format.

There's a free plan for up to 5 domains and 5 certificates, a free domain check that works without an account, and an API for scripts and CI. Paid plans with more domains and faster checks, down to hourly, are coming soon. If you create a free account now, everything you set up carries over when they launch.

If you have questions or ideas, email me at support@certimonitor.com. I read everything.