washingtonpost.com | DNSViz

washingtonpost.com

Updated: 2025-06-16 06:56:13 UTC (177 days ago) Go to most recent »

DNSSEC options (hide)

|?| RR types:
|?| DNSSEC algorithms:
|?| DS digest algorithms:
|?| Denial of existence:
|?| Redundant edges:
|?| Ignore RFC 8624:
|?| Ignore RFC 9276:
|?| Multi-signer:
|?| Trust anchors:
- Root zone KSK
|?| Additional trusted keys:

Notices

DNSSEC Authentication Chain

RRset status

Insecure (10)

washingtonpost.com/A
washingtonpost.com/A
washingtonpost.com/A
washingtonpost.com/A
washingtonpost.com/MX
washingtonpost.com/NS
washingtonpost.com/SOA
washingtonpost.com/SOA
washingtonpost.com/TXT
washingtonpost.com/TXT

Secure (2)

com/SOA
com/SOA

DNSKEY/DS/NSEC status

Secure (7)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 38696)
./DNSKEY (alg 8, id 53148)
NSEC3 proving non-existence of washingtonpost.com/DS
com/DNSKEY (alg 13, id 19718)
com/DNSKEY (alg 13, id 40097)
com/DS (alg 13, id 19718)

Delegation status

Insecure (1)

com to washingtonpost.com

Secure (1)

. to com

Notices

Warnings (2)

com to washingtonpost.com: Authoritative AAAA records exist for ns-404.awsdns-50.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
washingtonpost.com/TXT: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2600:9000:5301:9400::1, 2600:9000:5307:3000::1, UDP_-_EDNS0_4096_D_KN)

DNSKEY legend

Full legend

	SEP bit set
	Revoke bit set
	Trust anchor

See also

DNSSEC Debugger by Verisign Labs.

Download: png | svg

Warning

JavaScript is required to make the graph below interactive.

DNSSEC authentication graph