networkutils.org

Home / Security Tools / Subdomain Discovery

Subdomain Discovery

Security Tools

Passive enumeration from CT logs and DNS data.

Run this tool: the interactive Subdomain Discovery loads here (requires JavaScript). Input: Domain — e.g. example.org.

Description

Subdomain Discovery passively enumerates the subdomains of a domain using public Certificate Transparency logs and passive DNS data — no active scanning of the target is performed.

Features

✓ Passive enumeration from Certificate Transparency logs
✓ Passive DNS data correlation
✓ No packets sent to the target domain
✓ Deduplicated, sorted subdomain list

How to Use

Enter a domain name (example.org) and run the tool. The probe queries public CT logs and passive DNS sources for any subdomain recorded against the domain.

Input: Domain — e.g. example.org.

Understanding the Results

The output is a deduplicated list of discovered subdomains (dev., staging., api., mail., vpn.…). Use it to map your external attack surface or to find forgotten, exposed hosts. Because the source is passive public data, only subdomains that have appeared in a public certificate or DNS record will be found.

Common Use Cases & Examples

→ Map your external attack surface for a security audit.

→ Find forgotten or stale subdomains to decommission.

→ Discover subdomains created without change control.

→ Reconnaissance for an authorised penetration test.

Frequently Asked Questions

Will this find every subdomain I have?

No. Only subdomains that have appeared in a public Certificate Transparency log or passive DNS data are returned. Internal-only or never-certified subdomains that never resolved publicly will not appear. Treat the result as a lower bound of your external surface.

Is passive subdomain enumeration safe to run on any domain?

It only queries public databases and sends no traffic to the target, so it is non-intrusive. It is appropriate for mapping your own attack surface or for reconnaissance on assets you are authorised to assess.

Why did I find a subdomain I did not know about?

It was likely created by a team member or automation and issued a certificate, or it is leftover from an old project. Investigate each unexpected result — forgotten hosts are a common source of unpatched, exposed services.

About this tool

Maintained by
networkutils.org editorial team
Last updated
September 2026
Testing methodology
TLS checks perform a real TLS handshake with Node.js tls against port 443 and inspect the presented certificate chain; the Security Headers and Exposure Check tools issue HTTP requests from the server; Subdomain Discovery and CT Log Search query the public crt.sh Certificate Transparency service.
Technical references
RFC 6962 — Certificate Transparency