dej.in.ua | DNSViz

dej.in.ua

Updated: 2022-04-19 14:16:43 UTC (809 days ago) Go to most recent »

DNSSEC options (hide)

|?| RR types:
|?| DNSSEC algorithms:
|?| DS digest algorithms:
|?| Denial of existence:
|?| Redundant edges:
|?| Ignore RFC 8624:
|?| Ignore RFC 9276:
|?| Multi-signer:
|?| Trust anchors:
- Root zone KSK
|?| Additional trusted keys:

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 (6)

./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)

Delegation status

Insecure (2)

in.ua to dej.in.ua
ua to in.ua

Secure (1)

. to ua

Notices

Errors (3)

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. (194.58.197.4)

Warnings (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.

DNSKEY legend

Full legend

	SEP bit set
	Revoke bit set
	Trust anchor

See also

DNSSEC Debugger by Verisign Labs.

Download: png | svg

Warning

JavaScript is required to make the graph below interactive.

DNSSEC authentication graph