Post-Quantum Authoritative DNS

How our name servers answer, encrypt and sign, and how well, measured live

All checks passing Checked 4 minutes ago: 4 name servers on 8 addresses (IPv4 and IPv6), 5 zones, 5 transports.

Scan these name servers now Check your own domain's name servers Live monitor

The short version

Name servers
4
ns1, ns2, ns3, ns4 · 8 addresses
Zones
5
5 of 5 validate from the root
Post-quantum key exchange
32/32
encrypted answers in the latest check
Service availability
100%
of 2,016 five-minute checks since 4 Nov 2026, 13:17 UTC: every transport answered
Conformance checks passed
252
across 4 servers, none failed
Queries, last 24 h
284,747
24,470 of them encrypted

Our zones (fated.org, pqpdf.com, stlweb.dev, pqcrypta.com and philibertsecurity.com) are served by 4 authoritative name servers, each on IPv4 and IPv6. They answer over UDP, TCP, DNS over TLS, DNS over QUIC and DNS over HTTPS, and every encrypted transport negotiates a post-quantum key exchange built on ML-KEM (FIPS 203), with a classical curve beside it where the client offers that hybrid.

The zones are signed by a hidden signer that no resolver can reach, and each public server checks a zone's digest and every signature before it serves a byte of it. The Post-Quantum Web Analyzer, which holds other people's name servers to RFC 9250 and RFC 8484, measures these first; a health check asks every address over every transport every five minutes; and the servers count what they answer. Every figure below comes from one of those three, with its source and time beneath it.

How it fits together

A hidden signer feeds 4 public name servers, which answer resolvers over UDP, TCP, DNS over TLS, DNS over QUIC and DNS over HTTPS Hidden signer 5 zones · DNSSEC keys reachable by no resolver ns1.pqcrypta.com 2 addresses · verifies every zone ns2.pqcrypta.com 2 addresses · verifies every zone ns3.pqcrypta.com 2 addresses · verifies every zone ns4.pqcrypta.com 2 addresses · verifies every zone signed zones, encrypted and authenticated Resolvers UDP TCP DNS over TLS DNS over QUIC DNS over HTTPS
The transports at the right are the ones the health check asks of every address.

The hidden signer holds each zone and its DNSSEC private keys. It signs every change, adds a digest of the whole zone (ZONEMD, RFC 8976) and tells each public server there is a new version. It appears in no NS record: there is no address a resolver could ask it at, so the keys never sit on a machine that answers the Internet.

The public servers hold only signed copies. Each copy reaches them encrypted and authenticated in both directions, and before serving it each server checks the zone's digest and validates every signature, refusing a zone that fails either. A server can lose nothing the zones depend on: they hold no signing keys, and a copy that fails its checks is never served.

The one change a public server passes on is a certificate challenge. When the proxy on a server answers a DNS challenge (dns-01, or dns-account-01 where the CA offers it), it publishes the TXT record as a DNS UPDATE (RFC 2136) signed with that server's own key (TSIG, RFC 8945). The server accepts only TXT records, only under the challenge names of its own host names, and only with that key; it forwards the update to the signer, which signs the record like any other change. The proxy waits until every name server answers with it, and removes it once the CA has checked it.

In the last seven days the public servers took 105 new versions of the zones and checked every copy they loaded, 120 in all, against its digest and signatures, with none refused.

Source: the servers' own logs, read every five minutes · 11 Nov 2026, 13:07 UTC

Transports

Every address answers the same zones over every transport below. "Service" is the share of the five-minute checks in which at least one name server answered over that transport, which is what a resolver, trying the next server when one is slow, depends on; the times are from every address, asked from outside the servers' own networks.

Transport Standard Port Key exchange Service Median p95 Queries, 24 h
UDP RFC 1035 53/udp clear text 100% 1.1 ms 4.8 ms 214,847
TCP RFC 7766 53/tcp clear text 100% 1.7 ms 5.9 ms 56,990
DNS over TLS RFC 7858 853/tcp X25519-MLKEM768 100% 10 ms 44 ms 6,503
DNS over QUIC RFC 9250 853, 443/udp X25519-MLKEM768, SECP384R1-MLKEM1024 100% 8.5 ms 25 ms 6,464
DNS over HTTPS RFC 8484 443/tcp, h2 + h3 SECP384R1-MLKEM1024 100% 13 ms 60 ms 11,503

Source: the health check (since 4 Nov 2026, 13:17 UTC, 2,016 runs; key exchange in the latest run), the servers' own counters (queries; DNS over HTTPS: requests) · 11 Nov 2026, 13:05 UTC

Response time by transport, per day

  • UDP
  • TCP
  • DNS over TLS
  • DNS over QUIC
  • DNS over HTTPS
010204 Nov, UDP: 0.9 ms5 Nov, UDP: 0.9 ms6 Nov, UDP: 0.9 ms7 Nov, UDP: 1.0 ms8 Nov, UDP: 1.0 ms9 Nov, UDP: 0.9 ms10 Nov, UDP: 1.5 ms11 Nov, UDP: 1.8 ms4 Nov, TCP: 1.4 ms5 Nov, TCP: 1.5 ms6 Nov, TCP: 1.5 ms7 Nov, TCP: 1.6 ms8 Nov, TCP: 1.6 ms9 Nov, TCP: 1.6 ms10 Nov, TCP: 2.0 ms11 Nov, TCP: 2.3 ms4 Nov, DNS over TLS: 9.2 ms5 Nov, DNS over TLS: 9.7 ms6 Nov, DNS over TLS: 9.4 ms7 Nov, DNS over TLS: 9.8 ms8 Nov, DNS over TLS: 9.4 ms9 Nov, DNS over TLS: 9.4 ms10 Nov, DNS over TLS: 12 ms11 Nov, DNS over TLS: 15 ms4 Nov, DNS over QUIC: 8.3 ms5 Nov, DNS over QUIC: 8.4 ms6 Nov, DNS over QUIC: 8.4 ms7 Nov, DNS over QUIC: 8.4 ms8 Nov, DNS over QUIC: 8.3 ms9 Nov, DNS over QUIC: 8.4 ms10 Nov, DNS over QUIC: 8.8 ms11 Nov, DNS over QUIC: 9.5 ms4 Nov, DNS over HTTPS: 13 ms5 Nov, DNS over HTTPS: 13 ms6 Nov, DNS over HTTPS: 13 ms7 Nov, DNS over HTTPS: 13 ms8 Nov, DNS over HTTPS: 13 ms9 Nov, DNS over HTTPS: 14 ms10 Nov, DNS over HTTPS: 14 ms11 Nov, DNS over HTTPS: 16 ms4 Nov5 Nov6 Nov7 Nov8 Nov9 Nov10 Nov11 Novms
Each day's median over every address. The encrypted transports' times include their handshake: the health check opens a new connection for every question, where a resolver keeps one open. Point at a dot for its value.

Per server

Server UDPTCPDNS over TLSDNS over QUICDNS over HTTPS
ns1.pqcrypta.com 0.3 ms 0.5 ms 12 ms 8.2 ms 13 ms
ns2.pqcrypta.com 1.4 ms 2.0 ms 8.7 ms 8.4 ms 12 ms
ns3.pqcrypta.com 1.2 ms 2.0 ms 9.9 ms 8.6 ms 15 ms
ns4.pqcrypta.com 28 ms 56 ms 117 ms 119 ms 150 ms

Median time to an answer, both addresses of each server together.

DNS over HTTPS and discovery

DNS over HTTPS (RFC 8484) is served over HTTP/2 and HTTP/3 at /dns-query, by GET and by POST, with answers padded to a fixed block size and an HTTP cache lifetime taken from their TTLs.

Each server says which encrypted transports it serves in an SVCB record at _dns.<its name> (RFC 9461), so a resolver can find them without probing:

_dns.ns1.pqcrypta.com. SVCB 1 ns1.pqcrypta.com. alpn=dot,doq,h2,h3 dohpath=/dns-query{?dns}
_dns.ns2.pqcrypta.com. SVCB 1 ns2.pqcrypta.com. alpn=dot,doq,h2,h3 dohpath=/dns-query{?dns}
_dns.ns3.pqcrypta.com. SVCB 1 ns3.pqcrypta.com. alpn=dot,doq,h2,h3 dohpath=/dns-query{?dns}
_dns.ns4.pqcrypta.com. SVCB 1 ns4.pqcrypta.com. alpn=dot,doq,h2,h3 dohpath=/dns-query{?dns}

Source: the health check (the records as the zones publish them) · 11 Nov 2026, 13:05 UTC

Post-quantum key exchange

Every encrypted transport negotiates a key exchange built on ML-KEM (FIPS 203), so a recording of the traffic cannot be decrypted later by a quantum computer. The group a client gets depends on what it offers: a client that offers ML-KEM on its own can get that, one that offers only the hybrids gets a hybrid, and a client that offers neither still gets an answer, over a classical key exchange. This is what the analyzer's client negotiated with each server.

Server Transport TLS Cipher Key exchange (code point) Certificate By address
ns1.pqcrypta.com DNS over QUIC TLSv1.3 TLS13_AES_256_GCM_SHA384 X25519MLKEM768 (0x11EC) publicly trusted names 66.179.95.51
ns1.pqcrypta.com DNS over TLS TLSv1.3 TLS13_AES_256_GCM_SHA384 X25519MLKEM768 (0x11EC) publicly trusted names 66.179.95.51
ns1.pqcrypta.com DNS over HTTPS (h2) TLSv1.3 TLS13_AES_256_GCM_SHA384 MLKEM1024 (0x0202) publicly trusted names 66.179.95.51
ns1.pqcrypta.com DNS over HTTPS (h3) TLSv1.3 TLS13_AES_256_GCM_SHA384 MLKEM1024 (0x0202) publicly trusted names 66.179.95.51
ns2.pqcrypta.com DNS over QUIC TLSv1.3 TLS13_AES_256_GCM_SHA384 X25519MLKEM768 (0x11EC) publicly trusted names 74.208.108.89
ns2.pqcrypta.com DNS over TLS TLSv1.3 TLS13_AES_256_GCM_SHA384 X25519MLKEM768 (0x11EC) publicly trusted names 74.208.108.89
ns2.pqcrypta.com DNS over HTTPS (h2) TLSv1.3 TLS13_AES_256_GCM_SHA384 MLKEM1024 (0x0202) publicly trusted names 74.208.108.89
ns2.pqcrypta.com DNS over HTTPS (h3) TLSv1.3 TLS13_AES_256_GCM_SHA384 MLKEM1024 (0x0202) publicly trusted names 74.208.108.89
ns3.pqcrypta.com DNS over QUIC TLSv1.3 TLS13_AES_256_GCM_SHA384 X25519MLKEM768 (0x11EC) publicly trusted names 209.46.123.222
ns3.pqcrypta.com DNS over TLS TLSv1.3 TLS13_AES_256_GCM_SHA384 X25519MLKEM768 (0x11EC) publicly trusted names 209.46.123.222
ns3.pqcrypta.com DNS over HTTPS (h2) TLSv1.3 TLS13_AES_256_GCM_SHA384 MLKEM1024 (0x0202) publicly trusted names 209.46.123.222
ns3.pqcrypta.com DNS over HTTPS (h3) TLSv1.3 TLS13_AES_256_GCM_SHA384 MLKEM1024 (0x0202) publicly trusted names 209.46.123.222
ns4.pqcrypta.com DNS over QUIC TLSv1.3 TLS13_AES_256_GCM_SHA384 X25519MLKEM768 (0x11EC) publicly trusted names 35.245.35.45
ns4.pqcrypta.com DNS over TLS TLSv1.3 TLS13_AES_256_GCM_SHA384 X25519MLKEM768 (0x11EC) publicly trusted names 35.245.35.45
ns4.pqcrypta.com DNS over HTTPS (h2) TLSv1.3 TLS13_AES_256_GCM_SHA384 MLKEM1024 (0x0202) publicly trusted names 35.245.35.45
ns4.pqcrypta.com DNS over HTTPS (h3) TLSv1.3 TLS13_AES_256_GCM_SHA384 MLKEM1024 (0x0202) publicly trusted names 35.245.35.45

Source: the Post-Quantum Web Analyzer's latest scan of pqcrypta.com (scan it again) · 11 Nov 2026, 12:58 UTC

Standards conformance

The Post-Quantum Web Analyzer puts every name server it meets through its conformance checks, each citing the requirement it tests: up to 73 on a server that answers every transport, 33 of them on DNS over QUIC and 14 on DNS over HTTPS. Its catalogues map RFC 9250's 47 requirements and RFC 8484's 28 to the checks that cover them. These servers are where every check was tried first. Run the scan to see every check, its evidence and the requirement behind it.

Server Pass Fail RFC 9250 met RFC 8484 met Resolver compatibility Privacy
ns1.pqcrypta.com 63 0 27 of 27 tested 13 of 13 tested 100% 100%
ns2.pqcrypta.com 63 0 27 of 27 tested 13 of 13 tested 100% 100%
ns3.pqcrypta.com 63 0 27 of 27 tested 13 of 13 tested 100% 100%
ns4.pqcrypta.com 63 0 27 of 27 tested 13 of 13 tested 100% 100%

DNS over QUIC, and 0-RTT

A returning client can send its query in the first flight, before the handshake completes (0-RTT), which RFC 9250 section 4.5 allows for a query. These servers answer queries in 0-RTT, protect it against replay, and refuse anything that changes state sent that way.

Server Full handshake Query on an open connection 8 at once 0-RTT
ns1.pqcrypta.com 19 ms p95 78 ms 0.8 ms 19 ms 2.8 ms
ns2.pqcrypta.com 40 ms p95 58 ms 1.2 ms 19 ms 4.1 ms
ns3.pqcrypta.com 26 ms p95 71 ms 0.8 ms 2.6 ms 4.3 ms
ns4.pqcrypta.com 34 ms p95 72 ms 28 ms 43 ms 58 ms

Medians from the scanner's vantage point (US East (Virginia)), so they include the network path to each server.

Source: the Post-Quantum Web Analyzer's latest scan of pqcrypta.com (scan it again) · 11 Nov 2026, 12:58 UTC

DNSSEC

Every zone is signed with ECDSA P-256 with SHA-256 (algorithm 13), the algorithm every validating resolver must support. Denial of existence is NSEC3 with no extra iterations and no salt, as RFC 9276 recommends: it does not hand out the zone's names. Signatures are valid for 30 days and renewed long before they expire; zone-signing keys roll every 90 days automatically, and each key-signing key's DS at the parent is confirmed by the signer itself. Every version of every zone also carries a ZONEMD digest (SHA384).

Zone Chain from the root KSK DS at the parent ZSK, next roll Serial Last signed Signatures valid
pqcrypta.com secure 29714 active 29714 matches 81, 17 Jan 2027 1794346321 all servers 16 hours ago 26.5 days
stlweb.dev secure 19036 active 19036 matches 28226, 17 Jan 2027 1794339781 all servers 17 hours ago 26.5 days
fated.org secure 48434 active 48434 matches 37007, 17 Jan 2027 1794339781 all servers 17 hours ago 26.5 days
philibertsecurity.com secure 40725 active 40725 matches 59614, 17 Jan 2027 1794339781 all servers 17 hours ago 26.5 days
pqpdf.com secure 17165 active 17165 matches 49742, 17 Jan 2027 1794339781 all servers 17 hours ago 26.5 days

"Chain from the root": validated from the root's trust anchor through each parent's DS. "Signatures valid": the shortest time left on any SOA or DNSKEY signature any server serves.

Source: the health check (chains, DS, serials, signatures), the signer (keys and signing) · 11 Nov 2026, 13:05 UTC

Zone timers

TimerValueGuidance
refresh 4 hours 20 minutes to 12 hours (RFC 1912 section 2.2)
retry 1 hour a fraction of refresh (RFC 1912 section 2.2)
expire 14 days 2 to 4 weeks, longer than retry and minimum (RFC 1912 section 2.2)
minimum 1 hour the negative-caching TTL: 1 to 3 hours works well (RFC 2308 section 5)

Source: the Post-Quantum Web Analyzer's latest scan of pqcrypta.com · 11 Nov 2026, 12:58 UTC

What they answer

The servers count what they answer, by transport, response code and query type, and the EDNS options and flags queries carry. Counts only: no name and no address is recorded.

  • UDP
  • TCP
  • DNS over TLS
  • DNS over QUIC
  • DNS over HTTPS
010,00020,0004 Nov 14:00 UDP: 8,133 TCP: 1,881 DNS over TLS: 216 DNS over QUIC: 204 DNS over HTTPS: 3394 Nov 15:00 UDP: 7,748 TCP: 1,826 DNS over TLS: 210 DNS over QUIC: 192 DNS over HTTPS: 3004 Nov 16:00 UDP: 8,358 TCP: 1,826 DNS over TLS: 202 DNS over QUIC: 192 DNS over HTTPS: 3004 Nov 17:00 UDP: 7,633 TCP: 1,813 DNS over TLS: 226 DNS over QUIC: 192 DNS over HTTPS: 3004 Nov 18:00 UDP: 8,274 TCP: 1,835 DNS over TLS: 226 DNS over QUIC: 192 DNS over HTTPS: 3004 Nov 19:00 UDP: 9,188 TCP: 1,802 DNS over TLS: 218 DNS over QUIC: 288 DNS over HTTPS: 3004 Nov 20:00 UDP: 8,051 TCP: 1,865 DNS over TLS: 220 DNS over QUIC: 207 DNS over HTTPS: 3394 Nov 21:00 UDP: 7,517 TCP: 1,829 DNS over TLS: 221 DNS over QUIC: 192 DNS over HTTPS: 3004 Nov 22:00 UDP: 6,373 TCP: 1,783 DNS over TLS: 203 DNS over QUIC: 193 DNS over HTTPS: 3004 Nov 23:00 UDP: 6,727 TCP: 1,789 DNS over TLS: 208 DNS over QUIC: 192 DNS over HTTPS: 3005 Nov 00:00 UDP: 6,478 TCP: 1,799 DNS over TLS: 207 DNS over QUIC: 192 DNS over HTTPS: 3005 Nov 01:00 UDP: 7,230 TCP: 1,802 DNS over TLS: 205 DNS over QUIC: 288 DNS over HTTPS: 3005 Nov 02:00 UDP: 6,556 TCP: 1,853 DNS over TLS: 210 DNS over QUIC: 204 DNS over HTTPS: 3395 Nov 03:00 UDP: 6,684 TCP: 1,806 DNS over TLS: 204 DNS over QUIC: 193 DNS over HTTPS: 3005 Nov 04:00 UDP: 8,147 TCP: 1,818 DNS over TLS: 209 DNS over QUIC: 192 DNS over HTTPS: 3005 Nov 05:00 UDP: 7,992 TCP: 1,794 DNS over TLS: 218 DNS over QUIC: 193 DNS over HTTPS: 3005 Nov 06:00 UDP: 7,573 TCP: 1,816 DNS over TLS: 211 DNS over QUIC: 192 DNS over HTTPS: 3005 Nov 07:00 UDP: 8,099 TCP: 1,801 DNS over TLS: 204 DNS over QUIC: 288 DNS over HTTPS: 3005 Nov 08:00 UDP: 13,500 TCP: 1,814 DNS over TLS: 203 DNS over QUIC: 192 DNS over HTTPS: 3005 Nov 09:00 UDP: 7,229 TCP: 1,839 DNS over TLS: 217 DNS over QUIC: 192 DNS over HTTPS: 3005 Nov 10:00 UDP: 7,128 TCP: 1,811 DNS over TLS: 213 DNS over QUIC: 192 DNS over HTTPS: 3005 Nov 11:00 UDP: 11,055 TCP: 1,803 DNS over TLS: 206 DNS over QUIC: 192 DNS over HTTPS: 3005 Nov 12:00 UDP: 6,808 TCP: 1,751 DNS over TLS: 197 DNS over QUIC: 180 DNS over HTTPS: 2615 Nov 13:00 UDP: 7,674 TCP: 1,939 DNS over TLS: 229 DNS over QUIC: 216 DNS over HTTPS: 3785 Nov 14:00 UDP: 7,705 TCP: 1,825 DNS over TLS: 213 DNS over QUIC: 288 DNS over HTTPS: 3005 Nov 15:00 UDP: 8,077 TCP: 1,805 DNS over TLS: 218 DNS over QUIC: 288 DNS over HTTPS: 3025 Nov 16:00 UDP: 7,927 TCP: 1,829 DNS over TLS: 219 DNS over QUIC: 192 DNS over HTTPS: 3005 Nov 17:00 UDP: 8,434 TCP: 1,824 DNS over TLS: 219 DNS over QUIC: 288 DNS over HTTPS: 3005 Nov 18:00 UDP: 7,087 TCP: 1,814 DNS over TLS: 207 DNS over QUIC: 192 DNS over HTTPS: 3005 Nov 19:00 UDP: 7,165 TCP: 1,792 DNS over TLS: 200 DNS over QUIC: 288 DNS over HTTPS: 3005 Nov 20:00 UDP: 6,807 TCP: 1,820 DNS over TLS: 209 DNS over QUIC: 192 DNS over HTTPS: 3005 Nov 21:00 UDP: 7,058 TCP: 1,806 DNS over TLS: 235 DNS over QUIC: 192 DNS over HTTPS: 3005 Nov 22:00 UDP: 7,790 TCP: 1,815 DNS over TLS: 221 DNS over QUIC: 384 DNS over HTTPS: 3005 Nov 23:00 UDP: 6,838 TCP: 1,803 DNS over TLS: 210 DNS over QUIC: 192 DNS over HTTPS: 3006 Nov 00:00 UDP: 12,759 TCP: 1,794 DNS over TLS: 202 DNS over QUIC: 188 DNS over HTTPS: 2876 Nov 01:00 UDP: 6,365 TCP: 1,802 DNS over TLS: 208 DNS over QUIC: 192 DNS over HTTPS: 3006 Nov 02:00 UDP: 7,343 TCP: 1,903 DNS over TLS: 220 DNS over QUIC: 204 DNS over HTTPS: 3396 Nov 03:00 UDP: 6,858 TCP: 1,877 DNS over TLS: 231 DNS over QUIC: 204 DNS over HTTPS: 3396 Nov 04:00 UDP: 8,479 TCP: 1,813 DNS over TLS: 204 DNS over QUIC: 288 DNS over HTTPS: 3006 Nov 05:00 UDP: 7,698 TCP: 1,938 DNS over TLS: 236 DNS over QUIC: 216 DNS over HTTPS: 3786 Nov 06:00 UDP: 7,704 TCP: 1,849 DNS over TLS: 206 DNS over QUIC: 192 DNS over HTTPS: 3006 Nov 07:00 UDP: 7,085 TCP: 1,810 DNS over TLS: 208 DNS over QUIC: 192 DNS over HTTPS: 3006 Nov 08:00 UDP: 7,114 TCP: 1,814 DNS over TLS: 208 DNS over QUIC: 192 DNS over HTTPS: 3006 Nov 09:00 UDP: 15,724 TCP: 1,857 DNS over TLS: 207 DNS over QUIC: 192 DNS over HTTPS: 3006 Nov 10:00 UDP: 10,029 TCP: 1,853 DNS over TLS: 208 DNS over QUIC: 288 DNS over HTTPS: 3006 Nov 11:00 UDP: 11,069 TCP: 1,800 DNS over TLS: 207 DNS over QUIC: 192 DNS over HTTPS: 3006 Nov 12:00 UDP: 8,855 TCP: 1,794 DNS over TLS: 214 DNS over QUIC: 192 DNS over HTTPS: 3006 Nov 13:00 UDP: 7,554 TCP: 1,777 DNS over TLS: 219 DNS over QUIC: 200 DNS over HTTPS: 3206 Nov 14:00 UDP: 9,497 TCP: 1,901 DNS over TLS: 235 DNS over QUIC: 204 DNS over HTTPS: 3396 Nov 15:00 UDP: 7,379 TCP: 1,837 DNS over TLS: 213 DNS over QUIC: 194 DNS over HTTPS: 3006 Nov 16:00 UDP: 10,175 TCP: 1,887 DNS over TLS: 249 DNS over QUIC: 300 DNS over HTTPS: 3396 Nov 17:00 UDP: 8,609 TCP: 1,824 DNS over TLS: 230 DNS over QUIC: 288 DNS over HTTPS: 3006 Nov 18:00 UDP: 9,424 TCP: 1,812 DNS over TLS: 286 DNS over QUIC: 192 DNS over HTTPS: 3006 Nov 19:00 UDP: 8,019 TCP: 1,943 DNS over TLS: 244 DNS over QUIC: 218 DNS over HTTPS: 3786 Nov 20:00 UDP: 7,719 TCP: 1,828 DNS over TLS: 208 DNS over QUIC: 192 DNS over HTTPS: 3006 Nov 21:00 UDP: 7,388 TCP: 2,012 DNS over TLS: 234 DNS over QUIC: 204 DNS over HTTPS: 3396 Nov 22:00 UDP: 7,770 TCP: 2,244 DNS over TLS: 218 DNS over QUIC: 210 DNS over HTTPS: 3006 Nov 23:00 UDP: 7,409 TCP: 1,822 DNS over TLS: 219 DNS over QUIC: 288 DNS over HTTPS: 3007 Nov 00:00 UDP: 7,684 TCP: 1,835 DNS over TLS: 217 DNS over QUIC: 198 DNS over HTTPS: 3397 Nov 01:00 UDP: 7,148 TCP: 1,851 DNS over TLS: 252 DNS over QUIC: 204 DNS over HTTPS: 3397 Nov 02:00 UDP: 7,398 TCP: 1,805 DNS over TLS: 215 DNS over QUIC: 192 DNS over HTTPS: 3007 Nov 03:00 UDP: 7,454 TCP: 1,791 DNS over TLS: 236 DNS over QUIC: 192 DNS over HTTPS: 3007 Nov 04:00 UDP: 8,424 TCP: 1,792 DNS over TLS: 218 DNS over QUIC: 192 DNS over HTTPS: 3007 Nov 05:00 UDP: 7,404 TCP: 1,790 DNS over TLS: 215 DNS over QUIC: 288 DNS over HTTPS: 3007 Nov 06:00 UDP: 7,208 TCP: 1,795 DNS over TLS: 219 DNS over QUIC: 192 DNS over HTTPS: 3007 Nov 07:00 UDP: 6,643 TCP: 1,789 DNS over TLS: 208 DNS over QUIC: 192 DNS over HTTPS: 3007 Nov 08:00 UDP: 7,081 TCP: 1,804 DNS over TLS: 215 DNS over QUIC: 192 DNS over HTTPS: 3007 Nov 09:00 UDP: 15,481 TCP: 1,856 DNS over TLS: 208 DNS over QUIC: 288 DNS over HTTPS: 3007 Nov 10:00 UDP: 7,626 TCP: 1,813 DNS over TLS: 211 DNS over QUIC: 192 DNS over HTTPS: 3007 Nov 11:00 UDP: 12,190 TCP: 1,796 DNS over TLS: 222 DNS over QUIC: 192 DNS over HTTPS: 3007 Nov 12:00 UDP: 8,035 TCP: 1,808 DNS over TLS: 205 DNS over QUIC: 288 DNS over HTTPS: 3007 Nov 13:00 UDP: 7,334 TCP: 1,795 DNS over TLS: 218 DNS over QUIC: 192 DNS over HTTPS: 3007 Nov 14:00 UDP: 8,124 TCP: 1,724 DNS over TLS: 237 DNS over QUIC: 184 DNS over HTTPS: 3007 Nov 15:00 UDP: 9,035 TCP: 2,965 DNS over TLS: 431 DNS over QUIC: 408 DNS over HTTPS: 1,0027 Nov 16:00 UDP: 11,890 TCP: 1,903 DNS over TLS: 226 DNS over QUIC: 300 DNS over HTTPS: 3397 Nov 17:00 UDP: 7,571 TCP: 1,861 DNS over TLS: 224 DNS over QUIC: 204 DNS over HTTPS: 3397 Nov 18:00 UDP: 8,960 TCP: 1,835 DNS over TLS: 230 DNS over QUIC: 192 DNS over HTTPS: 3007 Nov 19:00 UDP: 8,401 TCP: 1,981 DNS over TLS: 244 DNS over QUIC: 216 DNS over HTTPS: 3517 Nov 20:00 UDP: 8,332 TCP: 1,946 DNS over TLS: 239 DNS over QUIC: 312 DNS over HTTPS: 3787 Nov 21:00 UDP: 8,281 TCP: 2,054 DNS over TLS: 286 DNS over QUIC: 336 DNS over HTTPS: 4567 Nov 22:00 UDP: 7,236 TCP: 1,800 DNS over TLS: 222 DNS over QUIC: 192 DNS over HTTPS: 3007 Nov 23:00 UDP: 7,257 TCP: 1,857 DNS over TLS: 274 DNS over QUIC: 266 DNS over HTTPS: 3398 Nov 00:00 UDP: 7,753 TCP: 1,915 DNS over TLS: 237 DNS over QUIC: 192 DNS over HTTPS: 3008 Nov 01:00 UDP: 8,260 TCP: 1,799 DNS over TLS: 248 DNS over QUIC: 298 DNS over HTTPS: 3008 Nov 02:00 UDP: 7,823 TCP: 1,814 DNS over TLS: 204 DNS over QUIC: 192 DNS over HTTPS: 3008 Nov 03:00 UDP: 7,331 TCP: 1,763 DNS over TLS: 208 DNS over QUIC: 192 DNS over HTTPS: 2968 Nov 04:00 UDP: 7,759 TCP: 1,840 DNS over TLS: 204 DNS over QUIC: 192 DNS over HTTPS: 3008 Nov 05:00 UDP: 7,695 TCP: 1,903 DNS over TLS: 215 DNS over QUIC: 192 DNS over HTTPS: 3008 Nov 06:00 UDP: 8,185 TCP: 1,818 DNS over TLS: 205 DNS over QUIC: 192 DNS over HTTPS: 3008 Nov 07:00 UDP: 6,794 TCP: 1,784 DNS over TLS: 215 DNS over QUIC: 194 DNS over HTTPS: 3008 Nov 08:00 UDP: 8,833 TCP: 1,814 DNS over TLS: 216 DNS over QUIC: 288 DNS over HTTPS: 3008 Nov 09:00 UDP: 7,907 TCP: 1,762 DNS over TLS: 207 DNS over QUIC: 188 DNS over HTTPS: 2928 Nov 10:00 UDP: 14,349 TCP: 2,670 DNS over TLS: 364 DNS over QUIC: 345 DNS over HTTPS: 7758 Nov 11:00 UDP: 8,641 TCP: 1,842 DNS over TLS: 237 DNS over QUIC: 199 DNS over HTTPS: 3108 Nov 12:00 UDP: 6,769 TCP: 1,846 DNS over TLS: 232 DNS over QUIC: 192 DNS over HTTPS: 3008 Nov 13:00 UDP: 6,550 TCP: 1,771 DNS over TLS: 206 DNS over QUIC: 192 DNS over HTTPS: 2988 Nov 14:00 UDP: 10,308 TCP: 1,858 DNS over TLS: 224 DNS over QUIC: 288 DNS over HTTPS: 3028 Nov 15:00 UDP: 8,061 TCP: 1,862 DNS over TLS: 230 DNS over QUIC: 204 DNS over HTTPS: 3358 Nov 16:00 UDP: 8,815 TCP: 1,818 DNS over TLS: 218 DNS over QUIC: 192 DNS over HTTPS: 3008 Nov 17:00 UDP: 7,833 TCP: 1,798 DNS over TLS: 207 DNS over QUIC: 192 DNS over HTTPS: 3008 Nov 18:00 UDP: 7,450 TCP: 1,802 DNS over TLS: 210 DNS over QUIC: 192 DNS over HTTPS: 3008 Nov 19:00 UDP: 7,644 TCP: 1,793 DNS over TLS: 219 DNS over QUIC: 192 DNS over HTTPS: 3008 Nov 20:00 UDP: 7,283 TCP: 1,805 DNS over TLS: 214 DNS over QUIC: 288 DNS over HTTPS: 3008 Nov 21:00 UDP: 7,855 TCP: 1,829 DNS over TLS: 231 DNS over QUIC: 192 DNS over HTTPS: 3008 Nov 22:00 UDP: 6,275 TCP: 1,621 DNS over TLS: 176 DNS over QUIC: 168 DNS over HTTPS: 2498 Nov 23:00 UDP: 6,875 TCP: 1,808 DNS over TLS: 209 DNS over QUIC: 192 DNS over HTTPS: 3009 Nov 00:00 UDP: 7,838 TCP: 1,865 DNS over TLS: 227 DNS over QUIC: 204 DNS over HTTPS: 3359 Nov 01:00 UDP: 8,566 TCP: 1,827 DNS over TLS: 208 DNS over QUIC: 192 DNS over HTTPS: 3009 Nov 02:00 UDP: 9,327 TCP: 1,746 DNS over TLS: 194 DNS over QUIC: 276 DNS over HTTPS: 2579 Nov 03:00 UDP: 8,197 TCP: 1,872 DNS over TLS: 218 DNS over QUIC: 203 DNS over HTTPS: 3399 Nov 04:00 UDP: 8,003 TCP: 1,821 DNS over TLS: 212 DNS over QUIC: 192 DNS over HTTPS: 3009 Nov 05:00 UDP: 8,138 TCP: 1,735 DNS over TLS: 191 DNS over QUIC: 180 DNS over HTTPS: 2619 Nov 06:00 UDP: 8,432 TCP: 2,032 DNS over TLS: 224 DNS over QUIC: 214 DNS over HTTPS: 3399 Nov 07:00 UDP: 9,117 TCP: 1,806 DNS over TLS: 219 DNS over QUIC: 192 DNS over HTTPS: 3009 Nov 08:00 UDP: 8,462 TCP: 1,808 DNS over TLS: 206 DNS over QUIC: 288 DNS over HTTPS: 3009 Nov 09:00 UDP: 8,192 TCP: 1,777 DNS over TLS: 207 DNS over QUIC: 180 DNS over HTTPS: 2619 Nov 10:00 UDP: 7,525 TCP: 1,871 DNS over TLS: 228 DNS over QUIC: 204 DNS over HTTPS: 3399 Nov 11:00 UDP: 8,379 TCP: 1,826 DNS over TLS: 207 DNS over QUIC: 192 DNS over HTTPS: 3009 Nov 12:00 UDP: 7,970 TCP: 1,734 DNS over TLS: 212 DNS over QUIC: 180 DNS over HTTPS: 2619 Nov 13:00 UDP: 9,745 TCP: 1,884 DNS over TLS: 230 DNS over QUIC: 204 DNS over HTTPS: 3399 Nov 14:00 UDP: 9,896 TCP: 1,818 DNS over TLS: 219 DNS over QUIC: 288 DNS over HTTPS: 3009 Nov 15:00 UDP: 8,821 TCP: 1,937 DNS over TLS: 250 DNS over QUIC: 218 DNS over HTTPS: 3789 Nov 16:00 UDP: 7,465 TCP: 1,728 DNS over TLS: 207 DNS over QUIC: 180 DNS over HTTPS: 2619 Nov 17:00 UDP: 8,199 TCP: 1,872 DNS over TLS: 235 DNS over QUIC: 300 DNS over HTTPS: 3399 Nov 18:00 UDP: 7,379 TCP: 1,893 DNS over TLS: 238 DNS over QUIC: 204 DNS over HTTPS: 3399 Nov 19:00 UDP: 9,410 TCP: 2,352 DNS over TLS: 322 DNS over QUIC: 384 DNS over HTTPS: 6129 Nov 20:00 UDP: 7,593 TCP: 1,815 DNS over TLS: 207 DNS over QUIC: 192 DNS over HTTPS: 3009 Nov 21:00 UDP: 7,727 TCP: 1,873 DNS over TLS: 222 DNS over QUIC: 204 DNS over HTTPS: 3399 Nov 22:00 UDP: 7,609 TCP: 1,922 DNS over TLS: 255 DNS over QUIC: 312 DNS over HTTPS: 3789 Nov 23:00 UDP: 6,666 TCP: 1,735 DNS over TLS: 216 DNS over QUIC: 190 DNS over HTTPS: 29410 Nov 00:00 UDP: 7,838 TCP: 1,778 DNS over TLS: 216 DNS over QUIC: 184 DNS over HTTPS: 29410 Nov 01:00 UDP: 7,032 TCP: 1,851 DNS over TLS: 227 DNS over QUIC: 202 DNS over HTTPS: 34010 Nov 02:00 UDP: 8,335 TCP: 1,718 DNS over TLS: 200 DNS over QUIC: 179 DNS over HTTPS: 26210 Nov 03:00 UDP: 7,300 TCP: 1,820 DNS over TLS: 210 DNS over QUIC: 192 DNS over HTTPS: 30210 Nov 04:00 UDP: 7,332 TCP: 1,799 DNS over TLS: 215 DNS over QUIC: 192 DNS over HTTPS: 29810 Nov 05:00 UDP: 7,454 TCP: 1,858 DNS over TLS: 225 DNS over QUIC: 300 DNS over HTTPS: 33810 Nov 06:00 UDP: 7,138 TCP: 1,807 DNS over TLS: 206 DNS over QUIC: 192 DNS over HTTPS: 30310 Nov 07:00 UDP: 7,041 TCP: 1,817 DNS over TLS: 201 DNS over QUIC: 192 DNS over HTTPS: 30010 Nov 08:00 UDP: 7,082 TCP: 1,735 DNS over TLS: 227 DNS over QUIC: 180 DNS over HTTPS: 26110 Nov 09:00 UDP: 8,038 TCP: 1,828 DNS over TLS: 212 DNS over QUIC: 192 DNS over HTTPS: 30010 Nov 10:00 UDP: 6,758 TCP: 1,865 DNS over TLS: 218 DNS over QUIC: 204 DNS over HTTPS: 33510 Nov 11:00 UDP: 8,166 TCP: 1,721 DNS over TLS: 206 DNS over QUIC: 276 DNS over HTTPS: 26110 Nov 12:00 UDP: 7,629 TCP: 1,867 DNS over TLS: 234 DNS over QUIC: 208 DNS over HTTPS: 33910 Nov 13:00 UDP: 7,293 TCP: 1,853 DNS over TLS: 210 DNS over QUIC: 200 DNS over HTTPS: 31210 Nov 14:00 UDP: 7,309 TCP: 1,808 DNS over TLS: 217 DNS over QUIC: 192 DNS over HTTPS: 29610 Nov 15:00 UDP: 8,060 TCP: 1,707 DNS over TLS: 200 DNS over QUIC: 178 DNS over HTTPS: 25310 Nov 16:00 UDP: 7,889 TCP: 1,805 DNS over TLS: 206 DNS over QUIC: 192 DNS over HTTPS: 29810 Nov 17:00 UDP: 8,126 TCP: 1,889 DNS over TLS: 220 DNS over QUIC: 296 DNS over HTTPS: 33510 Nov 18:00 UDP: 7,907 TCP: 1,813 DNS over TLS: 204 DNS over QUIC: 186 DNS over HTTPS: 29810 Nov 19:00 UDP: 9,336 TCP: 2,177 DNS over TLS: 226 DNS over QUIC: 216 DNS over HTTPS: 34110 Nov 20:00 UDP: 8,986 TCP: 2,588 DNS over TLS: 285 DNS over QUIC: 273 DNS over HTTPS: 54110 Nov 21:00 UDP: 8,686 TCP: 2,574 DNS over TLS: 302 DNS over QUIC: 275 DNS over HTTPS: 55810 Nov 22:00 UDP: 7,985 TCP: 2,653 DNS over TLS: 287 DNS over QUIC: 272 DNS over HTTPS: 52110 Nov 23:00 UDP: 10,708 TCP: 2,626 DNS over TLS: 290 DNS over QUIC: 364 DNS over HTTPS: 52111 Nov 00:00 UDP: 8,293 TCP: 2,360 DNS over TLS: 253 DNS over QUIC: 238 DNS over HTTPS: 45611 Nov 01:00 UDP: 11,248 TCP: 3,365 DNS over TLS: 443 DNS over QUIC: 448 DNS over HTTPS: 1,02611 Nov 02:00 UDP: 9,846 TCP: 2,650 DNS over TLS: 303 DNS over QUIC: 413 DNS over HTTPS: 60611 Nov 03:00 UDP: 9,678 TCP: 2,616 DNS over TLS: 295 DNS over QUIC: 282 DNS over HTTPS: 56911 Nov 04:00 UDP: 9,392 TCP: 2,480 DNS over TLS: 267 DNS over QUIC: 256 DNS over HTTPS: 50511 Nov 05:00 UDP: 8,731 TCP: 2,480 DNS over TLS: 269 DNS over QUIC: 256 DNS over HTTPS: 50611 Nov 06:00 UDP: 9,340 TCP: 2,501 DNS over TLS: 279 DNS over QUIC: 256 DNS over HTTPS: 50511 Nov 07:00 UDP: 8,827 TCP: 2,489 DNS over TLS: 269 DNS over QUIC: 256 DNS over HTTPS: 50511 Nov 08:00 UDP: 9,486 TCP: 2,479 DNS over TLS: 269 DNS over QUIC: 384 DNS over HTTPS: 50511 Nov 09:00 UDP: 8,878 TCP: 2,511 DNS over TLS: 269 DNS over QUIC: 256 DNS over HTTPS: 50511 Nov 10:00 UDP: 8,585 TCP: 2,483 DNS over TLS: 276 DNS over QUIC: 256 DNS over HTTPS: 50511 Nov 11:00 UDP: 9,282 TCP: 2,489 DNS over TLS: 318 DNS over QUIC: 256 DNS over HTTPS: 50511 Nov 12:00 UDP: 10,967 TCP: 2,404 DNS over TLS: 322 DNS over QUIC: 240 DNS over HTTPS: 45311 Nov 13:00 UDP: 1,211 TCP: 444 DNS over TLS: 50 DNS over QUIC: 48 DNS over HTTPS: 1024 Nov 14:008 Nov 01:0011 Nov 13:00queries
Queries per hour, by transport, since the servers began counting (23 Oct 2026, 18:04 UTC). The counts include our own monitoring: the health check asks every address over every transport every five minutes. Point at a bar for its values.

