DNS WireFormat Hex Packet Parser

Decode DNS header fields, compressed names and A, AAAA, CNAME, MX and TXT records from hexadecimal bytes locally.

Dns Wireformat Parser · Client runtimeSandboxed

Dns Wireformat Parser Input

Dns Wireformat Parser Output

Formatted results will render here in real time.

Dns Wireformat Parser: JavaScript is required to run this tool in the browser.

About this dns wireformat hex packet parser

Decode DNS header fields, compressed names and A, AAAA, CNAME, MX and TXT records from hexadecimal bytes locally Performs protocol inspection, IP calculation, and network analysis client-side without sending probes or exposing network topology.

Protocol mechanics & network logic

The execution engine processes input tokens and applies transformations in the browser sandbox. Specifically, Enter one DNS message as two-digit hex octets separated by whitespace, commas, colons or hyphens. Run locally to read questionRecords, answerRecords, authorityRecords and additionalRecords. No DNS query is sent.

Worked network diagnostic scenario

Scenario: Decode a compressed A answer for example.com.

Sample input:

12 34 81 80 00 01 00 01 00 00 00 00 07 65 78 61 6d 70 6c 65 03 63 6f 6d 00 00 01 00 01 c0 0c 00 01 00 01 80 00 00 01 00 04 c0 00 02 01

Processing: Read one question, follow the answer owner pointer c0 0c to byte 12, and decode four A bytes as 192.0.2.1.

Illustrative output:

{ "id": 4660, "qr": true, "opcode": 0, "authoritative": false, "truncated": false, "recursionDesired": true, "recursionAvailable": true, "responseCode": 0, "questions": 1, "answers": 1, "authorities": 0, "additionals": 0, "questionRecords": [ { "name": "example.com", "type": 1, "class": 1 } ], "bytes": 45, "answerRecords": [ { "name": "example.com", "type": 1, "typeName": "A", "class": 1, "ttl": 2147483649, "rdlength": 4, "rawHex": "c0 00 02 01", "data": "192.0.2.1" } ], "authorityRecords": [], "additionalRecords": [] }

Addressing limits & protocol boundaries

Operational constraints and validation boundaries: Limits: 65535 input characters, 1024 total questions and records, 63 bytes per label, 255 bytes per expanded name and 128 pointer hops. Compression pointers must target prior decoded name boundaries. A/AAAA/CNAME/MX/TXT are decoded for class IN; other classes and unsupported types retain rawHex with data null. AAAA uses eight hexadecimal groups; TXT preserves separate strings and escapes nonprintable bytes and backslashes as \DDD. Domain labels also escape dots; the root name is an empty string. Invalid lengths, cycles and trailing bytes are rejected. Supply the DNS message only, without TCP length or IP/UDP headers. No EDNS option decoding, DNSSEC validation or full DNS conformance claim.

Addressing calculations and subnet models in DNS WireFormat Hex Packet Parser follow IETF RFC definitions. Ensure subnet masks and CIDR prefixes match your network topology.

Offline network inspection boundary

Address parsing and CIDR calculations in DNS WireFormat Hex Packet Parser run entirely client-side without probing external IP networks or transmitting routing data.

IETF RFC specifications & IANA registries

IETF Request for Comments (RFC) standards and IANA registry references:

DNS WireFormat Hex Packet Parser verification · Audit standards

How to use it

No DNS query is sent.
Check the 12-byte header and all declared sections, including compressed names.
Click the action button or observe immediate live calculations rendered by DNS WireFormat Hex Packet Parser.

Frequently asked questions

What DNS fields does this parser read?+

Enter one DNS message as two-digit hex octets separated by whitespace, commas, colons or hyphens. No DNS query is sent.

Which input and result fields are available?+

No DNS query is sent.

Which byte-format limits actually apply?+

Limits: 65535 input characters, 1024 total questions and records, 63 bytes per label, 255 bytes per expanded name and 128 pointer hops.

What result does the worked example produce?+

id 4660; questions 1; answers 1; example.com; 192.0.2.1; bytes 45.