View on GitHub

DNSViz: A DNS visualization tool

huntsman.com

« 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)
  • huntsman.com/A
  • huntsman.com/MX
  • huntsman.com/NS
  • huntsman.com/SOA
  • huntsman.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 46594)
  • ./DNSKEY (alg 8, id 48903)
  • NSEC3 proving non-existence of huntsman.com/DS
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 39844)
  • com/DS (alg 8, id 30909)

Delegation statusDelegation status

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

NoticesNotices

Errors (1)
  • com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:502:1ca1::30, 2001:503:d414::30, 2001:503:eea3::30)
Warnings (1)
  • com to huntsman.com: The following NS name(s) were found in the delegation NS RRset (i.e., in the com zone), but not in the authoritative NS RRset: ns3.domainnetwork.com See RFC 1034, Sec. 4.2.2.

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