SSL-Tools

SSL check results of tempcup.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for tempcup.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, 26 Jul 2024 10:36:59 +0000

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

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

/mailservers/tempcup.de

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.tempcup.de
2a03:4000:3b:64::3
Results incomplete
10
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
mail.tempcup.de
185.163.118.62
 10
supported
mail.tempcup.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.tempcup.de

Certificate chain
  • mail.tempcup.de
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • E5
        • remaining
        • 384 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.tempcup.de
Alternative Names
  • mail.tempcup.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E5
validity period
Not valid before
2024-07-15
Not valid after
2024-10-13
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
F3:B3:57:5C:C1:47:64:32:C2:5B:BC:5F:4C:3B:D8:B3:0D:88:7F:E2:61:C3:E2:BD:33:E3:1B:C5:E1:7B:84:20
SHA1
89:A4:29:88:AA:13:51:A3:CE:BE:FD:FB:EE:DC:A7:64:A1:D6:E7:B7
X509v3 extensions
subjectKeyIdentifier
  • 88:16:0B:36:AC:2C:27:75:CD:45:8B:0C:51:13:96:83:EE:05:1F:85
authorityKeyIdentifier
  • keyid:9F:2B:5F:CF:3C:21:4F:9D:04:B7:ED:2B:2C:C4:C6:70:8B:D2:D7:0D
authorityInfoAccess
  • OCSP - URI:http://e5.o.lencr.org
  • CA Issuers - URI:http://e5.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
  • ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
  • Timestamp : Jul 15 16:07:57.200 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:43:07:6B:A8:BC:A4:1A:70:41:D1:75:A3:
  • BD:94:37:E7:3C:67:60:C4:51:20:C0:3A:F5:EC:BE:4E:
  • 28:3A:43:7C:02:21:00:84:A8:BF:A8:B8:77:A5:91:D0:
  • 9D:4B:6C:85:C9:6E:7B:E5:75:82:1D:45:C5:DC:69:6B:
  • 61:93:24:67:79:FB:14
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 19:98:10:71:09:F0:D6:52:2E:30:80:D2:9E:3F:64:BB:
  • 83:6E:28:CC:F9:0F:52:8E:EE:DF:CE:4A:3F:16:B4:CA
  • Timestamp : Jul 15 16:07:57.241 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:B5:71:E7:D3:C3:CA:00:33:F8:10:E1:
  • EF:C4:A9:81:94:BD:F1:B5:6F:AD:3A:6B:00:6A:72:4A:
  • C4:5E:71:AD:5E:02:20:29:E9:FB:71:93:B9:65:7C:B8:
  • C8:01:1F:B2:EF:60:A5:41:E8:DE:87:52:62:AA:87:F9:
  • 2D:94:10:8F:3A:40:18