amd.com
Updated:
2022-08-26 14:59:34 UTC (819 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- amd.com/A
- amd.com/MX
- amd.com/NS
- amd.com/SOA
- amd.com/TXT
Secure (2)
- com/SOA
- com/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 20826)
- NSEC3 proving non-existence of amd.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 amd.com
Secure (1)
- . to com
Notices
Warnings (3)
- ./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 amd.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): a13-67.akam.net, a26-64.akam.net, a1-155.akam.net, a5-64.akam.net, a8-65.akam.net, a28-64.akam.net See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
