View on GitHub

DNSViz: A DNS visualization tool

sf-lug.com

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

RRset statusRRset status

Secure (5)
  • sf-lug.com/A
  • sf-lug.com/AAAA
  • sf-lug.com/NS
  • sf-lug.com/SOA
  • sf-lug.com/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (9)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 48903)
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 39844)
  • com/DS (alg 8, id 30909)
  • sf-lug.com/DNSKEY (alg 8, id 25158)
  • sf-lug.com/DNSKEY (alg 8, id 33646)
  • sf-lug.com/DS (alg 8, id 33646)
  • sf-lug.com/DS (alg 8, id 33646)

Delegation statusDelegation status

Secure (2)
  • . to com
  • com to sf-lug.com

NoticesNotices

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