View on GitHub

DNSViz: A DNS visualization tool

gov.sl

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

RRset statusRRset status

Insecure (4)
  • gov.sl/MX
  • gov.sl/NS
  • gov.sl/SOA
  • gov.sl/TXT
Secure (1)
  • ./SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (8)
  • gov.sl/DNSKEY (alg 8, id 59736)
  • gov.sl/DNSKEY (alg 8, id 60991)
  • gov.sl/DS (alg 8, id 60991)
  • gov.sl/DS (alg 8, id 60991)
  • sl/DNSKEY (alg 7, id 1179)
  • sl/DNSKEY (alg 7, id 14507)
  • sl/DNSKEY (alg 7, id 40824)
  • sl/DNSKEY (alg 7, id 55940)
Secure (3)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 20826)
  • NSEC proving non-existence of sl/DS

Delegation statusDelegation status

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

NoticesNotices

Errors (3)
  • sl/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (51.195.14.249, UDP_-_EDNS0_512_D_KN)
  • 9yzbn0tph3.gov.sl/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • gov.sl/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (37)
  • RRSIG gov.sl/DS alg 7, id 14507: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.sl/DS alg 7, id 14507: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.sl/DS alg 7, id 55940: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.sl/DS alg 7, id 55940: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.sl/SOA alg 8, id 59736: The value of the Signature Inception field of the RRSIG RR (2022-08-26 14:30:07+00:00) is within possible clock skew range (25 seconds) of the current time (2022-08-26 14:30:32+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG gov.sl/TXT alg 8, id 59736: The value of the Signature Inception field of the RRSIG RR (2022-08-26 14:30:07+00:00) is within possible clock skew range (25 seconds) of the current time (2022-08-26 14:30:32+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG sl/DNSKEY alg 7, id 1179: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sl/DNSKEY alg 7, id 1179: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sl/DNSKEY alg 7, id 1179: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sl/DNSKEY alg 7, id 1179: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sl/DNSKEY alg 7, id 14507: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sl/DNSKEY alg 7, id 14507: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sl/DNSKEY alg 7, id 14507: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sl/DNSKEY alg 7, id 14507: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sl/DNSKEY alg 7, id 40824: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sl/DNSKEY alg 7, id 40824: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sl/DNSKEY alg 7, id 40824: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sl/DNSKEY alg 7, id 40824: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sl/DNSKEY alg 7, id 55940: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sl/DNSKEY alg 7, id 55940: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sl/DNSKEY alg 7, id 55940: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sl/DNSKEY alg 7, id 55940: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • gov.sl/DS (alg 8, id 60991): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov.sl/DS (alg 8, id 60991): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov.sl/DS (alg 8, id 60991): 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.sl/DS (alg 8, id 60991): 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.sl/TXT: 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. (51.195.14.249, UDP_-_EDNS0_4096_D_KN)
  • sl/DNSKEY (alg 7, id 1179): 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. (51.195.14.249, UDP_-_EDNS0_4096_D_KN)
  • sl/DNSKEY (alg 7, id 14507): 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. (51.195.14.249, UDP_-_EDNS0_4096_D_KN)
  • sl/DNSKEY (alg 7, id 40824): 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. (51.195.14.249, UDP_-_EDNS0_4096_D_KN)
  • sl/DNSKEY (alg 7, id 55940): 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. (51.195.14.249, UDP_-_EDNS0_4096_D_KN)
  • gov.sl/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.sl/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.sl/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.sl/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 9yzbn0tph3.gov.sl/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.sl/NSEC3PARAM 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