View on GitHub

DNSViz: A DNS visualization tool

rrb.gov

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

RRset statusRRset status

Insecure (5)
  • rrb.gov/A
  • rrb.gov/MX
  • rrb.gov/NS
  • rrb.gov/SOA
  • rrb.gov/TXT
Secure (1)
  • gov/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (4)
  • rrb.gov/DNSKEY (alg 7, id 22654)
  • rrb.gov/DNSKEY (alg 7, id 3533)
  • rrb.gov/DNSKEY (alg 7, id 3765)
  • rrb.gov/DNSKEY (alg 7, id 8672)
Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46594)
  • NSEC3 proving non-existence of rrb.gov/DS
  • gov/DNSKEY (alg 8, id 26665)
  • gov/DNSKEY (alg 8, id 40176)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

Insecure (1)
  • gov to rrb.gov
Secure (1)
  • . to gov

NoticesNotices

Errors (9)
  • NSEC3 proving non-existence of rrb.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of rrb.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • rrb.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (63.150.72.5)
  • rrb.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (63.150.72.5, UDP_-_NOEDNS_)
  • rrb.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (63.150.72.5, UDP_-_NOEDNS_)
  • rrb.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • rrb.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • rrb.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • 6hnf21eoys.rrb.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (24)
  • NSEC3 proving non-existence of rrb.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of rrb.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • RRSIG rrb.gov/A alg 7, id 8672: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG rrb.gov/DNSKEY alg 7, id 22654: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG rrb.gov/DNSKEY alg 7, id 22654: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG rrb.gov/DNSKEY alg 7, id 22654: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG rrb.gov/DNSKEY alg 7, id 22654: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG rrb.gov/DNSKEY alg 7, id 8672: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG rrb.gov/DNSKEY alg 7, id 8672: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG rrb.gov/DNSKEY alg 7, id 8672: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG rrb.gov/DNSKEY alg 7, id 8672: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG rrb.gov/MX alg 7, id 8672: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG rrb.gov/NS alg 7, id 8672: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG rrb.gov/SOA alg 7, id 8672: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG rrb.gov/TXT alg 7, id 8672: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • 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.
  • rrb.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • rrb.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • rrb.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • rrb.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 6hnf21eoys.rrb.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