SSL check results of finn.io

NEW You can also bulk check multiple servers.

Discover if the mail servers for finn.io can be reached through a secure connection.

To establish a secure connection a mail server has to offer STARTTLS (SSL), a trustworthy SSL certificate, support for the Diffie-Hellman-Algorithm to guarantee Perfect Forward Secrecy and must not be vulnerable against the Heartbleed attack. Futhermore we recommend using end-to-end encryption with GnuPG.

Summary

Report created Tue, 11 Dec 2018 20:44:54 +0000

The mailservers of finn.io can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @finn.io addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.seattlemesh.net
2001:41d0:1:e20d::1
1
supported
mail.seattlemesh.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
12 s
mail.seattlemesh.net
91.121.161.13
1
supported
mail.seattlemesh.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
12 s

Outgoing Mails

We have received emails from these servers with @finn.io sender addresses. Test mail delivery

Host TLS Version & Cipher
q.meshwith.me (91.121.161.13)
Insecure - not encrypted!

Certificates

First seen at:

CN=mail.seattlemesh.net

Certificate chain
Subject
Common Name (CN)
  • mail.seattlemesh.net
Alternative Names
  • autoconfig.acceleratenetworks.com
  • autoconfig.badzik.me
  • autoconfig.callpipe.com
  • autoconfig.finn.io
  • autoconfig.hoes.io
  • autoconfig.meshwith.me
  • autoconfig.octothorpe.club
  • autoconfig.seattlemesh.net
  • autoconfig.tomesh.net
  • autoconfig.uwave.fm
  • imap.seattlemesh.net
  • mail.badzik.me
  • mail.seattlemesh.net
  • mail.uwave.fm
  • mta-sts.finn.io
  • mta-sts.janky.solutions
  • pop.seattlemesh.net
  • q.meshwith.me
  • test.mail.meshwith.me
  • webmail.meshwith.me
  • webmail.tomesh.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2018-12-06
Not valid after
2019-03-06
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
6F:F3:E1:C8:EF:BD:40:E3:0B:7B:4D:82:5E:A0:B3:61:70:77:44:D3:A1:3B:60:5C:70:0F:02:04:4E:BD:4E:79
SHA1
62:A7:5A:19:A5:6A:63:1E:8F:D8:C0:B2:B0:C8:39:89:E8:95:DB:BF
X509v3 extensions
subjectKeyIdentifier
  • DA:50:3F:23:81:FD:05:DE:25:AD:AF:D4:57:63:E0:00:C3:D8:26:73
authorityKeyIdentifier
  • keyid:A8:4A:6A:63:04:7D:DD:BA:E6:D1:39:B7:A6:45:65:EF:F3:A8:EC:A1
authorityInfoAccess
  • OCSP - URI:http://ocsp.int-x3.letsencrypt.org
  • CA Issuers - URI:http://cert.int-x3.letsencrypt.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 55:81:D4:C2:16:90:36:01:4A:EA:0B:9B:57:3C:53:F0:
  • C0:E4:38:78:70:25:08:17:2F:A3:AA:1D:07:13:D3:0C
  • Timestamp : Dec 6 20:00:36.909 2018 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:54:43:26:BA:BE:A3:8C:B2:BB:15:45:B7:
  • 93:24:76:A0:4C:28:CA:A1:F4:AF:84:55:D0:A1:63:3B:
  • 54:49:57:51:02:21:00:C2:8B:96:45:65:DE:97:E4:DB:
  • DB:91:A6:59:7D:A4:33:AF:FC:E7:56:DE:64:F5:19:6B:
  • E2:38:E3:68:2F:21:16
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 63:F2:DB:CD:E8:3B:CC:2C:CF:0B:72:84:27:57:6B:33:
  • A4:8D:61:77:8F:BD:75:A6:38:B1:C7:68:54:4B:D8:8D
  • Timestamp : Dec 6 20:00:36.430 2018 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:93:E1:79:6D:1D:E8:6E:DD:D7:BB:6E:
  • F5:87:EC:64:17:50:B7:59:36:12:96:47:3D:4A:FF:32:
  • 58:A7:DE:5A:CC:02:21:00:CC:94:DE:3A:CC:05:AE:B8:
  • 1B:A7:86:75:AE:FF:C0:CE:A1:C6:EF:4D:D2:27:E9:3E:
  • 48:33:5B:B3:06:B5:83:64