SSL check results of wischmann-fahrzeugbau.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for wischmann-fahrzeugbau.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, 08 Nov 2025 01:30:27 +0000

The mailservers of wischmann-fahrzeugbau.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @wischmann-fahrzeugbau.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
wischmann-fahrzeugbau-de.mail.cloud.nospamproxy.com
193.37.132.171
5
supported
*.mail.cloud.nospamproxy.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
wischmann-fahrzeugbau-de.mail.cloud.nospamproxy.com
193.37.132.131
5
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 @wischmann-fahrzeugbau.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

      • 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-10-08
Not valid after
2026-01-06
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
0A:22:CD:D1:33:A4:8D:76:43:08:45:54:70:9B:0D:09:55:3D:DD:D9:04:5E:59:16:73:5E:A0:0F:19:75:7D:75
SHA1
DA:8B:BA:FD:F6:CB:57:82:BE:46:29:F7:6E:3F:A0:24:F1:AD:33:71
X509v3 extensions
subjectKeyIdentifier
  • 3C:C4:7B:D7:94:91:FB:B5:D0:1A:2F:09:A4:13:FB:A7:DB:96:59:20
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/115.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 : Oct 8 08:23:15.996 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:D0:12:DB:DC:2E:2D:CF:7A:5C:6B:01:
  • B8:1D:26:2D:40:32:C2:F7:DE:09:9F:09:46:EB:3A:CB:
  • A2:77:2E:1C:89:02:21:00:B4:F6:15:80:12:5B:BE:BA:
  • 30:A4:ED:03:AE:D3:AF:45:21:53:4E:44:22:2F:A4:CC:
  • 07:E6:C3:BD:03:8D:25:F8
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 19:86:D4:C7:28:AA:6F:FE:BA:03:6F:78:2A:4D:01:91:
  • AA:CE:2D:72:31:0F:AE:CE:5D:70:41:2D:25:4C:C7:D4
  • Timestamp : Oct 8 08:23:18.008 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:2C:32:87:94:97:58:96:6E:40:3E:83:51:
  • A6:4F:21:EE:0C:4E:46:75:E2:AF:03:FB:2B:B2:4E:65:
  • 81:6B:86:0A:02:21:00:83:A0:F7:C1:7B:16:AD:26:D3:
  • 7D:53:B4:EA:0C:E6:51:82:26:1B:EA:63:5D:53:CB:E5:
  • 59:41:E5:89:A6:9B:E4