View on GitHub

DNSViz: A DNS visualization tool

jitcreatives.de

« 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)
  • jitcreatives.de/A
  • jitcreatives.de/MX
  • jitcreatives.de/NS
  • jitcreatives.de/SOA
  • jitcreatives.de/TXT
Secure (1)
  • de/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (2)
  • jitcreatives.de/DNSKEY (alg 5, id 18934)
  • jitcreatives.de/DNSKEY (alg 5, id 3291)
Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 30903)
  • NSEC3 proving non-existence of jitcreatives.de/DS
  • de/DNSKEY (alg 8, id 19854)
  • de/DNSKEY (alg 8, id 26755)
  • de/DS (alg 8, id 26755)

Delegation statusDelegation status

Insecure (1)
  • de to jitcreatives.de
Secure (1)
  • . to de

NoticesNotices

Errors (3)
  • NSEC3 proving non-existence of jitcreatives.de/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 jitcreatives.de/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • jitcreatives.de/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (17)
  • NSEC3 proving non-existence of jitcreatives.de/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of jitcreatives.de/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • RRSIG jitcreatives.de/A alg 5, id 3291: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG jitcreatives.de/DNSKEY alg 5, id 18934: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG jitcreatives.de/DNSKEY alg 5, id 18934: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG jitcreatives.de/DNSKEY alg 5, id 3291: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG jitcreatives.de/DNSKEY alg 5, id 3291: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG jitcreatives.de/MX alg 5, id 3291: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG jitcreatives.de/NS alg 5, id 3291: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG jitcreatives.de/SOA alg 5, id 3291: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG jitcreatives.de/TXT alg 5, id 3291: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • jitcreatives.de/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • jitcreatives.de/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • jitcreatives.de/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • jitcreatives.de/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • jitcreatives.de/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
  • olfd3nhy78.jitcreatives.de/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