HTTPS and SVCB records: what they are and how to check them

Tell clients how to connect to a service: protocols such as HTTP/3, ports, address hints and ECH keys.

Check with the DNS Lookup

What it is

SVCB (service binding) and HTTPS are two closely related record types defined in RFC 9460 (2023). They let a domain tell clients, in a single DNS lookup, how to connect to a service: which protocols it supports (for example HTTP/2 and HTTP/3), which port to use, which IP addresses to try, and optionally the keys for Encrypted Client Hello (ECH), which hides the visited site name from network observers.

  • HTTPS (type 65) is the version for websites, used with https:// URLs. Browsers look it up alongside A and AAAA.
  • SVCB (type 64) is the general version, for other protocols that adopt it. For example, DNS over HTTPS and DNS over TLS servers can be discovered with SVCB (RFC 9461, RFC 9462).

The two have identical syntax; only their meaning differs.

How it works

Every HTTPS or SVCB record starts with a priority number that sets its mode:

  • AliasMode (priority 0): “this service is provided by another name”. It works like a CNAME but only for this service, so unlike a CNAME it is allowed at the zone apex, next to SOA, NS and MX records.
  • ServiceMode (priority 1 or higher): “connect to this target, with these parameters”. If several ServiceMode records exist, clients prefer the lowest priority number.

When a browser that supports the HTTPS record opens https://example.com/, it asks for the HTTPS record of example.com in parallel with A and AAAA. If it finds one advertising h3, it can connect with HTTP/3 straight away instead of first connecting with HTTP/2 and learning about HTTP/3 from a response header. If the record carries an ech parameter, the browser can encrypt the sensitive parts of the TLS handshake.

A client that does not understand the record simply ignores it and connects as before. For a service on a non-default port, the record name includes the port: _8443._https.example.com.

Syntax and fields

Field Example Meaning
Name example.com. The service name. For non-default ports: _port._scheme.name.
TTL 300 Cache lifetime in seconds.
Class IN Internet.
Type HTTPS or SVCB The record type.
Priority 1 0 = AliasMode; 1 and above = ServiceMode, lower preferred.
Target . or svc.example.net. Where to connect. . in ServiceMode means the owner name itself.
Parameters alpn="h3,h2" Zero or more key=value pairs (ServiceMode only).

The most common parameters are:

Key Meaning
alpn Application protocols supported, such as h3 (HTTP/3) and h2 (HTTP/2).
no-default-alpn The default protocol for the scheme (HTTP/1.1 for HTTPS) is not supported.
port The port to connect to, if not the default.
ipv4hint, ipv6hint IP addresses the client may use to start connecting before the A/AAAA lookup completes. They are hints: A and AAAA records remain authoritative.
ech Encrypted Client Hello configuration, in base64. Defined in a separate specification.
mandatory Parameters the client must understand to use this record.

Examples

A site supporting HTTP/3 and HTTP/2 on its own addresses:

example.com.   300  IN  HTTPS  1 . alpn="h3,h2" ipv4hint=192.0.2.10 ipv6hint=2001:db8::10
example.com.   300  IN  A      192.0.2.10
example.com.   300  IN  AAAA   2001:db8::10

The apex delegated to a CDN hostname with AliasMode, keeping address records as a fallback:

example.com.   300  IN  HTTPS  0 example.cdn.example.net.
example.com.   300  IN  A      198.51.100.80

www served by a provider on a ServiceMode target:

www.example.com.   300  IN  HTTPS  1 edge.example.net. alpn="h3,h2"

A service on a non-default port:

_8443._https.api.example.com.  300  IN  HTTPS  1 api.example.com. alpn="h2" port=8443

A generic SVCB record for a DNS-over-HTTPS server (RFC 9461):

_dns.resolver.example.net.  3600  IN  SVCB  1 doh.example.net. alpn="h2,h3" dohpath="/dns-query{?dns}"

Common mistakes

  • Address hints that disagree with A and AAAA. If you move servers, update ipv4hint and ipv6hint too, or remove them. Stale hints can send clients to the old server first.
  • Advertising h3 without HTTP/3 running. Clients will try QUIC over UDP port 443 first. If it is blocked, they fall back, but the first connection is slower.
  • Removing A and AAAA records. Many clients do not use HTTPS records, and AliasMode support is limited. Keep ordinary address records.
  • Parameters on an AliasMode record. AliasMode records must not carry parameters; they are ignored or make the record invalid.
  • Stale ECH keys. ECH configurations rotate. If you manage them yourself, publish the new key before the server starts using it. In practice, most sites rely on their CDN for ECH.
  • DNS panels that do not support the type. Some providers do not yet accept HTTPS or SVCB, or only through an API. Check what your provider supports before planning around them.

How to check it

Use the DNS lookup tool with type HTTPS (or SVCB). The result shows the priority, target and every parameter in presentation format. The “all records” view of the lookup tool includes HTTPS records, so you can see them next to A, AAAA and CNAME. Many CDNs publish HTTPS records for you; looking yours up is the easiest way to find out.

  • A and AAAA: still required; hints never replace them.
  • CNAME: the older aliasing mechanism, not allowed at the apex.
  • SRV: an earlier record for locating services by host and port.

Frequently asked questions

Do I need an HTTPS record?

No, websites work without one. An HTTPS record can make the first connection faster, by announcing HTTP/3 support so the browser does not have to discover it, and it is needed for Encrypted Client Hello. Many CDNs publish HTTPS records automatically for the domains they serve.

Is the HTTPS record related to TLS certificates?

Not directly. The name refers to the https:// scheme the record describes. Certificates are still validated in the usual way; the record only tells the client how to reach the service.

Can an HTTPS record replace a CNAME at the zone apex?

In principle, yes: AliasMode (priority 0) was designed to point the apex to another name. In practice, browser support for AliasMode is still limited, so keep A and AAAA records at the apex as a fallback.

Why does my HTTPS record show '.' as the target?

In ServiceMode, a target of '.' means 'this same name'. The client connects to the owner name's own A and AAAA addresses, using the parameters listed in the record.