View on GitHub

DNSViz: A DNS visualization tool

gov.rw

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

RRset statusRRset status

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

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (9)
  • ./DNSKEY (alg 8, id 11019)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • NSEC3 proving non-existence of gov.rw/DS
  • rw/DNSKEY (alg 8, id 19870)
  • rw/DNSKEY (alg 8, id 39755)
  • rw/DNSKEY (alg 8, id 64969)
  • rw/DS (alg 8, id 39755)
  • rw/DS (alg 8, id 39755)

Delegation statusDelegation status

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

NoticesNotices

Errors (5)
  • NSEC3 proving non-existence of gov.rw/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 gov.rw/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • rw zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (196.49.7.188)
  • rw/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2001:43f8:120::28, UDP_-_EDNS0_512_D_KN)
  • gov.rw/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
  • NSEC3 proving non-existence of gov.rw/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of gov.rw/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • rw to gov.rw: 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. (2001:43f8:120::28, UDP_-_EDNS0_4096_D_KN)
  • rw/DS (alg 8, id 39755): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • rw/DS (alg 8, id 39755): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • rw/DS (alg 8, id 39755): 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.
  • rw/DS (alg 8, id 39755): 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.rw/DS 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