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 (4)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 38696)
  • ./DNSKEY (alg 8, id 53148)
  • NSEC proving non-existence of sl/DS

Delegation statusDelegation status

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

NoticesNotices

Errors (25)
  • gov.sl/DNSKEY (alg 8, id 59736): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (45.83.41.38, UDP_-_EDNS0_4096_D_KN)
  • gov.sl/DNSKEY (alg 8, id 60991): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (45.83.41.38, UDP_-_EDNS0_4096_D_KN)
  • gov.sl/DS (alg 8, id 60991): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (45.83.41.38, UDP_-_EDNS0_4096_D_KN)
  • gov.sl/DS (alg 8, id 60991): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (45.83.41.38, UDP_-_EDNS0_4096_D_KN)
  • gov.sl/DS (alg 8, id 60991): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (45.83.41.38, UDP_-_EDNS0_4096_D_KN)
  • gov.sl/DS (alg 8, id 60991): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (45.83.41.38, UDP_-_EDNS0_4096_D_KN)
  • gov.sl/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (45.83.41.38, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • gov.sl/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (45.83.41.38, UDP_-_EDNS0_4096_D_KN)
  • gov.sl/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (45.83.41.38, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • gov.sl/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (45.83.41.38, UDP_-_EDNS0_4096_D_KN)
  • sl to gov.sl: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (45.83.41.38, UDP_-_EDNS0_4096_D_KN)
  • sl to gov.sl: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (45.83.41.38, UDP_-_EDNS0_4096_D_KN)
  • sl/DNSKEY (alg 7, id 1179): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (45.83.41.38, UDP_-_EDNS0_4096_D_KN)
  • sl/DNSKEY (alg 7, id 14507): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (45.83.41.38, UDP_-_EDNS0_4096_D_KN)
  • sl/DNSKEY (alg 7, id 40824): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (45.83.41.38, UDP_-_EDNS0_4096_D_KN)
  • sl/DNSKEY (alg 7, id 55940): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (45.83.41.38, UDP_-_EDNS0_4096_D_KN)
  • gov.sl/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • gov.sl/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • gov.sl/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • gov.sl/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • gov.sl/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • gov.sl/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • yza1q.ohl2v.gov.sl/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • gov.sl/CDS 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 (25)
  • 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 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/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