vfc.com

Updated: 2024-09-11 03:32:38 UTC (71 days ago) Go to most recent »

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./DNSKEY (alg 8, id 20038)
./DNSKEY (alg 8, id 20326)
NSEC3 proving non-existence of vfc.com/DS
com/DNSKEY (alg 13, id 19718)
com/DNSKEY (alg 13, id 59354)
com/DS (alg 13, id 19718)

com to vfc.com: 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. (192.54.112.30, UDP_-_NOEDNS_)
com to vfc.com: 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. (192.54.112.30, UDP_-_EDNS0_4096_D_KN)
com to vfc.com: 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. (192.54.112.30, UDP_-_EDNS0_4096_D_KN)
com zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (192.48.79.30)
com/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. (192.54.112.30, UDP_-_EDNS0_4096_D_KN)
vfc.com/DS has errors; select the "Denial of existence" DNSSEC option to see them.

com/DNSKEY (alg 13, id 19718): 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. (192.48.79.30, UDP_-_EDNS0_4096_D_KN)
com/DNSKEY (alg 13, id 59354): 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. (192.48.79.30, UDP_-_EDNS0_4096_D_KN)