View on GitHub

DNSViz: A DNS visualization tool

techdata.com

Updated: 2020-09-28 09:41:27 UTC (1515 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (5)
  • techdata.com/A
  • techdata.com/MX
  • techdata.com/NS
  • techdata.com/SOA
  • techdata.com/TXT
Secure (2)
  • com/SOA
  • com/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26116)
  • ./DNSKEY (alg 8, id 46594)
  • NSEC3 proving non-existence of techdata.com/DS
  • com/DNSKEY (alg 8, id 24966)
  • com/DNSKEY (alg 8, id 30909)
  • com/DS (alg 8, id 30909)

Delegation statusDelegation status

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

NoticesNotices

Errors (6)
  • techdata.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (169.153.202.46, 169.153.202.47, 2002:a999:8828::a999:8828)
  • techdata.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (169.153.202.46, 169.153.202.47, 2002:a999:8828::a999:8828, UDP_-_NOEDNS_)
  • techdata.com/DNSKEY: The response had an invalid RCODE (FORMERR). See RFC 1035, Sec. 4.1.1. (169.153.202.40, 169.153.202.41, UDP_-_EDNS0_512_D_K)
  • techdata.com/MX: The response had an invalid RCODE (FORMERR). See RFC 1035, Sec. 4.1.1. (169.153.202.40, 169.153.202.41, UDP_-_EDNS0_512_D_K)
  • techdata.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (169.153.202.46, 169.153.202.47, 2002:a999:8828::a999:8828, UDP_-_NOEDNS_)
  • techdata.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
  • com to techdata.com: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the com zone): ns4.techdata.com, ns3.techdata.com See RFC 1034, Sec. 4.2.2.
  • techdata.com/A: The response had an invalid RCODE (FORMERR) until the COOKIE EDNS option was removed. See RFC 6891, Sec. 6.1.2. (169.153.202.40, 169.153.202.41, UDP_-_EDNS0_4096_D_K)
  • techdata.com/MX: The response had an invalid RCODE (FORMERR) until the COOKIE EDNS option was removed. See RFC 6891, Sec. 6.1.2. (169.153.202.40, 169.153.202.41, UDP_-_EDNS0_4096_D_K)
  • techdata.com/NS: The response had an invalid RCODE (FORMERR) until the COOKIE EDNS option was removed. See RFC 6891, Sec. 6.1.2. (169.153.202.40, 169.153.202.41, UDP_-_EDNS0_4096_D_K)
  • techdata.com/SOA: The response had an invalid RCODE (FORMERR) until the COOKIE EDNS option was removed. See RFC 6891, Sec. 6.1.2. (169.153.202.40, 169.153.202.41, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • techdata.com/TXT: The response had an invalid RCODE (FORMERR) until the COOKIE EDNS option was removed. See RFC 6891, Sec. 6.1.2. (169.153.202.40, 169.153.202.41, UDP_-_EDNS0_4096_D_K)
  • techdata.com/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 9ol7ftjr54.techdata.com/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • techdata.com/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • techdata.com/DNSKEY 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