microsoft.com
Updated:
2024-11-13 19:37:50 UTC (8 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (6)
- microsoft.com/A
- microsoft.com/AAAA
- microsoft.com/MX
- microsoft.com/NS
- microsoft.com/SOA
- microsoft.com/TXT
Secure (2)
- com/SOA
- com/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 61050)
- NSEC3 proving non-existence of microsoft.com/DS
- com/DNSKEY (alg 13, id 19718)
- com/DNSKEY (alg 13, id 29942)
- com/DS (alg 13, id 19718)
Delegation status
Insecure (1)
- com to microsoft.com
Secure (1)
- . to com
Notices
Errors (1)
- ./DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (192.33.4.12, UDP_-_EDNS0_512_D_KN)
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.33.4.12, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY (alg 8, id 61050): 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.33.4.12, UDP_-_EDNS0_4096_D_KN)
- com to microsoft.com: Authoritative AAAA records exist for ns1-39.azure-dns.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
