hpc.mil
Updated:
2024-10-14 18:20:10 UTC (68 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 (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 61050)
- hpc.mil/DNSKEY (alg 13, id 43333)
- hpc.mil/DNSKEY (alg 13, id 7774)
- hpc.mil/DS (alg 13, id 43333)
- hpc.mil/DS (alg 13, id 43333)
- mil/DNSKEY (alg 8, id 20335)
- mil/DNSKEY (alg 8, id 26770)
- mil/DNSKEY (alg 8, id 63500)
- mil/DS (alg 8, id 63500)
Delegation status
Secure (2)
- . to mil
- mil to hpc.mil
Notices
Errors (1)
- ./DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (192.33.4.12, UDP_-_EDNS0_512_D_KN)
Warnings (4)
- hpc.mil/DS (alg 13, id 43333): 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 43333): 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 43333): 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 43333): 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.
