intel.com
Updated:
2022-05-17 21:33:10 UTC (922 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- intel.com/A
- intel.com/MX
- intel.com/NS
- intel.com/SOA
- intel.com/TXT
Secure (2)
- com/SOA
- com/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 47671)
- NSEC3 proving non-existence of intel.com/DS
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 37269)
- com/DS (alg 8, id 30909)
Delegation status
Insecure (1)
- com to intel.com
Secure (1)
- . to com
Notices
Errors (3)
- intel.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (213.190.153.35)
- intel.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (213.190.153.35, UDP_-_NOEDNS_)
- intel.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (213.190.153.35, UDP_-_NOEDNS_)
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 47671): 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 intel.com: The glue address(es) for ns2.intel.com (213.190.153.35) differed from its authoritative address(es) (134.191.190.35). See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
