View on GitHub

DNSViz: A DNS visualization tool

johndeere.com

Updated: 2023-03-10 01:19:17 UTC (652 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)
  • johndeere.com/A
  • johndeere.com/MX
  • johndeere.com/NS
  • johndeere.com/SOA
  • johndeere.com/TXT
Secure (2)
  • com/SOA
  • com/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 951)
  • NSEC3 proving non-existence of johndeere.com/DS
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 36739)
  • com/DS (alg 8, id 30909)

Delegation statusDelegation status

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

NoticesNotices

Errors (3)
  • johndeere.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2620:27::200:136, 2620:27::200:137, 2620:27:0:2004::200:242)
  • johndeere.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2620:27::200:136, 2620:27::200:137, 2620:27:0:2004::200:242, UDP_-_NOEDNS_)
  • johndeere.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2620:27::200:136, 2620:27::200:137, 2620:27:0:2004::200:242, UDP_-_NOEDNS_)

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