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

Secure (6)
  • broadcom.com/A
  • broadcom.com/MX
  • broadcom.com/NS
  • broadcom.com/NSEC3PARAM
  • broadcom.com/SOA
  • broadcom.com/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • broadcom.com/DNSKEY (alg 8, id 22263)
  • broadcom.com/DNSKEY (alg 8, id 24151)
  • broadcom.com/DNSKEY (alg 8, id 59010)
  • 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 46551)
  • com/DS (alg 8, id 30909)
Non_existent (1)
  • broadcom.com/DNSKEY (alg 8, id 21334)

Delegation statusDelegation status

Secure (2)
  • . to com
  • com to broadcom.com

NoticesNotices

Errors (3)
  • broadcom.com/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • qcxt7uajs1.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.
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.
  • broadcom.com/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • qcxt7uajs1.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.

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