mda.mil
Updated:
2022-04-13 13:22:18 UTC (983 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- mda.mil/A
- mda.mil/AAAA
- mda.mil/MX
- mda.mil/NS
- mda.mil/SOA
- mda.mil/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 47671)
- mda.mil/DNSKEY (alg 8, id 11124)
- mda.mil/DNSKEY (alg 8, id 42307)
- mda.mil/DS (alg 8, id 42307)
- mda.mil/DS (alg 8, id 42307)
- mil/DNSKEY (alg 8, id 4659)
- mil/DNSKEY (alg 8, id 49023)
- mil/DNSKEY (alg 8, id 56347)
- mil/DS (alg 8, id 56347)
Delegation status
Secure (2)
- . to mil
- mil to mda.mil
Notices
Errors (1)
- mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2608:4163:1:143::234, UDP_-_EDNS0_512_D_KN)
Warnings (4)
- mda.mil/DS (alg 8, id 42307): 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 42307): 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 42307): 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 42307): 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.
JavaScript is required to make the graph below interactive.
