ve
Updated:
2024-10-24 20:03:20 UTC (26 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (2)
- ve/NS
- ve/SOA
DNSKEY/DS/NSEC status
Secure (4)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 61050)
- ve/DNSKEY (alg 8, id 53545)
- ve/DS (alg 8, id 53545)
Delegation status
Secure (1)
- . to ve
Notices
Errors (14)
- 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.9.129.56)
- ve zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (190.9.129.56)
- ve zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2801:18:8800:1::4, 2801:18:8800:3:18ba:beff:fe61:d08b)
- ve/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (190.9.129.56, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
- ve/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2801:18:8800:1::4, 2801:18:8800:3:18ba:beff:fe61:d08b, UDP_-_NOEDNS_)
- ve/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (190.9.129.56, UDP_-_NOEDNS_)
- ve/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (190.9.129.56, TCP_-_NOEDNS_)
- ve/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (190.9.129.56, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
- ve/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- ve/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- ve/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- ve/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
- ve/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
- ayir3.htbwj.ve/A has errors; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
