Expert Tools

An HTTPS record (RFC 9460, a specific case of the more general SVCB record type) lets a domain tell a connecting client things about how to reach it over HTTPS before the client even opens a connection: which ALPN protocols it supports (so a client can go straight to HTTP/3 instead of negotiating up to it), IP addresses to skip an extra lookup, and an Encrypted ClientHello (ECH) configuration.

Nothing breaks without one

This record is new enough that most sites don't have one yet, and that's not a fault - a client without HTTPS-record support, or a domain without one, simply falls back to an ordinary A/AAAA lookup and the standard TLS handshake, exactly as every site has always worked. This check reports its absence as informational, not as a problem.

Alias form vs service form

A priority of 0 means AliasForm: this name has no parameters of its own and defers entirely to another name's own HTTPS record, similar in spirit to how a CNAME defers to its target. Any priority above 0 is ServiceForm, and its own parameters (if any) apply directly.

What ECH actually hides

Ordinarily, the hostname being requested is visible in plain text during the TLS handshake (in the Server Name Indication, or SNI). An Encrypted ClientHello configuration lets a supporting client encrypt that part of the handshake too, so a network observer sees only that a connection was made to the hosting provider, not which specific site behind it was requested.