SSL-Tools

SSL check results of flomah.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for flomah.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 Sat, 05 Jul 2025 08:56:24 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.flomah.de
2001:9e8:783a:c500:9209:d0ff:fe0a:8d63
 10
supported
flomah.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
3 s
mail.flomah.de
87.123.118.248
 10
supported
flomah.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=flomah.de

Certificate chain
  • flomah.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • flomah.de
Alternative Names
  • flomah.de
  • flomah.myds.me
  • mail.flomah.de
  • www.flomah.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-06-12
Not valid after
2025-09-10
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
0B:22:23:18:6D:B7:02:34:3F:FC:07:7A:D7:30:38:81:4D:5E:0A:BD:C6:2A:0D:E8:44:86:79:87:1E:C4:DC:AA
SHA1
3B:87:26:D5:AD:B4:07:B9:A1:50:88:16:A7:5C:05:F2:10:7F:11:14
X509v3 extensions
subjectKeyIdentifier
  • 1A:CE:BE:01:7B:0B:B3:76:1B:3D:A1:54:20:D9:3A:2A:69:A0:B5:A3
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r11.c.lencr.org/97.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 0D:E1:F2:30:2B:D3:0D:C1:40:62:12:09:EA:55:2E:FC:
  • 47:74:7C:B1:D7:E9:30:EF:0E:42:1E:B4:7E:4E:AA:34
  • Timestamp : Jun 12 16:04:55.288 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:12:F8:B3:5A:28:4D:66:16:F1:B3:35:84:
  • BA:81:0A:70:DE:1F:F5:6C:31:F5:97:33:E0:79:AA:A7:
  • B6:12:F1:E2:02:20:21:F6:51:AA:9D:AE:17:0C:15:5D:
  • 08:99:5D:35:73:77:FB:4A:74:79:B4:E0:A7:7F:DC:21:
  • C2:DA:8D:DF:AE:68
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 12:F1:4E:34:BD:53:72:4C:84:06:19:C3:8F:3F:7A:13:
  • F8:E7:B5:62:87:88:9C:6D:30:05:84:EB:E5:86:26:3A
  • Timestamp : Jun 12 16:04:55.274 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:42:2D:C5:7B:50:36:1B:71:25:DC:94:C9:
  • 0A:12:D1:E2:D9:C4:E7:19:E7:28:0B:F0:62:28:84:16:
  • 1B:32:A2:B0:02:20:04:C4:CB:90:D1:AB:93:14:16:29:
  • 4B:38:FA:95:1A:FE:30:F6:DA:7D:BD:A9:C2:06:7B:0D:
  • D2:0F:B7:9A:5A:B6