SSL check results of famcloud.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for famcloud.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 Thu, 25 May 2023 08:21:57 +0000

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

Servers

Incoming Mails

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

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

Outgoing Mails

We have received emails from these servers with @famcloud.de sender addresses. Test mail delivery

Host TLS Version & Cipher
mail.famcloud.de (37.120.165.109)
TLSv1.3 TLS_AES_256_GCM_SHA384

Certificates

First seen at:

CN=mail.famcloud.de

Certificate chain
  • mail.famcloud.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.famcloud.de
Alternative Names
  • mail.famcloud.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2023-04-04
Not valid after
2023-07-03
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
3B:0E:A0:A8:26:B6:7B:91:39:A5:23:46:FD:A3:0A:D7:2F:A5:6E:5F:C4:9D:DA:B3:29:47:B2:B1:CB:39:31:01
SHA1
16:B0:86:06:D4:FF:AC:EF:DD:17:06:80:49:CD:AE:63:8F:51:51:6C
X509v3 extensions
subjectKeyIdentifier
  • 55:C2:5E:D0:2D:89:FA:96:8C:41:75:FB:75:6A:82:EC:BA:E8:9C:84
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
  • 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 : B7:3E:FB:24:DF:9C:4D:BA:75:F2:39:C5:BA:58:F4:6C:
  • 5D:FC:42:CF:7A:9F:35:C4:9E:1D:09:81:25:ED:B4:99
  • Timestamp : Apr 4 08:29:56.200 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:2C:89:91:E5:D8:99:AE:01:65:5A:F0:B6:
  • 60:1B:C7:94:DF:97:E1:23:D7:AA:27:61:49:47:09:00:
  • E5:98:B9:F1:02:21:00:FD:E3:8B:51:29:83:C8:0B:C3:
  • 03:E6:7B:2B:7F:45:52:22:F7:23:E1:16:55:B4:50:2A:
  • BE:8A:17:35:B4:3E:41
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7A:32:8C:54:D8:B7:2D:B6:20:EA:38:E0:52:1E:E9:84:
  • 16:70:32:13:85:4D:3B:D2:2B:C1:3A:57:A3:52:EB:52
  • Timestamp : Apr 4 08:29:56.208 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:54:EB:5B:BA:5C:72:52:22:DC:BB:0E:D5:
  • 66:02:BB:76:FA:A2:06:38:F0:03:4C:84:1D:21:33:AB:
  • 3C:74:5A:D0:02:20:25:D6:2C:A3:97:A7:EB:D5:71:B2:
  • E7:41:EF:F8:D7:EA:6D:02:65:26:B5:72:C5:5D:C5:73:
  • 31:57:13:30:94:10