NSEC3 proving non-existence of niel.site/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 niel.site/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
niel.site zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (116.203.159.204)
niel.site zone: There was an error resolving the following NS name(s) to address(es): ns1.niel.site, ns2.niel.site
niel.site/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (116.203.159.204, UDP_-_NOEDNS_)
niel.site/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (116.203.159.204, UDP_-_NOEDNS_)
niel.site/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
. to site: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the . zone): g.nic.site See RFC 1034, Sec. 4.2.2.
site/DS (alg 8, id 51676): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
site/DS (alg 8, id 51676): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
site/DS (alg 8, id 51676): 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.
site/DS (alg 8, id 51676): 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.