dns.jp | DNSViz

dns.jp

Updated: 2020-06-22 20:03:50 UTC (1613 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 (3)

dns.jp/MX
dns.jp/NS
dns.jp/SOA

Secure (1)

jp/SOA

DNSKEY/DS/NSEC status

Secure (8)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 46594)
./DNSKEY (alg 8, id 48903)
NSEC3 proving non-existence of dns.jp/DS
jp/DNSKEY (alg 8, id 10218)
jp/DNSKEY (alg 8, id 39595)
jp/DNSKEY (alg 8, id 54678)
jp/DS (alg 8, id 39595)

Delegation status

Insecure (1)

jp to dns.jp

Secure (1)

. to jp

Notices

Errors (3)

NSEC3 proving non-existence of dns.jp/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 dns.jp/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
dns.jp/DS has errors; select the "Denial of existence" DNSSEC option to see them.

Warnings (3)

NSEC3 proving non-existence of dns.jp/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of dns.jp/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
dns.jp/DS has warnings; select the "Denial of existence" DNSSEC option to see them.

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