Skip to content
startupcybersecurity

Free Subdomain Finder

A subdomain finder lists the hostnames under a domain that appear in public Certificate Transparency logs, the records every trusted certificate authority must publish. It's passive: nothing is sent to your servers. Enter a domain to see its subdomains and which ones look like staging, admin or internal systems.

Jay Dabhi

Reviewed by , CISM · Cybersecurity Analyst

Updated

Passive: we read public certificate logs (crt.sh). No traffic reaches your servers.

Why your subdomains are already public

Every time a certificate authority issues a TLS certificate, it has to log it in public Certificate Transparency (CT) logs. Anyone, including attackers, can search those logs. So the moment you put a certificate on staging.yourstartup.com, that hostname is public, even if you never linked to it.

Which subdomains are risky

We flag names that usually mean non-production or internal systems, which tend to be less hardened than production:

  • dev, staging, test, qa, uat, preprod, sandbox
  • admin, internal, vpn, backup
  • jenkins, gitlab, grafana, kibana, jira
  • db, mysql, redis, elastic, phpmyadmin

What to do about exposed subdomains

Put staging and internal tools behind SSO or a VPN instead of relying on an obscure name. Delete DNS records for anything you've shut down: a record left pointing at a deleted cloud resource can be taken over (subdomain takeover). Keep a simple asset inventory so you know what is public.

To hide internal hostnames from CT logs in future, use a wildcard certificate (*.internal.yourstartup.com) or keep internal tools on a private network.

Frequently asked questions

Is using a subdomain finder legal?

Yes. Certificate Transparency logs are public by design so that anyone can audit certificate authorities. This tool only reads those logs and sends no traffic to the domain.

Why are some of my subdomains missing?

CT logs only include hostnames that have had a publicly trusted certificate. Hosts behind wildcard certificates, or without TLS at all, won't appear.

What is a subdomain takeover?

It happens when a DNS record still points to a cloud resource (an S3 bucket, a Heroku app, a GitHub Pages site) that you've deleted. An attacker claims that resource and serves content on your subdomain. Remove DNS records when you delete the resources behind them.