SSL-Tools

SSL check results of walser-gruppe.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for walser-gruppe.com 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 Mon, 11 Dec 2023 11:23:44 +0000

The mailservers of walser-gruppe.com can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @walser-gruppe.com addresses.

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

Outgoing Mails

We have not received any emails from a @walser-gruppe.com 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
      • R3
        • 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)
  • R3
validity period
Not valid before
2023-11-13
Not valid after
2024-02-11
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
5D:4B:62:0D:1E:94:D9:24:EB:91:38:83:9C:F3:A5:34:EB:84:99:51:19:32:67:A9:C5:0C:EF:D2:12:9B:DE:0E
SHA1
89:D7:F9:45:FC:46:B4:C1:6C:4F:4A:17:73:FE:44:01:C4:F2:60:5F
X509v3 extensions
subjectKeyIdentifier
  • E7:8A:8F:18:C8:E3:6F:B0:7F:17:81:71:C1:E9:08:6E:FA:A3:DC:80
authorityKeyIdentifier
  • keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
authorityInfoAccess
  • OCSP - URI:http://r3.o.lencr.org
  • CA Issuers - URI:http://r3.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Nov 13 07:19:26.581 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:61:15:74:43:E2:46:07:D2:A7:C3:14:7F:
  • C9:45:F1:00:66:65:13:39:0A:33:63:59:DC:37:15:3F:
  • 53:CC:37:FC:02:21:00:8C:C0:81:84:FE:41:53:54:16:
  • 45:8A:A3:E7:62:E3:E7:BE:BA:C7:E7:AE:24:27:51:7C:
  • 99:B1:8C:DF:B0:81:5E
  • 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 : Nov 13 07:19:26.586 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:E5:20:E1:30:86:4D:D4:99:26:3F:3A:
  • 9E:2D:21:98:28:9C:6E:8F:35:60:18:ED:48:6C:0B:A7:
  • 9F:6C:39:69:F2:02:21:00:9D:3C:53:33:AB:E3:02:5F:
  • A9:A6:8C:21:B1:52:AF:D9:3A:98:DF:AC:C2:A9:79:A8:
  • C2:26:4A:38:49:51:F1:89