View on GitHub

DNSViz: A DNS visualization tool

kg

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

RRset statusRRset status

Bogus (3)
  • kg/NS
  • kg/SOA
  • kg/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (2)
  • kg/DNSKEY (alg 5, id 49950)
  • kg/DNSKEY (alg 5, id 49954)
Secure (3)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 20826)
  • kg/DS (alg 8, id 45982)
Non_existent (1)
  • kg/DNSKEY (alg 8, id 45982)

Delegation statusDelegation status

Bogus (1)
  • . to kg

NoticesNotices

Errors (11)
  • . to kg: 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. (193.0.9.84, 195.38.160.36, 195.38.160.38, 2001:67c:e0::84, 2a11:a380::195:38:160:36, 2a11:a380::195:38:160:38, UDP_-_EDNS0_4096_D_KN)
  • . to kg: 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. (193.0.9.84, 195.38.160.36, 195.38.160.38, 2001:67c:e0::84, 2a11:a380::195:38:160:36, 2a11:a380::195:38:160:38, UDP_-_EDNS0_4096_D_KN)
  • kg/DNSKEY (alg 5, id 49950): The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (193.0.9.84, 195.38.160.36, 195.38.160.38, 2001:67c:e0::84, 2a11:a380::195:38:160:36, 2a11:a380::195:38:160:38, UDP_-_EDNS0_4096_D_KN)
  • kg/DNSKEY (alg 5, id 49954): The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (193.0.9.84, 195.38.160.36, 195.38.160.38, 2001:67c:e0::84, 2a11:a380::195:38:160:36, 2a11:a380::195:38:160:38, UDP_-_EDNS0_4096_D_KN)
  • kg/NS: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (193.0.9.84, 195.38.160.36, 195.38.160.38, 2001:67c:e0::84, 2a11:a380::195:38:160:36, 2a11:a380::195:38:160:38, UDP_-_EDNS0_4096_D_KN)
  • kg/SOA: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (193.0.9.84, 2001:67c:e0::84, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • kg/SOA: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (195.38.160.36, 195.38.160.38, 2a11:a380::195:38:160:36, 2a11:a380::195:38:160:38, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • kg/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • kg/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • kg/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • hitj2zd8fk.kg/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (16)
  • RRSIG kg/DNSKEY alg 5, id 49950: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kg/DNSKEY alg 5, id 49950: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kg/DNSKEY alg 5, id 49950: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kg/DNSKEY alg 5, id 49950: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kg/DNSKEY alg 5, id 49954: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kg/DNSKEY alg 5, id 49954: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kg/DNSKEY alg 5, id 49954: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kg/DNSKEY alg 5, id 49954: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kg/NS alg 5, id 49950: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kg/NS alg 5, id 49950: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kg/SOA alg 5, id 49950: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kg/SOA alg 5, id 49950: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • kg/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • kg/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • kg/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
  • hitj2zd8fk.kg/A 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