dns.jp
Updated:
2022-04-19 06:36:03 UTC (948 days ago)
Update now
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 (7)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 47671)
- NSEC3 proving non-existence of dns.jp/DS
- jp/DNSKEY (alg 8, id 18100)
- jp/DNSKEY (alg 8, id 23238)
- jp/DNSKEY (alg 8, id 43416)
- jp/DS (alg 8, id 18100)
Delegation status
Insecure (1)
- jp to dns.jp
Secure (1)
- . to jp
Notices
Errors (4)
- 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.
- jp/DS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (192.112.36.4, UDP_-_NOEDNS_)
- 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.
JavaScript is required to make the graph below interactive.