Last 24 hours: 284,747 queries

UDP214,847
TCP56,990
DNS over TLS6,503
DNS over QUIC6,464
DNS over HTTPS11,503

Query types

SOA73,168
DNSKEY70,948
A62,613
AAAA43,606
HTTPS21,732
TXT3,929
NS3,778
MX2,144

Response codes

NOERROR246,411
BADCOOKIE28,669
NXDOMAIN7,250
REFUSED2,015
BADVERS412
FORMERR29
NOTAUTH16
NOTIMPL2

EDNS options in queries

COOKIE68,044
PADDING16,923
EDNS-CLIENT-SUBNET9,115
NSID857
other410

Flags in queries

DO208,237
TC3,452

Last 7 days: 1,677,147 queries

UDP1,302,159
TCP303,208
DNS over TLS36,086
DNS over QUIC35,931
DNS over HTTPS54,108

Query types

DNSKEY403,361
A399,700
SOA395,758
AAAA288,272
HTTPS122,088
NS21,615
TXT21,248
MX11,425

Response codes

NOERROR1,472,133
BADCOOKIE154,190
NXDOMAIN36,841
REFUSED11,802
BADVERS2,219
FORMERR165
NOTAUTH22
NOTIMPL12

EDNS options in queries

COOKIE368,084
PADDING92,490
EDNS-CLIENT-SUBNET61,814
NSID4,770
other2,217

