View on GitHub

DNSViz: A DNS visualization tool

na

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

RRset statusRRset status

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

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (9)
  • ./DNSKEY (alg 8, id 18733)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 20826)
  • na/DNSKEY (alg 8, id 1953)
  • na/DNSKEY (alg 8, id 25079)
  • na/DNSKEY (alg 8, id 58095)
  • na/DS (alg 5, id 25076)
  • na/DS (alg 8, id 25079)
  • na/DS (alg 8, id 25079)
Non_existent (1)
  • na/DNSKEY (alg 5, id 25076)

Delegation statusDelegation status

Secure (1)
  • . to na

NoticesNotices

Errors (12)
  • . to na: The DS RRset for the zone included algorithm 5 (RSASHA1), but no DS RR matched a DNSKEY with algorithm 5 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (45.54.45.54, 185.28.194.194, 185.38.108.108, 195.253.64.7, 204.61.216.35, 2001:500:14:6035:ad::1, 2a01:5b0:4::7, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
  • na zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2607:f740:45::54)
  • na/DNSKEY (alg 8, id 1953): The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (45.54.45.54, 185.28.194.194, 185.38.108.108, 195.253.64.7, 204.61.216.35, 2001:500:14:6035:ad::1, 2a01:5b0:4::7, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
  • na/DNSKEY (alg 8, id 25079): The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (45.54.45.54, 185.28.194.194, 185.38.108.108, 195.253.64.7, 204.61.216.35, 2001:500:14:6035:ad::1, 2a01:5b0:4::7, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
  • na/DNSKEY (alg 8, id 58095): The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (45.54.45.54, 185.28.194.194, 185.38.108.108, 195.253.64.7, 204.61.216.35, 2001:500:14:6035:ad::1, 2a01:5b0:4::7, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
  • na/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2607:f740:45::54, UDP_-_NOEDNS_)
  • na/NS: The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (45.54.45.54, 185.28.194.194, 185.38.108.108, 195.253.64.7, 204.61.216.35, 2001:500:14:6035:ad::1, 2a01:5b0:4::7, UDP_-_EDNS0_4096_D_KN)
  • na/NSEC3PARAM: The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (45.54.45.54, 185.28.194.194, 185.38.108.108, 195.253.64.7, 204.61.216.35, 2001:500:14:6035:ad::1, 2a01:5b0:4::7, UDP_-_EDNS0_4096_D_KN)
  • na/SOA: The DS RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (45.54.45.54, 185.28.194.194, 185.38.108.108, 195.253.64.7, 204.61.216.35, 2001:500:14:6035:ad::1, 2a01:5b0:4::7, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • na/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • d59y2lasqf.na/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • na/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
  • na/DS (alg 5, id 25076): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • na/DS (alg 5, id 25076): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • na/DS (alg 5, id 25076): 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.
  • na/DS (alg 5, id 25076): 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.
  • na/DS (alg 8, id 25079): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • na/DS (alg 8, id 25079): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • na/DS (alg 8, id 25079): 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.
  • na/DS (alg 8, id 25079): 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.
  • na/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • d59y2lasqf.na/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