NSEC3 proving non-existence of www.gov.co/DS: 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 www.gov.co/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
www.gov.co zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (190.60.118.11)
www.gov.co/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (190.60.118.11, TCP_-_EDNS0_4096_D)
www.gov.co/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
8hj9etou45.www.gov.co/A has errors; select the "Denial of existence" DNSSEC option to see them.
www.gov.co/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (17)
NSEC3 proving non-existence of www.gov.co/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of www.gov.co/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
co to www.gov.co: The following NS name(s) were found in the delegation NS RRset (i.e., in the co zone), but not in the authoritative NS RRset: ns3.mintic.gov.co, ns4.mintic.gov.co See RFC 1034, Sec. 4.2.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): 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/DS (alg 8, id 21754): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
co/DS (alg 8, id 21754): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
co/DS (alg 8, id 21754): 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 21754): 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.
net to akamaiedge.net: Authoritative AAAA records exist for a11-192.akamaiedge.net, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
net to edgekey.net: Authoritative AAAA records exist for a13-65.akam.net, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
net to edgekey.net: Authoritative AAAA records exist for a5-65.akam.net, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
net to edgekey.net: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the net zone): a11-65.akam.net, ns1-2.akam.net, a9-65.akam.net, a3-65.akam.net See RFC 1034, Sec. 4.2.2.
net to edgekey.net: The following NS name(s) were found in the delegation NS RRset (i.e., in the net zone), but not in the authoritative NS RRset: ns1-66.akam.net, ns4-66.akam.net, ns5-66.akam.net, ns7-65.akam.net See RFC 1034, Sec. 4.2.2.
www.gov.co/DS has warnings; select the "Denial of existence" DNSSEC option to see them.