Guides HTTPS / SVCB
What is an HTTPS/SVCB record?
A browser can receive extra information before connecting to your website. When is an HTTPS record useful, and what should your host arrange?
A visitor opens example.com. The browser first looks up your website’s address, then connects. During that lookup, you can also give it information about your site’s connection options. A browser that supports this can take those options into account before it connects. This extra DNS setting is called an HTTPS record.
Start with an ordinary visit to example.com
A browser can look up example.com’s ordinary address and open the secure website. It does not need an HTTPS record to do this.
Now suppose your host also offers a newer connection option. An HTTPS record can announce it in advance to browsers that understand the setting. Such a browser can consider the option immediately. One example is HTTP/3, a way of carrying web traffic. Whether it is faster depends on the browser, network and server. A browser without support still needs the ordinary route.
What should the owner do?
Start with your host. Ask whether it already publishes HTTPS records and which settings fit your server. Do not add a second record yourself if the provider manages it. An absent record costs no points in the scan.
If you manage the setting yourself, copy the supplied name and value. For our example site, check example.com. Then use a suitable browser to check the actual website connection. A correctly written DNS record does not prove the server offers the announced option or that every browser uses it.
The HTTPS/SVCB names and record fields
The extra website setting is an HTTPS record, record type 65. You may also encounter SVCB: the more general framework for binding services to connection settings. SVCB is record type 64. An application has to define how it uses that framework. HTTP uses the HTTPS record. The types are not interchangeable.
An HTTPS record has a priority, a target name and optional parameters. A ServiceMode record might look like this: example.com. HTTPS 1 . alpn="h3,h2".
A priority above zero means ServiceMode. Lower values are preferred. Here the dot makes the owner name, example.com, the effective target name. alpn="h3,h2" adds HTTP/3 and HTTP/2 to the SVCB ALPN set. For HTTPS, http/1.1 also belongs to that set by default unless the record contains no-default-alpn. This lets a supporting client decide which transports are candidates before connecting.
Parameters include:
alpn: protocol identifiers such ash3andh2.ipv4hintandipv6hint: preliminary addresses a client may try. The client should still query A and/or AAAA for the target name and should prefer locally available A/AAAA answers over the hints.port: a non-standard port.ech: a binary ECHConfigList. A compatible client can use it to put the real SNI in the encrypted inner ClientHello. DNS queries, the destination IP and traffic metadata can still reveal or suggest the destination. SVCB/HTTPS is the primary DNS bootstrap for ECH. Clients can obtain ECH configuration through other mechanisms as well.
Publishing and checking in practice
- Start with the host or CDN: does the actual service support the intended protocols, and can the provider manage the record? Use its specified mode, target name and parameters.
- Check the name where clients should find the record. For
https://example.com, that is example.com. Forhttps://www.example.com, also check www.example.com. - An administrator could query
dig example.com HTTPS, for example. The sample answerexample.com. HTTPS 1 . alpn="h3,h2"publishes connection options for example.com. It does not prove that the server offers HTTP/3. - With AliasMode, follow the HTTPS bindings. Check the final targets’ A/AAAA addresses and retain a working ordinary A/AAAA and HTTPS route for the original name.
- Test the original URL with a client that supports the desired option. Check that the actual connection uses the intended protocol and that the certificate is valid for the original hostname. For ECH, the client, server and published ECH configuration must also work together.
DNS Radar checks the DNS answers and discovered bindings. It does not make a server connection or test a certificate, specific browser behaviour or actual use of HTTP/3 or ECH. Use the scan alongside your service provider’s connection checks, not as proof that every client uses the published options.
AliasMode is not ServiceMode
Only priority 0 means AliasMode: example.com. HTTPS 0 cdn.provider.net.. The client then continues the HTTPS lookup at cdn.provider.net. Parameters on an AliasMode record are ignored.
A record such as example.com. HTTPS 1 cdn.provider.net. alpn="h3,h2" is therefore not an alias. In ServiceMode it describes an alternative endpoint with connection parameters.
AliasMode can sit at the apex alongside other record types, where a CNAME cannot. It applies only to the specific SVCB-compatible record type: an HTTPS alias does not change A, AAAA or MX lookups. A working A/AAAA route at the original name therefore remains important for older clients. An SVCB-optional client that has followed at least one AliasMode record also tries the final alias target without SvcParams before falling back to an ordinary non-SVCB connection.
An alternative target name does not change the website URL. With a binding from example.com to cdn.provider.net, the client still visits example.com. The HTTP request and certificate must therefore remain valid for example.com. That is also the real server name the client uses for TLS (SNI, possibly encrypted with ECH). The target must serve that site. A certificate only for cdn.provider.net is not enough. This is not a redirect to another website URL.
Also watch the dot: HTTPS 1 . uses the record’s own name as the target, but HTTPS 0 . indicates that the service is unavailable. The latter is advisory. Clients may ignore it and try an ordinary connection without SVCB.
Further options and client-specific behaviour
Support for this extra DNS information is optional for existing HTTP protocols. The standard calls this SVCB-optional. With no record, or with no usable ServiceMode record, such a client can use the ordinary connection path. That is why the absence of HTTPS/SVCB costs no points in the scan.
The record can still be useful when:
- you want supporting clients to consider an HTTP/3 endpoint immediately. Whether that is actually faster depends on the client, network and configuration.
- you want to provide an ECHConfigList through DNS.
- you want to direct supporting clients from the apex to a CDN's HTTPS configuration.
Providers may publish HTTPS records automatically. Check their documentation or DNS control panel before adding a second, potentially conflicting record yourself.
SVCB-optional does not mean every failure leads to ordinary A/AAAA fallback. If SVCB resolution over cryptographically protected DNS fails with an authentication error, SERVFAIL, transport error or timeout, RFC 9460 says the client should stop to prevent a downgrade. An AliasMode record, or a ServiceMode record compatible with that client, can also signal an HTTP client to treat an http URL like a temporary redirect to https. Which ServiceMode records are compatible depends on the client.
Where it can go wrong
The record has to match the real service. If it advertises only a protocol the client does not support or the endpoint does not offer, that route is unusable. Fallback between transports is client behaviour and is not guaranteed.
A stale ipv4hint or ipv6hint can delay an initial connection attempt. Hints are not a replacement for current A/AAAA answers. AliasMode chains, equal priorities and mandatory parameters are also processed per client. Do not only test whether the record is syntactically valid. Make sure the target name and its A/AAAA records remain reachable as well.
For ECH, publishing the parameter alone is not enough: the client, server and the rest of the configuration must support ECH. Encrypted DNS also helps prevent the same hostname from already being visible in the DNS query.
Primary sources
Frequently asked questions
Is it bad if I have no HTTPS/SVCB record?
No. If your ordinary A/AAAA route and HTTPS service work, SVCB-optional HTTP clients can connect without this record. You lose no points for it in the scan.
What's the difference between HTTPS and SVCB?
SVCB is the general framework (record type 64), which an application can use through its own mapping. HTTPS is the HTTP mapping and has record type 65. HTTP clients that implement this standard therefore query an HTTPS record for an HTTPS origin.
Can I use this to replace a CNAME on my apex?
For supporting clients, HTTPS AliasMode can take over part of that role. Use priority 0 and no parameters. The alias applies only to HTTPS queries. Older clients keep using the original name's A/AAAA records. The URL and certificate name remain the original name for supporting clients too.
Do I have to create it myself?
Usually not. A CDN or host may publish it automatically. If you create it yourself, check that your DNS provider supports record type 65 and that the mode, target name and parameters precisely match the service.