Back to Blog
subdomains

How to Find Every Subdomain Your Organization Owns

Certificate Transparency logs, DNS brute force, and passive sources reveal more subdomains than you expect — the list is always bigger than you think.

ThreatPort Security Team
July 23, 2026
2 min read

Every subdomain your organization owns is an entry point to your infrastructure. Subdomains are created for specific purposes — staging environments, APIs, marketing campaigns, third-party integrations — and are often forgotten after the purpose is served. The list of subdomains is always bigger than you think, because forgotten subdomains are the ones that attackers find first.

The discovery process uses multiple sources. No single source finds all subdomains. Certificate Transparency logs find subdomains that have been issued TLS certificates. DNS brute force finds subdomains that are in DNS but not in CT logs. Passive sources (search engines, web archives) find subdomains that are linked from other websites.

Certificate Transparency Logs

CT logs are the most valuable source for subdomain discovery. Every TLS certificate issued for your domain is logged, and the certificate reveals the subdomain. ThreatPort's subdomain monitoring queries CT logs to discover subdomains that have been issued certificates. This includes staging environments, internal tools, and forgotten services.

DNS Records

DNS records are public and reveal subdomain names. A DNS zone transfer (if misconfigured) reveals all records. DNS brute force tests common subdomain names (www, mail, api, staging, dev) against your domain. Passive DNS databases record historical DNS resolutions, revealing subdomains that may no longer be active.

Passive Sources

Search engines index subdomains that are linked from other websites. Web archives (Wayback Machine) record subdomains that were previously active. Code repositories (GitHub, GitLab) may contain subdomain names in configuration files or deployment scripts.

Why the List Is Always Bigger

The list is always bigger because subdomains are created and forgotten. A developer creates a staging subdomain for testing and forgets to remove it. A marketing campaign creates a subdomain for a landing page and forgets to decommission it. A third-party integration creates a subdomain for an API endpoint and forgets to clean it up. These forgotten subdomains are the ones that attackers find first.

How ThreatPort Helps

ThreatPort combines multiple discovery sources to find every subdomain. The subdomain monitoring queries Certificate Transparency logs and performs DNS enumeration to discover subdomains. The scan produces a complete list that you can compare against your internal inventory. Combined with open port monitoring, you can see which subdomains are active and what services they expose.

We use essential cookies to operate this site and optional analytics cookies to improve it. Cookie Policy