SSL check results of emcare.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for emcare.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 Sat, 16 Aug 2025 00:30:07 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mx1.emcare.de
109.233.139.211
15
supported
mx1.emcare.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=mx1.emcare.de

Certificate chain
  • mx1.emcare.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)
  • mx1.emcare.de
Alternative Names
  • mx1.emcare.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-06-02
Not valid after
2025-08-31
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
36:15:FB:69:0C:18:FD:95:45:51:09:25:FA:7B:F2:1B:EB:14:D8:09:58:FC:25:F7:63:AB:54:B1:00:4E:E9:2E
SHA1
22:E2:23:81:48:55:70:1E:35:F1:28:9A:1F:0D:5B:73:B6:6A:9A:33
X509v3 extensions
subjectKeyIdentifier
  • A1:C5:29:14:9F:EC:1B:1F:90:0C:24:A1:EC:38:C2:6C:35:9C:74:FB
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/124.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : ED:3C:4B:D6:E8:06:C2:A4:A2:00:57:DB:CB:24:E2:38:
  • 01:DF:51:2F:ED:C4:86:C5:70:0F:20:DD:B7:3E:3F:E0
  • Timestamp : Jun 2 08:37:36.495 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:10:8F:99:10:85:D6:55:A3:A0:8E:16:90:
  • E1:FD:16:2F:0F:A5:08:D0:73:FF:D3:D1:23:91:F6:A1:
  • 3C:1D:A9:E0:02:21:00:9F:1D:F0:C5:64:94:23:C6:7A:
  • 24:E1:A9:61:48:9E:54:ED:03:AF:F9:B4:5F:AD:9B:CD:
  • C0:76:B5:BB:8F:4D:36
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DD:DC:CA:34:95:D7:E1:16:05:E7:95:32:FA:C7:9F:F8:
  • 3D:1C:50:DF:DB:00:3A:14:12:76:0A:2C:AC:BB:C8:2A
  • Timestamp : Jun 2 08:37:36.572 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:5B:02:AE:12:B9:21:68:E6:7B:9D:F3:FF:
  • 79:5B:3E:2E:86:42:81:9E:95:81:BF:4E:85:F3:5B:93:
  • 80:59:B6:1C:02:20:66:D2:49:B0:45:7F:8A:E9:C6:42:
  • 03:DD:C2:54:0A:8D:A6:FC:DB:F6:D7:67:99:E9:C2:60:
  • AB:A3:F3:BB:90:37