FREE & OPEN
THE OPEN PROTOCOL PLAYGROUND

Make every packet make sense.

Explore the conversations that connect our world. One packet at a time.

66 protocolsZero paywalls. Endless curiosity.

DNS-over-HTTPS

Web & applicationIntermediate

Carry a DNS message inside an HTTPS exchange.

SIMULATION01 / 03
Loading topology…
0.0s / 2.8s
01
STEP 1 OF 3Client → Server / peer

TLS established

HTTPS authenticates the resolver endpoint before the DNS exchange.

#TIMESOURCE → DESTINATIONMESSAGE
0.000192.0.2.10198.51.100.20TLS established
1.400192.0.2.10198.51.100.20POST /dns-query
2.800198.51.100.20192.0.2.10200 DNS response

Carry a DNS message inside an HTTPS exchange.

Explain TLS established and distinguish it from 200 DNS response.

Prerequisites: DNS, HTTPS

Ready to test your understanding?

Rebuild the exchange. Read the fields. Find the mistakes.

Learn from the sourceRFC 8484Protocol guide

DNS-over-HTTPS: protocol guide / panduan protokol

Carry a DNS message inside an HTTPS exchange.

Bawa pesan DNS di dalam pertukaran HTTPS.

Communication walkthrough / Alur komunikasi

  1. TLS established

    HTTPS authenticates the resolver endpoint before the DNS exchange.

    HTTPS mengautentikasi endpoint resolver sebelum pertukaran DNS.

  2. POST /dns-query

    The body is a binary DNS message, not JSON.

    Body berupa pesan DNS biner, bukan JSON.

  3. 200 DNS response

    HTTP success and DNS RCODE are distinct results and must both be checked.

    Keberhasilan HTTP dan RCODE DNS adalah hasil berbeda yang harus diperiksa.

Source and simulation scope

This is a simplified, deterministic teaching scenario. Timing is illustrative. Messages grouped within one event are explicitly condensed. Hexadecimal fixtures, where shown, contain only the indicated protocol ADU, not a full network capture. No PCAP files are supplied.

RFC 8484 ↗