View on GitHub

DNSViz: A DNS visualization tool

fortinet.com

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

RRset statusRRset status

Secure (2)
  • com/SOA
  • com/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 42351)
  • NSEC3 proving non-existence of fortinet.com/DS
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 31510)
  • com/DNSKEY (alg 8, id 58540)
  • com/DS (alg 8, id 30909)

Delegation statusDelegation status

Lame (1)
  • com to fortinet.com
Secure (1)
  • . to com

NoticesNotices

Errors (14)
  • fortinet.com zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (65.39.139.161, 96.45.36.48, 208.91.113.63)
  • fortinet.com zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (65.39.139.161, 96.45.36.48, 208.91.113.63)
  • fortinet.com zone: There was an error resolving the following NS name(s) to address(es): ns1.fortinet.com, ns2.fortinet.com, ns3.fortinet.com
  • fortinet.com/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (65.39.139.161, 96.45.36.48, 208.91.113.63, UDP_-_NOEDNS_)
  • fortinet.com/AAAA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (65.39.139.161, 96.45.36.48, 208.91.113.63, UDP_-_NOEDNS_)
  • fortinet.com/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (65.39.139.161, 96.45.36.48, 208.91.113.63, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • fortinet.com/MX: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (65.39.139.161, 96.45.36.48, 208.91.113.63, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • fortinet.com/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (65.39.139.161, 96.45.36.48, 208.91.113.63, UDP_-_NOEDNS_)
  • fortinet.com/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (65.39.139.161, 96.45.36.48, 208.91.113.63, TCP_-_NOEDNS_)
  • fortinet.com/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (65.39.139.161, 96.45.36.48, 208.91.113.63, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • fortinet.com/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (65.39.139.161, 96.45.36.48, 208.91.113.63, UDP_-_NOEDNS_)
  • nuadygsk8j.fortinet.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • fortinet.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • fortinet.com/DNSKEY has errors; 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