dej.in.ua
Updated:
2022-11-06 19:40:27 UTC (792 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (8)
- dej.in.ua/A
- dej.in.ua/AAAA
- dej.in.ua/CAA
- dej.in.ua/MX
- dej.in.ua/NS
- dej.in.ua/SOA
- dej.in.ua/TXT
- in.ua/SOA
Secure (2)
- ua/SOA
- ua/SOA
DNSKEY/DS/NSEC status
Secure (7)
- ./DNSKEY (alg 8, id 18733)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of in.ua/DS
- ua/DNSKEY (alg 13, id 29381)
- ua/DNSKEY (alg 13, id 48349)
- ua/DNSKEY (alg 13, id 61148)
- ua/DS (alg 13, id 48349)
Delegation status
Insecure (2)
- in.ua to dej.in.ua
- ua to in.ua
Secure (1)
- . to ua
Notices
Errors (3)
- ./DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (193.0.14.129, UDP_-_EDNS0_512_D_KN)
- 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.
Warnings (4)
- . to ua: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the . zone): nn.ns.ua See RFC 1034, Sec. 4.2.2.
- . to ua: The following NS name(s) were found in the delegation NS RRset (i.e., in the . zone), but not in the authoritative NS RRset: cd1.ns.ua See RFC 1034, Sec. 4.2.2.
- 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.
JavaScript is required to make the graph below interactive.
