dnsx
v1.3.0 open-sourceThe section your link pointed to isn't on dnsx's page any more, so we've brought you to the top.
dnsx is a fast and multi-purpose DNS toolkit allow to run multiple DNS queries of your choice with a list of user-supplied resolvers.
dnsx -d example.com -w wordlist.txt -auto-wildcard -silent
subfinder -silent -d example.com | dnsx -silent -a -ot '{{host}} {{a}} {{query-time}}'
dnsx -l example.com,api.example.com,dev.example.com -a -resp
dnsx -l targets.txt -a -timeout 2
echo example.com | dnsx -recon
echo example.com | dnsx -recon -e TXT,MX
echo hollisterco.com | dnsx -any -resp
echo example.com | dnsx -json --omit-raw
dnsx --domain example.com -caa
dnsx --name-server ns1.example.com -axfr
dnsx -d example.com -rcode
dnsx -i 10.0.0.0/24
dnsx -domain example.com -trace
dnsx -d example.com -stats
Summary
dnsx is an open-source DNS toolkit, released under an MIT-style open license at no cost, that runs queries and brute-forces subdomains through the retryabledns library. It is a command-line tool, used via stdin/stdout so it chains with other recon utilities, and it fits recon work like resolving active subdomains from subfinder output, pulling A/AAAA/CNAMECNAMEA DNS record type that maps one hostname to another as a canonical alias, letting cyber tools track infrastructure by following chains of names to their true origin./PTR/MX/TXT/SRVSRVA DNS record type that advertises the hostname and port for a specific service, letting clients discover endpoints without hardcoded addresses./SOA records, or reverse-resolving an IP range, with custom resolvers, TCPTCPA network protocol that delivers a reliable, ordered stream of bytes between two endpoints. It detects lost data and retransmits it./UDPUDPA network protocol that sends individual messages without guaranteeing delivery or order. Applications trade built-in reliability for less overhead and can add their own recovery./DOHDOHDNS over HTTPS, an IETF standard (RFC 8484) that tunnels DNS queries inside encrypted HTTPS traffic, making resolution indistinguishable from web traffic and bypassing traditional DNS-based monitoring./DOT support, and automatic wildcard filtering comparable to the project's own shuffledns. It is aimed at people doing asset discovery and attack-surface mapping, such as red teamers and recon-focused security engineers, rather than application developers. First committed in 2020 and still active, with 41 contributors, 54 commits and 15 releases in the past year, and a release 36 days ago.
dnsx is a fast and multi-purpose DNS toolkit allow to run multiple DNS queries of your choice with a list of user-supplied resolvers.
How dnsx helps
Which of these subdomains from my recon list are actually alive right now?
takes a list of hostnames on stdin, resolves each one, and prints only the ones that answer, filtering out dead names before they waste time in later scan stages
Which hosts in this domain exist but were never listed anywhere I found them?
brute-forces a wordlist against the domain through user-supplied resolvers and reports which guesses resolve, surfacing subdomains no source handed you directly
Is this wildcard DNS setup going to poison my subdomain results with false positives?
detects wildcard responses automatically across registrable roots using A/AAAA comparison and filters matching hosts out of the result set before you see them
What mail, name, and text infrastructure sits behind this domain?
queries MX, NS, TXT, SRV, and SOA records for each host and prints them alongside the hostname, giving you the supporting infrastructure without separate lookups per record type
Which IP range resolves back to which hostnames?
reverse-resolves each address in a range through PTR queries and lists the hostname each IP maps to, turning a raw CIDR into named assets
Are my DNS lookups being seen or blocked by something between me and the resolver?
lets you route queries over TCP/UDP/DOH/DOT or through a SOCKS5 proxy, so you can compare answers across transports and confirm whether plain UDP is being intercepted or dropped
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 dnsx, 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 dnsx 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…
Commercials
pricing & packaging history · ProjectDiscovery vendor page23 readings of ProjectDiscovery's pricing page since Feb 2024, with 7 relaunches of its plan lineup and 4 changes to what its plans include — each one dated, compared with the reading before it, and explained for someone buying the tool.
Pricing and packaging history is included with Researcher and Business. See how every vendor we track sells, and how that has changed over time, using data we don't publish anywhere else.
See plans → Already subscribed? Sign in →Plans by offering
Each offering on the pricing page links to its own page of plans, read at its latest capture.
Plan relaunches
Plans, prices and descriptions are quoted from the vendor's own pricing page as we read it on each date. A plan missing from a later reading is shown as no longer listed on the page — a statement about the page, not the product. Readings that failed to show any plans are left out rather than read as a change.
Website history
projectdiscovery.io, every changeProjectDiscovery's home page and 3 more pages as they looked each month from August 2021 to October 2026: 18 renders, 4 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Releases
12 entries
No entries match these filters.
- July 20261
- December 20251
- February 20251
- March 20241
- September 20231
- February 20231
- September 20221
- February 20221
- November 20211
- June 20212
- November 20201
Project health
Issue, contributor and maintainer activity in projectdiscovery/dnsx, 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 3 +3 joined · −2 left, last 12 months
- Bus factor 2 committers behind half the commits
- Community-filed 77% of issues opened, last 12 months
- Median time to close 194 days first maintainer reply 16 days
- Open backlog 0 of 158 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 0
- Contributors / month 0
- Commits / month 0
- Stars 2,878
- bugs 39%
- features 33%
- other 28%
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.