NSEC3 proving non-existence of bestwell.com.tw/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 bestwell.com.tw/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
Warnings (4)
NSEC3 proving non-existence of bestwell.com.tw/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of bestwell.com.tw/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
com.tw to bestwell.com.tw: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the com.tw zone): ns1.hinetidc.net, ns2.hinetidc.net, ns03.idc.hinet.net, ns02.idc.hinet.net, ns01.idc.hinet.net, ns.hinetidc.net See RFC 1034, Sec. 4.2.2.
com.tw to bestwell.com.tw: The following NS name(s) were found in the delegation NS RRset (i.e., in the com.tw zone), but not in the authoritative NS RRset: ns.idc.hinet.net, ns2.idc.hinet.net, ns3.idc.hinet.net See RFC 1034, Sec. 4.2.2.