View on GitHub

DNSViz: A DNS visualization tool

gilead.com

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

RRset statusRRset status

Secure (5)
  • gilead.com/A
  • gilead.com/MX
  • gilead.com/NS
  • gilead.com/SOA
  • gilead.com/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (9)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 951)
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 36739)
  • com/DS (alg 8, id 30909)
  • gilead.com/DNSKEY (alg 13, id 50181)
  • gilead.com/DNSKEY (alg 13, id 61559)
  • gilead.com/DS (alg 13, id 50181)
  • gilead.com/DS (alg 13, id 50181)

Delegation statusDelegation status

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

NoticesNotices

Warnings (4)
  • gilead.com/DS (alg 13, id 50181): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gilead.com/DS (alg 13, id 50181): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gilead.com/DS (alg 13, id 50181): 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.
  • gilead.com/DS (alg 13, id 50181): 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