SSL-Tools

SSL check results of wfgsha.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for wfgsha.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 Sat, 23 Nov 2024 01:30:38 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
wfgsha-de.mail.cloud.nospamproxy.com
178.212.92.204
 10
supported
*.mail.cloud.nospamproxy.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
wfgsha-de.mail.cloud.nospamproxy.com
193.37.132.36
 10
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 @wfgsha.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
2024-09-08
Not valid after
2024-12-07
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
1A:42:BB:6A:99:DA:50:41:DB:FE:17:7F:F4:86:A3:FC:AC:D3:82:C8:26:07:2B:0D:08:12:FD:67:C3:AA:21:F1
SHA1
A4:51:5A:D3:E7:2E:BE:F8:27:C3:8E:1B:5C:B9:86:17:FB:64:A5:AD
X509v3 extensions
subjectKeyIdentifier
  • 5A:2C:2E:E4:14:56:94:32:D1:57:B8:F3:D3:F0:45:55:A0:4A:87:9C
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : Sep 8 07:19:28.242 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:9D:1C:1F:15:CB:52:EC:0F:62:AA:AC:
  • 48:47:03:EE:E1:35:EA:64:63:05:AC:B7:A2:97:96:C3:
  • 97:D0:4A:F0:EC:02:20:2F:4B:02:A2:88:E9:D5:1D:89:
  • 4A:22:BC:5C:26:A1:53:70:FE:41:5F:3E:EF:F2:7E:EC:
  • AF:AE:BA:E4:1C:2C:0E
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DF:E1:56:EB:AA:05:AF:B5:9C:0F:86:71:8D:A8:C0:32:
  • 4E:AE:56:D9:6E:A7:F5:A5:6A:01:D1:C1:3B:BE:52:5C
  • Timestamp : Sep 8 07:19:28.581 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:4B:5D:E6:78:71:D2:33:71:06:96:85:95:
  • FC:68:32:4F:3A:4E:E5:0E:D4:AA:B6:80:AF:11:13:30:
  • 80:8A:B6:35:02:21:00:8D:CC:59:EC:9F:A3:A9:89:7D:
  • E4:2B:44:03:33:7F:24:2F:22:DE:08:A5:EF:4A:1E:03:
  • 06:DD:28:B1:57:F0:04