How to Find All Subdomains of a Website
The fastest way to find a website’s subdomains is to look them up in public SSL certificate logs. Type the domain, such as tiki.vn, into the subdomain finder and in a few seconds you get every name that ever received a certificate, with the date it first appeared. It never scans, and never sends a request to the website you look up.
What a subdomain is, and why you should know them all
A subdomain is the part in front of the main domain, like shop.tiki.vn or blog.tiki.vn. Over time a business collects many of them: a store, a blog, test sites, email systems, internal tools. The person who created one may have left long ago, while the subdomain is still there.
A forgotten subdomain is a real risk. It may run old software nobody updates, or expose a test admin page. To clean up, you first need to know what you have.
Steps to find subdomains
- Open the subdomain finder.
- Enter the domain. You can paste a full link like https://www.tiki.vn/abc and the tool extracts tiki.vn. If you type m.tiki.vn, it is searched as tiki.vn.
- Press search and wait for the list.
- Use the filter box to search by keyword, and switch between newest first and A-Z.
- Copy everything, or download a .txt or .csv file to keep.
How to read the results
Each row is a name with the date it first appeared in the certificate logs. That is usually when the subdomain got its first SSL certificate, so it tells you roughly how long the name has existed.
- Names first seen in the last 30 days carry a “new” badge. If you don’t remember creating one, ask whoever manages your systems.
- Names containing dev, test, staging, old or demo are usually test environments. Look at these first.
- Click a name to try opening it. If the page doesn’t load, the name may have been deleted or may no longer point anywhere.
- The total count is shown above the list. For very large domains the list is cut to the first 10,000 names, but the total is still the real number.
What to do with forgotten subdomains
If you find a subdomain that is no longer used, don’t just leave it.
Delete the DNS record. This matters most. Say shop.yourcompany.com once pointed to a third-party service, and you cancelled the service but forgot the record. The name still points to a place nobody controls. An attacker can claim that place and show their own content under your domain name. This is called subdomain takeover. Visitors see your real domain name, so they trust it easily.
Remove or update test sites. If you don’t need one, shut it down. If you still use it, update the software and set a password.
Keep a record. Save the .csv, search again in a few weeks and compare. Any new name you don’t recognize deserves a question.
Limits to keep in mind
The data comes from crt.name, a public index of SSL certificate logs, so:
- Only names that once had a public SSL certificate appear. Internal systems without a certificate won’t be listed.
- Names covered only by a wildcard certificate like *.example.com don’t show up on their own.
- A listed name may no longer exist, because the tool does no DNS check.
- Results are cached for 24 hours, so they can be up to a day old.
Treat it as a strong first list, not an absolute inventory. When you need certainty, compare with the DNS records where you manage the domain.
Other ways to find subdomains
Certificate logs give the widest list for the least effort, but no single source has everything. These methods fill the gaps:
- Your DNS zone (for your own domain). Log in where the domain’s DNS is managed, such as Cloudflare, your registrar or your hosting panel, and open or export the list of records. This is the only complete list of names that exist right now, including internal ones that never had a certificate.
- A site: search. Type
site:example.com -wwwinto Google or Bing. You only see subdomains that have pages in the search index, so the list is short, but it shows which ones the public can actually find. - A certificate search site. crt.sh lets you search the same certificate logs by hand. Search for
%.example.comto see the raw certificates, including issuer and expiry date, when you need more detail than a list of names. - Command-line tools. Security teams use open-source tools such as subfinder or amass, which combine many passive sources. Some can also guess names from a word list, which sends real traffic to the domain, so only do that on domains you own or are allowed to test.
- DNS zone transfer. In the past, many DNS servers handed their full record list to anyone who asked. Almost all of them block this today, so don’t expect it to work.
Subdomains or subsites?
People often search for the “subsites” of a website. That can mean two different things:
- A subdomain, like blog.example.com. These are what the methods above find.
- A section inside the same domain, like example.com/blog. Sections are just folders on one site, so they never appear in certificate logs. To list them, open the site’s sitemap, usually at example.com/sitemap.xml, or run a
site:example.comsearch and look at the paths.
If you are not sure which one you need, start with the subdomain list, then check the sitemap of each main domain you find.
Finally, only dig deeper into domains you own or have permission to test. Find the subdomains of your own domain for free right now, no signup needed.