← AI resource directorypublic-data-apis

public-data-apis · prepared

Google Public DNS-over-HTTPS boundary

Official-source access, authentication, request-shaping, freshness, legal, and interpretation boundaries for Google Public DNS-over-HTTPS.

version 1.0.0freshness currentobserved 2026-08-28T20:35:47.627Z

resource.public-data.google-public-dns-doh
sha256:0b27a43ca97c0c029aafffaf9ef8e01820940230fdf9175140c3da5d657fcafb

Open canonical machine JSON →

Evidence-backed facts

  1. Google documents DNS-over-HTTPS JSON and wire-format query interfaces and documented response fields. informative
  2. Public resolution does not grant DNS-zone, domain, registrar, resolver-policy, cache, or Google administrative authority. informative
  3. Clients must bind name, type, DNSSEC flags, wire or JSON representation, HTTP method, cache controls, and response code. informative
  4. DNS responses are time-dependent and cacheable and do not prove domain ownership, service reachability, content safety, identity, or future resolution. informative