View on GitHub

DNSViz: A DNS visualization tool

1001h.store

Updated: 2021-07-27 17:22:01 UTC (1220 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

Insecure (5)
  • 1001h.store/A
  • 1001h.store/MX
  • 1001h.store/NS
  • 1001h.store/SOA
  • 1001h.store/TXT
Secure (1)
  • store/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (4)
  • 1001h.store/DNSKEY (alg 13, id 57983)
  • 1001h.store/DNSKEY (alg 13, id 58486)
  • 1001h.store/DNSKEY (alg 8, id 12429)
  • 1001h.store/DNSKEY (alg 8, id 16492)
Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26838)
  • NSEC3 proving non-existence of 1001h.store/DS
  • store/DNSKEY (alg 8, id 16342)
  • store/DNSKEY (alg 8, id 51154)
  • store/DNSKEY (alg 8, id 63945)
  • store/DS (alg 8, id 16342)
  • store/DS (alg 8, id 16342)

Delegation statusDelegation status

Insecure (1)
  • store to 1001h.store
Secure (1)
  • . to store

NoticesNotices

Errors (6)
  • NSEC3 proving non-existence of 1001h.store/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of 1001h.store/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • 1001h.store/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • hra7kgzqd2.1001h.store/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • 1001h.store/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • 1001h.store/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (9)
  • . to store: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the . zone): c.nic.store See RFC 1034, Sec. 4.2.2.
  • store/DS (alg 8, id 16342): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • store/DS (alg 8, id 16342): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • store/DS (alg 8, id 16342): 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.
  • store/DS (alg 8, id 16342): 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.
  • store/DS (alg 8, id 16342): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
  • store/DS (alg 8, id 16342): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
  • store/DS (alg 8, id 16342): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
  • store/DS (alg 8, id 16342): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)

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