move.mil
Updated:
2024-07-25 11:29:40 UTC (1 day ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (3)
- move.mil/NS
- move.mil/SOA
- move.mil/TXT
DNSKEY/DS/NSEC status
Secure (13)
- ./DNSKEY (alg 8, id 20038)
- ./DNSKEY (alg 8, id 20326)
- mil/DNSKEY (alg 8, id 16801)
- mil/DNSKEY (alg 8, id 21018)
- mil/DNSKEY (alg 8, id 54036)
- mil/DS (alg 8, id 16801)
- move.mil/DNSKEY (alg 13, id 15830)
- move.mil/DNSKEY (alg 13, id 28994)
- move.mil/DNSKEY (alg 13, id 43792)
- move.mil/DS (alg 13, id 15830)
- move.mil/DS (alg 13, id 15830)
- move.mil/DS (alg 13, id 43792)
- move.mil/DS (alg 13, id 43792)
Delegation status
Secure (2)
- . to mil
- mil to move.mil
Notices
Errors (8)
- mil to move.mil: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (199.252.154.243, 199.252.155.243, 199.252.157.235, 199.252.162.243, 199.252.180.243, 2608:120:c:162::243, 2608:140:c:157::235, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- mil to move.mil: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no DS RR matched a DNSKEY with algorithm 13 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (199.252.154.243, 199.252.155.243, 199.252.157.235, 199.252.162.243, 199.252.180.243, 2608:120:c:162::243, 2608:140:c:157::235, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- move.mil/DS (alg 13, id 15830): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- move.mil/DS (alg 13, id 15830): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- move.mil/DS (alg 13, id 43792): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- move.mil/DS (alg 13, id 43792): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- move.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- move.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
- ./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)
- ./DNSKEY: 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_512_D_KN)
- move.mil/DS (alg 13, id 15830): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- move.mil/DS (alg 13, id 15830): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- move.mil/DS (alg 13, id 43792): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- move.mil/DS (alg 13, id 43792): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- move.mil/NS: 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. (2608:4122:2:154::243, 2608:4163:1:143::243, 2608:c144:1:155::243, 2608:c184:1:180::243, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
