View on GitHub

DNSViz: A DNS visualization tool

key.com

Updated: 2024-09-17 19:08:46 UTC (20 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

Secure (6)
  • key.com/A
  • key.com/MX
  • key.com/NS
  • key.com/NSEC3PARAM
  • key.com/SOA
  • key.com/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (13)
  • ./DNSKEY (alg 8, id 20038)
  • ./DNSKEY (alg 8, id 20326)
  • com/DNSKEY (alg 13, id 19718)
  • com/DNSKEY (alg 13, id 59354)
  • com/DS (alg 13, id 19718)
  • key.com/DNSKEY (alg 8, id 25112)
  • key.com/DNSKEY (alg 8, id 37104)
  • key.com/DNSKEY (alg 8, id 4540)
  • key.com/DS (alg 8, id 16921)
  • key.com/DS (alg 8, id 25112)
  • key.com/DS (alg 8, id 35975)
  • key.com/DS (alg 8, id 42121)
  • key.com/DS (alg 8, id 64315)
Non_existent (4)
  • key.com/DNSKEY (alg 8, id 16921)
  • key.com/DNSKEY (alg 8, id 35975)
  • key.com/DNSKEY (alg 8, id 42121)
  • key.com/DNSKEY (alg 8, id 64315)

Delegation statusDelegation status

Secure (2)
  • . to com
  • com to key.com

NoticesNotices

Errors (16)
  • key.com zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (150.171.10.32, 2603:1061:0:10::20)
  • key.com zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (150.171.10.32, 2603:1061:0:10::20)
  • key.com/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (150.171.10.32, 2603:1061:0:10::20, UDP_-_EDNS0_4096_D_KN)
  • key.com/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (150.171.10.32, 2603:1061:0:10::20, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • key.com/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (150.171.10.32, 2603:1061:0:10::20, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • key.com/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (150.171.10.32, 2603:1061:0:10::20, UDP_-_EDNS0_4096_D_KN)
  • key.com/NSEC3PARAM: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (150.171.10.32, 2603:1061:0:10::20, UDP_-_EDNS0_4096_D_KN)
  • key.com/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (150.171.10.32, 2603:1061:0:10::20, TCP_-_EDNS0_4096_D_N)
  • key.com/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (150.171.10.32, 2603:1061:0:10::20, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • key.com/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (150.171.10.32, 2603:1061:0:10::20, UDP_-_EDNS0_4096_D_KN)
  • key.com/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
  • 68h3b.pduf0.key.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • key.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • key.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • key.com/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • key.com/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (6)
  • com to key.com: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the com zone): ns1-32.azure-dns.com See RFC 1034, Sec. 4.2.2.
  • key.com/CDS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • key.com/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • key.com/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 68h3b.pduf0.key.com/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • key.com/CDNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.

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