hpc.mil

Updated: 2023-12-12 20:11:58 UTC (380 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/DNSKEY (alg 13, id 15771)
hpc.mil/DNSKEY (alg 13, id 51716)
hpc.mil/DS (alg 13, id 51716)
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. (2001:480:b0:f003::226)
hpc.mil/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (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. (2001:480:b0:f003::226, UDP_-_NOEDNS_)

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: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the mil zone): auth-sandiego.dren.mil, auth-wpafb.dren.mil See RFC 1034, Sec. 4.2.2.
mil to hpc.mil: The following NS name(s) were found in the delegation NS RRset (i.e., in the mil zone), but not in the authoritative NS RRset: auth-east.dren.mil, auth-west.dren.mil See RFC 1034, Sec. 4.2.2.