huntsman.com | DNSViz

huntsman.com

Updated: 2020-07-07 16:45:48 UTC (1620 days ago) Go to most recent »

DNSSEC options (hide)

|?| RR types:
|?| DNSSEC algorithms:
|?| DS digest algorithms:
|?| Denial of existence:
|?| Redundant edges:
|?| Ignore RFC 8624:
|?| Ignore RFC 9276:
|?| Multi-signer:
|?| Trust anchors:
- Root zone KSK
|?| Additional trusted keys:

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 (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 status

Insecure (1)

com to huntsman.com

Secure (1)

. to com

Notices

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 set
	Revoke bit set
	Trust anchor

See also

DNSSEC Debugger by Verisign Labs.

Download: png | svg

Warning

JavaScript is required to make the graph below interactive.

DNSSEC authentication graph