test.00001.y.dotnxdomain.net
Updated:
2021-06-30 03:32:03 UTC (1240 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 14631)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26838)
- dotnxdomain.net/DNSKEY (alg 5, id 15135)
- dotnxdomain.net/DNSKEY (alg 5, id 18553)
- dotnxdomain.net/DS (alg 5, id 18553)
- dotnxdomain.net/DS (alg 5, id 18553)
- net/DNSKEY (alg 8, id 35886)
- net/DNSKEY (alg 8, id 6203)
- net/DS (alg 8, id 35886)
- y.dotnxdomain.net/DS (alg 5, id 29911)
Non_existent (1)
- y.dotnxdomain.net/DNSKEY (alg 5, id 29911)
Delegation status
Bogus (1)
- dotnxdomain.net to y.dotnxdomain.net
Secure (2)
- . to net
- net to dotnxdomain.net
Notices
Errors (4)
- ./DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2001:7fd::1, UDP_-_EDNS0_512_D_KN)
- dotnxdomain.net to y.dotnxdomain.net: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11.
- test.00001.y.dotnxdomain.net/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (162.223.8.90, 2607:fc50:1001:9500::2, UDP_-_NOEDNS_)
- y.dotnxdomain.net zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (162.223.8.90, 2607:fc50:1001:9500::2)
Warnings (13)
- RRSIG dotnxdomain.net/DNSKEY alg 5, id 15135: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG dotnxdomain.net/DNSKEY alg 5, id 15135: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG dotnxdomain.net/DNSKEY alg 5, id 18553: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG dotnxdomain.net/DNSKEY alg 5, id 18553: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG y.dotnxdomain.net/DS alg 5, id 15135: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- dotnxdomain.net/DS (alg 5, id 18553): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- dotnxdomain.net/DS (alg 5, id 18553): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- dotnxdomain.net/DS (alg 5, id 18553): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- dotnxdomain.net/DS (alg 5, id 18553): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- y.dotnxdomain.net/DS (alg 5, id 29911): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- y.dotnxdomain.net/DS (alg 5, id 29911): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- y.dotnxdomain.net/DS (alg 5, id 29911): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- y.dotnxdomain.net/DS (alg 5, id 29911): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
JavaScript is required to make the graph below interactive.
