SSL-Tools

SSL check results of mail.futurepace.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.futurepace.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 Wed, 24 Apr 2024 07:12:01 +0000

The mailservers of mail.futurepace.de can be reached through a secure connection.

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.futurepace.de
78.46.194.158
 -
supported
mail.futurepace.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
5 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.futurepace.de

Certificate chain
  • mail.futurepace.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.futurepace.de
Alternative Names
  • mail.futurepace.de
  • mail.schauer.org
  • shawshank.sytes.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-14
Not valid after
2024-07-13
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
98:E4:41:49:C2:90:F5:5E:89:9A:11:63:3E:5E:4C:A6:24:4F:A3:0E:1A:69:66:E2:79:08:B1:4A:05:AF:A4:81
SHA1
7E:95:B6:FE:6C:CF:30:CD:72:58:5F:13:DC:81:82:A0:92:8A:DC:8B
X509v3 extensions
subjectKeyIdentifier
  • 88:09:F9:20:DD:E0:6D:CC:BC:69:88:D7:ED:AE:28:08:55:0E:0F:EF
authorityKeyIdentifier
  • keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
authorityInfoAccess
  • OCSP - URI:http://r3.o.lencr.org
  • CA Issuers - URI:http://r3.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3B:53:77:75:3E:2D:B9:80:4E:8B:30:5B:06:FE:40:3B:
  • 67:D8:4F:C3:F4:C7:BD:00:0D:2D:72:6F:E1:FA:D4:17
  • Timestamp : Apr 14 01:17:25.987 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:A0:BC:47:31:F4:29:68:04:BB:4A:5A:
  • 83:AE:0D:58:FF:D9:1D:A0:60:A8:3B:37:9D:14:CB:C9:
  • 47:92:2A:B0:58:02:20:71:42:BF:58:4D:90:23:C1:EE:
  • 12:05:9F:28:64:60:79:73:C1:BC:A2:19:96:99:68:9A:
  • 53:34:6D:1C:12:37:9D
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DF:E1:56:EB:AA:05:AF:B5:9C:0F:86:71:8D:A8:C0:32:
  • 4E:AE:56:D9:6E:A7:F5:A5:6A:01:D1:C1:3B:BE:52:5C
  • Timestamp : Apr 14 01:17:26.230 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:C6:A0:01:69:F6:4D:AF:A4:02:7B:29:
  • C7:FC:A4:42:7D:A1:59:4B:AA:9B:36:0A:4A:1F:BE:FC:
  • 72:E9:88:2C:C1:02:21:00:D4:D1:31:AD:C0:AB:10:15:
  • 6B:F6:13:41:13:34:09:43:21:E2:F8:55:5A:13:23:69:
  • E1:3C:D5:A9:CE:75:F9:52