SSL check results of helpmaster.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for helpmaster.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 Tue, 17 Feb 2026 12:26:58 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
helpmaster-de.mail.cloud.nospamproxy.com
193.37.132.131
4
supported
*.mail.cloud.nospamproxy.com
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
helpmaster-de.mail.cloud.nospamproxy.com
193.37.132.171
4
supported
*.mail.cloud.nospamproxy.com
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
office.helpmaster.de
92.50.81.34
Results incomplete
6
supported
not checked
DANE
missing
PFS
not checked
Heartbleed
not vulnerable
Weak ciphers
not checked
1 s

Outgoing Mails

We have received emails from these servers with @helpmaster.de sender addresses. Test mail delivery

Host TLS Version & Cipher
office.helpmaster.de (92.50.81.34)
TLSv1.2 ECDHE-RSA-AES256-SHA384

Certificates

First seen at:

CN=*.mail.cloud.nospamproxy.com

Certificate chain
  • *.mail.cloud.nospamproxy.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption

      • R12
        • 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)
  • R12
validity period
Not valid before
2025-12-31
Not valid after
2026-03-31
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
CE:B1:08:37:EF:45:94:D0:66:73:DD:CD:0F:F2:19:F9:C2:AC:51:15:BA:4D:7F:E0:2D:29:BB:2A:E0:86:97:16
SHA1
AC:28:33:4C:B5:A3:DD:BE:05:AF:E7:54:B7:45:ED:D7:B6:91:5F:F9
X509v3 extensions
subjectKeyIdentifier
  • 24:8F:8C:31:BE:30:3A:63:E9:92:08:1F:C1:60:4A:3E:5A:F4:FF:74
authorityKeyIdentifier
  • keyid:00:B5:29:F2:2D:8E:6F:31:E8:9B:4C:AD:78:3E:FA:DC:E9:0C:D1:D2
authorityInfoAccess
  • CA Issuers - URI:http://r12.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r12.c.lencr.org/54.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 49:9C:9B:69:DE:1D:7C:EC:FC:36:DE:CD:87:64:A6:B8:
  • 5B:AF:0A:87:80:19:D1:55:52:FB:E9:EB:29:DD:F8:C3
  • Timestamp : Dec 31 08:23:16.374 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:FC:37:B5:A8:EB:B5:A9:01:7A:AE:D9:
  • 73:DE:97:42:22:A5:2A:CA:EC:13:C9:73:CA:A7:B8:5A:
  • 92:7F:4E:3A:E5:02:21:00:DF:EC:8E:77:DC:62:32:34:
  • 73:2B:EC:C2:6F:DF:25:07:46:0D:DA:E0:49:5A:AB:0C:
  • CC:93:6E:6D:0A:6F:C2:54
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A5:C9:78:92:5D:57:46:17:82:87:0D:D8:89:66:0B:5C:
  • 55:64:8B:7D:00:40:F2:EC:07:68:51:D1:88:69:19:F7
  • Timestamp : Dec 31 08:23:16.830 2025 GMT
  • Extensions: 00:00:05:00:2D:62:7C:61
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:1C:E0:7F:A9:4E:8D:FA:EF:77:84:CE:37:
  • 95:0C:7C:9E:68:3E:84:8F:71:1B:A8:C1:EB:73:19:58:
  • 81:2C:66:3F:02:20:3C:05:A5:7B:23:36:18:A0:67:6B:
  • 00:85:8E:B2:F2:2F:1A:5B:44:75:FC:C9:67:5D:57:DB:
  • 1A:10:D4:DB:11:C1

DANE

DNS-based Authentication of Named Entities (DANE) is a protocol to allow X.509 certificates to be bound to DNS using TLSA records and DNSSEC.

Name Options DNSSEC Matches
_25._tcp.helpmaster-de.mail.cloud.nospamproxy.com
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
—
_25._tcp.helpmaster-de.mail.cloud.nospamproxy.com
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid
_25._tcp.helpmaster-de.mail.cloud.nospamproxy.com
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
—
_25._tcp.helpmaster-de.mail.cloud.nospamproxy.com
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
—
_25._tcp.helpmaster-de.mail.cloud.nospamproxy.com
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
—