Flags in queries

DO1,257,156
TC22,951

Source: the servers' own counters, and the requests to DNS over HTTPS (counting since 23 Oct 2026, 18:04 UTC) · 11 Nov 2026, 13:07 UTC

How it is watched

Every five minutes a health check asks every address over every transport from outside the servers' own networks, and requires a publicly trusted certificate for the server's name, one that verifies for the address too (as a client given the address rather than the name checks it), and a post-quantum key exchange on each encrypted one. It checks that every server serves the signer's serial and keys, that every signature has a safe margin left, that the answers validate through each server, and at each parent, where the zone is delegated and whether its DS matches. System Telemetry's DNS tab shows each run.

2026-11-04: 129 runs, every transport answered in 129 2026-11-05: 288 runs, every transport answered in 288 2026-11-06: 287 runs, every transport answered in 287 2026-11-07: 289 runs, every transport answered in 289 2026-11-08: 288 runs, every transport answered in 288 2026-11-09: 287 runs, every transport answered in 287 2026-11-10: 290 runs, every transport answered in 290 2026-11-11: 158 runs, every transport answered in 158
2,016 runs since 4 Nov 2026, 13:17 UTC, one cell a day; in 2,016 of them every transport was answered.

Source: the health check's history · 11 Nov 2026, 13:05 UTC

