mda.mil

Updated: 2025-10-03 20:33:48 UTC (84 days ago) Go to most recent »

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 38696)
./DNSKEY (alg 8, id 46441)
./DNSKEY (alg 8, id 61809)
mda.mil/DNSKEY (alg 8, id 0)
mda.mil/DNSKEY (alg 8, id 50941)
mda.mil/DS (alg 8, id 50941)
mda.mil/DS (alg 8, id 50941)
mil/DNSKEY (alg 8, id 45019)
mil/DNSKEY (alg 8, id 57558)
mil/DNSKEY (alg 8, id 65239)
mil/DS (alg 8, id 45019)

mda.mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (199.9.182.33, 199.9.182.34, 199.9.230.31, 199.9.230.32)
mda.mil zone: There was an error resolving the following NS name(s) to address(es): ns03.mda.mil
mda.mil/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.9.182.33, 199.9.182.34, 199.9.230.31, 199.9.230.32, UDP_-_NOEDNS_)
mda.mil/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.9.182.33, 199.9.182.34, 199.9.230.31, 199.9.230.32, UDP_-_NOEDNS_)

mda.mil/DS (alg 8, id 50941): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
mda.mil/DS (alg 8, id 50941): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
mda.mil/DS (alg 8, id 50941): 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.
mda.mil/DS (alg 8, id 50941): 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.
mil to mda.mil: A glue records exist for ns04.mda.mil, but there are no corresponding authoritative A records. See RFC 1034, Sec. 4.2.2.