Skip to content
thenetworktools
Sign in

tool / subdomains

Subdomains

Find subdomains of a domain.

try

Workflow & Diagnostics

How Subdomains works

Search and find known subdomains of any domain without active brute force. Discovers staging servers, mail endpoints, and API gateways from public certificate transparency logs.

1

Enter an apex root domain (e.g. example.com).

2

Review discovered public subdomains and hostnames.

3

Audit for orphaned records or exposed development environments.

Specifications & Scope

About Subdomains

01 / What it does
Search and find known subdomains of any domain without active brute force. Discovers staging servers, mail endpoints, and API gateways from public certificate transparency logs.
02 / How to use
1. Enter an apex root domain (e.g. example.com). 2. Review discovered public subdomains and hostnames. 3. Audit for orphaned records or exposed development environments.
03 / Good to know
Only subdomains that have had a public SSL certificate issued appear in CT logs. It is a fast, passive map of your public attack surface, not an invasive brute-force scan.

Got Questions?

Frequently Asked Questions

It queries public Certificate Transparency (CT) logs from major certificate authorities. Every time an SSL/TLS certificate is issued for a domain or subdomain, it is recorded in these tamper-proof cryptographic logs.

Knowledge Base

Technical Guides & Reference

All guides
Technical Reference & Standards

Tool Details & Usage Guide

RFC specifications, input expectations, outputs, and edge limitations.

Overview

The Subdomain Finder performs passive, non-intrusive asset discovery for any domain name. By aggregating public Certificate Transparency (CT) logs from major certificate authorities (via CertSpotter, crt.sh, and public intelligence feeds), it uncovers known hostnames, staging servers, mail endpoints, and API gateways associated with the apex domain.

Because this discovery relies entirely on immutable, publicly audited cryptographic logs, no invasive scanning packets or brute-force queries are sent to the target organization’s infrastructure, making it completely safe, fast, and privacy-preserving.


How to Check Subdomains of a Domain

  1. Enter the Apex Domain: Provide the root domain (e.g., example.com or company.org). Strip prefixes like https:// or www—the engine automatically cleans the input.
  2. Instant CT Log Aggregation: The tool queries public Certificate Transparency logs to aggregate all Subject Alternative Name (SAN) entries ever issued by trusted CAs.
  3. Inspect & Triage Discovered Names: Review the list of discovered subdomains to map your organization’s attack surface or find forgotten cloud assets.
  4. Export Findings: Copy individual hostnames or export the full list for security audits, DNS migrations, or penetration testing documentation.

What to Look For in Discovered Subdomains

  • Staging & Development Environments: Look for subdomains like dev.example.com, stage.example.com, or test-api.example.com. Development servers frequently run older software versions, lack production web application firewalls (WAF), or expose debug endpoints.
  • Orphaned Subdomains (Subdomain Takeover Risk): Subdomains pointing to third-party SaaS platforms (e.g., AWS S3, GitHub Pages, Heroku, Zendesk) where the underlying hosting resource was deleted but the DNS CNAME record was left active. Attackers can claim the abandoned SaaS bucket and serve phishing content under your brand.
  • Legacy Mail & Infrastructure Hostnames: Identify unmonitored mail servers (mail2.example.com, smtp-out.example.com) that may require SPF/DKIM authentication or decommission.
  • Shadow IT & Microservices: Discover endpoints spun up by internal teams that bypassed central IT governance.

Capability Limitations & Verification Boundaries

To maintain high speed and adhere to ethical standards, this tool adheres to specific technical boundaries:

  • Passive CT Logs Only: Only subdomains that have had a publicly trusted SSL/TLS certificate issued will appear in these logs.
  • No Active Brute-Forcing: The tool does not perform wordlist brute-forcing against DNS servers, so non-public internal hostnames without certificates are not listed.
  • Historical vs. Live DNS: A hostname found in a Certificate Transparency log proves a certificate was issued; it does not guarantee that the subdomain currently has an active DNS A/AAAA record or is online today. Validate live resolution using our DNS Lookup or Full Security Audit.