SSL-Tools

SSL check results of seeboxs.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for seeboxs.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 Tue, 11 Mar 2025 12:38:41 +0000

The mailservers of seeboxs.com can be reached through a secure connection.

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.tiboxs.com
2a01:e0a:831:7680:92b1:1cff:fe9f:c214
 10
supported
mail.tiboxs.com
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
mail.tiboxs.com
82.65.4.39
 10
supported
mail.tiboxs.com
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.tiboxs.com

Certificate chain
  • mail.tiboxs.com
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.tiboxs.com
Alternative Names
  • mail.boubou.me
  • mail.seeboxs.com
  • mail.tiboxs.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-03-11
Not valid after
2025-06-09
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
89:A2:42:5B:29:95:34:A8:B8:BA:54:33:90:8D:72:09:85:53:29:57:E8:61:1D:7E:A0:C5:28:D2:B2:4D:A7:95
SHA1
AB:4A:EF:C0:28:47:08:BD:93:F7:A0:C1:76:49:78:43:0B:C9:35:78
X509v3 extensions
subjectKeyIdentifier
  • BC:B6:23:91:9F:CA:BB:FB:BA:58:D9:A6:F6:24:D8:5A:9B:86:65:B3
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 : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Mar 11 11:42:33.137 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:C3:76:54:44:03:43:C9:FF:E6:46:C0:
  • 80:A6:68:D4:21:46:1D:95:FC:26:28:78:11:AD:6F:2F:
  • F8:06:71:94:75:02:21:00:D4:46:DF:D3:37:D8:DE:68:
  • 3A:68:9A:9F:A5:08:D4:FC:B8:A0:0E:B5:67:EA:00:AD:
  • EB:AB:E7:72:CA:C2:30:CA
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 4E:75:A3:27:5C:9A:10:C3:38:5B:6C:D4:DF:3F:52:EB:
  • 1D:F0:E0:8E:1B:8D:69:C0:B1:FA:64:B1:62:9A:39:DF
  • Timestamp : Mar 11 11:42:33.130 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:A8:A1:40:49:5A:AC:9A:BC:15:30:83:
  • 11:B4:18:69:05:33:AA:DC:17:7C:0D:18:CC:D6:66:25:
  • 79:96:08:A5:A2:02:20:01:34:39:A9:3F:DF:A3:67:B3:
  • 95:71:A7:56:61:89:11:FC:DF:08:D5:9D:DC:08:EE:31:
  • B0:67:B0:D7:D7:7D:B7

DANE

DNS-based Authentication of Named Entities (DANE) is a protocol to allow X.509 certificates to be bound to DNS using TLSA records and DNSSEC.

Name Options DNSSEC Matches
_25._tcp.mail.tiboxs.com
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid