SSL-Tools

SSL check results of relay.acs-cloud.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for relay.acs-cloud.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 Tue, 15 Jul 2025 12:04:24 +0000

The mailservers of relay.acs-cloud.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @relay.acs-cloud.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
relay.acs-cloud.de
212.99.205.58
 -
supported
relay.acs-cloud.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
4 s
relay.acs-cloud.de
2a05:1740:10:55::587
 -
supported
relay.acs-cloud.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
8 s

Outgoing Mails

We have not received any emails from a @relay.acs-cloud.de address so far. Test mail delivery

Certificates

First seen at:

CN=relay.acs-cloud.de

Certificate chain
  • relay.acs-cloud.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • relay.acs-cloud.de
Alternative Names
  • autoconfig.acs-cloud.de
  • autodiscover.acs-cloud.de
  • relay.acs-cloud.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-06-20
Not valid after
2025-09-18
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
47:EF:A9:71:42:5C:80:12:7A:DB:90:8E:4A:BE:EA:AB:BF:EA:14:30:6E:50:8A:69:AC:23:70:2D:A5:1B:5F:66
SHA1
D3:4A:BB:4A:84:67:40:77:CE:A3:0A:7E:73:52:A4:BA:88:3B:B8:A9
X509v3 extensions
subjectKeyIdentifier
  • 20:03:66:75:E0:49:A6:D0:6E:A3:C0:74:DB:C2:63:E7:BF:04:EF:48
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/37.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7D:59:1E:12:E1:78:2A:7B:1C:61:67:7C:5E:FD:F8:D0:
  • 87:5C:14:A0:4E:95:9E:B9:03:2F:D9:0E:8C:2E:79:B8
  • Timestamp : Jun 20 14:30:03.417 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:F3:CF:4E:9D:DE:7F:F4:A3:B5:43:E6:
  • 9F:98:64:FA:E4:5C:54:EF:46:05:CE:3B:53:66:D6:35:
  • A8:3C:CC:30:F2:02:21:00:C0:84:76:B5:E8:C6:05:25:
  • 97:1A:3D:BF:8C:61:CD:7A:B7:3A:54:47:A8:33:5F:5C:
  • 31:DF:88:03:F7:BB:48:E2
  • 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 20 14:30:03.418 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:A5:E4:8F:DA:02:E3:FC:55:DE:44:28:
  • F0:9A:73:53:C1:38:BD:CB:7E:8F:EB:C0:7C:69:AD:7C:
  • 9C:7A:76:EC:63:02:21:00:AA:59:CE:D6:E5:76:09:0D:
  • D7:D5:9C:5D:FE:B5:AD:A3:26:A1:12:3D:7B:ED:A1:60:
  • 07:10:28:B2:5B:43:AD:51