key.com

Updated: 2024-11-19 19:00:40 UTC (1 day ago) Update now

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

Secure (6)

key.com/A
key.com/MX
key.com/NS
key.com/NSEC3PARAM
key.com/SOA
key.com/TXT

DNSKEY/DS/NSEC status

Secure (15)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 61050)
com/DNSKEY (alg 13, id 19718)
com/DNSKEY (alg 13, id 29942)
com/DS (alg 13, id 19718)
key.com/DNSKEY (alg 8, id 18215)
key.com/DNSKEY (alg 8, id 25112)
key.com/DNSKEY (alg 8, id 51063)
key.com/DNSKEY (alg 8, id 56070)
key.com/DS (alg 8, id 16921)
key.com/DS (alg 8, id 18215)
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 status

Secure (2)

. to com
com to key.com

Notices

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.
pqi3o.okd73.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/CDNSKEY 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.

Warnings (7)

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/DNSKEY (alg 8, id 18215): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2600:1480:800::43, UDP_-_EDNS0_4096_D_KN)
key.com/DNSKEY (alg 8, id 25112): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2600:1480:800::43, UDP_-_EDNS0_4096_D_KN)
key.com/DNSKEY (alg 8, id 51063): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2600:1480:800::43, UDP_-_EDNS0_4096_D_KN)
key.com/DNSKEY (alg 8, id 56070): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2600:1480:800::43, UDP_-_EDNS0_4096_D_KN)
key.com/TXT: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2600:1480:800::43, UDP_-_EDNS0_4096_D_KN)
key.com/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.