View on GitHub

DNSViz: A DNS visualization tool

dej.in.ua

DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (8)
  • dej.in.ua/A
  • dej.in.ua/AAAA
  • dej.in.ua/MX
  • dej.in.ua/NS
  • dej.in.ua/NSEC3PARAM
  • dej.in.ua/SOA
  • dej.in.ua/TXT
  • in.ua/SOA
Secure (2)
  • ua/SOA
  • ua/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (4)
  • dej.in.ua/DNSKEY (alg 13, id 147)
  • dej.in.ua/DNSKEY (alg 13, id 59537)
  • dej.in.ua/DNSKEY (alg 7, id 27921)
  • dej.in.ua/DNSKEY (alg 7, id 34073)
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 statusDelegation status

Insecure (2)
  • in.ua to dej.in.ua
  • ua to in.ua
Secure (1)
  • . to ua

NoticesNotices

Errors (8)
  • 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.
  • lm5useotyg.dej.in.ua/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • dej.in.ua/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (24)
  • 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.
  • RRSIG dej.in.ua/A alg 7, id 34073: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG dej.in.ua/AAAA alg 7, id 34073: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG dej.in.ua/DNSKEY alg 7, id 27921: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG dej.in.ua/DNSKEY alg 7, id 27921: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG dej.in.ua/DNSKEY alg 7, id 27921: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG dej.in.ua/DNSKEY alg 7, id 27921: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG dej.in.ua/DNSKEY alg 7, id 34073: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG dej.in.ua/DNSKEY alg 7, id 34073: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG dej.in.ua/DNSKEY alg 7, id 34073: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG dej.in.ua/DNSKEY alg 7, id 34073: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG dej.in.ua/MX alg 7, id 34073: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG dej.in.ua/NS alg 7, id 34073: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG dej.in.ua/NSEC3PARAM alg 7, id 34073: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG dej.in.ua/SOA alg 7, id 34073: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG dej.in.ua/TXT alg 7, id 34073: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • in.ua to dej.in.ua: No response was received from the server over UDP (tried 10 times) until the DO EDNS flag was cleared (however, this server appeared to respond legitimately to other queries with the DO EDNS flag set). See RFC 6891, Sec. 6.1.4. (194.58.197.4, UDP_-_EDNS0_4096_D_KN)
  • lm5useotyg.dej.in.ua/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • dej.in.ua/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • dej.in.ua/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • dej.in.ua/DS has warnings; select the "Denial of existence" DNSSEC option to see them.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph