dfas.mil

Updated: 2023-03-16 20:16:36 UTC (650 days ago) Go to most recent »

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 951)
dfas.mil/DS (alg 8, id 44764)
mil/DNSKEY (alg 8, id 53035)
mil/DNSKEY (alg 8, id 62470)
mil/DNSKEY (alg 8, id 8715)
mil/DS (alg 8, id 62470)

dfas.mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (204.34.89.139, 204.34.97.19)
dfas.mil zone: There was an error resolving the following NS name(s) to address(es): dzu15.dfas.mil, dzu5.dfas.mil
dfas.mil/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (204.34.89.139, 204.34.97.19, UDP_-_NOEDNS_)
dfas.mil/DS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.252.154.234, UDP_-_NOEDNS_)
dfas.mil/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.252.154.234, 204.34.89.139, 204.34.97.19, UDP_-_NOEDNS_)
mil to dfas.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.
dfas.mil/DS has errors; select the "Denial of existence" DNSSEC option to see them.

dfas.mil/DS (alg 8, id 44764): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
dfas.mil/DS (alg 8, id 44764): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
dfas.mil/DS (alg 8, id 44764): 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.
dfas.mil/DS (alg 8, id 44764): 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.