_acme-challenge.vadim.com.ru
Updated:
2022-09-16 18:28:56 UTC (845 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (9)
- _acme-challenge.vadim.com.ru/A (NODATA)
- _acme-challenge.vadim.com.ru/A (NXDOMAIN)
- _acme-challenge.vadim.com.ru/AAAA (NODATA)
- _acme-challenge.vadim.com.ru/AAAA (NXDOMAIN)
- _acme-challenge.vadim.com.ru/TXT (NXDOMAIN)
- vadim.com.ru/SOA
- vadim.com.ru/SOA
- vadim.com.ru/SOA
- vadim.com.ru/SOA
Secure (1)
- com.ru/SOA
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 20826)
- NSEC3 proving non-existence of vadim.com.ru/DS
- com.ru/DNSKEY (alg 8, id 36276)
- com.ru/DNSKEY (alg 8, id 42205)
- com.ru/DNSKEY (alg 8, id 55656)
- com.ru/DS (alg 8, id 42205)
- ru/DNSKEY (alg 8, id 33257)
- ru/DNSKEY (alg 8, id 33540)
- ru/DNSKEY (alg 8, id 53643)
- ru/DS (alg 8, id 33257)
Delegation status
Insecure (1)
- com.ru to vadim.com.ru
Secure (2)
- . to ru
- ru to com.ru
Notices
Errors (4)
- NSEC3 proving non-existence of vadim.com.ru/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 vadim.com.ru/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- ru zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:678:14:0:193:232:156:17)
- vadim.com.ru zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (2a02:6b8::213)
Warnings (14)
- NSEC3 proving non-existence of vadim.com.ru/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of vadim.com.ru/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- _acme-challenge.vadim.com.ru/A (NODATA): The server returned a no error (NOERROR) response when queried for _acme-challenge.vadim.com.ru having record data of type A, but returned a name error (NXDOMAIN) when queried for _acme-challenge.vadim.com.ru having record data of type AAAA. See RFC 1034, Sec. 4.3.2. (2a02:6b8:0:1::213, UDP_-_EDNS0_4096_D_KN)
- _acme-challenge.vadim.com.ru/A (NODATA): The server returned a no error (NOERROR) response when queried for _acme-challenge.vadim.com.ru having record data of type A, but returned a name error (NXDOMAIN) when queried for _acme-challenge.vadim.com.ru having record data of type TXT. See RFC 1034, Sec. 4.3.2. (2a02:6b8:0:1::213, UDP_-_EDNS0_4096_D_KN)
- _acme-challenge.vadim.com.ru/A (NXDOMAIN): No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (2a02:6b8::213, UDP_-_EDNS0_4096_D_KN)
- _acme-challenge.vadim.com.ru/A (NXDOMAIN): The server returned a no error (NOERROR) response when queried for _acme-challenge.vadim.com.ru having record data of type AAAA, but returned a name error (NXDOMAIN) when queried for _acme-challenge.vadim.com.ru having record data of type A. See RFC 1034, Sec. 4.3.2. (2a02:6b8::213, UDP_-_EDNS0_4096_D)
- _acme-challenge.vadim.com.ru/AAAA (NODATA): 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. (2a02:6b8::213, UDP_-_EDNS0_4096_D_KN)
- _acme-challenge.vadim.com.ru/AAAA (NODATA): The server returned a no error (NOERROR) response when queried for _acme-challenge.vadim.com.ru having record data of type AAAA, but returned a name error (NXDOMAIN) when queried for _acme-challenge.vadim.com.ru having record data of type A. See RFC 1034, Sec. 4.3.2. (2a02:6b8::213, UDP_-_EDNS0_4096_D)
- _acme-challenge.vadim.com.ru/AAAA (NODATA): The server returned a no error (NOERROR) response when queried for _acme-challenge.vadim.com.ru having record data of type AAAA, but returned a name error (NXDOMAIN) when queried for _acme-challenge.vadim.com.ru having record data of type TXT. See RFC 1034, Sec. 4.3.2. (2a02:6b8::213, UDP_-_EDNS0_4096_D_KN)
- _acme-challenge.vadim.com.ru/AAAA (NXDOMAIN): 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. (2a02:6b8:0:1::213, UDP_-_EDNS0_4096_D_KN)
- _acme-challenge.vadim.com.ru/AAAA (NXDOMAIN): The server returned a no error (NOERROR) response when queried for _acme-challenge.vadim.com.ru having record data of type A, but returned a name error (NXDOMAIN) when queried for _acme-challenge.vadim.com.ru having record data of type AAAA. See RFC 1034, Sec. 4.3.2. (2a02:6b8:0:1::213, UDP_-_EDNS0_4096_D_KN)
- _acme-challenge.vadim.com.ru/TXT (NXDOMAIN): 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. (2a02:6b8:0:1::213, UDP_-_EDNS0_4096_D_KN)
- _acme-challenge.vadim.com.ru/TXT (NXDOMAIN): The server returned a no error (NOERROR) response when queried for _acme-challenge.vadim.com.ru having record data of type A, but returned a name error (NXDOMAIN) when queried for _acme-challenge.vadim.com.ru having record data of type TXT. See RFC 1034, Sec. 4.3.2. (2a02:6b8:0:1::213, UDP_-_EDNS0_4096_D_KN)
- _acme-challenge.vadim.com.ru/TXT (NXDOMAIN): The server returned a no error (NOERROR) response when queried for _acme-challenge.vadim.com.ru having record data of type AAAA, but returned a name error (NXDOMAIN) when queried for _acme-challenge.vadim.com.ru having record data of type TXT. See RFC 1034, Sec. 4.3.2. (2a02:6b8::213, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
