Launching today
Certly
Know before your SSL, domain, or DNS breaks
10 followers
Know before your SSL, domain, or DNS breaks
10 followers
Monitor SSL certificates, domain expiry, and DNS/DNSSEC across all your sites. Track every DNS record change and get alerted on Slack, email, or webhook before anything lapses — so you never find out from your customers.
Does Certly handle wildcard certs the same as standard ones, and what happens if I rotate a cert through your system does the alerting reset automatically or do I need to reconfigure anything?
@neriman91088467
Great questions! Wildcard certs are handled exactly the same as standard ones — Certly checks the certificate your server actually presents for the monitored hostname, and wildcard matching (e.g. *.example.com covering
api.example.com
) is validated the same way a browser would.
Rotation needs zero reconfiguration. Certly doesn’t sit in your issuance pipeline — it observes the live cert from the outside once a day. So when you rotate, the next check simply sees the new expiry date and the countdown resets automatically. Alerts fire at 30/14/7/1 days before expiry, so after a rotation you just won’t hear from us again until the new cert approaches those thresholds. Nothing to reset, nothing to tell us.
How does certly handle certificate transparency logs? Like if someone manages to issue a sneaky cert for one of my domains, can it catch that too or only stuff I've already set up?
@songlzkara50786
Honest answer: not yet — but it’s on the roadmap, and you’ve picked exactly the feature I’m most excited to build next.
We already pull CT issuance data for the free public checker, but the daily monitoring currently tracks the certs your servers actually present, plus domain expiry, DNS record changes, and DMARC/SPF posture. The DNS-change alerts do cover part of the “sneaky issuance” story — most rogue certs start with a DNS or nameserver takeover, and Certly flags those the same day.
Full CT monitoring — alerting when any cert is issued for your domain that you didn’t expect, including lookalike domains — is planned. If you’d like, I’m happy to ping you when it ships.
Love how the dashboard surfaces every record type without making you dig through nested menus. The Slack alerts with the exact affected domain and expiry timestamp are a nice touch.
@ayferbesir3488
Thank you! That was a very deliberate choice — the whole point of Certly is that you glance at one screen and know if anything needs attention, so burying records behind clicks would defeat the purpose.
Same thinking behind the alerts: if you’re getting pinged at 9 AM, the message should already contain everything you need to act — no logging in just to find out which domain it was. Glad that’s landing the way it was intended!
finally something that caught a sneaky DNSSEC validation issue on a subdomain i forgot about, the slack alert was clear and pointed me straight to the record
@sevim1088807
This is exactly the scenario Certly was built for — the forgotten subdomain is always the one that breaks. Nobody gets paged for the thing they’re already watching.
Really glad the alert pointed you straight to the record too. DNSSEC failures are cryptic enough on their own; the alert should do the diagnosing for you, not hand you a puzzle. Thanks for sharing this — reports like this one are the best part of launching.
Caught a sneaky DNS record change on one of my side projects that I would have totally missed otherwise. Slack alert arrived a few minutes before the cert was set to renew, saved me an embarrassing email from a client.
@yiitellezf6fz
Side projects are exactly where this stuff slips through — glad Certly caught it before your client did. Thanks for sharing!
The DNS change history view is such a smart move, makes it dead simple to spot which tweak broke prod last week. Slack alerts on the expiry thresholds feel just right too.
@semasf8r
That view exists for exactly that “what changed last Tuesday?” moment — glad it’s earning its keep. And good to hear the alert thresholds feel right; tuning them to be useful-but-not-noisy took a few iterations. Thanks!