dej.in.ua

Updated: 2022-04-21 02:31:21 UTC (803 days ago) Go to most recent »

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 47671)
NSEC3 proving non-existence of in.ua/DS
ua/DNSKEY (alg 13, id 17727)
ua/DNSKEY (alg 13, id 48349)
ua/DS (alg 13, id 48349)

NSEC3 proving non-existence of in.ua/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 in.ua/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
in.ua zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2a01:3f1:c001::53)
ua/DS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:7fe::53, UDP_-_NOEDNS_)

NSEC3 proving non-existence of in.ua/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of in.ua/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
in.ua to dej.in.ua: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the in.ua zone): ns2.h0zt.in, ns1.h0zt.in See RFC 1034, Sec. 4.2.2.
in.ua to dej.in.ua: The following NS name(s) were found in the delegation NS RRset (i.e., in the in.ua zone), but not in the authoritative NS RRset: ns1.dezh.in, ns2.dezh.in See RFC 1034, Sec. 4.2.2.