View on GitHub

DNSViz: A DNS visualization tool

aksteel.com

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

RRset statusRRset status

Insecure (2)
  • aksteel.com/NS
  • aksteel.com/SOA
Secure (2)
  • com/SOA
  • com/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 20038)
  • ./DNSKEY (alg 8, id 20326)
  • NSEC3 proving non-existence of aksteel.com/DS
  • com/DNSKEY (alg 13, id 19718)
  • com/DNSKEY (alg 13, id 59354)
  • com/DS (alg 13, id 19718)

Delegation statusDelegation status

Insecure (1)
  • com to aksteel.com
Secure (1)
  • . to com

NoticesNotices

Errors (1)
  • com zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (192.48.79.30)
Warnings (2)
  • com/DNSKEY (alg 13, id 19718): 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. (192.48.79.30, UDP_-_EDNS0_4096_D_KN)
  • com/DNSKEY (alg 13, id 59354): 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. (192.48.79.30, UDP_-_EDNS0_4096_D_KN)

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