How to find all subdomains of a website

A domain rarely stands alone. Around it sits a whole family: mail. for email, api. for apps, dev. and staging. for test environments, vpn., blog.... These are subdomains. The catch: over time, even the team running a system forgets which subdomains it created — and forgotten ones, especially test environments left open to the Internet, are a classic security weak point.

The secret is in the SSL certificate logs

Every time an SSL certificate (the HTTPS padlock) is issued for a domain or subdomain, that fact must be written to a Certificate Transparency log — a global public ledger anyone can search. The interesting side effect: almost every subdomain that ever ran HTTPS leaves a trace in these logs, even if the site itself was shut down long ago.

The Tools TEKVN Subdomain Finder reads two large log sources (crt.sh and Cert Spotter), merges and de-duplicates the names, then checks DNS live in your browser to see which names are still alive and which IPs they point to.

Steps: enumerate a domain's subdomains

  1. Open the Subdomain Finder tool.
  2. Enter the root domain, for example tekvn.net, and start the search. Popular domains have long logs — a few seconds up to half a minute is normal.
  3. The main table lists subdomains that are currently live, with their current IP addresses. Names without an IP are grouped separately — use the "Show N subdomains without an IP" button to see the historical ones too.
  4. Scroll to IP statistics to see which IPs host the most subdomains — a quick way to picture how many servers a system has.

Reading the results correctly

The "Cloudflare" badge next to an IP

If the IP belongs to a Cloudflare range, that is the edge (CDN/firewall) address, not the origin server's IP. Sites behind Cloudflare always hide their real address this way — the badge tells you they use Cloudflare, not where the server actually is.

A subdomain with no IP

Usually one of three things: the subdomain was shut down but its certificate remains in the logs; it is used internally with no public DNS; or its DNS record was deleted during a cleanup. For your own system, every unfamiliar name in this group deserves one question: "what is this, and is it still needed?"

One IP hosting many unfamiliar subdomains

If IP statistics show a strange address hosting lots of names you don't recognize, the system may have been migrated at some point — or someone on the team spun up a test service and forgot to tear it down.

Limits you should know

Try it on your own domain: open the Subdomain Finder and see what your system currently shows the Internet.

Related guides: How to look up a domain's Whois record · How to get 2FA codes from a secret key