View on GitHub

DNSViz: A DNS visualization tool

congressionaldirectory.gov

Updated: 2021-12-07 18:31:40 UTC (903 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

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

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (2)
  • congressionaldirectory.gov/DNSKEY (alg 7, id 10898)
  • congressionaldirectory.gov/DNSKEY (alg 7, id 42246)
Secure (6)
  • ./DNSKEY (alg 8, id 14748)
  • ./DNSKEY (alg 8, id 20326)
  • congressionaldirectory.gov/DS (alg 13, id 2371)
  • gov/DNSKEY (alg 8, id 6229)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
Non_existent (1)
  • congressionaldirectory.gov/DNSKEY (alg 13, id 2371)

Delegation statusDelegation status

Bogus (1)
  • gov to congressionaldirectory.gov
Secure (1)
  • . to gov

NoticesNotices

Errors (9)
  • congressionaldirectory.gov/A: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. (162.140.15.100, 162.140.64.100, 162.140.252.180, 162.140.254.200, UDP_-_EDNS0_4096_D_KN)
  • congressionaldirectory.gov/DNSKEY (alg 7, id 10898): The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. (162.140.15.100, 162.140.64.100, 162.140.252.180, 162.140.254.200, UDP_-_EDNS0_4096_D_KN)
  • congressionaldirectory.gov/DNSKEY (alg 7, id 42246): The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. (162.140.15.100, 162.140.64.100, 162.140.252.180, 162.140.254.200, UDP_-_EDNS0_4096_D_KN)
  • congressionaldirectory.gov/NS: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. (162.140.15.100, 162.140.64.100, 162.140.252.180, 162.140.254.200, UDP_-_EDNS0_4096_D_KN)
  • congressionaldirectory.gov/NSEC3PARAM: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. (162.140.15.100, 162.140.64.100, 162.140.252.180, 162.140.254.200, UDP_-_EDNS0_4096_D_KN)
  • congressionaldirectory.gov/SOA: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. (162.140.15.100, 162.140.64.100, 162.140.252.180, 162.140.254.200, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • congressionaldirectory.gov/TXT: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. (162.140.15.100, 162.140.64.100, 162.140.252.180, 162.140.254.200, UDP_-_EDNS0_4096_D_KN)
  • gov to congressionaldirectory.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. (162.140.15.100, 162.140.64.100, 162.140.252.180, 162.140.254.200, UDP_-_EDNS0_4096_D_KN)
  • gov to congressionaldirectory.gov: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no DS RR matched a DNSKEY with algorithm 13 that signs the zone's DNSKEY RRset. (162.140.15.100, 162.140.64.100, 162.140.252.180, 162.140.254.200, UDP_-_EDNS0_4096_D_KN)
Warnings (11)
  • RRSIG congressionaldirectory.gov/A alg 7, id 10898: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1).
  • RRSIG congressionaldirectory.gov/DNSKEY alg 7, id 10898: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1).
  • RRSIG congressionaldirectory.gov/DNSKEY alg 7, id 10898: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1).
  • RRSIG congressionaldirectory.gov/DNSKEY alg 7, id 42246: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1).
  • RRSIG congressionaldirectory.gov/DNSKEY alg 7, id 42246: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1).
  • RRSIG congressionaldirectory.gov/NS alg 7, id 10898: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1).
  • RRSIG congressionaldirectory.gov/NSEC3PARAM alg 7, id 10898: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1).
  • RRSIG congressionaldirectory.gov/SOA alg 7, id 10898: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1).
  • RRSIG congressionaldirectory.gov/SOA alg 7, id 10898: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1).
  • RRSIG congressionaldirectory.gov/TXT alg 7, id 10898: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1).
  • gov to congressionaldirectory.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): ns2.gpo.gov, ns1.gpo.gov

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