hpc.mil

Updated: 2023-12-05 21:38:54 UTC (388 days ago) Go to most recent »

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 46780)
hpc.mil/DS (alg 13, id 51716)
mil/DNSKEY (alg 8, id 16801)
mil/DNSKEY (alg 8, id 29343)
mil/DNSKEY (alg 8, id 51225)
mil/DS (alg 8, id 16801)

hpc.mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (140.32.45.226, 140.32.59.226, 140.32.61.226, 2001:480:a0:f003::226, 2001:480:a1:f003::226, 2001:480:b0:f003::226)
hpc.mil zone: There was an error resolving the following NS name(s) to address(es): auth-apg.dren.mil, auth-east.dren.mil
hpc.mil/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (140.32.45.226, 140.32.59.226, 140.32.61.226, 2001:480:a0:f003::226, 2001:480:a1:f003::226, 2001:480:b0:f003::226, UDP_-_NOEDNS_)
hpc.mil/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (140.32.45.226, 140.32.59.226, 140.32.61.226, 2001:480:a0:f003::226, 2001:480:a1:f003::226, 2001:480:b0:f003::226, UDP_-_NOEDNS_)
mil to hpc.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.

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