Subdomain Radar — Passive OSINT Enumeration avatar

Subdomain Radar — Passive OSINT Enumeration

Pricing

from $1.00 / 1,000 results

Go to Apify Store
Subdomain Radar — Passive OSINT Enumeration

Subdomain Radar — Passive OSINT Enumeration

Discover subdomains silently. No brute-force — pure OSINT from 5 passive sources with DNS resolve, HTTP probing & takeover detection.

Pricing

from $1.00 / 1,000 results

Rating

0.0

(0)

Developer

Saregaa

Saregaa

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

13 days ago

Last modified

Share

🔍 Subdomain Enumeration Toolkit

Passive subdomain discovery with DNS validation, HTTP probing, and takeover detection.

Built for security researchers, bug bounty hunters, and penetration testers who need fast, reliable subdomain enumeration without noisy brute-force traffic.


✨ What it does

For each target domain the Actor:

  1. Collects subdomains from 5 passive OSINT sources simultaneously
  2. Resolves DNS — finds the live IP address for each subdomain
  3. Probes HTTP/HTTPS — checks status code, page title, server header, and redirects
  4. Detects takeover risks — flags subdomains pointing to unclaimed cloud services

🗂️ Sources

SourceTypeAPI key needed
CertspotterCertificate Transparency logsNo
HackerTargetPassive DNS archiveNo
RapidDNSPassive DNS archiveNo
AlienVault OTXThreat intelligenceFree (optional)
URLScan.ioInternet scan archiveNo

All sources are passive — no direct scanning, no brute-force, no traffic to the target.


🛡️ Takeover detection

Automatically checks 30+ services for dangling CNAME records:

GitHub Pages · Heroku · AWS S3 · AWS CloudFront · Azure Web Apps · Azure Blob · Netlify · Webflow · Shopify · Fastly · Zendesk · Ghost · GitBook · WP Engine · Surge · Bitbucket · Tumblr · and more.

Each finding is labeled as high (dangling — no IP) or medium (resolves but CNAME points to a cloud service).


⚙️ Input

FieldTypeDefaultDescription
domainsstring[]Required. Target domains, e.g. example.com
otxApiKeystringOTX API key for extra results.Get free key →
doResolvebooleantrueResolve DNS A records
doProbebooleantrueHTTP/HTTPS probe per live host
doTakeoverbooleantrueSubdomain takeover detection
probeTimeoutSecsinteger7Timeout per HTTP probe request
maxConcurrencyinteger30Parallel DNS/HTTP workers
useApifyProxybooleanfalseRoute probes through Apify residential proxies

📦 Output

Each subdomain is saved as one row in the dataset:

{
"domain": "tesla.com",
"subdomain": "api.tesla.com",
"sources": ["Certspotter", "RapidDNS"],
"dns_resolves": true,
"dns_ip": "23.62.104.69",
"http_status": 200,
"http_title": "Tesla API",
"http_server": "nginx",
"http_redirect": "",
"is_live": true,
"takeover_risk": "none",
"takeover_service": "",
"scanned_at": "2026-05-30T12:00:00+00:00"
}

takeover_risk values: none / medium / high

A RUN_METADATA record is also saved to the Key-Value Store:

{
"total_domains": 1,
"total_subdomains": 308,
"live_http": 291,
"takeover_high": 2,
"takeover_medium": 5,
"scanned_at": "2026-05-30T12:00:00+00:00"
}

💡 Example use cases

  • Bug bounty recon — map the full attack surface before starting an engagement
  • Penetration testing — discover forgotten staging, dev, and internal subdomains
  • Takeover hunting — find orphaned subdomains pointing to unclaimed Heroku apps, S3 buckets, GitHub Pages
  • Competitor intelligence — understand a company's infrastructure layout
  • Attack surface monitoring — run on a schedule to catch newly created subdomains

💰 Pricing

This Actor uses Pay-Per-Event billing:

EventCost
Actor start$0.05 flat per run
Per discovered subdomain$0.001 per subdomain

Example: scanning tesla.com and finding 308 subdomains costs $0.05 + 308 × $0.001 = $0.358.


AlienVault OTX significantly increases subdomain coverage — in tests it added 100+ unique subdomains on top of other sources.

  1. Register free at otx.alienvault.com
  2. Go to Settings → API Key
  3. Paste the key into the otxApiKey input field

Free tier: 10,000 requests/hour.


🖥️ Local testing

# Install dependencies
pip install -r requirements.txt
# Create input
mkdir -p storage/key_value_stores/default
cat > storage/key_value_stores/default/INPUT.json << 'JSON'
{
"domains": ["example.com"],
"otxApiKey": "your_key_here",
"doProbe": true,
"doTakeover": true
}
JSON
# Run
python src/main.py

Results are saved to storage/datasets/default/.


📋 Memory requirements

  • 512 MB — sufficient for most single-domain runs
  • 1024 MB — recommended for 10+ domains or large domains with 500+ subdomains

Use only on domains you own or have explicit written permission to test. The author is not responsible for misuse. This tool performs passive reconnaissance only — it does not send any traffic directly to the target.