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