SSL-Tools

SSL check results of freifunk-muensterland.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for freifunk-muensterland.net 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

JSON Refresh

Report created Sun, 19 Jul 2020 18:08:04 +0000

The mailservers of freifunk-muensterland.net can be reached through an encrypted connection.

However, we found problems that may affect the security.

Servers

Incoming Mails

These servers are responsible for incoming mails to @freifunk-muensterland.net addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.freifunk-muensterland.de
2a01:4f8:191:21e1::af
 10
supported
mail.freifunk-muensterland.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
supported
  • SSL_RSA_WITH_RC4_128_SHA
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
16 s
mail.freifunk-muensterland.de
148.251.208.169
 10
supported
mail.freifunk-muensterland.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
supported
  • SSL_RSA_WITH_RC4_128_SHA
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
16 s

Outgoing Mails

We have not received any emails from a @freifunk-muensterland.net address so far. Test mail delivery

Certificates

First seen at:

CN=mail.freifunk-muensterland.de

Certificate chain
Subject
Common Name (CN)
  • mail.freifunk-muensterland.de
Alternative Names
  • mail.freifunk-muensterland.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2020-07-12
Not valid after
2020-10-10
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
AE:63:D3:BF:8C:19:4F:58:23:58:6B:6C:46:C9:50:FB:37:3E:46:38:63:9B:7A:C4:98:5A:85:1A:43:BC:3F:FC
SHA1
7A:A2:50:0C:10:13:03:E4:99:ED:2D:9A:F3:A7:57:BD:59:6E:89:3A
X509v3 extensions
subjectKeyIdentifier
  • F9:8E:8E:DD:99:95:24:9B:82:51:1A:4B:EA:86:0D:2A:5B:C2:07:E9
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 : 07:B7:5C:1B:E5:7D:68:FF:F1:B0:C6:1D:23:15:C7:BA:
  • E6:57:7C:57:94:B7:6A:EE:BC:61:3A:1A:69:D3:A2:1C
  • Timestamp : Jul 12 04:47:15.625 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:AC:0E:FB:AD:F2:42:D6:63:12:3D:0C:
  • 91:E8:C0:62:FE:98:2A:18:B6:AA:22:11:CC:00:B5:49:
  • FF:04:DD:C5:01:02:20:42:F0:A2:21:2D:BC:85:D2:30:
  • 26:D3:EB:8B:D8:0F:B7:34:1A:6C:D6:03:4F:B7:41:CA:
  • E3:26:0F:42:88:8D:72
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
  • 15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
  • Timestamp : Jul 12 04:47:15.848 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:FC:CD:43:00:C5:65:3C:26:D8:47:89:
  • 0F:96:DE:1F:E3:59:B3:88:60:6B:A0:EE:60:65:E6:3E:
  • 59:2E:E3:F6:3B:02:21:00:EC:FF:E7:B6:4E:D5:65:5D:
  • 20:C9:B5:29:A9:E1:98:39:14:C1:40:14:07:A3:AC:6D:
  • 8F:73:82:72:1D:F0:88:77