NetSight beta
Updated

Subdomain Finder

Discover subdomains for any domain by aggregating Certificate Transparency logs, passive DNS, threat-intel feeds and web archives. Passive discovery, no probing of the target.

About subdomain discovery

We enumerate subdomains by aggregating multiple passive intelligence sources: Certificate Transparency logs, passive-DNS feeds, threat-intel datasets and web archives. No packets are sent to the target itself, only public datasets are queried. This is pure passive reconnaissance. Each discovered host is then resolved over DNS-over-HTTPS so you can tell live hosts from stale records, and hosts confirmed by several independent lookups are marked.

Method

  • Several independent passive datasets are queried in parallel and merged.
  • Every host is resolved over DNS-over-HTTPS; live hosts are separated from stale records.
  • Resolved IPs are checked against Cloudflare's network so you can see which hosts are proxied.

Sources run isolated, so a single provider being down only removes its results, never the whole lookup. Wildcard entries (*.example.com) are filtered and duplicates are merged. Internal or expired subdomains may still appear.

When it's useful

  • Mapping an organization's external attack surface before a penetration test.
  • Finding forgotten staging or admin endpoints that still have certs.
  • Due diligence on a domain you're about to acquire.

Questions

Is this legal?
Yes. Only public datasets are queried and no packets are sent to the target itself. This is pure passive reconnaissance.
Why don't I see a subdomain I know exists?
If it was never exposed in any public dataset (no TLS certificate, no passive-DNS record, no archive entry), it won't appear. Internal-only or self-signed subdomains are invisible to passive discovery.
How fresh are the results?
Most sources update within minutes to hours. Newly issued certificates tend to show up quickly; some archives can lag by days.