Certly

About Certly

Certly watches the certificate and domain layer that almost every team assumes is on autopilot until the morning a renewal silently fails and customers hit a browser interstitial instead of a checkout page. The premise is that automated renewal is not the same as verified renewal: a cron can succeed while the server keeps serving the old chain, an ACME client can renew a cert nobody reloaded, a registrar auto-renew can bounce on an expired card. Certly does not read your renewal config — it fetches what your host actually serves and grades that, which is the only signal that matches what a visitor experiences. A monitored domain covers four surfaces: TLS certificate expiry on the served chain, domain registration expiry and registry status including NXDOMAIN and suspension diagnosis, DNS and DNSSEC record activity, and email-authentication posture through DMARC and SPF spoofing checks. Alerts are staged at 30, 14, 7 and one day rather than fired once, and they route to email, Slack, Discord or a webhook, with per-record muting so a noisy DNS zone does not train the team to ignore the channel. Onboarding is a paste of the domain — no agent to install, no nameserver change, no DNS delegation — and there is a signed-out instant check plus a live demo before any account exists. Agencies get client grouping and a year of history on the top tier, which is the shape of the buyer this is really built for: someone holding a hundred and fifty domains they did not personally register.

Key Features

Tags