読み込み中...
読み込み中...
RFC 8484に基づき、HTTPS URI、configured URI Template、GET/POST、application/dns-message、client-to-server privacy境界をexact6で確認できます。
最終更新日 ・ by yuzlrin
| 項目 | 内容 |
|---|---|
| Transport | HTTPS URI scheme — A DoH request URI MUST use the https scheme; RFC 8484 does not require an explicit port 443. (§5) |
| Endpoint | Configured URI Template — The DoH client uses its configured URI Template; selecting, configuring, discovering, and updating it are outside the protocol, so an arbitrary unconfigured URI is not implied. (§3) |
| GET | One DNS request in the dns URI-template variable (base64url) — The dns variable carries one DNS query encoded with base64url for an HTTP GET request. Servers MUST implement GET; a client may choose GET for a query. (§4.1) |
| POST | One DNS query in the request body with media Content-Type — The HTTP request body carries one DNS query and identifies its media type with Content-Type. Servers MUST implement POST; a client may choose POST for a query. (§4.1) |
| Media type / response | application/dns-message support is mandatory — Clients and servers MUST support application/dns-message, the only response media type RFC 8484 defines; other negotiated response media types MAY be used. (§4.1 / §4.2 / §5.4 / §6) |
| Privacy boundary | TLS protects client-to-DoH-server transport — TLS transport integrity and confidentiality end at the DoH server, which receives the DNS query and response data; resolver trust remains. (§8 / §9) |