huntsman.com
Updated:
2021-06-07 06:24:58 UTC (1263 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset 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 status
Secure (6)
- ./DNSKEY (alg 8, id 14631)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of huntsman.com/DS
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 54714)
- com/DS (alg 8, id 30909)
Delegation status
Insecure (1)
- com to huntsman.com
Secure (1)
- . to com
Notices
Errors (4)
- com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:503:231d::2:30)
- huntsman.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2610:a1:1023::100)
- huntsman.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2610:a1:1023::100, UDP_-_NOEDNS_)
- huntsman.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2610:a1:1023::100, UDP_-_NOEDNS_)
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.
JavaScript is required to make the graph below interactive.
