militaryonesource.mil
Updated:
2023-03-27 14:35:18 UTC (464 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (4)
- militaryonesource.mil/A
- militaryonesource.mil/NS
- militaryonesource.mil/SOA
- militaryonesource.mil/TXT
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 60955)
- ./DNSKEY (alg 8, id 951)
- mil/DNSKEY (alg 8, id 53035)
- mil/DNSKEY (alg 8, id 62470)
- mil/DNSKEY (alg 8, id 8715)
- mil/DS (alg 8, id 62470)
- militaryonesource.mil/DNSKEY (alg 13, id 21583)
- militaryonesource.mil/DNSKEY (alg 13, id 22226)
- militaryonesource.mil/DNSKEY (alg 13, id 42667)
- militaryonesource.mil/DS (alg 13, id 42667)
- militaryonesource.mil/DS (alg 13, id 42667)
Delegation status
Secure (2)
- . to mil
- mil to militaryonesource.mil
Notices
Errors (2)
- militaryonesource.mil/DS (alg 13, id 42667): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- militaryonesource.mil/DS (alg 13, id 42667): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
Warnings (3)
- militaryonesource.mil/DS (alg 13, id 42667): 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.
- militaryonesource.mil/DS (alg 13, id 42667): 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.
- militaryonesource.mil/SOA: 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:c144:1:155::243, UDP_-_EDNS0_4096_D_KN_0x20)
JavaScript is required to make the graph below interactive.
