Free HTTPS Record Lookup & Checker

Quick select:
Your IP:
Check the DNS record Propagation in Multi-Region Check Multi-Region
Domain Type Primary NS Responsible Person Serial Refresh Retry Expire Minimum TTL
Name Server IP Address TTL
Domain Type TTL Record Value
Trace Result
Domain Type Record Status
Domain Type Record Status
Rate this result

Check live HTTPS DNS records, TTL values, and trace the full root-to-authoritative resolution path.

HTTPS (Service Binding) Records Overview

What is a HTTPS record?

An HTTPS record (type 65) tells clients how to connect to a service over HTTPS, advertising parameters such as supported protocols (ALPN, e.g. h2/h3), IP hints, and Encrypted Client Hello (ECH) keys - before a connection is made.

Why do you need a HTTPS record?

HTTPS records let browsers connect more efficiently and securely, for example by upgrading straight to HTTP/3 or using ECH, without extra round trips. They are increasingly published by CDNs such as Cloudflare.

HTTPS record structure

An HTTPS record includes a priority, a target, and service parameters. Example: example.com. 3600 IN HTTPS 1 . alpn="h2,h3" ipv4hint="192.0.2.1"

How to create a HTTPS record?

Most managed DNS providers and CDNs generate HTTPS records automatically. To add one manually, create an HTTPS record with a priority, a target (. for the same name), and service parameters such as alpn and ipv4hint.

FAQs

An A record only provides an IP address. An HTTPS record additionally advertises how to connect (protocols, IP hints, ECH), letting clients optimize and secure the connection up front.

alpn lists the application protocols the server supports, such as h2 (HTTP/2) and h3 (HTTP/3), so clients can pick the best one immediately.

Support is growing. Modern Chrome, Firefox, and Safari query HTTPS records; clients that don't simply fall back to normal A/AAAA resolution.

HTTPS (type 65) is a specialized form of the more general SVCB (type 64) record, tailored for web (HTTPS) services.

HTTPS Record Troubleshooting & Common Fixes

Browsers fail to negotiate HTTP/3 or stall on initial connection

When an HTTPS record advertises alpn="h3,h2", modern browsers immediately attempt an opportunistic UDP handshake for HTTP/3 (QUIC) on port 443. If your hosting firewall, cloud security group, or upstream ISP blocks UDP port 443, the connection stalls until the browser's QUIC connection timer expires and falls back to TCP.

How to fix: Ensure UDP port 443 is open on your firewall and cloud network filters (e.g. AWS Security Groups, UFW, or firewalld). If your web server (Nginx or Apache) does not have HTTP/3 configured, update the ALPN parameter in your HTTPS record to alpn="h2" so clients do not waste round trips attempting failed QUIC handshakes.

TLS handshake failure: “SSL_ERROR_UNRECOGNIZED_NAME_ALERT” with ECH

Many modern CDN setups automatically publish Encrypted Client Hello (ech) parameters inside HTTPS type 65 records. If visitors use modern browsers (Chrome 117+, Firefox) connecting through an enterprise SSL-inspection appliance or local proxy that does not support ECH, the handshake is aborted with a security alert.

How to fix: If you manage origin servers behind a CDN, confirm that your edge CDN and origin proxy configurations share synchronized ECH keys. Alternatively, temporarily disable Encrypted Client Hello in your CDN edge dashboard until client network proxies in your user base support ECH handshake extensions.

Stale IP hints (ipv4hint / ipv6hint) after server or CDN migration

HTTPS records frequently bundle ipv4hint and ipv6hint parameters to eliminate extra A and AAAA lookups. If you migrate web hosting or swap CDN providers but forget to update manually published HTTPS records, client browsers will attempt connecting to your decommissioned server IP addresses first.

How to fix: Check your live HTTPS record output above for outdated IP hints. If your DNS provider supports automatic service binding, allow the system to dynamically generate hints from your apex records. If manually authored, update both the ipv4hint and ipv6hint values to match your new server addresses immediately.

DNS Info extension for Chrome is now available

Install

Install