SSL check results of server.clemens-mauritius.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for server.clemens-mauritius.de 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 Fri, 12 Oct 2018 12:42:34 +0000

The mailservers of server.clemens-mauritius.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @server.clemens-mauritius.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
server.clemens-mauritius.de
138.201.245.196
-
supported
kommit.clemens-mauritius.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
server.clemens-mauritius.de
2a01:4f8:c17:5a0c::2
-
supported
kommit.clemens-mauritius.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

We have not received any emails from a @server.clemens-mauritius.de address so far. Test mail delivery

Certificates

First seen at:

CN=kommit.clemens-mauritius.de

Certificate chain
Subject
Common Name (CN)
  • kommit.clemens-mauritius.de
Alternative Names
  • kommit.clemens-mauritius.de
  • m.clemens-mauritius.de
  • newsletter.clemens-mauritius.de
  • server.clemens-mauritius.de
  • www.clemens-mauritius.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2018-08-27
Not valid after
2018-11-25
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
15:30:88:F4:23:50:34:5C:B5:7B:7C:25:B5:DE:1C:5C:D5:CE:7E:7F:16:10:7B:AC:CB:81:A5:F4:AD:49:BE:F2
SHA1
40:9E:F6:AD:D7:AB:65:4A:00:53:B0:CB:69:40:75:3C:B2:D2:23:9F
X509v3 extensions
subjectKeyIdentifier
  • FA:A6:4E:BC:75:43:01:EA:95:65:0E:1F:63:35:DC:04:12:1B:E9:22
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
  • User Notice:
  • Explicit Text: This Certificate may only be relied upon by Relying Parties and only in accordance with the Certificate Policy found at https://letsencrypt.org/repository/
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 : Aug 27 19:47:18.471 2018 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:AB:F0:CF:DC:3C:86:32:96:66:96:AC:
  • 14:D3:AA:50:D2:E4:AB:90:DC:C2:10:EE:00:2B:F0:62:
  • 0B:2D:CA:AA:B6:02:20:39:1B:B9:F0:42:D2:D5:D0:16:
  • 05:FA:C5:F9:70:4F:10:74:BB:B4:80:F3:DB:84:E0:CB:
  • 8C:7C:33:D2:E4:74:4A
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 29:3C:51:96:54:C8:39:65:BA:AA:50:FC:58:07:D4:B7:
  • 6F:BF:58:7A:29:72:DC:A4:C3:0C:F4:E5:45:47:F4:78
  • Timestamp : Aug 27 19:47:18.436 2018 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:E8:C2:E9:AF:A9:53:1D:E4:AB:0F:B0:
  • E1:E6:81:B1:41:B7:40:26:F5:61:90:0D:AC:1A:E2:08:
  • 15:E2:30:2E:90:02:21:00:C7:AC:B5:E3:81:1A:24:A6:
  • C5:1E:09:A9:CB:4F:73:E3:78:CC:FF:D8:69:DA:F9:10:
  • 3C:C7:B7:00:8A:11:2E:39