ve
Updated:
2023-07-20 10:29:55 UTC (474 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 (14)
- . 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) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (190.202.128.43)
- 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, 200.7.5.14, 2001:1398:276:0:200:7:5:14, 2801:18:8800:1::4)
- ve/DNSKEY: No response was received from the server over UDP (tried 11 times). See RFC 1035, Sec. 4.2. (190.202.128.43, UDP_-_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: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 10 times) with the DO bit set. See RFC 4035, Sec. 3.2.1. (190.202.128.43, UDP_-_EDNS0_4096_)
- ve/SOA: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 11 times) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (190.202.128.43, UDP_-_NOEDNS__0x20)
- 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, TCP_-_EDNS0_4096_D_N)
- ve/SOA: No response was received from the server over UDP (tried 10 times) until the DO EDNS flag was cleared (however, this server appeared to respond legitimately to other queries with the DO EDNS flag set). See RFC 6891, Sec. 6.1.4. (190.202.128.43, UDP_-_EDNS0_4096_D_KN)
- ve/SOA: No response was received from the server over UDP (tried 11 times) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (190.202.128.43, UDP_-_EDNS0_4096_D_KN_0x20)
- ve/SOA: The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (190.202.128.43, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- ve/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- xk489gjqym.ve/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (1)
- ve/NS: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (190.202.128.43, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
