mn.gov
Updated:
2021-12-28 14:50:42 UTC (1061 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- mn.gov/A
- mn.gov/MX
- mn.gov/NS
- mn.gov/NSEC3PARAM
- mn.gov/SOA
- mn.gov/TXT
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 14748)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 9799)
- gov/DNSKEY (alg 8, id 6229)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- mn.gov/DNSKEY (alg 8, id 35602)
- mn.gov/DNSKEY (alg 8, id 40102)
- mn.gov/DNSKEY (alg 8, id 44289)
- mn.gov/DS (alg 8, id 40102)
- mn.gov/DS (alg 8, id 40102)
Delegation status
Secure (2)
- . to gov
- gov to mn.gov
Notices
Errors (3)
- mn.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- q97hurv8xf.mn.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- mn.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
- mn.gov/DS (alg 8, id 40102): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- mn.gov/DS (alg 8, id 40102): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- mn.gov/DS (alg 8, id 40102): 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.
- mn.gov/DS (alg 8, id 40102): 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.
- mn.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- q97hurv8xf.mn.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- mn.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
