THE PRACTICAL GUIDE · NORMANDIN SYSTEMS
Get more from ARPA Decoder
ARPA Decoder: Decode IPv4/6 ARPA addresses or PTR record. IPv4 reverse-DNS names reverse the octets before adding in-addr.arpa; decoding reveals the address represented by the reverse-lookup owner name. IP calculations describe address space; they do not tell you whether a host is online or whether a firewall permits traffic. Prefix lengths divide an address into network and host portions, and a one-bit prefix change can substantially change the number of included addresses. Confirm whether you are working with IPv4 or IPv6 and use the same family throughout a calculation. For network planning, record both the human-readable notation and the exact boundaries. This helps catch accidental overlap, oversized allowlists, and assumptions about which addresses are usable.
Guide updated October 13, 2026
How to use this tool
- Begin with a representative input. For a practical test, use: 1.2.0.192.in-addr.arpa. Replace demonstration values only after you understand the output.
- Enter the address, range, or prefix in the syntax requested by the tool, using the correct IPv4 or IPv6 address family.
- Inspect the network boundaries and the size of the resulting address space, especially when a calculation broadens or subdivides a range.
- Compare the result with neighboring subnets and your intended allocation before applying it to a router, firewall, or configuration file.
SEE IT IN PRACTICE
A worked example
1.2.0.192.in-addr.arpa
192.0.2.1
For IPv6, reverse DNS uses reversed hexadecimal nibbles under ip6.arpa, not reversed colon-separated groups.
Translate the owner name carefully
For 192.0.2.1, the IPv4 reverse owner is 1.2.0.192.in-addr.arpa. The PTR value is a hostname, not another reversed address. IPv6 uses a different representation: individual hexadecimal nibbles are reversed under ip6.arpa. Keep these conventions distinct when moving between address families, and preserve the full address when checking an unfamiliar reverse name.
Authority and forward DNS are separate
A forward A or AAAA record maps a hostname to an address, while a PTR record sits in the reverse zone for the address. The organizations controlling those zones can differ. Generating or decoding the owner name does not publish either mapping. Confirm reverse-zone authority with the address provider, then query the authoritative record and check any forward-confirmation requirements of the consuming service.
When this tool is useful
- Read reverse-DNS logs
- Check a PTR owner name
- Translate reverse-zone notation
Tips for a better result
- Decoding a reverse name does not perform a PTR lookup or prove that a DNS record exists.
- An address being mathematically inside a subnet does not prove that the address is assigned, reachable, or authorized for access.
- Keep prefix lengths visible in documentation; an address without its prefix is insufficient to describe a subnet allocation.
Frequently asked questions
Why is the IPv4 address written backward in a reverse-DNS name?
Reverse DNS organizes address space hierarchically. Reversing the octets places the most significant address portion closer to the DNS hierarchy’s right-hand side before in-addr.arpa.
Why does the prefix length matter?
The prefix length controls how many bits identify the network. Increasing the prefix length makes the block smaller; decreasing it makes the block larger and can include addresses beyond your intended scope.
Can I paste the result directly into a firewall?
First verify the destination’s accepted syntax and the policy’s intended scope. A mathematically correct range can still grant too much access, overlap another rule, or behave differently because of rule ordering.
What happens to the information I enter?
The utility processes your input in this browser. Some tools retain field values in browser storage or the URL; avoid entering secrets in shareable fields. Page and asset requests still go to the hosting provider. Read the privacy and offline-use notes for details.