View on GitHub

DNSViz: A DNS visualization tool

xd.gov

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

RRset statusRRset status

Bogus (2)
  • xd.gov/NSEC3PARAM (NODATA)
  • xd.gov/SOA
Secure (6)
  • xd.gov/A
  • xd.gov/MX
  • xd.gov/NS
  • xd.gov/NSEC3PARAM
  • xd.gov/SOA
  • xd.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (5)
  • NSEC proving non-existence of xd.gov/NSEC3PARAM
  • xd.gov/DNSKEY (alg 7, id 17670)
  • xd.gov/DNSKEY (alg 7, id 64625)
  • xd.gov/DNSKEY (alg 8, id 42511)
  • xd.gov/DNSKEY (alg 8, id 46809)
Secure (15)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26838)
  • gov/DNSKEY (alg 8, id 57735)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • xd.gov/DNSKEY (alg 7, id 12645)
  • xd.gov/DNSKEY (alg 7, id 28313)
  • xd.gov/DNSKEY (alg 7, id 45308)
  • xd.gov/DNSKEY (alg 8, id 35964)
  • xd.gov/DNSKEY (alg 8, id 39501)
  • xd.gov/DNSKEY (alg 8, id 412)
  • xd.gov/DS (alg 7, id 12645)
  • xd.gov/DS (alg 7, id 12645)
  • xd.gov/DS (alg 8, id 412)
  • xd.gov/DS (alg 8, id 412)

Delegation statusDelegation status

Secure (2)
  • . to gov
  • gov to xd.gov

NoticesNotices

