tutanota.com

Updated: 2020-09-17 05:27:22 UTC (1481 days ago) Go to most recent »

DNSSEC options (hide)

|?| RR types:
|?| DNSSEC algorithms:
|?| DS digest algorithms:
|?| Denial of existence:
|?| Redundant edges:
|?| Ignore RFC 8624:
|?| Ignore RFC 9276:
|?| Multi-signer:
|?| Trust anchors:
- Root zone KSK
|?| Additional trusted keys:

Notices

DNSSEC Authentication Chain

RRset status

Bogus (6)

tutanota.com/A
tutanota.com/AAAA
tutanota.com/MX
tutanota.com/NS
tutanota.com/SOA
tutanota.com/TXT

DNSKEY/DS/NSEC status

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 status

Bogus (1)

com to tutanota.com

Secure (1)

. to com

Notices

Errors (11)

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. (205.251.193.126, 205.251.195.43, 205.251.196.52, 205.251.198.178, 2600:9000:5301:7e00::1, 2600:9000:5303:2b00::1, 2600:9000:5304:3400::1, 2600:9000:5306:b200::1, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_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. (205.251.193.126, 205.251.195.43, 205.251.196.52, 205.251.198.178, 2600:9000:5301:7e00::1, 2600:9000:5303:2b00::1, 2600:9000:5304:3400::1, 2600:9000:5306:b200::1, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
tutanota.com/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (205.251.193.126, 205.251.195.43, 205.251.196.52, 205.251.198.178, 2600:9000:5301:7e00::1, 2600:9000:5303:2b00::1, 2600:9000:5304:3400::1, 2600:9000:5306:b200::1, UDP_-_EDNS0_4096_D_K)
tutanota.com/AAAA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (205.251.193.126, 205.251.195.43, 205.251.196.52, 205.251.198.178, 2600:9000:5301:7e00::1, 2600:9000:5303:2b00::1, 2600:9000:5304:3400::1, 2600:9000:5306:b200::1, UDP_-_EDNS0_4096_D_K)
tutanota.com/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (205.251.193.126, 205.251.195.43, 205.251.196.52, 205.251.198.178, 2600:9000:5301:7e00::1, 2600:9000:5303:2b00::1, 2600:9000:5304:3400::1, 2600:9000:5306:b200::1, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
tutanota.com/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (205.251.193.126, 205.251.195.43, 205.251.196.52, 205.251.198.178, 2600:9000:5301:7e00::1, 2600:9000:5303:2b00::1, 2600:9000:5304:3400::1, 2600:9000:5306:b200::1, UDP_-_EDNS0_4096_D_K)
tutanota.com/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (205.251.193.126, 205.251.195.43, 205.251.196.52, 205.251.198.178, 2600:9000:5301:7e00::1, 2600:9000:5303:2b00::1, 2600:9000:5304:3400::1, 2600:9000:5306:b200::1, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
tutanota.com/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (205.251.193.126, 205.251.195.43, 205.251.196.52, 205.251.198.178, 2600:9000:5301:7e00::1, 2600:9000:5303:2b00::1, 2600:9000:5304:3400::1, 2600:9000:5306:b200::1, UDP_-_EDNS0_4096_D_K)
tutanota.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
tutanota.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
q14z57mcbe.tutanota.com/A has errors; select the "Denial of existence" DNSSEC option to see them.

Warnings (1)

com to tutanota.com: Authoritative AAAA records exist for ns-382.awsdns-47.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.