View on GitHub

DNSViz: A DNS visualization tool

tn

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

RRset statusRRset status

Secure (2)
  • tn/NS
  • tn/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (5)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 61050)
  • tn/DNSKEY (alg 8, id 36171)
  • tn/DNSKEY (alg 8, id 8629)
  • tn/DS (alg 8, id 8629)

Delegation statusDelegation status

Secure (1)
  • . to tn

NoticesNotices

Errors (16)
  • tn zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (196.216.168.25)
  • tn zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (196.216.168.25)
  • tn zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (41.228.63.62, 2c0f:fab0:ffff:4:41:228:62:63)
  • tn/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2c0f:fab0:ffff:5:41:228:63:62, UDP_-_EDNS0_512_D_KN)
  • tn/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.216.168.25, 2001:43f8:120::25, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • tn/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (41.228.63.62, UDP_-_NOEDNS_)
  • tn/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.216.168.25, UDP_-_NOEDNS_)
  • tn/NS: There was an error communicating with the server over UDP (EACCES). See RFC 1035, Sec. 4.2. (2c0f:fab0:ffff:4:41:228:62:63, UDP_-_EDNS0_4096_D_KN)
  • tn/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.216.168.25, 2001:43f8:120::25, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • tn/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.216.168.25, TCP_-_NOEDNS_)
  • tn/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • tn/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • tn/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • s83f9.gdw5t.tn/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • tn/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • tn/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
  • tn/NS: 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. (2c0f:fab0:ffff:5:41:228:63:62, UDP_-_EDNS0_4096_D_KN)
  • tn/SOA: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (147.28.0.39, 2c0f:fab0:ffff:5:41:228:63:62, UDP_-_EDNS0_4096_D_KN)
  • tn/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • tn/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