Errors (14)
  • NSEC proving non-existence of xd.gov/NSEC3PARAM: The following queries resulted in an answer response, even though the bitmap in the NSEC RR indicates that the queried records don't exist: xd.gov/NSEC3PARAM See RFC 4035, Sec. 3.1.3.1.
  • NSEC proving non-existence of xd.gov/NSEC3PARAM: The following queries resulted in an answer response, even though the bitmap in the NSEC RR indicates that the queried records don't exist: xd.gov/NSEC3PARAM See RFC 4035, Sec. 3.1.3.1.
  • gov to xd.gov: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (148.129.75.22, 148.129.129.22, 2610:20:2000:101::16:0, 2610:20:2010:a04::16:0, TCP_-_EDNS0_4096_D_KN)
  • gov to xd.gov: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no DS RR matched a DNSKEY with algorithm 7 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (148.129.75.22, 148.129.129.22, 2610:20:2000:101::16:0, 2610:20:2010:a04::16:0, TCP_-_EDNS0_4096_D_KN)
  • gov to xd.gov: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (148.129.75.22, 148.129.129.22, 2610:20:2000:101::16:0, 2610:20:2010:a04::16:0, TCP_-_EDNS0_4096_D_KN)
  • xd.gov/DNSKEY (alg 7, id 12645): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (148.129.75.22, 148.129.129.22, 2610:20:2000:101::16:0, 2610:20:2010:a04::16:0, TCP_-_EDNS0_4096_D_KN)
  • xd.gov/DNSKEY (alg 7, id 45308): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (148.129.75.22, 148.129.129.22, 2610:20:2000:101::16:0, 2610:20:2010:a04::16:0, TCP_-_EDNS0_4096_D_KN)
  • xd.gov/DNSKEY (alg 7, id 64625): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (148.129.75.11, 148.129.129.31, 2610:20:2000:101::18:0, 2610:20:2010:a04::18:0, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
  • xd.gov/DNSKEY (alg 8, id 35964): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (148.129.75.22, 148.129.129.22, 2610:20:2000:101::16:0, 2610:20:2010:a04::16:0, TCP_-_EDNS0_4096_D_KN)
  • xd.gov/DNSKEY (alg 8, id 412): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (148.129.75.22, 148.129.129.22, 2610:20:2000:101::16:0, 2610:20:2010:a04::16:0, TCP_-_EDNS0_4096_D_KN)
  • xd.gov/DNSKEY (alg 8, id 46809): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (148.129.75.11, 148.129.129.31, 2610:20:2000:101::18:0, 2610:20:2010:a04::18:0, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
  • xd.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • xd.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • jhp2ba5vzk.xd.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (56)
  • RRSIG NSEC proving non-existence of xd.gov/NSEC3PARAM alg 7, id 64625: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG xd.gov/A alg 7, id 45308: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG xd.gov/A alg 7, id 64625: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG xd.gov/DNSKEY alg 7, id 12645: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG xd.gov/DNSKEY alg 7, id 12645: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG xd.gov/DNSKEY alg 7, id 12645: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG xd.gov/DNSKEY alg 7, id 12645: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG xd.gov/DNSKEY alg 7, id 12645: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG xd.gov/DNSKEY alg 7, id 12645: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG xd.gov/DNSKEY alg 7, id 17670: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG xd.gov/DNSKEY alg 7, id 17670: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG xd.gov/DNSKEY alg 7, id 17670: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG xd.gov/DNSKEY alg 7, id 17670: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG xd.gov/DNSKEY alg 7, id 45308: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG xd.gov/DNSKEY alg 7, id 45308: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG xd.gov/DNSKEY alg 7, id 45308: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG xd.gov/DNSKEY alg 7, id 45308: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG xd.gov/DNSKEY alg 7, id 45308: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG xd.gov/DNSKEY alg 7, id 45308: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG xd.gov/DNSKEY alg 7, id 64625: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG xd.gov/DNSKEY alg 7, id 64625: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG xd.gov/DNSKEY alg 7, id 64625: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG xd.gov/DNSKEY alg 7, id 64625: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG xd.gov/MX alg 7, id 45308: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG xd.gov/MX alg 7, id 64625: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG xd.gov/NS alg 7, id 45308: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG xd.gov/NS alg 7, id 64625: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG xd.gov/NSEC3PARAM alg 7, id 45308: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG xd.gov/SOA alg 7, id 45308: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG xd.gov/SOA alg 7, id 64625: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG xd.gov/SOA alg 7, id 64625: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG xd.gov/TXT alg 7, id 45308: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG xd.gov/TXT alg 7, id 64625: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • gov to xd.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): ns1e.census.gov, ns2e.census.gov See RFC 1034, Sec. 4.2.2.
  • xd.gov/DNSKEY (alg 7, id 12645): 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. (2610:20:2000:101::18:0, 2610:20:2010:a04::18:0, UDP_-_EDNS0_4096_D_KN)
  • xd.gov/DNSKEY (alg 7, id 17670): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (148.129.75.11, 148.129.129.31, 2610:20:2000:101::18:0, 2610:20:2010:a04::18:0, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
  • xd.gov/DNSKEY (alg 7, id 28313): 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. (2610:20:2000:101::18:0, 2610:20:2010:a04::18:0, UDP_-_EDNS0_4096_D_KN)
  • xd.gov/DNSKEY (alg 7, id 28313): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (148.129.75.22, 148.129.129.22, 2610:20:2000:101::16:0, 2610:20:2010:a04::16:0, TCP_-_EDNS0_4096_D_KN)
  • xd.gov/DNSKEY (alg 7, id 45308): 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. (2610:20:2000:101::18:0, 2610:20:2010:a04::18:0, UDP_-_EDNS0_4096_D_KN)
  • xd.gov/DNSKEY (alg 8, id 35964): 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. (2610:20:2000:101::18:0, 2610:20:2010:a04::18:0, UDP_-_EDNS0_4096_D_KN)
  • xd.gov/DNSKEY (alg 8, id 39501): 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. (2610:20:2000:101::18:0, 2610:20:2010:a04::18:0, UDP_-_EDNS0_4096_D_KN)
  • xd.gov/DNSKEY (alg 8, id 39501): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (148.129.75.22, 148.129.129.22, 2610:20:2000:101::16:0, 2610:20:2010:a04::16:0, TCP_-_EDNS0_4096_D_KN)
  • xd.gov/DNSKEY (alg 8, id 412): 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. (2610:20:2000:101::18:0, 2610:20:2010:a04::18:0, UDP_-_EDNS0_4096_D_KN)
  • xd.gov/DNSKEY (alg 8, id 42511): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (148.129.75.11, 148.129.129.31, 2610:20:2000:101::18:0, 2610:20:2010:a04::18:0, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
  • xd.gov/DS (alg 7, id 12645): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • xd.gov/DS (alg 7, id 12645): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • xd.gov/DS (alg 7, id 12645): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • xd.gov/DS (alg 7, id 12645): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • xd.gov/DS (alg 8, id 412): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • xd.gov/DS (alg 8, id 412): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • xd.gov/DS (alg 8, id 412): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • xd.gov/DS (alg 8, id 412): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • jhp2ba5vzk.xd.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • xd.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • xd.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • xd.gov/AAAA 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