View on GitHub

DNSViz: A DNS visualization tool

tutanota.com

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

RRset statusRRset status

Bogus (6)
  • tutanota.com/A
  • tutanota.com/AAAA
  • tutanota.com/MX
  • tutanota.com/NS
  • tutanota.com/SOA
  • tutanota.com/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (2)
  • tutanota.com/DNSKEY (alg 10, id 3457)
  • tutanota.com/DNSKEY (alg 10, id 35475)
Secure (10)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46594)
  • com/DNSKEY (alg 8, id 24966)
  • com/DNSKEY (alg 8, id 30909)
  • com/DS (alg 8, id 30909)
  • tutanota.com/DS (alg 10, id 14901)
  • tutanota.com/DS (alg 10, id 17764)
  • tutanota.com/DS (alg 10, id 50241)
  • tutanota.com/DS (alg 10, id 51433)
  • tutanota.com/DS (alg 10, id 594)
Non_existent (5)
  • tutanota.com/DNSKEY (alg 10, id 14901)
  • tutanota.com/DNSKEY (alg 10, id 17764)
  • tutanota.com/DNSKEY (alg 10, id 50241)
  • tutanota.com/DNSKEY (alg 10, id 51433)
  • tutanota.com/DNSKEY (alg 10, id 594)

Delegation statusDelegation status

Bogus (1)
  • com to tutanota.com
Secure (1)
  • . to com

NoticesNotices

Errors (4)
  • com to tutanota.com: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (185.119.136.14, 2a01:5b0:8::e, UDP_-_EDNS0_4096_D_K)
  • com to tutanota.com: The DS RRset for the zone included algorithm 10 (RSASHA512), but no DS RR matched a DNSKEY with algorithm 10 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (185.119.136.14, 2a01:5b0:8::e, UDP_-_EDNS0_4096_D_K)
  • i85mrds64f.tutanota.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • tutanota.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (11)
  • RRSIG tutanota.com/A alg 10, id 35475: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG tutanota.com/AAAA alg 10, id 35475: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG tutanota.com/DNSKEY alg 10, id 3457: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG tutanota.com/DNSKEY alg 10, id 3457: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG tutanota.com/MX alg 10, id 35475: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG tutanota.com/NS alg 10, id 35475: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG tutanota.com/SOA alg 10, id 35475: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG tutanota.com/TXT alg 10, id 35475: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • i85mrds64f.tutanota.com/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • tutanota.com/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • tutanota.com/DNSKEY 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