Tools / Subdomain finder

Subdomain finder & subdomain takeover checker

List the subdomains of your domain from public certificate transparency logs, see which are live, and find the ones at risk: DNS records that still point to a deleted cloud service (subdomain takeover) and dev, staging or admin systems reachable from the internet.

What is subdomain takeover?

A team launches promo.example.com on a cloud service (Heroku, GitHub Pages, Azure, an S3 bucket), later deletes the service, but forgets the DNS record. The record now points at a name anyone can register. An attacker claims it and serves their own content on your subdomain: phishing pages, malware, or scripts that read cookies set for your whole domain. It is one of the most common findings in bug bounty programmes, and it is fixed by deleting one DNS record.

How it works

  1. Every public TLS certificate is recorded in certificate transparency logs. We read those logs (Cert Spotter, with crt.sh as a fallback) for certificates issued to your domain.
  2. Each subdomain is resolved live through DNS-over-HTTPS to see whether it still exists and where it points.
  3. CNAME records pointing to claimable services are checked against the public can-i-take-over-xyz fingerprints: a target that no longer exists, or the service's "unclaimed" page.
  4. Live names that look like dev, staging, test, admin or database systems are flagged for review.

If a takeover risk is found

Delete the DNS record if the service is no longer used, or re-create the resource under your own account. Then review how DNS records are removed when projects end, so it does not happen again.

Frequently asked questions

Will it find every subdomain?

It finds every subdomain that has ever had a public TLS certificate, which covers most websites and APIs. Names that never had a certificate, or that are covered only by a wildcard certificate, may not appear.

Why does it list subdomains that no longer exist?

Certificate logs are permanent. A name shown as "no longer in DNS" had a certificate once but no longer resolves; that is normal and harmless.

Is a dev or staging subdomain a problem?

Only if it is reachable without protection. Test systems often run old code, debug settings and weak passwords. Put them behind a login, VPN or IP allow-list.

Do you probe my subdomains?

Only lightly: DNS lookups for every name, and one request to the homepage of subdomains that point at a claimable service, to look for its "unclaimed" page. No port scanning, no brute forcing of names.

Related checks