www.gov.co
Updated:
2020-06-05 16:59:04 UTC (1584 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (6)
- akamaiedge.net/SOA
- e36193.dscb.akamaiedge.net/A
- e36193.dscb.akamaiedge.net/AAAA
- e36193.dscb.akamaiedge.net/AAAA
- gov.co.edgekey.net/CNAME
- www.gov.co/CNAME
Secure (3)
- co/SOA
- net/SOA
- net/SOA
DNSKEY/DS/NSEC status
Secure (14)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 48903)
- NSEC3 proving non-existence of akamaiedge.net/DS
- NSEC3 proving non-existence of edgekey.net/DS
- NSEC3 proving non-existence of www.gov.co/DS
- co/DNSKEY (alg 8, id 10384)
- co/DNSKEY (alg 8, id 43834)
- co/DNSKEY (alg 8, id 63993)
- co/DNSKEY (alg 8, id 64278)
- co/DS (alg 8, id 43834)
- co/DS (alg 8, id 43834)
- net/DNSKEY (alg 8, id 35886)
- net/DNSKEY (alg 8, id 36059)
- net/DS (alg 8, id 35886)
Delegation status
Insecure (4)
- akamaiedge.net to dscb.akamaiedge.net
- co to www.gov.co
- net to akamaiedge.net
- net to edgekey.net
Secure (2)
- . to co
- . to net
Notices
Errors (7)
- 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.
- 9ct8pkqg60.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 (20)
- 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.
- akamaiedge.net to dscb.akamaiedge.net: The glue address(es) for n1dscb.akamaiedge.net (63.233.61.187, 63.233.61.197, 63.233.61.198) differed from its authoritative address(es) (63.233.61.197). See RFC 1034, Sec. 4.2.2.
- akamaiedge.net to dscb.akamaiedge.net: The glue address(es) for n2dscb.akamaiedge.net (63.233.61.186, 63.233.61.216, 204.237.221.221) differed from its authoritative address(es) (63.233.61.186). See RFC 1034, Sec. 4.2.2.
- akamaiedge.net to dscb.akamaiedge.net: The glue address(es) for n3dscb.akamaiedge.net (63.233.61.198, 63.233.61.199, 63.233.61.200) differed from its authoritative address(es) (63.233.61.198). See RFC 1034, Sec. 4.2.2.
- akamaiedge.net to dscb.akamaiedge.net: The glue address(es) for n4dscb.akamaiedge.net (63.233.61.160, 199.239.183.220, 204.237.221.223) differed from its authoritative address(es) (199.239.183.220). See RFC 1034, Sec. 4.2.2.
- akamaiedge.net to dscb.akamaiedge.net: The glue address(es) for n5dscb.akamaiedge.net (63.233.61.196, 63.233.61.198, 165.254.96.24) differed from its authoritative address(es) (165.254.96.24). See RFC 1034, Sec. 4.2.2.
- akamaiedge.net to dscb.akamaiedge.net: The glue address(es) for n6dscb.akamaiedge.net (63.233.61.159, 63.233.61.217, 63.233.61.219) differed from its authoritative address(es) (63.233.61.217). See RFC 1034, Sec. 4.2.2.
- akamaiedge.net to dscb.akamaiedge.net: The glue address(es) for n7dscb.akamaiedge.net (63.233.61.186, 199.239.183.222, 204.237.221.239) differed from its authoritative address(es) (204.237.221.239). See RFC 1034, Sec. 4.2.2.
- 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 43834): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- co/DS (alg 8, id 43834): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- co/DS (alg 8, id 43834): 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 43834): 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.
JavaScript is required to make the graph below interactive.
