hpc.mil
Updated:
2022-04-29 17:06:17 UTC (988 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- hpc.mil/A
- hpc.mil/AAAA
- hpc.mil/MX
- hpc.mil/NS
- hpc.mil/SOA
- hpc.mil/TXT
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 47671)
- hpc.mil/DNSKEY (alg 13, id 22897)
- hpc.mil/DNSKEY (alg 13, id 55014)
- hpc.mil/DNSKEY (alg 13, id 63068)
- hpc.mil/DS (alg 13, id 55014)
- hpc.mil/DS (alg 13, id 55014)
- mil/DNSKEY (alg 8, id 44790)
- mil/DNSKEY (alg 8, id 4659)
- mil/DNSKEY (alg 8, id 56347)
- mil/DS (alg 8, id 56347)
Delegation status
Secure (2)
- . to mil
- mil to hpc.mil
Notices
Errors (2)
- mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2608:c144:1:155::234)
- mil/DS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (192.36.148.17, 2001:7fe::53, UDP_-_NOEDNS_)
Warnings (4)
- hpc.mil/DS (alg 13, id 55014): 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 55014): 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 55014): 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 55014): 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.
