Certificate log lookup
Free subdomain finder for any domain.
Enter a domain to find subdomains named on its public TLS certificates, each with the date of its first certificate and the date its latest one runs out. It is a lookup, not a scan: nothing is sent to the domain. 10 searches a day, no account needed.
- No account needed
- 10 free searches a day
- Nothing sent to the domain
- Subdomains listed per search
- 500Subdomains listed per search
- Free searches a day
- 10Free searches a day
- Certificate dates per subdomain
- 2Certificate dates per subdomain
- Requests sent to the searched domain
- 0Requests sent to the searched domain
What you get
What the subdomain checker shows for each domain.
Browsers such as Chrome and Safari only trust an HTTPS certificate that has been published to a public Certificate Transparency log, and every hostname on the certificate is published with it. The subdomain finder reads that record for your domain and returns one clean list: each subdomain once, in alphabetical order, with its certificate dates.
- blog.example.comfirst certificate 2019-03-12
- shop.example.comfirst certificate 2020-08-04
- staging.example.comfirst certificate 2021-11-30
- status.example.comfirst certificate 2023-02-17
Example figures
Two dates for every subdomain
First certificate is the day the earliest logged certificate naming the subdomain took effect. Valid until is the day its latest one runs out. A valid-until date in the past is a strong hint that the name has been retired.
- *.example.com
- Yes
- No
Wildcard certificate detection
A certificate for *.example.com covers any subdomain without naming it. The result says Yes or No, so you know when names may be missing from the list.
500
Subdomains listed per search
The full count, with 500 names listed
Big domains can have thousands of logged names. You always get the total. The table, the copied list and the CSV carry the first 500 in alphabetical order.
- subdomain
- first certificate
- certificate valid until
A subdomain list you can copy or download
Copy puts one subdomain per line on your clipboard, ready for a crawler or a spreadsheet. The CSV adds both dates in three columns: subdomain, first certificate and certificate valid until.
- crt.sh: Full
- Cert Spotter: Current only
A second source when the first is slow
crt.sh holds the full history and sometimes does not answer in time. The finder then reads Cert Spotter, which returns certificates still in date, and marks the log history as Current only so you know the list may be short.
Find the subdomains of any domain.
See the subdomains named on its public certificates, with dates. Free, no account needed.
How it works
How to find subdomains in three steps.
- 1
Enter a domain
Type a domain such as example.com. A full address works too: the finder takes the domain from it and drops a leading www. Enter a subdomain, such as shop.example.com, to list only the names beneath it.
- 2
We read the certificate logs
The finder asks crt.sh, a public search over the Certificate Transparency logs, for every certificate issued under the domain and collects the hostnames on them. Large domains can take up to 30 seconds.
- 3
Review, copy or export
You see how many subdomains were found, whether the domain uses a wildcard certificate, and whether the full log history answered. Below that sits the table of names and dates. Copy the list or download it as a CSV.
What it does not do
A passive subdomain lookup, not a subdomain scanner.
Many tools sold as a subdomain scanner combine several methods. This one uses a single method, certificate logs, and tells you so. The upside is a quiet search: nothing reaches the domain you look up. The cost is coverage, and these are the gaps.
Quicker than reading the logs by hand.
- You can run the same subdomain search yourself on crt.sh. The raw answer has one row per certificate, not one per subdomain. A busy name shows up dozens of times, wildcard entries sit among real hostnames, and a certificate shared by several sites brings in names from other domains.
- The finder does the sorting for you. It keeps only the names under your domain, lists each one once, leaves out www and the bare domain, turns wildcard entries into a single flag and works out both dates for every name.
What it leaves out
- It does not guess names such as dev, staging or mail from a wordlist and test them against DNS. A subdomain that never had its own certificate will not turn up here.
- It does not resolve the names or request their pages. A listed subdomain may have been switched off years ago, and the valid-until date is your only clue.
- You get no IP addresses, open ports, server software or takeover warnings. Treat the list as a starting inventory, not a security report.
- It does not read the domain's DNS records, follow links on its pages or search for indexed hostnames.
- The table holds subdomain names and certificate dates. Nothing else.
- It will not beat everything. A command-line tool that combines many sources and brute-forces DNS finds more names. Use this page for a fast first list, and a tool like that when you need depth and have permission to probe.
Use cases
Four reasons to check the subdomains of a domain.
Find what is exposed
Staging sites, test servers and old campaign pages often outlive their purpose. The list shows which of them carry your name in public.
See how a rival is organised
Find the blogs, shops, help centres and regional sites a competitor runs on subdomains. First-certificate dates show roughly when each one appeared.
List everything before you move
Before a redesign or a domain change, collect every subdomain you can so none is left without a redirect.
Retire what nobody uses
A DNS record that still points at a cancelled service is how subdomain takeovers start. Use the list to decide which names to review and remove.
Who it's for
Built for the people who look after a domain.
SEO specialists
Get the hostnames to check for duplicate content, pages that compete with the main site, and staging copies that should not be indexed.
Site owners
See which subdomains of your website are on public record, including ones a past agency or a former team set up.
Developers
Take stock of the hostnames a project has collected before you clean up DNS, and spot certificates that are about to run out.
Security teams
Start a subdomain enumeration from records anyone can read, without touching the target, then hand the list to the active tools you are cleared to run.
FAQ
Questions, answered.
A subdomain finder lists the subdomains that belong to a domain, such as blog.example.com or shop.example.com. This one finds them in Certificate Transparency logs, the public record of the TLS certificates that certificate authorities issue.
Enter the domain above and run the search. You get every subdomain named on a publicly logged certificate. No single method finds them all, so for a complete picture pair this list with the DNS zone itself if the domain is yours, or with a DNS-based tool if you have permission to probe it.
The logs only hold names that have had their own publicly logged certificate. A subdomain served under a wildcard certificate, one that uses plain HTTP and one on an internal network are not in them. Check the wildcard certificate line: Yes means the domain has subdomains the logs may never name.
No to both. It does not brute-force DNS, scan ports or load the subdomains it lists. It reads public records only, which is why nothing is sent to the domain you search. To see whether a name still answers, look it up in a DNS checker or open it in a browser.
The logs keep every certificate ever published, so a name retired years ago still appears. Look at the valid-until date. If it is in the past, the subdomain's last certificate has run out and it is probably no longer served over HTTPS.
Technically, yes: www.example.com is a subdomain of example.com. It is rarely the name you are looking for, so the finder leaves it out along with the bare domain. Everything else found under the domain is counted.
Yes. You can run 10 searches a day without an account. Each result lists up to 500 subdomains and shows the full count. If the log history line says Current only, the full history did not answer and the list comes from certificates still in date, so run the search again later.
The tool reads only public records that certificate authorities publish. It sends nothing to the domain you search, so the site's owner sees no traffic from it. What you do with the list is subject to the law and the site's terms where you are.