WEB
ECH Checker
Inspect Encrypted Client Hello deployment
Input
Terminal
About ECH Checker
Verify SNI Encryption on the Wire
Encrypted Client Hello (ECH) hides the Server Name Indication during the TLS handshake. Without ECH every TLS 1.3 connection leaks the destination hostname in plaintext, regardless of HTTPS or DoH. ECH wraps the inner Client Hello with HPKE so on-path observers see only the cover (public_name) of the host. The guide to Encrypted Client Hello covers how the inner and outer halves fit together, why ESNI was abandoned, and how to turn ECH on in Firefox and Chrome.
The ECH key itself is published in DNS. If those DNS queries travel in plaintext, the name you are about to visit leaks there instead, which is why ECH is usually paired with encrypted DNS.
What the tool reads
This tool runs a DNS HTTPS resource record lookup (RFC 9460) for the input domain, extracts the ech= SvcParam, then parses the ECHConfigList per RFC 9849.
For each ECHConfig in the list the tool surfaces:
- Version — 0xfe0d, the value RFC 9849 defines and every shipping browser implements
- config_id — short identifier the client echoes during the handshake
- KEM — HPKE Key Encapsulation Mechanism (DHKEM X25519 by default on Cloudflare)
- Public key — server's HPKE public key, as raw hex
- Cipher suites — KDF and AEAD combinations the server accepts
- maximum_name_length — padding hint for inner Client Hello length leakage
- public_name — cover hostname that appears unencrypted on the wire
- Extensions — any future ECHConfig extensions present
How to use ECH Checker
- Enter the domainJust
example.com. No protocol prefix, no port. The tool resolves the apex or subdomain you give it. - Hit Check ECH DeploymentA DNS HTTPS RR (TYPE65) query runs from the packet.guru server against 1.1.1.1. The raw resource record is returned alongside the parsed ECHConfigList.
- Read the reportStatus pill tells you deployed, RR present without ECH, or no RR at all. Each ECHConfig block shows the HPKE parameters and public_name (the cover hostname that observers actually see).
- Cross-check the wireOpen Firefox 119+ with DoH on, visit the domain, and inspect the TLS handshake in DevTools or Wireshark. Inner Client Hello fields should be encrypted. Cross-reference with SSL Checker for the certificate that ECH protects and DNS Lookup to confirm the HTTPS RR.
Frequently Asked Questions
- It queries the HTTPS resource record (DNS type 65) for the domain, looks for an ech= SvcParam, base64-decodes it, then parses the binary ECHConfigList per RFC 9849. You get one block per ECHConfig in the list with version, HPKE KEM, public key, cipher suites, public_name, and any extensions.
- The domain advertises HTTPS service binding (alpn, ipv4hint, ipv6hint) but has not published an ECHConfigList. SNI is still visible in plaintext on this host. On Cloudflare-proxied zones the ech= value is added automatically once the ECH setting is on, which is the default on the Free plan. On self-hosted nginx you need OpenSSL 3.5+ ECH support plus an ECHConfigList generator and the public_name aligned to a real cover hostname.
- Cloudflare publishes a shared cover so every ECH-enabled customer points the unencrypted SNI to cloudflare-ech.com. Observers on the path see a generic name that does not identify which Cloudflare customer the client is actually connecting to. The real destination only exists inside the encrypted inner Client Hello.
- The lookup is a public DNS query for the HTTPS RR. The tool resolves against 1.1.1.1 over UDP. The request is logged for rate limiting only and do not retain the looked-up domain or response.
- Free, no signup, rate-limited per IP. Lookup timeout 8 seconds. Private IPs and reserved names refused for security.