SSL-Tools

SSL check results of tecuplast.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for tecuplast.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

JSON Refresh

Report created Fri, 21 Jan 2022 08:19:14 +0000

We can not guarantee a secure connection to the mailservers of tecuplast.de!

Please contact the operator of tecuplast.de and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/tecuplast.de

Servers

Incoming Mails

These servers are responsible for incoming mails to @tecuplast.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.tecuplast.de
135.181.88.124
Results incomplete
10
supported
not checked
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
cmx.secutray.com
85.10.211.203
 30
supported
cmx.rapidware.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
supported
  • ECDHE_RSA_WITH_RC4_128_SHA
  • SSL_RSA_WITH_RC4_128_SHA
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
11 s

Outgoing Mails

We have not received any emails from a @tecuplast.de address so far. Test mail delivery

Certificates

First seen at:

CN=cmx.rapidware.de

Certificate chain
  • cmx.rapidware.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch
    • Expired
Subject
Common Name (CN)
  • cmx.rapidware.de
Alternative Names
  • cmx.rapidware.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2019-05-29
Not valid after
2019-08-27
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
C6:68:D0:65:F7:C8:3B:8C:83:84:EF:55:0B:68:45:07:36:6D:50:34:51:0E:03:52:33:BB:C6:68:06:61:61:53
SHA1
DE:B6:6C:BB:4C:16:CC:EB:3A:B8:8F:63:7F:6B:CD:06:7F:CF:5E:B4
X509v3 extensions
subjectKeyIdentifier
  • BB:BB:38:43:B6:94:EA:2D:48:4E:F5:C8:53:46:DF:B2:84:1B:98:67
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 : 74:7E:DA:83:31:AD:33:10:91:21:9C:CE:25:4F:42:70:
  • C2:BF:FD:5E:42:20:08:C6:37:35:79:E6:10:7B:CC:56
  • Timestamp : May 29 14:48:50.878 2019 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:A6:AC:62:5E:AA:90:3C:A1:2C:D0:75:
  • E4:6F:AE:39:F2:4E:FC:4D:F9:82:00:CC:29:4F:D7:83:
  • 98:28:EF:D3:16:02:20:4A:25:E0:60:8F:A5:ED:6E:DF:
  • 75:CC:70:6C:02:34:B8:61:CC:2F:BB:63:BD:9F:64:20:
  • 31:35:B1:A1:B1:CA:97
  • 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 : May 29 14:48:50.910 2019 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:D8:52:10:DB:57:20:A5:20:CD:26:41:
  • 0B:67:3F:9F:D3:55:A8:38:EE:15:11:89:E7:DA:8B:B0:
  • F7:8D:A4:B6:55:02:20:76:6D:29:3B:23:DE:D9:F1:7D:
  • 5F:F1:9B:60:F0:35:8A:4B:0D:7E:74:59:DC:87:DD:3D:
  • D6:96:82:E8:D8:FA:C6