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 Fri, 09 Feb 2024 20:02:06 +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
2024-01-30
Not valid after
2024-04-29
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
2E:09:EA:15:27:C3:97:F5:0D:38:62:C2:B1:7A:3E:F2:96:9A:39:FA:91:D0:04:A1:F0:55:0D:0C:A4:36:51:3C
SHA1
41:84:BC:94:E9:FD:89:58:1E:2F:1D:BE:F9:B8:FE:86:D5:AC:11:96
X509v3 extensions
subjectKeyIdentifier
  • A5:73:40:E0:65:D1:AD:71:BB:0B:55:4C:B4:C5:7F:3C:5F:58:E8:B8
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 : A2:E2:BF:D6:1E:DE:2F:2F:07:A0:D6:4E:6D:37:A7:DC:
  • 65:43:B0:C6:B5:2E:A2:DA:B7:8A:F8:9A:6D:F5:17:D8
  • Timestamp : Jan 30 07:01:54.278 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:F4:D6:1C:4F:F5:00:02:A9:15:A2:C5:
  • FC:AC:2C:39:6C:D9:F2:FD:F7:96:EF:FD:07:38:9E:E4:
  • EA:30:E1:70:5D:02:21:00:EC:2E:DE:EC:A5:C5:B7:7F:
  • 92:8D:8B:D5:96:A4:E3:D2:0D:12:D6:59:FB:80:2F:5D:
  • 3C:94:03:27:9E:C5:DB:7E
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
  • B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
  • Timestamp : Jan 30 07:01:54.374 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:2C:C4:CF:73:EE:BB:89:8A:2D:BC:0D:CB:
  • 02:B1:B5:38:F3:04:D7:42:FD:61:05:C4:86:92:79:EA:
  • 86:01:73:A4:02:21:00:E3:71:97:E1:26:FB:BD:62:28:
  • F4:9F:60:15:CC:8F:EB:72:58:D2:EE:04:B8:29:69:A3:
  • BB:9E:ED:FC:A1:1D:14