Among the name servers the scanner has measured

Every scan on the Post-Quantum Web Analyzer asks the scanned domain's name servers over the same transports. Leaving ours out, it has measured 1,510 name-server hosts: 25 answer DNS over TLS, 8 DNS over QUIC and 6 DNS over HTTPS (of 1,510 asked over it); 17 negotiated a post-quantum key exchange and 3 publish an RFC 9461 discovery record. Ours, 4 hosts: 4 DNS over TLS, 4 DNS over QUIC, 4 DNS over HTTPS, 4 post-quantum, 4 with a discovery record.

Operator Hosts DoT DoQ DoH Post-quantum Discovery
pqcrypta.com (ours) 4 4 4 4 4 4
facebook.com 4 4 0 0 4 0
ipv64.net 2 2 0 2 0 0
instagram.com 4 4 0 0 4 0
whatsapp.net 4 4 0 0 4 0
m-online.net 3 3 3 0 0 0
wikimedia.org 3 3 0 0 0 0
ojos.tv 2 2 2 2 2 0
quicojs.dev 2 2 2 2 2 2
fixt.co.il 1 1 1 0 1 1

Operators whose name servers answer at least one encrypted transport, by the name servers' domain, from the scanner's vantage point.

Source: the Post-Quantum Web Analyzer's corpus, measured since 19 Oct 2026, 00:27 UTC

