mcc.gov
Updated:
2021-06-07 16:44:31 UTC (1262 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- mcc.gov/A
- mcc.gov/MX
- mcc.gov/NS
- mcc.gov/SOA
- mcc.gov/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 14631)
- ./DNSKEY (alg 8, id 20326)
- gov/DNSKEY (alg 8, id 48498)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- mcc.gov/DNSKEY (alg 8, id 12000)
- mcc.gov/DNSKEY (alg 8, id 47476)
- mcc.gov/DNSKEY (alg 8, id 62718)
- mcc.gov/DS (alg 8, id 47476)
- mcc.gov/DS (alg 8, id 47476)
Delegation status
Secure (2)
- . to gov
- gov to mcc.gov
Notices
Errors (3)
- mcc.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- mcc.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- 3guac1l6di.mcc.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
- mcc.gov/DS (alg 8, id 47476): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- mcc.gov/DS (alg 8, id 47476): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- mcc.gov/DS (alg 8, id 47476): 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.
- mcc.gov/DS (alg 8, id 47476): 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.
- mcc.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- mcc.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- 3guac1l6di.mcc.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
