SSL-Tools

SSL check results of coxalo.han-solo.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for coxalo.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 Thu, 10 Jul 2025 14:54:45 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.coxalo.han-solo.net
83.138.82.165
 0
supported
coxalo.han-solo.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
16 s
mail.coxalo.han-solo.net
83.138.82.165
 10
supported
coxalo.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 @coxalo.han-solo.net address so far. Test mail delivery

Certificates

First seen at:

CN=coxalo.han-solo.net

Certificate chain
  • coxalo.han-solo.net
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • coxalo.han-solo.net
Alternative Names
  • coxalo.han-solo.net
  • mail.coxalo.han-solo.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-07-01
Not valid after
2025-09-29
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
A3:41:DF:79:3A:30:E3:BC:79:05:F4:ED:41:D2:7F:97:DA:10:D2:9F:F6:1E:AC:CE:51:46:3D:61:AA:EF:C0:9D
SHA1
4D:20:8E:E6:7C:8C:BB:FD:35:30:BE:DF:31:36:81:06:86:CD:01:5D
X509v3 extensions
subjectKeyIdentifier
  • 55:B0:CD:24:F1:82:0C:66:70:53:F0:E0:C6:A3:04:BC:D6:9E:F8:87
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r10.c.lencr.org/87.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 12:F1:4E:34:BD:53:72:4C:84:06:19:C3:8F:3F:7A:13:
  • F8:E7:B5:62:87:88:9C:6D:30:05:84:EB:E5:86:26:3A
  • Timestamp : Jul 1 09:25:19.139 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:DD:9A:87:AF:ED:4B:BA:40:AB:B7:D2:
  • CB:39:BF:55:84:00:C8:2C:CA:F4:39:BE:07:A5:B0:B3:
  • AA:E8:93:07:4C:02:21:00:B8:C7:16:FE:E6:A6:80:A1:
  • BA:15:AC:1C:9B:E0:A9:94:41:07:F6:19:04:DB:53:F6:
  • 26:63:9D:AA:C6:FD:FC:91
  • 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 : Jul 1 09:25:21.139 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:2B:9C:39:80:A2:B3:F3:13:BF:EB:31:91:
  • 25:9A:20:D4:7C:82:6B:F6:50:87:20:59:11:BA:08:2E:
  • 15:A7:A0:77:02:20:6E:32:3E:11:27:2F:6C:95:12:96:
  • 33:63:91:16:4B:32:95:B5:BE:C5:19:45:32:93:8F:F1:
  • 39:2E:BF:0A:38:22