moprosecutors.gov
Updated:
2020-03-18 14:08:21 UTC (1708 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (2)
- gov/SOA
- moprosecutors.gov/A (NXDOMAIN)
DNSKEY/DS/NSEC status
Secure (7)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 33853)
- NSEC3 proving non-existence of moprosecutors.gov/A
- gov/DNSKEY (alg 8, id 36558)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Secure (1)
- . to gov
Notices
Errors (3)
- NSEC3 proving non-existence of moprosecutors.gov/A: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of moprosecutors.gov/A: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
- NSEC3 proving non-existence of moprosecutors.gov/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of moprosecutors.gov/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- gov/DS (alg 8, id 7698): 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.
- gov/DS (alg 8, id 7698): 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.
- gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
