broadcom.com

Updated: 2023-04-03 21:19:03 UTC (632 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

Secure (6)

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

DNSKEY/DS/NSEC status

Secure (13)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 60955)
./DNSKEY (alg 8, id 951)
broadcom.com/DNSKEY (alg 8, id 22263)
broadcom.com/DNSKEY (alg 8, id 24151)
broadcom.com/DNSKEY (alg 8, id 42939)
broadcom.com/DNSKEY (alg 8, id 64284)
broadcom.com/DS (alg 8, id 21334)
broadcom.com/DS (alg 8, id 24151)
broadcom.com/DS (alg 8, id 24151)
com/DNSKEY (alg 8, id 30909)
com/DNSKEY (alg 8, id 36739)
com/DS (alg 8, id 30909)

Non_existent (1)

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

Delegation status

Secure (2)

. to com
com to broadcom.com

Notices

Errors (6)

broadcom.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:502:4612::2a1, 2610:a1:1014::2a1)
broadcom.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:502:4612::2a1, 2610:a1:1014::2a1, UDP_-_NOEDNS_)
broadcom.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:502:4612::2a1, 2610:a1:1014::2a1, UDP_-_NOEDNS_)
eq2ri5jafc.broadcom.com/A 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.
broadcom.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.

Warnings (11)

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.
eq2ri5jafc.broadcom.com/A 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.
broadcom.com/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.