SSL-Tools

SSL check results of aecust.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for aecust.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 Fri, 01 Aug 2025 00:31:27 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
aecust-de.mail.cloud.nospamproxy.com
193.37.132.131
 0
supported
*.mail.cloud.nospamproxy.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
aecust-de.mail.cloud.nospamproxy.com
193.37.132.171
 0
supported
*.mail.cloud.nospamproxy.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=*.mail.cloud.nospamproxy.com

Certificate chain
  • *.mail.cloud.nospamproxy.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • *.mail.cloud.nospamproxy.com
Alternative Names
  • *.mail.cloud.nospamproxy.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-07-05
Not valid after
2025-10-03
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
B0:CF:A9:24:34:3F:01:72:EC:25:08:EE:D7:C3:55:8D:B5:21:E8:21:DC:41:30:C6:E2:04:5A:BD:B6:C8:BE:0E
SHA1
2E:43:B4:BE:1C:26:B5:6C:B6:98:35:3C:AB:2A:C8:C0:92:49:79:D5
X509v3 extensions
subjectKeyIdentifier
  • F0:56:0A:84:FE:EB:CE:1A:2F:DC:62:56:AD:67:88:E1:6E:E6:7B:60
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/20.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : Jul 5 07:19:34.006 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:A7:62:3D:F1:D8:87:0F:CB:BF:DC:3F:
  • D6:D4:1E:48:56:21:6D:4F:54:52:35:FB:E2:42:48:E3:
  • 3D:D2:44:38:FA:02:21:00:BF:C9:C5:9F:68:62:EF:25:
  • 85:47:46:5B:B2:15:D6:47:D0:29:73:ED:79:C4:22:AE:
  • 7F:5B:92:88:BD:C4:B5:15
  • 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 : Jul 5 07:19:34.061 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:0B:99:9E:67:72:1F:14:AB:B4:F3:3F:48:
  • DD:E5:A4:9F:62:84:4B:91:01:41:4F:20:6E:95:13:5E:
  • CF:1C:C4:B6:02:21:00:CC:A3:2E:E7:6D:64:59:E7:21:
  • 96:65:D0:A8:03:7E:62:BC:1B:A1:B1:10:55:19:0F:26:
  • 78:2C:FD:34:55:CB:DA