dej.in.ua
Updated:
2022-04-19 02:18:05 UTC (998 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (7)
- dej.in.ua/A
- dej.in.ua/AAAA
- dej.in.ua/MX
- dej.in.ua/NS
- dej.in.ua/SOA
- dej.in.ua/TXT
- in.ua/SOA
Secure (1)
- ua/SOA
DNSKEY/DS/NSEC status
Secure (7)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 47671)
- NSEC3 proving non-existence of in.ua/DS
- 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)
Delegation status
Insecure (2)
- in.ua to dej.in.ua
- ua to in.ua
Secure (1)
- . to ua
Notices
Errors (6)
- 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.
- 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.
- NSEC3 proving non-existence of in.ua/DS: No NSEC3 RR matches the SNAME (in.ua). See RFC 5155, Sec. 8.6.
- NSEC3 proving non-existence of in.ua/DS: No NSEC3 RR matches the SNAME (in.ua). See RFC 5155, Sec. 8.6.
Warnings (4)
- 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.
- 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.
