View on GitHub

DNSViz: A DNS visualization tool

census.gov

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

RRset statusRRset status

Secure (6)
  • census.gov/A
  • census.gov/AAAA
  • census.gov/MX
  • census.gov/NS
  • census.gov/SOA
  • census.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (20)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26116)
  • census.gov/DNSKEY (alg 7, id 16613)
  • census.gov/DNSKEY (alg 7, id 35807)
  • census.gov/DNSKEY (alg 7, id 7143)
  • census.gov/DNSKEY (alg 8, id 11658)
  • census.gov/DNSKEY (alg 8, id 26416)
  • census.gov/DNSKEY (alg 8, id 54045)
  • census.gov/DS (alg 7, id 21455)
  • census.gov/DS (alg 7, id 57002)
  • census.gov/DS (alg 7, id 7143)
  • census.gov/DS (alg 7, id 7143)
  • census.gov/DS (alg 8, id 22578)
  • census.gov/DS (alg 8, id 2484)
  • census.gov/DS (alg 8, id 26416)
  • census.gov/DS (alg 8, id 26416)
  • gov/DNSKEY (alg 8, id 15489)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
Non_existent (4)
  • census.gov/DNSKEY (alg 7, id 21455)
  • census.gov/DNSKEY (alg 7, id 57002)
  • census.gov/DNSKEY (alg 8, id 22578)
  • census.gov/DNSKEY (alg 8, id 2484)

Delegation statusDelegation status

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

NoticesNotices

Errors (18)
  • census.gov zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (148.129.75.11, 148.129.129.31)
  • census.gov zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (148.129.75.11, 148.129.129.31)
  • census.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2610:20:2000:101::18:0, 2610:20:2010:a04::18:0)
  • census.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2610:20:2000:101::18:0, 2610:20:2010:a04::18:0, UDP_-_NOEDNS_)
  • census.gov/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (148.129.75.11, 148.129.129.31, UDP_-_EDNS0_4096_D_K)
  • census.gov/AAAA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (148.129.75.11, 148.129.129.31, UDP_-_EDNS0_4096_D_K)
  • census.gov/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (148.129.75.11, 148.129.129.31, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • census.gov/DS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2620:74:28::2:30, UDP_-_NOEDNS_)
  • census.gov/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (148.129.75.11, 148.129.129.31, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • census.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2610:20:2000:101::18:0, 2610:20:2010:a04::18:0, 2620:74:28::2:30, UDP_-_NOEDNS_)
  • census.gov/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (148.129.75.11, 148.129.129.31, UDP_-_EDNS0_4096_D_K)
  • census.gov/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (148.129.75.11, 148.129.129.31, TCP_-_EDNS0_4096_D)
  • census.gov/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (148.129.75.11, 148.129.129.31, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • census.gov/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (148.129.75.11, 148.129.129.31, UDP_-_EDNS0_4096_D_K)
  • j4y298sgpq.census.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • census.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • census.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • census.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (52)
  • RRSIG census.gov/A alg 7, id 35807: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG census.gov/AAAA alg 7, id 35807: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG census.gov/DNSKEY alg 7, id 35807: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG census.gov/DNSKEY alg 7, id 35807: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG census.gov/DNSKEY alg 7, id 35807: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG census.gov/DNSKEY alg 7, id 35807: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG census.gov/DNSKEY alg 7, id 35807: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG census.gov/DNSKEY alg 7, id 35807: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG census.gov/DNSKEY alg 7, id 7143: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG census.gov/DNSKEY alg 7, id 7143: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG census.gov/DNSKEY alg 7, id 7143: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG census.gov/DNSKEY alg 7, id 7143: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG census.gov/DNSKEY alg 7, id 7143: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG census.gov/DNSKEY alg 7, id 7143: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG census.gov/MX alg 7, id 35807: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG census.gov/NS alg 7, id 35807: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG census.gov/SOA alg 7, id 35807: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG census.gov/TXT alg 7, id 35807: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • census.gov/DNSKEY (alg 7, id 16613): 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:2101:16::17:0, UDP_-_EDNS0_4096_D_K)
  • census.gov/DNSKEY (alg 7, id 35807): 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:2101:16::17:0, UDP_-_EDNS0_4096_D_K)
  • census.gov/DNSKEY (alg 7, id 7143): 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:2101:16::17:0, UDP_-_EDNS0_4096_D_K)
  • census.gov/DNSKEY (alg 8, id 11658): 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:2101:16::17:0, UDP_-_EDNS0_4096_D_K)
  • census.gov/DNSKEY (alg 8, id 26416): 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:2101:16::17:0, UDP_-_EDNS0_4096_D_K)
  • census.gov/DNSKEY (alg 8, id 54045): 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:2101:16::17:0, UDP_-_EDNS0_4096_D_K)
  • census.gov/DS (alg 7, id 21455): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • census.gov/DS (alg 7, id 21455): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • census.gov/DS (alg 7, id 21455): 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.
  • census.gov/DS (alg 7, id 21455): 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.
  • census.gov/DS (alg 7, id 57002): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • census.gov/DS (alg 7, id 57002): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • census.gov/DS (alg 7, id 57002): 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.
  • census.gov/DS (alg 7, id 57002): 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.
  • census.gov/DS (alg 7, id 7143): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • census.gov/DS (alg 7, id 7143): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • census.gov/DS (alg 7, id 7143): 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.
  • census.gov/DS (alg 7, id 7143): 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.
  • census.gov/DS (alg 8, id 2484): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • census.gov/DS (alg 8, id 2484): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • census.gov/DS (alg 8, id 2484): 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.
  • census.gov/DS (alg 8, id 2484): 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.
  • census.gov/DS (alg 8, id 26416): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • census.gov/DS (alg 8, id 26416): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • census.gov/DS (alg 8, id 26416): 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.
  • census.gov/DS (alg 8, id 26416): 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.
  • gov to census.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): ns-a2e.census.gov, hq-inf-edns01.tco.census.gov, ns-b2e.census.gov, bcc-inf-edns01.tco.census.gov See RFC 1034, Sec. 4.2.2.
  • gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov/DS (alg 8, id 7698): 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.
  • gov/DS (alg 8, id 7698): 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.
  • j4y298sgpq.census.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • census.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • census.gov/DNSKEY 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