The HTTPS record (and its general form, SVCB) lets a site tell browsers how to connect before they do: which protocols it speaks (HTTP/2, HTTP/3), the addresses to use, and the key for Encrypted Client Hello. It can also alias a domain’s apex, which a CNAME cannot.
| Type numbers | HTTPS 65, SVCB 64 |
| Published | 2023 |
| Usually set by | Your CDN or DNS host |
| Defined in | RFC 9460 |
Look up the HTTPS records of any name
One question to DNS, answered as it is. You can change the record type too.
What it does
A record with priority 0 is an alias: “for this name, use that one” — legal at the apex, unlike CNAME. Any other priority is service mode, carrying parameters such as alpn (protocols), ipv4hint/ipv6hint (addresses) and ech (Encrypted Client Hello keys).
Browsers that read HTTPS records can go straight to HTTP/3 and hide the site name from observers with ECH. Browsers that do not simply ignore the record.
How it is written
| Field | Meaning |
|---|---|
| Priority | 0 = alias mode; 1 or more = service mode |
| Target | The name to use (“.” = this name) |
| Parameters | alpn, port, ipv4hint, ipv6hint, ech … |
Examples
example.com. 300 IN HTTPS 1 . alpn="h3,h2" ipv4hint=203.0.113.10
Connect to example.com itself, HTTP/3 or HTTP/2 offered.
example.com. 300 IN HTTPS 0 cdn.example.net.
Alias mode: use the CDN’s record — at the apex.
Common mistakes
- Hints (ipv4hint) left pointing at old addresses after a move.
- Hand-written HTTPS records that disagree with what the CDN actually serves.
What we recommend
Let your CDN manage HTTPS records; if you publish one by hand, keep its hints in step with your A and AAAA records.
Sources
Checked on 25 September 2026 against these official sources: