NSEC3 proving non-existence of fi.cr/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 fi.cr/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
RRSIG fi.cr/DNSKEY alg 13, id 15493: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG fi.cr/DNSKEY alg 13, id 15493: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
bncr.fi.cr/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (15)
NSEC3 proving non-existence of fi.cr/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of fi.cr/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
akamaiedge.net to dscx.akamaiedge.net: The glue address(es) for n1dscx.akamaiedge.net (128.241.216.206, 204.2.136.206) differed from its authoritative address(es) (204.2.136.206). See RFC 1034, Sec. 4.2.2.
akamaiedge.net to dscx.akamaiedge.net: The glue address(es) for n2dscx.akamaiedge.net (128.241.216.207, 204.237.221.222) differed from its authoritative address(es) (204.237.221.222). See RFC 1034, Sec. 4.2.2.
akamaiedge.net to dscx.akamaiedge.net: The glue address(es) for n3dscx.akamaiedge.net (128.241.216.199, 128.241.216.201) differed from its authoritative address(es) (128.241.216.201). See RFC 1034, Sec. 4.2.2.
akamaiedge.net to dscx.akamaiedge.net: The glue address(es) for n4dscx.akamaiedge.net (128.241.216.200, 128.241.216.214) differed from its authoritative address(es) (128.241.216.214). See RFC 1034, Sec. 4.2.2.
akamaiedge.net to dscx.akamaiedge.net: The glue address(es) for n5dscx.akamaiedge.net (128.241.216.208, 204.237.221.222) differed from its authoritative address(es) (128.241.216.208). See RFC 1034, Sec. 4.2.2.
akamaiedge.net to dscx.akamaiedge.net: The glue address(es) for n6dscx.akamaiedge.net (128.241.216.201, 128.241.216.206) differed from its authoritative address(es) (128.241.216.201). See RFC 1034, Sec. 4.2.2.
akamaiedge.net to dscx.akamaiedge.net: The glue address(es) for n7dscx.akamaiedge.net (128.241.220.29, 204.2.136.198) differed from its authoritative address(es) (128.241.220.29). See RFC 1034, Sec. 4.2.2.
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.
bncr.fi.cr/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.