nmsc.gov
Updated:
2021-04-13 13:04:10 UTC (1322 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- nmsc.gov/A
- nmsc.gov/MX
- nmsc.gov/NS
- nmsc.gov/SOA
- nmsc.gov/TXT
DNSKEY/DS/NSEC status
Secure (13)
- ./DNSKEY (alg 8, id 14631)
- ./DNSKEY (alg 8, id 20326)
- gov/DNSKEY (alg 8, id 27306)
- gov/DNSKEY (alg 8, id 48498)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- nmsc.gov/DNSKEY (alg 8, id 1163)
- nmsc.gov/DNSKEY (alg 8, id 17543)
- nmsc.gov/DNSKEY (alg 8, id 17786)
- nmsc.gov/DNSKEY (alg 8, id 4237)
- nmsc.gov/DNSKEY (alg 8, id 54233)
- nmsc.gov/DS (alg 8, id 4237)
- nmsc.gov/DS (alg 8, id 4237)
Delegation status
Secure (2)
- . to gov
- gov to nmsc.gov
Notices
Warnings (4)
- nmsc.gov/DS (alg 8, id 4237): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- nmsc.gov/DS (alg 8, id 4237): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- nmsc.gov/DS (alg 8, id 4237): 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.
- nmsc.gov/DS (alg 8, id 4237): 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.
