SSL-Tools

SSL check results of fawice.han-solo.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for fawice.han-solo.net 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 Wed, 09 Jul 2025 00:30:18 +0000

The mailservers of fawice.han-solo.net can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @fawice.han-solo.net addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.fawice.han-solo.net
83.138.84.231
 0
supported
fawice.han-solo.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
16 s
mail.fawice.han-solo.net
83.138.84.231
 10
supported
fawice.han-solo.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
16 s

Outgoing Mails

We have not received any emails from a @fawice.han-solo.net address so far. Test mail delivery

Certificates

First seen at:

CN=fawice.han-solo.net

Certificate chain
  • fawice.han-solo.net
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • fawice.han-solo.net
Alternative Names
  • fawice.han-solo.net
  • mail.fawice.han-solo.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-06-11
Not valid after
2025-09-09
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
CA:C9:09:91:24:47:C8:74:0C:F9:8D:C4:79:7F:8D:4F:D2:F8:9D:DC:32:97:9F:55:C3:3E:7E:3C:3F:C8:85:7E
SHA1
E8:C6:B5:F9:65:D0:E4:F3:DC:9A:E6:86:05:F7:BE:A7:3D:97:E2:EF
X509v3 extensions
subjectKeyIdentifier
  • 64:DD:B2:47:D2:FC:F9:94:74:B5:B3:92:F1:88:E1:90:20:2A:E8:01
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r11.c.lencr.org/27.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : Jun 11 08:54:23.824 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:B3:BF:29:25:8A:B0:32:9E:17:A1:95:
  • 00:CC:92:9A:FF:D7:DF:02:CF:75:46:23:64:77:D0:FE:
  • 16:C4:A8:DB:12:02:20:3D:DC:EE:95:52:AC:3B:9F:A6:
  • 52:99:5E:05:4F:0C:62:5C:4B:B8:F4:9B:2C:30:C9:E0:
  • 45:F8:25:2B:0F:09:2E
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 0D:E1:F2:30:2B:D3:0D:C1:40:62:12:09:EA:55:2E:FC:
  • 47:74:7C:B1:D7:E9:30:EF:0E:42:1E:B4:7E:4E:AA:34
  • Timestamp : Jun 11 08:54:23.807 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:2F:A7:83:E9:2F:9D:AC:94:DA:5D:2B:D6:
  • 31:4F:49:2B:6D:1D:94:B0:9C:F1:03:8F:A5:E1:D7:3B:
  • 51:85:6F:36:02:20:66:C2:43:6F:C0:2D:66:57:EA:7A:
  • BC:2A:56:7F:E9:81:E9:03:22:CC:44:10:B6:CC:47:D0:
  • 85:8B:02:04:96:47