insecure.mufj.jp

Updated: 2021-02-28 08:52:03 UTC (1393 days ago) Update now

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

insecure.mufj.jp/CNAME
www.e-ontap.com/A

Secure (3)

com/SOA
com/SOA
mufj.jp/SOA

DNSKEY/DS/NSEC status

Secure (14)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 42351)
NSEC3 proving non-existence of e-ontap.com/DS
NSEC3 proving non-existence of insecure.mufj.jp/DS
com/DNSKEY (alg 8, id 30909)
com/DNSKEY (alg 8, id 58540)
com/DS (alg 8, id 30909)
jp/DNSKEY (alg 8, id 11244)
jp/DNSKEY (alg 8, id 4239)
jp/DNSKEY (alg 8, id 46369)
jp/DS (alg 8, id 46369)
mufj.jp/DNSKEY (alg 7, id 19682)
mufj.jp/DNSKEY (alg 7, id 60678)
mufj.jp/DS (alg 7, id 60678)

Non_existent (1)

mufj.jp/DNSKEY (alg 13, id 18023)

Delegation status

Insecure (2)

com to e-ontap.com
mufj.jp to insecure.mufj.jp

Secure (3)

. to com
. to jp
jp to mufj.jp

Notices

Errors (13)

NSEC3 proving non-existence of insecure.mufj.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 insecure.mufj.jp/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
RRSIG insecure.mufj.jp/CNAME alg 13, id 18023: The Signer's Name field of the RRSIG RR (mufj.jp) does not match the name of the zone containing the RRset (insecure.mufj.jp). See RFC 4035, Sec. 5.3.1.
jp zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:2f8:0:100::153)
insecure.mufj.jp/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
insecure.mufj.jp/DS has errors; select the "Denial of existence" DNSSEC option to see them.
insecure.mufj.jp/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
insecure.mufj.jp/SOA has errors; select the "Denial of existence" DNSSEC option to see them.
insecure.mufj.jp/MX has errors; select the "Denial of existence" DNSSEC option to see them.
insecure.mufj.jp/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
xza29475d8.insecure.mufj.jp/A has errors; select the "Denial of existence" DNSSEC option to see them.
insecure.mufj.jp/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
insecure.mufj.jp/NS has errors; select the "Denial of existence" DNSSEC option to see them.

Warnings (17)

NSEC3 proving non-existence of insecure.mufj.jp/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of insecure.mufj.jp/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
RRSIG NSEC3 proving non-existence of insecure.mufj.jp/DS alg 7, id 19682: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG NSEC3 proving non-existence of insecure.mufj.jp/DS alg 7, id 19682: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG mufj.jp/DNSKEY alg 7, id 19682: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG mufj.jp/DNSKEY alg 7, id 19682: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG mufj.jp/DNSKEY alg 7, id 60678: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG mufj.jp/DNSKEY alg 7, id 60678: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG mufj.jp/SOA alg 7, id 19682: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
com/DS (alg 8, id 30909): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
com/DS (alg 8, id 30909): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
mufj.jp to insecure.mufj.jp: The following NS name(s) were found in the delegation NS RRset (i.e., in the mufj.jp zone), but not in the authoritative NS RRset: ns3.mufj.jp See RFC 1034, Sec. 4.2.2.
mufj.jp/DS (alg 7, id 60678): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
mufj.jp/DS (alg 7, id 60678): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
www.e-ontap.com/A: The server responded with no OPT record, rather than with RCODE FORMERR. See RFC 6891, Sec. 7. (14.192.44.1, 49.212.106.253, UDP_-_EDNS0_4096_D_KN)
xza29475d8.insecure.mufj.jp/A has warnings; select the "Denial of existence" DNSSEC option to see them.
insecure.mufj.jp/DS has warnings; select the "Denial of existence" DNSSEC option to see them.