How does the HTTPS record replace CNAME flattening at the apex domain?

With SvcPriority 0 (AliasForm), the HTTPS record instructs the client to resolve the target domain directly, providing an RFC-standard way to alias the root apex domain without non-standard CNAME flattening.

Updated: August 2026 • Verified v1.2

RFC 9460 DNS HTTPS & SVCB Record Generator

Internet & NetworkNew

Local Browser Execution: Your input is processed locally in your browser and is not sent to UTL servers.

Record = Domain TTL IN HTTPS SvcPriority TargetName [SvcParams]

Was this calculation helpful?

Understanding Your Results

Generates valid DNS HTTPS/SVCB zone file records in AliasForm (priority 0) or ServiceForm (priority > 0), formatting SvcParams for ALPN (h2,h3), port, IPv4/IPv6 hints, and providing BIND, RFC master file, and cloud provider commands.

Practical Guidance & Next Steps

Use HTTPS AliasForm (priority 0) at the apex/root domain (@) as an RFC-standard CNAME alternative. Use ServiceForm (e.g. priority 1) to instruct modern browsers to initiate HTTP/3 (QUIC) immediately without waiting for an Alt-Svc HTTP response header.

What is this?

A network engineering tool that constructs RFC 9460 Service Binding (SVCB) and HTTPS DNS resource records.

How does it work?

1. Choose AliasMode (priority 0) or ServiceMode (priority > 0). 2. Select ALPN protocols (h2, h3) and specify IPv4/IPv6 hints. 3. Copy the formatted BIND zone entry or RFC 9460 record string.

Why use it?

Enables zero-round-trip HTTP/3 QUIC connection establishment and standard apex domain aliasing.

Technical Scope & Calculation Limitations

RFC 9460 standard formatting for BIND and major DNS hosters.

Frequently Asked Questions

HTTPS (Type 65) is a specialized DNS resource record defined in RFC 9460 that allows clients to negotiate connection parameters like ALPN protocols (HTTP/2, HTTP/3), port numbers, and IP hints concurrently with DNS resolution.

Windows Desktop & Widget Options