dnsrecon
1.6.1 open-sourceThe section your link pointed to isn't on dnsrecon's page any more, so we've brought you to the top.
DNSRecon is a Python script that enumerates DNS records, checks for zone transfers, brute forces subdomains, and supports security assessment and network troubleshooting.
uv run dnsrecon -d example.com -t std -s -w --shodan --shodan-key "$SHODAN_API_KEY" curl -H "X-Shodan-Api-Key: $SHODAN_API_KEY" "http://127.0.0.1:5000/general_enum?domain=example.com&do_spf=true&do_whois=true&do_shodan=true&shodan_active=true" export DNSRECON_WORDLIST_DIRS="/opt/dnsrecon-wordlists:/srv/shared-wordlists" uv run dnsrecon -d example.com -t std -s -w --shodan --shodan-active --shodan-key "$SHODAN_API_KEY" curl -H "X-Shodan-Api-Key: $SHODAN_API_KEY" "http://127.0.0.1:5000/general_enum?domain=example.com&do_spf=true&do_whois=true&do_shodan=true&shodan_active=true" export DNSRECON_WORDLIST_DIRS="/opt/dnsrecon-wordlists:/srv/shared-wordlists" uv run dnsrecon -d example.com -t std -s -w --shodan --shodan-key "$SHODAN_API_KEY" curl -H "X-Shodan-Api-Key: $SHODAN_API_KEY" "http://127.0.0.1:5000/general_enum?domain=example.com&do_spf=true&do_whois=true&do_shodan=true&shodan_active=true" export DNSRECON_WORDLIST_DIRS="/opt/dnsrecon-wordlists:/srv/shared-wordlists" uv run dnsrecon -d example.com -t std -s -w --shodan --shodan-key "$SHODAN_API_KEY" uv run dnsrecon -d example.com -t std -s -w --shodan --shodan-active --shodan-key "$SHODAN_API_KEY" curl -s -H "X-Shodan-Api-Key: $SHODAN_API_KEY" "http://127.0.0.1:5000/general_enum?domain=example.com&do_spf=true&do_whois=true&do_shodan=true&shodan_active=true" python restdnsrecon.py dnsrecon -iL targets.txt -t std -o results.json dnsrecon -d example.com -r 192.168.1.0/24,10.0.0.0/24 dnsrecon -d example.com -n ns1.example.com dnsrecon -d example.com -b
Summary
dnsrecon is an open-source command-line tool for DNS reconnaissance, free to use, and run from a terminal via uv run dnsrecon or its bundled REST APIREST APIA web API design style where clients interact with resources over HTTP using standard methods like GET, POST, and DELETE, giving cyber tools a predictable, language-agnostic way to integrate with external services. for scripted access. It covers zone transfer checks, general record enumeration (MX, SOA, NS, A, AAAA, SPFSPFAn email authentication standard that lets a domain owner publish, via DNS, which mail servers are authorized to send on its behalf, so receiving servers can reject spoofed senders., TXT, CAA), SRVSRVA DNS record type that advertises the hostname and port for a specific service, letting clients discover endpoints without hardcoded addresses. and TLDTLDThe rightmost label in a domain name (e.g., .com, .gov, .uk), maintained by IANA's root zone. Cyber tools filter or pivot on TLDs to scope scans, flag suspicious registrations, or classify traffic by geography or type. expansion, wildcard detection, subdomain brute-forcing with wordlists, PTR lookups over a CIDRCIDRA notation for a block of IP addresses, such as 10.0.0.0/24. The number after the slash says how many leading address bits identify the network., and cache-snooping, with optional Shodan netblock expansion layered on SPF and WHOIS results. It's aimed at penetration testers and bug-bounty researchers mapping a domain's DNS footprint before deeper assessment, and its own README frames it as a Python re-implementation of an older Ruby recon script rather than a competitor to any named tool. Started in 2010 and still active, with 90 contributors and 16 releases in the tracked window, the most recent only 53 days old.
DNSRecon is a Python script that enumerates DNS records, checks for zone transfers, brute forces subdomains, and supports security assessment and network troubleshooting.
How dnsrecon helps
Which DNS records exist for this domain right now, across mail, name, address and text records?
queries and reports SOA, NS, MX, A, AAAA, SPF, TXT and CAA records in one pass, giving a baseline footprint before deeper testing
Which subdomains actually resolve, beyond the ones already known?
brute-forces host names from a wordlist against A and AAAA lookups and lists the ones that return an address
Will a positive brute-force hit turn out to be a wildcard false positive?
checks whether the domain resolves any random hostname before brute-forcing, so wildcard responses can be told apart from real hosts
Which IP addresses in a block I control have PTR records pointing somewhere unexpected?
walks a given IP range or CIDR doing reverse lookups and reports the hostname each address resolves back to
Has a given internal or resolved hostname already been cached by a DNS server, revealing that someone recently queried it?
checks a target name server for cached A, AAAA and CNAME entries against a supplied list of hosts, without triggering a fresh query
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for dnsrecon, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail dnsrecon puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
23 entries
No entries match these filters.
- October 20262
- September 20262
- August 20265
- May 20261
- February 20261
- December 20252
- September 20251
- July 20252
- October 20241
- June 20221
- April 20221
- April 20211
- February 20211
- October 20171
- July 20141
Project health
Issue, contributor and maintainer activity in darkoperator/dnsrecon, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 7 −1 vs prior 12 months
- Maintainers 2 +2 joined · −3 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close 18 days first maintainer reply 18 days
- Open backlog 1 of 131 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 1
- Contributors / month 0
- Commits / month 0
- Stars 3,070
- other 100%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.