silganholdings.com

Updated: 2024-08-26 12:58:10 UTC (89 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 silganholdings.com/DS
com/DNSKEY (alg 13, id 19718)
com/DNSKEY (alg 13, id 59354)
com/DS (alg 13, id 19718)

silganholdings.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (38.83.193.11, 205.246.18.2, 205.246.18.4)
silganholdings.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (38.83.193.11, 205.246.18.2, 205.246.18.4, UDP_-_NOEDNS_)
silganholdings.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (38.83.193.11, 205.246.18.2, 205.246.18.4, UDP_-_NOEDNS_)

./DNSKEY (alg 8, id 20038): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
./DNSKEY (alg 8, id 20326): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
com to silganholdings.com: 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.41.162.30, UDP_-_EDNS0_4096_D_KN)
com to silganholdings.com: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the com zone): ns1.netsynergy.com, ns.netsynergy.com, ns2.netsynergy.com See RFC 1034, Sec. 4.2.2.
silganholdings.com/DS has warnings; select the "Denial of existence" DNSSEC option to see them.