View on GitHub

DNSViz: A DNS visualization tool

awsl.blog

Updated: 2021-02-06 15:11:01 UTC (1384 days ago) Update now
« 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 (6)
  • awsl.blog/A
  • awsl.blog/AAAA
  • awsl.blog/MX
  • awsl.blog/NS
  • awsl.blog/SOA
  • awsl.blog/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 42351)
  • awsl.blog/DNSKEY (alg 13, id 2371)
  • awsl.blog/DNSKEY (alg 13, id 34505)
  • awsl.blog/DS (alg 13, id 2371)
  • blog/DNSKEY (alg 8, id 16976)
  • blog/DNSKEY (alg 8, id 40719)
  • blog/DS (alg 8, id 16976)
  • blog/DS (alg 8, id 16976)
  • blog/DS (alg 8, id 43975)
Non_existent (1)
  • blog/DNSKEY (alg 8, id 43975)

Delegation statusDelegation status

Secure (2)
  • . to blog
  • blog to awsl.blog

NoticesNotices

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