hpc.mil
Updated:
2023-12-27 13:22:56 UTC (366 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 30903)
- ./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 51225)
- mil/DNSKEY (alg 8, id 51706)
- mil/DS (alg 8, id 16801)
Delegation status
Secure (2)
- . to mil
- mil to hpc.mil
Notices
Warnings (6)
- 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-west.dren.mil See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
