outlook-com.olc.protection.outlook.com
Updated:
2023-03-20 14:35:27 UTC (647 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (11)
- olc.protection.outlook.com/SOA
- olc.protection.outlook.com/SOA
- outlook-com.olc.protection.outlook.com/A
- outlook-com.olc.protection.outlook.com/A
- outlook-com.olc.protection.outlook.com/A
- outlook-com.olc.protection.outlook.com/A
- outlook-com.olc.protection.outlook.com/A
- outlook.com/SOA
- outlook.com/SOA
- outlook.com/SOA
- outlook.com/SOA
Secure (1)
- com/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 951)
- NSEC3 proving non-existence of outlook.com/DS
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 36739)
- com/DS (alg 8, id 30909)
Delegation status
Insecure (3)
- com to outlook.com
- outlook.com to protection.outlook.com
- protection.outlook.com to olc.protection.outlook.com
Secure (1)
- . to com
Notices
Errors (2)
- protection.outlook.com to olc.protection.outlook.com: An SOA RR with owner name (olc.protection.outlook.com) not matching the zone name (protection.outlook.com) was returned with the NODATA response. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (104.47.2.8, 104.47.38.8, 104.47.40.8, 104.47.44.8, UDP_-_EDNS0_4096_D_KN)
- outlook-com.olc.protection.outlook.com/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (1)
- outlook.com to protection.outlook.com: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (104.47.40.8, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
