How it works

CertControl queries Certificate Transparency (CT) logs via crt.sh (with automatic fallback to CertSpotter) to retrieve every certificate ever issued for a domain. Since every publicly trusted certificate must be logged in a CT log, this gives a near-complete picture of your subdomain landscape — including services spun up by developers, partners, or forgotten projects.

For each discovered subdomain, CertControl then:

  • Performs a DNS resolution check to determine if the subdomain is currently live
  • Runs a dangling domain check — detecting DNS records that point to unclaimed cloud resources (S3, Azure, GitHub Pages, etc.)
  • Cross-references with your existing monitored endpoints so you can see at a glance what is already covered
1

Go to Scanner → Subdomains

In the left-hand menu click Scanner, then select the Subdomains tab.

2

Enter a root domain and search

Type your root domain — for example example.com — and click Discover. Do not include www. or a subdomain prefix; always use the root domain to get a full picture.

Tip: Run discovery on all your root domains, not just the primary one. Acquisitions and product sub-brands often have forgotten subdomains with old certificates.
3

Review the results

Each row in the results table shows:

ColumnWhat it means
HostnameThe discovered subdomain
DNSResolved IP address, or "no DNS" if the record no longer exists
Statuslive DNS resolves   dangling DNS points to unclaimed resource   not monitored not yet in your endpoint list
Shared IPNumber of other subdomains resolving to the same IP — useful for spotting shared hosting
4

Add unmonitored subdomains as endpoints

Click Add to endpoints next to any subdomain marked not monitored to immediately start scanning it. CertControl will run a full certificate and TLS scan within seconds.

Dangling subdomains are a high-priority security risk — a DNS record pointing to an unclaimed resource can be taken over by anyone. Investigate and remove or redirect these immediately.