ve
Updated:
2023-07-19 19:28:07 UTC (490 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (2)
- ve/NS
- ve/SOA
DNSKEY/DS/NSEC status
Bogus (3)
- ve/DNSKEY (alg 8, id 14092)
- ve/DNSKEY (alg 8, id 45093)
- ve/DNSKEY (alg 8, id 62041)
Secure (3)
- ./DNSKEY (alg 8, id 11019)
- ./DNSKEY (alg 8, id 20326)
- ve/DS (alg 8, id 14092)
Delegation status
Bogus (1)
- . to ve
Notices
Errors (7)
- . to ve: 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. (190.9.129.56, 200.0.68.10, 2801:14:a000::10, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
- . to ve: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (190.9.129.56, 200.0.68.10, 2801:14:a000::10, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
- ve zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (45.175.22.4, 45.175.22.88, 190.202.128.43, 200.7.5.14, 2001:1398:276:0:200:7:5:14, 2801:18:8800:1::4, 2801:18:8800:3:18ba:beff:fe61:d08b)
- ve/DNSKEY: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (190.202.128.43, TCP_-_EDNS0_4096_D_KN)
- ve/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (45.175.22.4, 45.175.22.88, 200.7.5.14, 2001:1398:276:0:200:7:5:14, 2801:18:8800:1::4, 2801:18:8800:3:18ba:beff:fe61:d08b, UDP_-_EDNS0_4096_D_KN)
- ve/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (45.175.22.4, 45.175.22.88, 190.202.128.43, 200.7.5.14, 2001:1398:276:0:200:7:5:14, 2801:18:8800:1::4, 2801:18:8800:3:18ba:beff:fe61:d08b, TCP_-_EDNS0_4096_D_N)
- ve/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
