Know the moment a certificate is issued for your domain
Certificate Transparency logs record every certificate a public CA issues. DNS Assistant watches them for your domains and tells you when something appears that should not be there: a certificate from a CA you never authorised, a hostname you did not know existed, or a wildcard nobody asked for.
Every certificate is public. Almost nobody is watching.
When a Certificate Authority issues a certificate, it is published to public, append only logs. That is the system working as designed, and it is also the only public record you get when someone obtains a certificate for a name you own.
The certificate for a staging host an outside contractor provisioned, the wildcard issued to a team that has since left, the certificate from a CA your CAA records never authorised: all of it is public, all of it is permanent, and none of it reaches you unless something is watching on your behalf.
Three detections
Enable them individually or together on any domain you have verified.
A certificate from a CA you never authorised
Your CAA records state which Certificate Authorities may issue for your domain. We compare the authorising CA on every new certificate against those records. A certificate issued outside that set is the strongest signal Certificate Transparency can give you, and it is what the system was built to surface.
Requires your domain to publish CAA records.
A hostname you did not know existed
A certificate for a name that is not in your inventory means a host exists that you were not tracking. Shadow IT, a forgotten staging environment, a contractor deployment, or an attacker establishing infrastructure on a subdomain you no longer control.
New names enter your subdomain inventory, not just your alert feed.
A wildcard certificate you did not expect
A wildcard certificate covers every hostname under your domain. When one appears and nobody on your side requested it, that is worth knowing the same day rather than at the next audit.
Covers newly issued wildcards across all monitored domains.
A certificate is evidence, not just an event
Most Certificate Transparency monitors tell you a certificate was issued. That is useful, and it is where most of them stop.
DNS Assistant treats a certificate as evidence about your attack surface. A hostname that appears in Certificate Transparency becomes part of your subdomain inventory, which means it is then checked for the things that actually cause incidents: dangling CNAME records pointing at deprovisioned services, NS delegations to nameservers you no longer control, and hosts resolving to infrastructure nobody owns any more.
The certificate is how you learn the host exists. The takeover risk is why it matters.
How it works
We read the logs so you do not have to
Certificate Transparency logs are append only and ordered by insertion time, with no way to query them by domain. Finding certificates for one name means indexing the entire corpus. We consume maintained indexes over those logs rather than asking you to build one.
Checks are incremental
After an initial backfill, each check retrieves only what is new since the last one using a per domain cursor. That keeps monitoring current without re-reading the whole history every time.
Alerts arrive where you already work
Certificate findings are delivered through the same notification channels as your DNS, WHOIS, SPF, DKIM and dangling DNS monitoring, so there is no separate console to watch.
Findings are scoped to your organisation
Two companies monitoring the same domain get their own findings, their own alert state and their own acknowledgements. Nothing is shared across tenants.
Entirely passive
Certificate Transparency monitoring never contacts the domains you monitor. Everything comes from the public log record, so it works on hosts you cannot reach and leaves no trace on the target.
Questions
Which Certificate Transparency logs do you cover?
We read maintained indexes over the public log ecosystem rather than tailing individual logs, so coverage follows those indexes rather than a fixed list of operators.
Do I need to install anything?
No. Certificate Transparency monitoring is entirely passive. We never contact your infrastructure to perform it, which means it works on hosts you cannot reach and leaves no trace on the target.
Does this replace certificate expiry monitoring?
No, it complements it. Expiry monitoring covers certificates you know about. Certificate Transparency monitoring covers the ones you do not.
What do I need to configure?
Add the domain, verify ownership, then enable a certificate alert rule with the detections you want. Nothing else is required.
Start watching your certificates
Add a domain, verify ownership, and enable the detections you want. No credit card required.