SSL-Tools

SSL check results of swhosting.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for swhosting.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 Sat, 27 Jul 2024 00:30:24 +0000

We can not guarantee a secure connection to the mailservers of swhosting.com!

Please contact the operator of swhosting.com and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/swhosting.com

Servers

Incoming Mails

These servers are responsible for incoming mails to @swhosting.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.swhosting.com
81.25.112.69
 10
supported
mail.swhosting.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s
mailaux.swhosting.com
107.170.129.134
Results incomplete
20
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.swhosting.com

Certificate chain
  • mail.swhosting.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.swhosting.com
Alternative Names
  • mail.swhosting.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2024-06-30
Not valid after
2024-09-28
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
9C:3C:27:91:84:4E:63:A4:AE:BE:32:26:30:5E:EF:E8:FA:85:43:33:69:58:9A:61:8A:2C:F1:E7:D5:4D:8F:3C
SHA1
23:1C:6D:27:2C:99:CF:93:84:80:51:A1:2E:57:CB:8B:11:43:FA:C3
X509v3 extensions
subjectKeyIdentifier
  • D2:81:48:DD:CA:EC:89:41:C5:05:E7:00:CB:9F:15:D7:17:A1:BA:F2
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
  • ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
  • Timestamp : Jun 30 22:59:10.946 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:08:E0:70:74:43:A7:0C:6D:AA:7F:66:5C:
  • 1C:1E:65:BC:3D:16:D0:92:99:EF:27:67:BB:4D:2D:64:
  • BE:7C:9D:D4:02:21:00:90:DC:5C:CC:2C:45:E9:34:8A:
  • 46:59:AF:A4:72:90:B8:22:6B:C1:FB:20:A7:93:3A:5C:
  • 8E:6C:1D:11:30:BB:F4
  • 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 : Jun 30 22:59:12.949 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:65:CB:42:75:9F:EC:32:BA:63:A1:EB:1F:
  • CB:EE:91:D0:53:BB:B2:94:01:54:5A:08:30:EE:68:98:
  • 85:B8:D5:86:02:20:25:3B:ED:B9:E9:A6:01:F4:17:58:
  • 6C:4E:73:F2:31:C7:71:E3:9C:47:A5:9F:71:93:19:9A:
  • AE:8B:1C:4A:74:69