chk.com
Updated:
2022-08-26 14:35:56 UTC (818 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- chk.com/A
- chk.com/MX
- chk.com/NS
- chk.com/SOA
- chk.com/TXT
Secure (1)
- com/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 20826)
- NSEC3 proving non-existence of chk.com/DS
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 32298)
- com/DS (alg 8, id 30909)
Delegation status
Insecure (1)
- com to chk.com
Secure (1)
- . to com
Notices
Warnings (4)
- ./DNSKEY (alg 8, id 20326): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY (alg 8, id 20826): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
- com to chk.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): aplbctprd102.chkenergy.com See RFC 1034, Sec. 4.2.2.
- com to chk.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: ns.chkenergy.com, ns2.chkenergy.com See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
