View on GitHub

DNSViz: A DNS visualization tool

rrb.gov

Updated: 2023-10-10 17:33:32 UTC (407 days ago) Update now
« 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 (6)
  • rrb.gov/A
  • rrb.gov/MX
  • rrb.gov/NS
  • rrb.gov/NSEC3PARAM
  • 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 19352)
  • rrb.gov/DNSKEY (alg 7, id 22654)
  • rrb.gov/DNSKEY (alg 7, id 31802)
  • rrb.gov/DNSKEY (alg 7, id 3765)
Secure (10)
  • ./DNSKEY (alg 8, id 11019)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46780)
  • NSEC3 proving non-existence of rrb.gov/DS
  • gov/DNSKEY (alg 8, id 10104)
  • gov/DNSKEY (alg 8, id 40921)
  • gov/DNSKEY (alg 8, id 64280)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 64280)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

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

NoticesNotices

Errors (6)
  • 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/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • k9zc8d4bo7.rrb.gov/A 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.
Warnings (21)
  • 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 31802: 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 31802: 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 31802: 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 31802: 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 31802: 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 31802: 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 31802: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG rrb.gov/NSEC3PARAM alg 7, id 31802: 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 31802: 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 31802: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • 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.
  • k9zc8d4bo7.rrb.gov/A 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.

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