washingtonpost.com | DNSViz

washingtonpost.com

Updated: 2021-04-17 19:54:06 UTC (1313 days ago) Update now

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/A
washingtonpost.com/MX
washingtonpost.com/NS
washingtonpost.com/SOA
washingtonpost.com/SOA
washingtonpost.com/TXT

Secure (2)

com/SOA
com/SOA

DNSKEY/DS/NSEC status

Secure (7)

./DNSKEY (alg 8, id 14631)
./DNSKEY (alg 8, id 20326)
NSEC3 proving non-existence of washingtonpost.com/DS
com/DNSKEY (alg 8, id 30909)
com/DNSKEY (alg 8, id 54714)
com/DNSKEY (alg 8, id 58540)
com/DS (alg 8, id 30909)

Delegation status

Insecure (1)

com to washingtonpost.com

Secure (1)

. to com

Notices

Warnings (1)

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.

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