subjack
v3.1.0 open-sourceThe section your link pointed to isn't on subjack's page any more, so we've brought you to the top.
Subjack is a DNS takeover scanner written in Go that scans domains concurrently to identify ones vulnerable to hijacking.
subjack -w subdomains.txt -srv -t 50 -o results.json subjack -w subdomains.txt -r resolvers.txt -ssl -o results.json subjack -w domains.txt -ar -o results.txt cat domains.txt | subjack -ns -axfr -o results.txt subjack -w domains.txt -mail -o results.txt subjack -w subdomains.txt -t 100 -r resolvers.txt -o results.json -json
Summary
subjack is an open-source DNS takeover scanner, written in Go, that checks lists of domains for signs they can be hijacked. It runs as a command-line tool installed via go install, scanning domains concurrently and writing results to a file or stdout, with subdomains typically piped in from a separate recon or enumeration tool. It covers dangling CNAMEs, expired NS delegations, stale A records on major cloud providers, zone transfers, and 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./MX/SRVSRVA DNS record type that advertises the hostname and port for a specific service, letting clients discover endpoints without hardcoded addresses. record takeovers, which makes it a fit for penetration testers and bug bounty hunters doing subdomain-takeover reconnaissance rather than continuous monitoring teams. It sits in the subdomain-takeover corner of the reconnaissance space, a narrower complement to broader subdomain-enumeration tools that feed it targets. First committed in 2017 and still active, with 10 contributors, 23 commits in the past year, and a release as recently as 158 days ago.
Subjack is a DNS takeover scanner written in Go that scans domains concurrently to identify ones vulnerable to hijacking.
How subjack helps
Which of my subdomains have dangling CNAMEs pointing to a service nobody claimed?
matches each CNAME target against its fingerprint set of cloud and SaaS providers and flags the ones that resolve to an unclaimed endpoint, so a false positive still needs a manual double-check
Do any of my zones sit on a nameserver that's expired or been deleted from its cloud DNS provider?
checks whether the delegated nameservers still resolve and are still registered, catching zones left pointing at a deleted Route 53, Google Cloud DNS, Azure DNS, DigitalOcean, Vultr or Linode zone
Are any of my A records still pointing at a cloud IP I already tore down?
resolves each domain's A record and checks it against the address ranges of AWS, GCP, Azure, DigitalOcean, Linode, Vultr and Oracle Cloud for signs the underlying host is gone
Can someone pull my whole zone file with a zone transfer?
attempts an AXFR against each domain's nameservers, bruteforcing likely NS hostnames first, and reports which targets hand over their records
Could someone spoof mail from my domain or intercept it through an expired record?
parses SPF include directives and MX records, checks whether the domains they point to have expired, and flags the ones open to registration
Which of these subdomains don't even exist yet and could be grabbed outright?
flags targets that return NXDOMAIN and are available for registration, separate from the takeover checks against live records
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 subjack, 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 subjack 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
4 entries
No entries match these filters.
- October 20261
- March 20262
- April 20181
Project health
Issue, contributor and maintainer activity in haccer/subjack, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 1 +1 vs prior 12 months
- Maintainers 1 +1 joined · −0 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 5.8 years first maintainer reply 2.2 days
- Open backlog 2 of 60 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 2
- Contributors / month 0
- Commits / month 0
- Stars 2,113
- 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.