View on GitHub

DNSViz: A DNS visualization tool

whitehouse.gov

DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (6)
  • whitehouse.gov/A
  • whitehouse.gov/AAAA
  • whitehouse.gov/NS
  • whitehouse.gov/NSEC3PARAM
  • whitehouse.gov/SOA
  • whitehouse.gov/TXT
Secure (1)
  • gov/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (4)
  • whitehouse.gov/DNSKEY (alg 7, id 11210)
  • whitehouse.gov/DNSKEY (alg 7, id 24048)
  • whitehouse.gov/DNSKEY (alg 7, id 3093)
  • whitehouse.gov/DNSKEY (alg 7, id 49620)
Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 9799)
  • NSEC3 proving non-existence of whitehouse.gov/DS
  • gov/DNSKEY (alg 8, id 7030)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

Insecure (1)
  • gov to whitehouse.gov
Secure (1)
  • . to gov

NoticesNotices

Errors (6)
  • NSEC3 proving non-existence of whitehouse.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of whitehouse.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • whitehouse.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • whitehouse.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • zgh5kru0vc.whitehouse.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • whitehouse.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (24)
  • NSEC3 proving non-existence of whitehouse.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of whitehouse.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • RRSIG whitehouse.gov/A alg 7, id 49620: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG whitehouse.gov/AAAA alg 7, id 49620: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG whitehouse.gov/DNSKEY alg 7, id 24048: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG whitehouse.gov/DNSKEY alg 7, id 24048: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG whitehouse.gov/DNSKEY alg 7, id 24048: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG whitehouse.gov/DNSKEY alg 7, id 24048: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG whitehouse.gov/DNSKEY alg 7, id 3093: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG whitehouse.gov/DNSKEY alg 7, id 3093: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG whitehouse.gov/DNSKEY alg 7, id 3093: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG whitehouse.gov/DNSKEY alg 7, id 3093: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG whitehouse.gov/NS alg 7, id 49620: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG whitehouse.gov/NSEC3PARAM alg 7, id 49620: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG whitehouse.gov/SOA alg 7, id 49620: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG whitehouse.gov/TXT alg 7, id 49620: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • gov to whitehouse.gov: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the gov zone): usw6.akam.net, usw5.akam.net See RFC 1034, Sec. 4.2.2.
  • gov/DS (alg 8, id 7698): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
  • gov/DS (alg 8, id 7698): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
  • whitehouse.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • whitehouse.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • whitehouse.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • zgh5kru0vc.whitehouse.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • whitehouse.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph