View on GitHub

DNSViz: A DNS visualization tool

llp

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

RRset statusRRset status

Secure (3)
  • llp/NS
  • llp/NSEC3PARAM
  • llp/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 951)
  • llp/DNSKEY (alg 13, id 3225)
  • llp/DNSKEY (alg 13, id 37206)
  • llp/DNSKEY (alg 7, id 16200)
  • llp/DNSKEY (alg 7, id 27216)
  • llp/DNSKEY (alg 7, id 53960)
  • llp/DNSKEY (alg 7, id 62753)
  • llp/DS (alg 7, id 16200)
  • llp/DS (alg 7, id 27216)
  • llp/DS (alg 7, id 27216)

Delegation statusDelegation status

Secure (1)
  • . to llp

NoticesNotices

Warnings (30)
  • RRSIG llp/DNSKEY alg 7, id 27216: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG llp/DNSKEY alg 7, id 27216: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG llp/DNSKEY alg 7, id 27216: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG llp/DNSKEY alg 7, id 27216: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG llp/DNSKEY alg 7, id 27216: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG llp/DNSKEY alg 7, id 27216: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG llp/DNSKEY alg 7, id 53960: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG llp/DNSKEY alg 7, id 53960: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG llp/DNSKEY alg 7, id 53960: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG llp/DNSKEY alg 7, id 53960: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG llp/DNSKEY alg 7, id 53960: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG llp/DNSKEY alg 7, id 53960: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG llp/NS alg 7, id 53960: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG llp/NSEC3PARAM alg 7, id 53960: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG llp/SOA alg 7, id 53960: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • llp/DNSKEY (alg 13, id 3225): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:67c:13cc::1:157, TCP_-_EDNS0_4096_D_KN)
  • llp/DNSKEY (alg 13, id 37206): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:67c:13cc::1:157, TCP_-_EDNS0_4096_D_KN)
  • llp/DNSKEY (alg 7, id 16200): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:67c:13cc::1:157, TCP_-_EDNS0_4096_D_KN)
  • llp/DNSKEY (alg 7, id 27216): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:67c:13cc::1:157, TCP_-_EDNS0_4096_D_KN)
  • llp/DNSKEY (alg 7, id 53960): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:67c:13cc::1:157, TCP_-_EDNS0_4096_D_KN)
  • llp/DNSKEY (alg 7, id 62753): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:67c:13cc::1:157, TCP_-_EDNS0_4096_D_KN)
  • llp/DNSKEY: The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:67c:13cc::1:157, UDP_-_EDNS0_512_D_KN)
  • llp/DS (alg 7, id 27216): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • llp/DS (alg 7, id 27216): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • llp/DS (alg 7, id 27216): 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.
  • llp/DS (alg 7, id 27216): 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.
  • llp/SOA: The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:67c:13cc::1:157, UDP_-_EDNS0_4096_D_KN)
  • llp/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • llp/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • h2py05mfu9.llp/A 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