Skip to content

Free subdomain finder

Find your domain's subdomains in public certificate transparency logs. The names are listed, never contacted.

Searches public certificate logs. Nothing on your servers is contacted. What happens to the domain you enter

Example report

example.com
  • 1 passed

7 names in certificate transparency logs

From unexpired certificates in public logs (crt.sh). None of these names was contacted.

  • api.example.com
  • mail.example.com
  • old-blog.example.com
  • shop.example.com
  • staging.example.com
  • vpn.example.com
  • www.example.com

What the subdomain search looks at

  • Certificate logs

    Unexpired, publicly trusted certificates naming the domain, from crt.sh.

  • Names under the domain

    Every name within the domain, up to 1,000.

  • Wildcards

    A wildcard certificate is listed by the name it covers.

  • Listed, not scanned

    None of the names found is contacted.

Names that never had a certificate of their own, or have only expired ones, do not appear.

Keep watch after you've fixed it

Ironfang Security rechecks a verified domain every week or every day and tells you what changed: new findings, fixes and certificates nearing expiry.

Free during the preview. Domain verification required.

  1. NewIssue detected
  2. FixedConfirmed by recheck
  3. ReopenedDetected again

How the check works

  • A search of crt.sh, a public certificate transparency search service, for unexpired certificates naming the domain or any name under it.
  • Every name in those certificates that falls within the domain, up to 1,000.
  • Wildcard entries such as *.api.example.org, listed by the name they cover: api.example.org.
  • None of the names found is contacted. The search touches crt.sh, not your systems.

Reading a result

Publicly trusted certificates are recorded in certificate transparency logs (RFC 6962), which anyone can search. Each name you have put on a certificate, for a staging site, a mail server or a service since retired, is public, and attackers read the same logs to find hosts to try.

Read the list as an inventory check. Each name should be one you recognise and still use. A name you do not recognise may be a service someone set up without telling you. One you no longer use may still have a DNS record pointing at a host or platform you have given up, which the dangling DNS checker looks for.

crt.sh is often busy. When it does not answer, the result says the search could not be completed, which is not the same as finding no names; try again in a few minutes.

What it does not do

  • It finds only names that have appeared in a publicly trusted certificate. It does not guess names, query DNS for them or read zone files.
  • A wildcard certificate hides the individual names it covers; only the wildcard's base name is listed.
  • Only unexpired certificates are searched, so names whose certificates have all expired are not shown. The list stops at 1,000 names.
  • Results are reused for an hour, so a certificate issued in the last hour may not appear yet.

What happens to the domain you enter

The check runs from Ironfang Security's published scanner address with the same low-impact limits as a scan. Nothing you enter is stored or logged. A result is reused for five minutes, and a certificate log search for an hour, so a repeat check is quick and the domain is not checked again.

Guides

A few things worth knowing

How does this subdomain finder work?
It searches certificate transparency logs, the public record of certificates issued by publicly trusted certificate authorities, for names under the domain. It does not guess names or query the domain's DNS.
Why is a subdomain I know about missing?
It has not appeared under its own name in an unexpired, publicly trusted certificate. It may be covered by a wildcard certificate, use a private certificate or none at all, or have only expired certificates.
Can I keep subdomains out of certificate transparency logs?
Not with a publicly trusted certificate for that name: browsers expect those to be logged. A wildcard certificate keeps individual names out of the logs, at the cost of one key covering every name beneath it.