View on GitHub

DNSViz: A DNS visualization tool

accelerateit.digital

Updated: 2021-05-09 23:36:09 UTC (1500 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 (1)
  • digital/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 14631)
  • ./DNSKEY (alg 8, id 20326)
  • NSEC3 proving non-existence of accelerateit.digital/DS
  • digital/DNSKEY (alg 8, id 10926)
  • digital/DNSKEY (alg 8, id 51340)
  • digital/DS (alg 8, id 51340)
  • digital/DS (alg 8, id 51340)

Delegation statusDelegation status

Lame (1)
  • digital to accelerateit.digital
Secure (1)
  • . to digital

NoticesNotices

Errors (17)
  • NSEC3 proving non-existence of accelerateit.digital/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 accelerateit.digital/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • accelerateit.digital zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (27.124.125.1, 27.124.125.2, 2a00:fd80:aaaa:ffff::bbbb:1, 2a00:fd80:aaaa:ffff::bbbb:2)
  • accelerateit.digital zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (27.124.125.1, 27.124.125.2, 2a00:fd80:aaaa:ffff::bbbb:1, 2a00:fd80:aaaa:ffff::bbbb:2)
  • accelerateit.digital/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (27.124.125.1, 27.124.125.2, 2a00:fd80:aaaa:ffff::bbbb:1, 2a00:fd80:aaaa:ffff::bbbb:2, UDP_-_EDNS0_4096_D_KN)
  • accelerateit.digital/AAAA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (27.124.125.1, 27.124.125.2, 2a00:fd80:aaaa:ffff::bbbb:1, 2a00:fd80:aaaa:ffff::bbbb:2, UDP_-_EDNS0_4096_D_KN)
  • accelerateit.digital/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (27.124.125.1, 27.124.125.2, 2a00:fd80:aaaa:ffff::bbbb:1, 2a00:fd80:aaaa:ffff::bbbb:2, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • accelerateit.digital/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (27.124.125.1, 27.124.125.2, 2a00:fd80:aaaa:ffff::bbbb:1, 2a00:fd80:aaaa:ffff::bbbb:2, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • accelerateit.digital/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (27.124.125.1, 27.124.125.2, 2a00:fd80:aaaa:ffff::bbbb:1, 2a00:fd80:aaaa:ffff::bbbb:2, UDP_-_EDNS0_4096_D_KN)
  • accelerateit.digital/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (27.124.125.1, 27.124.125.2, 2a00:fd80:aaaa:ffff::bbbb:1, 2a00:fd80:aaaa:ffff::bbbb:2, TCP_-_EDNS0_4096_D_N)
  • accelerateit.digital/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (27.124.125.1, 27.124.125.2, 2a00:fd80:aaaa:ffff::bbbb:1, 2a00:fd80:aaaa:ffff::bbbb:2, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • accelerateit.digital/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (27.124.125.1, 27.124.125.2, 2a00:fd80:aaaa:ffff::bbbb:1, 2a00:fd80:aaaa:ffff::bbbb:2, UDP_-_EDNS0_4096_D_KN)
  • digital zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:dcd:4::7)
  • 8pzmlfix7v.accelerateit.digital/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • accelerateit.digital/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • accelerateit.digital/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • accelerateit.digital/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
  • NSEC3 proving non-existence of accelerateit.digital/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of accelerateit.digital/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • digital/DS (alg 8, id 51340): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • digital/DS (alg 8, id 51340): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • digital/DS (alg 8, id 51340): 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.
  • digital/DS (alg 8, id 51340): 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.
  • accelerateit.digital/DS 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