View on GitHub

DNSViz: A DNS visualization tool

congressionaldirectory.gov

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

RRset statusRRset status

Secure (5)
  • congressionaldirectory.gov/A
  • congressionaldirectory.gov/NS
  • congressionaldirectory.gov/NSEC3PARAM
  • congressionaldirectory.gov/SOA
  • congressionaldirectory.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 14748)
  • ./DNSKEY (alg 8, id 20326)
  • congressionaldirectory.gov/DNSKEY (alg 7, id 42246)
  • congressionaldirectory.gov/DNSKEY (alg 7, id 43637)
  • congressionaldirectory.gov/DNSKEY (alg 7, id 65033)
  • congressionaldirectory.gov/DS (alg 7, id 42246)
  • congressionaldirectory.gov/DS (alg 7, id 42246)
  • gov/DNSKEY (alg 8, id 57735)
  • 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 congressionaldirectory.gov

NoticesNotices

Errors (4)
  • congressionaldirectory.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • t9yibmrxlh.congressionaldirectory.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • congressionaldirectory.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • congressionaldirectory.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (33)
  • RRSIG congressionaldirectory.gov/A alg 7, id 43637: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG congressionaldirectory.gov/A alg 7, id 65033: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG congressionaldirectory.gov/DNSKEY alg 7, id 42246: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG congressionaldirectory.gov/DNSKEY alg 7, id 42246: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG congressionaldirectory.gov/DNSKEY alg 7, id 42246: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG congressionaldirectory.gov/DNSKEY alg 7, id 43637: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG congressionaldirectory.gov/DNSKEY alg 7, id 43637: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG congressionaldirectory.gov/DNSKEY alg 7, id 43637: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG congressionaldirectory.gov/DNSKEY alg 7, id 65033: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG congressionaldirectory.gov/DNSKEY alg 7, id 65033: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG congressionaldirectory.gov/DNSKEY alg 7, id 65033: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG congressionaldirectory.gov/NS alg 7, id 43637: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG congressionaldirectory.gov/NS alg 7, id 65033: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG congressionaldirectory.gov/NSEC3PARAM alg 7, id 43637: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG congressionaldirectory.gov/NSEC3PARAM alg 7, id 65033: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG congressionaldirectory.gov/SOA alg 7, id 43637: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG congressionaldirectory.gov/SOA alg 7, id 43637: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG congressionaldirectory.gov/SOA alg 7, id 65033: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG congressionaldirectory.gov/SOA alg 7, id 65033: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG congressionaldirectory.gov/TXT alg 7, id 43637: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG congressionaldirectory.gov/TXT alg 7, id 65033: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • congressionaldirectory.gov/DS (alg 7, id 42246): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • congressionaldirectory.gov/DS (alg 7, id 42246): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • congressionaldirectory.gov/DS (alg 7, id 42246): 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.
  • congressionaldirectory.gov/DS (alg 7, id 42246): 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.
  • congressionaldirectory.gov/TXT: 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. (162.140.15.100, 162.140.254.200, UDP_-_EDNS0_4096_D_KN)
  • gov/DS (alg 8, id 7698): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (192.5.5.241, UDP_-_EDNS0_4096_D_KN)
  • gov/DS (alg 8, id 7698): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (192.5.5.241, UDP_-_EDNS0_4096_D_KN)
  • congressionaldirectory.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • congressionaldirectory.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • congressionaldirectory.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • congressionaldirectory.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • t9yibmrxlh.congressionaldirectory.gov/A 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