mgi.gov
Updated:
2023-01-16 22:42:54 UTC (686 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- mgi.gov/A
- mgi.gov/AAAA
- mgi.gov/NS
- mgi.gov/NSEC3PARAM
- mgi.gov/SOA
- mgi.gov/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 951)
- gov/DNSKEY (alg 8, id 24250)
- gov/DNSKEY (alg 8, id 56278)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- mgi.gov/DNSKEY (alg 8, id 1567)
- mgi.gov/DNSKEY (alg 8, id 42336)
- mgi.gov/DS (alg 8, id 1567)
- mgi.gov/DS (alg 8, id 1567)
Delegation status
Secure (2)
- . to gov
- gov to mgi.gov
Notices
Errors (3)
- mgi.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- rhq83y4062.mgi.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- mgi.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
- mgi.gov/DS (alg 8, id 1567): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- mgi.gov/DS (alg 8, id 1567): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- mgi.gov/DS (alg 8, id 1567): 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.
- mgi.gov/DS (alg 8, id 1567): 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.
- mgi.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- rhq83y4062.mgi.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- mgi.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
