View on GitHub

DNSViz: A DNS visualization tool

ke

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

RRset statusRRset status

Bogus (3)
  • ke/NS (NODATA)
  • ke/NSEC3PARAM (NODATA)
  • ke/SOA (NODATA)
Secure (3)
  • ke/NS
  • ke/NSEC3PARAM
  • ke/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 20826)
  • ke/DNSKEY (alg 8, id 10600)
  • ke/DNSKEY (alg 8, id 30228)
  • ke/DNSKEY (alg 8, id 41201)
  • ke/DS (alg 8, id 41201)
  • ke/DS (alg 8, id 41201)

Delegation statusDelegation status

Secure (1)
  • . to ke

NoticesNotices

Errors (18)
  • ke zone: The server(s) did not respond authoritatively for the namespace. See RFC 1035, Sec. 4.1.1. (196.1.4.3, 196.1.4.130, 198.32.67.9)
  • ke zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:43f8:10:0:50c0:a8ff:feee:30)
  • ke/DNSKEY (alg 8, id 10600): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (196.1.4.3, 196.1.4.130, 198.32.67.9, UDP_-_EDNS0_4096_D_KN)
  • ke/DNSKEY (alg 8, id 30228): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (196.1.4.3, 196.1.4.130, 198.32.67.9, UDP_-_EDNS0_4096_D_KN)
  • ke/DNSKEY (alg 8, id 41201): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (196.1.4.3, 196.1.4.130, 198.32.67.9, UDP_-_EDNS0_4096_D_KN)
  • ke/NS (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (196.1.4.3, 196.1.4.130, 198.32.67.9, UDP_-_EDNS0_4096_D_KN)
  • ke/NS (NODATA): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (196.1.4.3, 196.1.4.130, 198.32.67.9, UDP_-_EDNS0_4096_D_KN)
  • ke/NS (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (196.1.4.3, 196.1.4.130, 198.32.67.9, UDP_-_EDNS0_4096_D_KN)
  • ke/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:43f8:10:0:50c0:a8ff:feee:30, UDP_-_NOEDNS_)
  • ke/NSEC3PARAM (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (196.1.4.3, 196.1.4.130, 198.32.67.9, UDP_-_EDNS0_4096_D_KN)
  • ke/NSEC3PARAM (NODATA): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (196.1.4.3, 196.1.4.130, 198.32.67.9, UDP_-_EDNS0_4096_D_KN)
  • ke/NSEC3PARAM (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (196.1.4.3, 196.1.4.130, 198.32.67.9, UDP_-_EDNS0_4096_D_KN)
  • ke/SOA (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (196.1.4.3, 196.1.4.130, 198.32.67.9, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • ke/SOA (NODATA): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (196.1.4.3, 196.1.4.130, 198.32.67.9, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • ke/SOA (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (196.1.4.3, 196.1.4.130, 198.32.67.9, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • 6tjzepcryg.ke/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • ke/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • ke/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
  • ke/DNSKEY: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (196.1.4.3, 196.1.4.130, 198.32.67.9, UDP_-_EDNS0_512_D_KN)
  • ke/DS (alg 8, id 41201): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ke/DS (alg 8, id 41201): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ke/DS (alg 8, id 41201): 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.
  • ke/DS (alg 8, id 41201): 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.
  • 6tjzepcryg.ke/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ke/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ke/CNAME 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