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 (7)
  • census.gov/A
  • census.gov/AAAA
  • census.gov/MX
  • census.gov/NS
  • census.gov/NSEC3PARAM
  • census.gov/SOA
  • census.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (17)
  • ./DNSKEY (alg 8, id 14748)
  • ./DNSKEY (alg 8, id 20326)
  • census.gov/DNSKEY (alg 7, id 30680)
  • census.gov/DNSKEY (alg 7, id 44298)
  • census.gov/DNSKEY (alg 7, id 63134)
  • census.gov/DNSKEY (alg 7, id 7667)
  • census.gov/DNSKEY (alg 8, id 11455)
  • census.gov/DNSKEY (alg 8, id 18390)
  • census.gov/DNSKEY (alg 8, id 51750)
  • census.gov/DNSKEY (alg 8, id 63105)
  • census.gov/DS (alg 7, id 44298)
  • census.gov/DS (alg 7, id 44298)
  • census.gov/DS (alg 8, id 11455)
  • census.gov/DS (alg 8, id 11455)
  • gov/DNSKEY (alg 8, id 6229)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

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

NoticesNotices

Errors (2)
  • 80dr74xutk.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.
Warnings (42)
  • RRSIG census.gov/A alg 7, id 63134: 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 63134: 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 44298: 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 44298: 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 44298: 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 44298: 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 44298: 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 44298: 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 44298: 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 44298: 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 63134: 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 63134: 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 63134: 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 63134: 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 63134: 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 63134: 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 63134: 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 63134: 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 63134: 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 63134: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG census.gov/NSEC3PARAM alg 7, id 63134: 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 63134: 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 63134: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • census.gov/DNSKEY (alg 7, id 30680): 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)
  • census.gov/DNSKEY (alg 7, id 44298): 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)
  • census.gov/DNSKEY (alg 7, id 63134): 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)
  • census.gov/DNSKEY (alg 7, id 7667): 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)
  • census.gov/DNSKEY (alg 8, id 11455): 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)
  • census.gov/DNSKEY (alg 8, id 18390): 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)
  • census.gov/DNSKEY (alg 8, id 51750): 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)
  • census.gov/DNSKEY (alg 8, id 63105): 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)
  • census.gov/DS (alg 7, id 44298): 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 44298): 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 44298): 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 44298): 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 11455): 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 11455): 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 11455): 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 11455): 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.
  • 80dr74xutk.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