gov.rw
Updated:
2023-01-04 14:32:49 UTC (736 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset 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 status
Secure (9)
- ./DNSKEY (alg 8, id 18733)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 951)
- NSEC3 proving non-existence of gov.rw/DS
- rw/DNSKEY (alg 8, id 31126)
- rw/DNSKEY (alg 8, id 36820)
- rw/DNSKEY (alg 8, id 39755)
- rw/DS (alg 8, id 39755)
- rw/DS (alg 8, id 39755)
Delegation status
Insecure (1)
- rw to gov.rw
Secure (1)
- . to rw
Notices
Errors (18)
- 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.
- gov.rw/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.49.7.186, UDP_-_NOEDNS_)
- gov.rw/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.49.7.186, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
- gov.rw/DS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.49.7.186, UDP_-_NOEDNS_)
- gov.rw/MX: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.49.7.186, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
- gov.rw/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.49.7.186, UDP_-_NOEDNS_)
- gov.rw/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.49.7.186, TCP_-_NOEDNS_)
- gov.rw/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.49.7.186, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
- gov.rw/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.49.7.186, UDP_-_NOEDNS_)
- rw zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (196.49.7.186)
- rw/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.49.7.186, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
- 8smfr9bpde.gov.rw/A has errors; select the "Denial of existence" DNSSEC option to see them.
- gov.rw/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- gov.rw/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- gov.rw/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- gov.rw/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
- gov.rw/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
- . to rw: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the . zone): ns2.ricta.org.rw See RFC 1034, Sec. 4.2.2.
- 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/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.
JavaScript is required to make the graph below interactive.
