PAGES
← all tools
◆ Reconnaissance & OSINT

subjack

v3.1.0 open-source

Subjack is a DNS takeover scanner written in Go that scans domains concurrently to identify ones vulnerable to hijacking.

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

all 9 features, with the evidence for each →

Languages

Not documented

Features

9 capabilities · 1 backed by code, an API document or a real run

Built from subjack's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • subjack covers 1 of the 13 network discovery and scanning capabilities we track.

What subjack offers you

  • Command-line interface1
DNS record enumeration 5 features Network discovery and scanning since 2026
DNS record takeover detection verified Checks for subdomain/DNS takeover opportunities including stale A records pointing to dead IPs, available-for-purchase nameservers, zone transfer exposure, and SPF/MX record hijacking risks. 3 releases · 5 other sources · first seen Mar 2026

Shared capability: DNS record enumeration

Also counts toward: Command-line interface

release

  • Switches domain availability checks from the heavyweight zonedb dependency to RDAP (RFC 9083) with a whois fallback, eliminating OOM on small VPSes v3.1.0 · Oct 2026 · source · release history
  • Adds dangling NS delegation checks for deleted cloud DNS zones on Route53, Google Cloud DNS, Azure DNS, and others via -ns. v3.0.0 · Mar 2026 · source · release history
  • Adds zone transfer (AXFR) detection with NS hostname bruteforcing via -axfr. v3.0.0 · Mar 2026 · source · release history

command line

  • --ar — Check for stale A records pointing to dead IPs (may require root for ICMP). v3.0.0 · Mar 2026 · command-line history
  • --axfr — Check for zone transfers (AXFR) including NS bruteforce. v3.0.0 · Mar 2026 · command-line history
  • --mail — Check for SPF include and MX record takeovers. v3.0.0 · Mar 2026 · command-line history
  • --ns — Check if nameservers are available for purchase (NS takeover). v3.0.0 · Mar 2026 · command-line history

example

  • Test single domain for zone transfers subjack -d example.com -axfr -o results.json
SRV record takeover detection shipped Detects SRV record takeovers where targets point to registrable domains. 2 releases · 1 other source · first seen Mar 2026

Shared capability: DNS record enumeration

release

  • Adds -srv flag to opt in to SRV record takeover detection (~28 DNS queries per domain for SIP, XMPP, LDAP, Kerberos, IMAP, CalDAV, and more)⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v3.1.0 · Oct 2026 · source · release history
  • Adds SRV record takeover detection for SRV targets pointing to registrable domains. v3.0.0 · Mar 2026 · source · release history

example

  • Scan for SRV record takeovers alongside standard CNAME checks — useful when targets run SIP, XMPP, or LDAP services with potentially expired backend domains subjack -w subdomains.txt -srv -t 50 -o results.json v3.1.0 · Oct 2026 · source
Email record takeover detection shipped Detects SPF include and MX record takeover opportunities for expired domains. 1 release · 1 other source · first seen Mar 2026

Shared capability: DNS record enumeration

release

  • Adds SPF include and MX record takeover detection for expired domains via -mail. v3.0.0 · Mar 2026 · source · release history

example

  • Hunt for SPF include and MX record takeover opportunities across a list of targets. subjack -w domains.txt -mail -o results.txt v3.0.0 · Mar 2026 · source
Stale A record detection across cloud providers shipped Detects stale A records pointing to deleted resources across AWS, GCP, Azure, DigitalOcean, Linode, Vultr, and Oracle Cloud. 1 release · 1 other source · first seen Mar 2026

Shared capability: DNS record enumeration

release

  • Adds stale A record detection across AWS, GCP, Azure, DigitalOcean, Linode, Vultr, and Oracle Cloud via -ar. v3.0.0 · Mar 2026 · source · release history

example

  • Scan a domain list for stale A records on cloud providers — useful after a cloud VM is deleted but DNS still points to the old IP. subjack -w domains.txt -ar -o results.txt v3.0.0 · Mar 2026 · source
Dangling NS delegation and zone transfer exposure detection shipped Checks for dangling NS delegations on cloud providers and zone transfer exposure in a single pass. 1 other source · first seen Mar 2026

Shared capability: DNS record enumeration

example

  • Check for dangling NS delegations and zone transfer exposure in one pass, piping targets from a recon tool. cat domains.txt | subjack -ns -axfr -o results.txt v3.0.0 · Mar 2026 · source
Other / not yet classified 4 features Features we have not matched to a capability yet. A suggested match is marked.
DNS resolver configuration shipped suggested Supplies a custom list of DNS resolvers with random selection and fallback to avoid rate-limiting or improve accuracy. 3 releases · 2 other sources · first seen Apr 2018

Suggested capability: Subdomain enumeration. This is our guess, not confirmed.

release

  • Allows -r resolver list entries in host:port format, not just bare IP addresses v3.1.0 · Oct 2026 · source · release history
  • New -r flag to supply a custom list of DNS resolvers with random selection and fallback. v2.2.0 · Mar 2026 · source · release history
  • Adds JetBrains & Microsoft Azure fingerprinting capabilities 1.3 · Apr 2018 · source · release history

example

  • Use a custom resolver list with non-standard ports (e.g. an internal DNS forwarder) to route all subjack queries through specific resolvers subjack -w subdomains.txt -r resolvers.txt -ssl -o results.json v3.1.0 · Oct 2026 · source
  • Use a custom resolver list instead of system DNS to avoid rate-limiting or improve accuracy during large subdomain takeover scans. subjack -w subdomains.txt -t 100 -r resolvers.txt -o results.json -json v2.2.0 · Mar 2026 · source
Azure Traffic Manager false positive reduction shipped suggested Uses Azure Traffic Manager API verification to reduce false positives in takeover detection. 2 releases · first seen Apr 2018

Suggested capability: Subdomain enumeration. This is our guess, not confirmed.

release

  • Adds Azure Traffic Manager API verification to reduce false positives. v3.0.0 · Mar 2026 · source · release history
  • Adds --nxdomain flag to check for subdomains pointing to non-existent domains and their registration availability 1.3 · Apr 2018 · source · release history
Comprehensive result output shipped Writes all scan results to the output file, not only vulnerable findings. 1 release · first seen Mar 2026

release

  • Writes all results to the output file, not only vulnerable findings. v3.0.0 · Mar 2026 · source · release history
Subdomain takeover detection via CNAME chain traversal shipped Detects takeovers by traversing multi-level CNAME chains up to 10 levels deep. 1 release · first seen Mar 2026

release

  • Adds CNAME chain takeover detection traversing multi-level chains up to 10 deep. v3.0.0 · Mar 2026 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. 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 →

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…

Explore the full chart →

Releases

Show

4 entries

  1. October 20261
  2. March 20262
  3. April 20181
    Show

    4 entries

    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.

    1. Contributors 1 +1 vs prior 12 months
    2. Maintainers 1 +1 joined · −0 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 100% of issues opened, last 12 months
    5. Median time to close 5.8 years first maintainer reply 2.2 days
    6. Open backlog 2 of 60 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 2
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 2,113
    Issue themes, last 12 months
    • 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.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →