About CertiMonitor
CertiMonitor keeps an eye on the parts of a domain that expire: TLS certificates, domain registrations, and the SPF, DKIM and DMARC records that protect your email. When something is close to running out or stops working, it alerts your team by email, Slack, Discord, Microsoft Teams or webhook, before visitors run into a browser warning.
Who I am
I'm Jaime Guerrero, a software engineer in New York. I build and run CertiMonitor myself, including the support inbox, so if you email support@certimonitor.com you're writing to me.
Why I built it
Certificates and domains rarely expire because nobody knew the date. They expire because a renewal job broke without anyone noticing, or because the reminder went to someone who left. With certificate lifetimes going from 398 days to 47 by 2029, renewals will happen eight times as often, and there are more chances for one to go wrong. I wanted a single place that watches all of it and says something early. I wrote more about why I built CertiMonitor.
How it works
CertiMonitor checks your domains from the outside, the way a browser or mail server sees them. There's nothing to install and no credentials to hand over. Alert destinations are stored encrypted, passwords and API keys are hashed, and card payments are handled by Stripe, so card details never reach my servers.
There's an API if you want to manage domains from scripts or CI, and a free domain check you can use without an account. I also write about certificates and email security on the blog.
Contact
support@certimonitor.com for questions and feedback, security@certimonitor.com for security reports.