Ask them yourself

With kdig (version 3.3 or later for DNS over QUIC). Add +tls-ca to check the certificate against the system's roots; kdig prints the key exchange it negotiated. Or let the scanner ask them.

# DNS over QUIC
kdig @ns1.pqcrypta.com +quic +tls-ca fated.org SOA

# DNS over QUIC on the port HTTP/3 answers
kdig @ns1.pqcrypta.com -p 443 +quic +tls-ca fated.org SOA

# DNS over TLS
kdig @ns1.pqcrypta.com +tls +tls-ca fated.org SOA

# DNS over HTTPS (HTTP/2)
kdig @ns1.pqcrypta.com +https=/dns-query +tls-ca fated.org SOA

# By address: the certificate is checked against the address
kdig @66.179.95.51 +https=/dns-query +tls-ca fated.org SOA

# The server's discovery record (RFC 9461)
kdig @ns1.pqcrypta.com _dns.ns1.pqcrypta.com SVCB

# DNSSEC, validated
delv @ns1.pqcrypta.com fated.org SOA

# The zone digest
kdig @ns1.pqcrypta.com fated.org ZONEMD +dnssec

Frequently asked questions

Why run our own authoritative name servers?

Two reasons. The zones carry HTTPS records with Encrypted Client Hello configurations whose post-quantum keys make them longer than a registrar's DNS would accept, and they rotate weekly, so the servers must take updates automatically. And the Post-Quantum Web Analyzer checks other people's name servers for DNS over QUIC, DNS over TLS and DNS over HTTPS with a post-quantum key exchange: ours are where every one of those checks is held to its standard first.

What do the zones' HTTPS records tell a browser before it connects?

Which protocols the site speaks (h3 and h2), its Encrypted Client Hello configuration, and, on pqcrypta.com's names, the key exchange groups its server takes, most preferred first (tls-supported-groups, draft-ietf-tls-key-share-prediction). With the groups, a client sends the key share the server will choose, an ML-KEM one, in its first ClientHello, rather than guessing and being asked to retry. They are measured from the server over TCP and QUIC at every publish, never typed in, and checked against it hourly; the Post-Quantum Web Analyzer holds any site's list to the groups and order it measures there. Every record also carries the addresses its name answers on (ipv4hint and ipv6hint), taken from the zone's own A and AAAA at every publish and checked against them on every health check, so a client can start connecting from the HTTPS answer alone, without waiting for the address lookups.

What is a hidden signer?

A DNS server that holds the zones and their DNSSEC private keys, signs every change, and answers nothing but zone transfers to the public servers. No resolver can reach it and it appears in no NS record, so the keys never sit on a machine that answers the Internet. The public servers hold only signed copies, verify each one before serving it, and refuse one that fails.

Is a DNSSEC signature post-quantum?

Not yet, anywhere: DNSSEC algorithms need an IANA number that every validating resolver implements, and no post-quantum signature algorithm has one. The zones are signed with the algorithm every validator must support. What is post-quantum here is the transport: DNS over TLS, QUIC and HTTPS, and the transfers between our servers, use an ML-KEM key exchange, so a recording of the traffic cannot be decrypted later by a quantum computer.

Why does a name server need post-quantum encryption at all?

Which names a resolver looks up reveals what its users are visiting, and an encrypted session recorded today can be decrypted once a large quantum computer exists. A key exchange built on ML-KEM (FIPS 203), alone or in a hybrid with a classical curve, keeps the session private.

Is 0-RTT safe for DNS?

For a query, yes: RFC 9250 allows a query in 0-RTT data, because a replayed query only repeats an answer. Anything that changes state must not be accepted that way. These servers answer queries in 0-RTT, protect it against replay, and refuse an update sent in early data with Extended DNS Error 26, Too Early.

Can I query these servers over DNS over QUIC myself?

Yes. The commands under "Ask them yourself" do it with kdig, which asks over DNS over QUIC from version 3.3, and over DNS over TLS and DNS over HTTPS. DNS over QUIC answers on UDP 853, and on 443 as well, for a network that passes UDP 443 and not 853. Any client can, too: the servers answer for their own zones only, to anyone, and refuse everything else.

How can I check my own name servers?

Scan your domain with the Post-Quantum Web Analyzer: it asks each of its name servers over DNS over QUIC, DNS over TLS and DNS over HTTPS, reports the key exchange each uses, and puts every server through the same conformance checks shown here for ours, RFC 9250's and RFC 8484's among them.

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions