./DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (192.228.79.201, UDP_-_EDNS0_512_D_KN)
wgkmz1lu26.broadcom.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
broadcom.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
broadcom.com/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (17)
./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. (199.9.14.201, UDP_-_EDNS0_4096_D_KN)
./DNSKEY (alg 8, id 60955): 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. (199.9.14.201, UDP_-_EDNS0_4096_D_KN)
broadcom.com/DS (alg 8, id 21334): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
broadcom.com/DS (alg 8, id 21334): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
broadcom.com/DS (alg 8, id 21334): 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.
broadcom.com/DS (alg 8, id 21334): 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.
broadcom.com/DS (alg 8, id 24151): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
broadcom.com/DS (alg 8, id 24151): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
broadcom.com/DS (alg 8, id 24151): 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.
broadcom.com/DS (alg 8, id 24151): 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.
com/DS (alg 8, id 30909): No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (192.228.79.201, UDP_-_EDNS0_4096_D_KN)
com/DS (alg 8, id 30909): No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (192.228.79.201, UDP_-_EDNS0_4096_D_KN)
com/DS (alg 8, id 30909): 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. (199.9.14.201, UDP_-_EDNS0_4096_D_KN)
com/DS (alg 8, id 30909): 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. (199.9.14.201, UDP_-_EDNS0_4096_D_KN)
wgkmz1lu26.broadcom.com/A has warnings; select the "Denial of existence" DNSSEC option to see them.
broadcom.com/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
broadcom.com/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.