NSEC3 proving non-existence of ipfs.io/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 ipfs.io/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
ipfs.io/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
NSEC3 proving non-existence of ipfs.io/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of ipfs.io/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
io to ipfs.io: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the io zone): ns5.dnsmadeeasy.com, ns7.dnsmadeeasy.com, ns6.dnsmadeeasy.com See RFC 1034, Sec. 4.2.2.
ipfs.io/DS has warnings; select the "Denial of existence" DNSSEC option to see them.