broadcom.com

Updated: 2022-06-01 17:04:29 UTC (843 days ago) Go to most recent »

DNSSEC options (hide)

|?| RR types:
|?| DNSSEC algorithms:
|?| DS digest algorithms:
|?| Denial of existence:
|?| Redundant edges:
|?| Ignore RFC 8624:
|?| Ignore RFC 9276:
|?| Multi-signer:
|?| Trust anchors:
- Root zone KSK
|?| Additional trusted keys:

Notices

DNSSEC Authentication Chain

RRset status

Bogus (6)

broadcom.com/A
broadcom.com/MX
broadcom.com/NS
broadcom.com/NSEC3PARAM
broadcom.com/SOA
broadcom.com/TXT

DNSKEY/DS/NSEC status

Bogus (4)

broadcom.com/DNSKEY (alg 8, id 12723)
broadcom.com/DNSKEY (alg 8, id 21334)
broadcom.com/DNSKEY (alg 8, id 2733)
broadcom.com/DNSKEY (alg 8, id 52800)

Secure (8)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 47671)
broadcom.com/DS (alg 8, id 21334)
broadcom.com/DS (alg 8, id 21334)
broadcom.com/DS (alg 8, id 61210)
com/DNSKEY (alg 8, id 30909)
com/DNSKEY (alg 8, id 37269)
com/DS (alg 8, id 30909)

Non_existent (1)

broadcom.com/DNSKEY (alg 8, id 61210)

Delegation status

Bogus (1)

com to broadcom.com

Secure (1)

. to com

Notices

Errors (16)

broadcom.com/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (156.154.130.100, 156.154.131.100, 2610:a1:1022::100, 2610:a1:1023::100, UDP_-_EDNS0_4096_D_KN)
broadcom.com/DNSKEY (alg 8, id 12723): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (156.154.130.100, 156.154.131.100, 2610:a1:1022::100, 2610:a1:1023::100, UDP_-_EDNS0_4096_D_KN)
broadcom.com/DNSKEY (alg 8, id 21334): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (156.154.130.100, 156.154.131.100, 2610:a1:1022::100, 2610:a1:1023::100, UDP_-_EDNS0_4096_D_KN)
broadcom.com/DNSKEY (alg 8, id 2733): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (156.154.130.100, 156.154.131.100, 2610:a1:1022::100, 2610:a1:1023::100, UDP_-_EDNS0_4096_D_KN)
broadcom.com/DNSKEY (alg 8, id 52800): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (156.154.130.100, 156.154.131.100, 2610:a1:1022::100, 2610:a1:1023::100, UDP_-_EDNS0_4096_D_KN)
broadcom.com/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (156.154.130.100, 156.154.131.100, 2610:a1:1022::100, 2610:a1:1023::100, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
broadcom.com/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (156.154.130.100, 156.154.131.100, 2610:a1:1022::100, 2610:a1:1023::100, UDP_-_EDNS0_4096_D_KN)
broadcom.com/NSEC3PARAM: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (156.154.130.100, 156.154.131.100, 2610:a1:1022::100, 2610:a1:1023::100, UDP_-_EDNS0_4096_D_KN)
broadcom.com/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (156.154.130.100, 156.154.131.100, 2610:a1:1022::100, 2610:a1:1023::100, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
broadcom.com/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (156.154.130.100, 156.154.131.100, 2610:a1:1022::100, 2610:a1:1023::100, UDP_-_EDNS0_4096_D_KN)
com to broadcom.com: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (156.154.130.100, 156.154.131.100, 2610:a1:1022::100, 2610:a1:1023::100, UDP_-_EDNS0_4096_D_KN)
com to broadcom.com: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (156.154.130.100, 156.154.131.100, 2610:a1:1022::100, 2610:a1:1023::100, UDP_-_EDNS0_4096_D_KN)
broadcom.com/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
wgm5ie1kdj.broadcom.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
broadcom.com/DNSKEY 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.

Warnings (8)

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 61210): 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 61210): 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 61210): 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 61210): 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.