appliedmaterials.com

Updated: 2022-05-17 20:59:46 UTC (919 days ago) Go to most recent »

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 47671)
appliedmaterials.com/DNSKEY (alg 13, id 32297)
appliedmaterials.com/DNSKEY (alg 13, id 39216)
appliedmaterials.com/DS (alg 13, id 32297)
appliedmaterials.com/DS (alg 13, id 32297)
com/DNSKEY (alg 8, id 30909)
com/DNSKEY (alg 8, id 37269)
com/DS (alg 8, id 30909)

./DNSKEY (alg 8, id 20326): 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.112.36.4, UDP_-_EDNS0_4096_D_KN)
./DNSKEY (alg 8, id 47671): 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.112.36.4, UDP_-_EDNS0_4096_D_KN)
appliedmaterials.com/DS (alg 13, id 32297): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
appliedmaterials.com/DS (alg 13, id 32297): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
appliedmaterials.com/DS (alg 13, id 32297): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
appliedmaterials.com/DS (alg 13, id 32297): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.