networkutils.org

Home / DNS Tools / Zone Transfer Test

Zone Transfer Test

DNS Tools

Detect name servers that expose AXFR publicly.

Run this tool: the interactive Zone Transfer Test loads here (requires JavaScript). Input: Domain — e.g. example.org.

Description

The Zone Transfer Test checks whether a domain's authoritative name servers expose a full AXFR zone transfer to the public — a serious misconfiguration that leaks the entire zone contents, including internal hostnames.

Features

✓ AXFR transfer attempt against every authoritative NS
✓ Per-name-server transfer status
✓ Detects publicly readable zone misconfiguration
✓ Full record enumeration when a transfer succeeds

How to Use

Enter a domain name (example.org) and run the tool. The probe requests an AXFR zone transfer from each authoritative name server and reports whether it was permitted.

Input: Domain — e.g. example.org.

Understanding the Results

Each line shows a name server and whether the transfer was ALLOWED or DENIED. ALLOWED is a security problem — it means anyone can download the entire zone, exposing subdomains and internal records that are not otherwise discoverable. A healthy configuration denies AXFR to all untrusted sources.

Common Use Cases & Examples

→ Audit authoritative name servers for accidental AXFR exposure.

→ Verify transfer restrictions after a DNS provider migration.

→ Demonstrate a misconfiguration to a client or vendor.

→ Confirm secondaries still replicate while public transfer is denied.

Frequently Asked Questions

Why is an open AXFR a security risk?

It lets anyone download the entire zone — every subdomain, internal hostname and record — in one request. This reveals your internal topology and hosts that were meant to be unguessable, expanding your attack surface for targeted attacks.

Should AXFR ever be allowed?

Only between your own primary and secondary name servers, restricted by source IP / TSIG. It should never be permitted to the public internet or arbitrary source addresses.

How do I fix an open zone transfer?

On your name server, restrict allow-transfer (BIND) or the equivalent to your secondaries’ IPs or a TSIG key, and remove any wildcard allow rules. Re-run this tool to confirm every NS now denies public AXFR.

About this tool

Maintained by
networkutils.org editorial team
Last updated
September 2026
Testing methodology
DNS queries run through Node.js dns.promises and, for DNSSEC record types (DS/DNSKEY) and the AD validation flag, through Cloudflare DNS-over-HTTPS (application/dns-json). The Propagation Check queries 10 public recursive resolvers directly and compares their A-record answers. The DNS SuperTool performs its checks client-side in your browser over DNS-over-HTTPS using Cloudflare and Google.
Technical references
RFC 5936 — DNS Zone Transfer Protocol (AXFR)