3m.com
Updated:
2024-08-15 18:47:43 UTC (97 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- 3m.com/A
- 3m.com/MX
- 3m.com/NS
- 3m.com/SOA
- 3m.com/TXT
Secure (1)
- com/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20038)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of 3m.com/DS
- com/DNSKEY (alg 13, id 19718)
- com/DNSKEY (alg 13, id 59354)
- com/DS (alg 13, id 19718)
Delegation status
Insecure (1)
- com to 3m.com
Secure (1)
- . to com
Notices
Warnings (4)
- ./DNSKEY (alg 8, id 20038): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY (alg 8, id 20326): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
- com to 3m.com: Authoritative AAAA records exist for a.ns.3m.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- com to 3m.com: Authoritative AAAA records exist for b.ns.3m.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.
