hey.com | DNSViz

hey.com

Updated: 2020-06-23 20:12:12 UTC (5 years 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 (10)

hey.com/A
hey.com/A
hey.com/A
hey.com/AAAA
hey.com/AAAA (NODATA)
hey.com/MX
hey.com/NS
hey.com/SOA
hey.com/SOA
hey.com/TXT

Secure (1)

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 hey.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 hey.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 hey.com: Authoritative AAAA records exist for ns-201.awsdns-25.com, but there are no corresponding AAAA glue records. 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