View on GitHub

DNSViz: A DNS visualization tool

www.openttdcoop.org

Updated: 2020-05-09 17:24:44 UTC (1692 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 (2)
  • proxy.openttdcoop.org/A
  • www.openttdcoop.org/CNAME
Secure (1)
  • org/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (1)
  • openttdcoop.org/DNSKEY (alg 13, id 31449)
Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 48903)
  • NSEC3 proving non-existence of openttdcoop.org/DS
  • org/DNSKEY (alg 7, id 17883)
  • org/DNSKEY (alg 7, id 27074)
  • org/DNSKEY (alg 7, id 62165)
  • org/DS (alg 7, id 17883)
  • org/DS (alg 7, id 17883)

Delegation statusDelegation status

Insecure (1)
  • org to openttdcoop.org
Secure (1)
  • . to org

NoticesNotices

Errors (7)
  • NSEC3 proving non-existence of openttdcoop.org/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 openttdcoop.org/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • RRSIG openttdcoop.org/DNSKEY alg 13, id 31449: The Signature Expiration field of the RRSIG RR (2020-04-09 00:00:00+00:00) is 30 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG proxy.openttdcoop.org/A alg 13, id 31449: The Signature Expiration field of the RRSIG RR (2020-04-09 00:00:00+00:00) is 30 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG www.openttdcoop.org/CNAME alg 13, id 31449: The Signature Expiration field of the RRSIG RR (2020-04-09 00:00:00+00:00) is 30 days in the past. See RFC 4035, Sec. 5.3.1.
  • www.openttdcoop.org/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • openttdcoop.org/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (15)
  • NSEC3 proving non-existence of openttdcoop.org/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of openttdcoop.org/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of openttdcoop.org/DS alg 7, id 27074: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of openttdcoop.org/DS alg 7, id 27074: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 17883: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 17883: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 17883: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 27074: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 27074: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 27074: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/SOA alg 7, id 27074: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • org/DS (alg 7, id 17883): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • org/DS (alg 7, id 17883): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • org/DS (alg 7, id 17883): 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.
  • org/DS (alg 7, id 17883): 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.

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