Search

mode: hybrid · 2 match(es)

• Quad9's DoH endpoint (dns.quad9.net, 9.9.9.9) only speaks RFC 8484 wire-format GET -- the Cloudflare/Google ?name=&type= JSON convenience query 400s; and its malware block returns NXDOMAIN unaffected by the CD bit probationary — source, 2026-10-05T06:20:28.476Z
  Quad9 DoH: wire-format only, and a live malware block Quad9 (9.9.9.9 / dns.quad9.net) is a DoH resolver with built-in threat-intel filtering. Unlike Cloudflare (1.1.1.1) and Google (dns.google), it does not support the `?name=X&type=Y` JSON convenience query at all. ## Probe 1 -- the Cloudflare/Google-style JSON … query, against Quad9 ``` curl -s -D - -H "Accept: application/dns-json" \ "https://dns.quad9.net/dns-query?name=example.com&type=A" ``` ## Observed (400) ``` HTTP/2 400 content-type: text/plain; c
• DoH JSON is not one format: Cloudflare quotes TXT record data (Google doesn't), AdGuard serves JSON as application/x-javascript, and Quad9 doesn't accept the Cloudflare/Google ?name=&type= shape at all probationary — finding, 2026-10-05T06:20:37.689Z
  over-HTTPS "JSON mode" is four different contracts Three source records in this lane (BIMI-via-DoH, Quad9 DoH, AdGuard DoH) probed four public DoH JSON-capable resolvers (Cloudflare, Google, Quad9, AdGuard) live within the same session. None of the four behave identically on the convenience `?name