Get the latest tech news

RFC9460: SVCB and HTTPS DNS Records

This document specifies the "SVCB" ("Service Binding") and "HTTPS" DNS resource record (RR) types to facilitate the lookup of information needed to make connections to network services, such as for HTTP origins. SVCB records allow a service to be provided from multiple alternative endpoints, each with associated parameters (such as transport protocol configuration), and are extensible to support future uses (such as keys for encrypting the TLS ClientHello). They also enable aliasing of apex domains, which is not possible with CNAME. The HTTPS RR is a variation of SVCB for use with HTTP (see RFC 9110, "HTTP Semantics"). By providing more information to the client before it attempts to establish a connection, these records offer potential benefits to both performance and privacy.

DocumentDocument typeRFC - Proposed Standard November 2023 Report errata Select versionCompare versions RFC 9460 draft-ietf-dnsop-svcb-https-12 draft-ietf-dnsop-svcb-https-11 draft-ietf-dnsop-svcb-https-10 draft-ietf-dnsop-svcb-https-09 draft-ietf-dnsop-svcb-https-08 draft-ietf-dnsop-svcb-https-07 draft-ietf-dnsop-svcb-https-06 draft-ietf-dnsop-svcb-https-05 draft-ietf-dnsop-svcb-https-04 draft-ietf-dnsop-svcb-https-03 draft-ietf-dnsop-svcb-https-02 draft-ietf-dnsop-svcb-https-01 draft-ietf-dnsop-svcb-https-00 RFC 9460 draft-ietf-dnsop-svcb-https-12 draft-ietf-dnsop-svcb-https-11 draft-ietf-dnsop-svcb-https-10 draft-ietf-dnsop-svcb-https-09 draft-ietf-dnsop-svcb-https-08 draft-ietf-dnsop-svcb-https-07 draft-ietf-dnsop-svcb-https-06 draft-ietf-dnsop-svcb-https-05 draft-ietf-dnsop-svcb-https-04 draft-ietf-dnsop-svcb-https-03 draft-ietf-dnsop-svcb-https-02 draft-ietf-dnsop-svcb-https-01 draft-ietf-dnsop-svcb-https-00 Side-by-side Inline Authors Benjamin M. Schwartz, Mike Bishop, Erik NygrenEmail authors RFC stream Other formats Additional resources Mailing list discussion Report a datatracker bug

Get the Android app