Toolsky

Free Online Tools & Utilities for Every Task.

Subdomain Finder

Discover subdomains for any domain using public records and certificates.

Most organisations own far more subdomains than anyone remembers creating: a staging server from two redesigns ago, a forgotten test shop, an old mail host. The subdomain finder pulls together the subdomains of any domain that are visible in public records and certificate data, so you can see the full public footprint of a domain in one list instead of guessing at names one by one.

Where the Subdomain List Comes From

Subdomains leak into public view through several channels, and this tool draws on them rather than probing the target server directly. The richest source is Certificate Transparency: when a TLS certificate is issued for a host such as shop.example.com, that name is written into public logs that anyone can search. DNS records, historical registration data and other public indexes add further names — a subdomain that once pointed somewhere publicly tends to leave a trace.

This approach has a practical consequence: the finder reports what the public record shows, not what exists on a private network. An internal-only host that never had a public certificate or public DNS entry will not appear, and that is expected behaviour rather than a miss. For the live DNS picture of a single known host, the DNS Lookup tool digs into its current records directly.

What the Finder Does for You

  • Enumerates publicly recorded subdomains for the domain you enter, gathered from certificate logs and public records.
  • One search instead of manual guessing — no trying dev., test., old. prefixes by hand.
  • Surfaces forgotten assets — staging, legacy and campaign hosts that teams created and never documented.
  • Starting point for audits — pair the list with ownership checks via Domain Whois and per-host reviews to build a complete inventory.

How to Run a Subdomain Search

  1. Enter the root domain you want to investigate (for example example.com) — without any subdomain prefix.
  2. Start the search and give the public sources a moment to respond.
  3. Review the resulting list of subdomains.
  4. Note any names you do not recognise or no longer expect to exist.
  5. Check the unfamiliar ones individually to see whether they still resolve and what they serve.
  6. Record the confirmed list in your asset inventory so the next audit starts from documentation, not discovery.

What People Use the Results For

Cleaning up your own attack surface. A forgotten staging subdomain often runs old software with weak or shared passwords, and dangling subdomains that point at decommissioned services can be claimed by strangers for phishing. A periodic finder run gives security teams a list to verify, secure or retire; checking each host's certificate health with the SSL Checker is a natural next step.

Pre-migration and redesign inventories. Before moving a site or changing hosts, teams list every subdomain so nothing breaks silently — the careers page and the help centre are usually hosted on subdomains nobody mentions in the planning meeting.

Acquisition and handover checks. When a business buys a website or changes agencies, the finder offers a quick reality check on what actually exists under the domain — including regional sites, landing-page hosts and legacy campaign pages the seller's own summary may have forgotten to mention.

Brand and portfolio checks. Agencies inheriting a client's web presence use the finder to discover what actually exists under the client's domain before quoting maintenance work, instead of trusting a handover document that is two years old.

Read the Results With These Limits in Mind

  • Public record only. Hosts that were never publicly certified or resolved will not appear. The absence of a name proves nothing about private infrastructure.
  • History is included. Some returned names may be dead or long decommissioned — treat the list as candidates to verify, not as a live map.
  • Stay on your own ground. Reviewing public information about domains is normal research, but actively testing, logging into or probing other people's systems without permission crosses legal lines in most jurisdictions. Inventory and audit domains you own or are authorised to assess.
  • Wildcard setups blur the picture. Domains with wildcard DNS or wildcard certificates may show few names even though many hosts respond, because individual names were never recorded anywhere.

The certificate system behind much of this data is described in the Certificate Transparency overview published on Wikipedia, for readers who want the background.

Frequently Asked Questions About Finding Subdomains

What exactly is a subdomain?

It is a name under a main domain: in blog.example.com, blog is the subdomain. Organisations use them to separate services — mail, shops, help centres, staging — under one brand.

Will the finder discover every subdomain that exists?

No tool can promise that. It finds subdomains visible in public records and certificates; purely internal hosts that never appeared publicly stay hidden, by design.

Does the search scan or attack the target website?

No. It queries public data sources such as certificate logs rather than hammering the domain's own servers, so a search does not load or probe the site itself.

Why does the list include subdomains that no longer work?

Public records keep history. A certificate issued three years ago stays in the logs even after the host is retired, so some results are historical entries worth verifying and then ignoring.

Can I check a competitor's subdomains?

The underlying data is public, and looking at it is ordinary research. What you must not do is use the list to probe, access or test systems you have no authorisation for.

What should I do with a subdomain I do not recognise?

Check whether it still resolves, what it serves and which certificate it presents. If it belongs to your organisation, document and secure it; if it points to a service you no longer control, remove the DNS record so it cannot be taken over.

How often should I re-run a search on my own domain?

Whenever teams launch new services, and at least a few times a year as routine hygiene — new certificates are issued constantly, and each one can reveal a host someone forgot to log.

Know Your Whole Front Door

You cannot secure, migrate or maintain subdomains you do not know exist. Run the finder on your domains, verify what comes back, and keep the inventory current — the list takes minutes to build and can prevent the kind of surprise nobody wants from a forgotten corner of their own domain.