View on GitHub

DNSViz: A DNS visualization tool

broadcom.com

DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Bogus (5)
  • broadcom.com/A
  • broadcom.com/MX
  • broadcom.com/NS
  • broadcom.com/SOA
  • broadcom.com/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (4)
  • broadcom.com/DNSKEY (alg 8, id 34674)
  • broadcom.com/DNSKEY (alg 8, id 42558)
  • broadcom.com/DNSKEY (alg 8, id 45183)
  • broadcom.com/DNSKEY (alg 8, id 61210)
Secure (7)
  • ./DNSKEY (alg 8, id 14631)
  • ./DNSKEY (alg 8, id 20326)
  • broadcom.com/DS (alg 8, id 61210)
  • broadcom.com/DS (alg 8, id 61210)
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 54714)
  • com/DS (alg 8, id 30909)

Delegation statusDelegation status

Bogus (1)
  • com to broadcom.com
Secure (1)
  • . to com

NoticesNotices

Errors (19)
  • ./DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (192.112.36.4, UDP_-_EDNS0_512_D_KN)
  • broadcom.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2610:a1:1023::100)
  • 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, UDP_-_EDNS0_4096_D_KN)
  • broadcom.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2610:a1:1023::100, UDP_-_NOEDNS_)
  • broadcom.com/DNSKEY (alg 8, id 34674): 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, UDP_-_EDNS0_4096_D_KN)
  • broadcom.com/DNSKEY (alg 8, id 42558): 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, UDP_-_EDNS0_4096_D_KN)
  • broadcom.com/DNSKEY (alg 8, id 45183): 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, UDP_-_EDNS0_4096_D_KN)
  • broadcom.com/DNSKEY (alg 8, id 61210): 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, 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, 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, UDP_-_EDNS0_4096_D_KN)
  • broadcom.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2610:a1:1023::100, UDP_-_NOEDNS_)
  • 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, 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, 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, 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, UDP_-_EDNS0_4096_D_KN)
  • broadcom.com/AAAA 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.
  • 1qye2zau6t.broadcom.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
  • 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.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph