SSL-Tools

SSL check results of boubou.me

NEW You can also bulk check multiple servers.

Discover if the mail servers for boubou.me 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, 20 Mar 2025 20:53:51 +0000

The mailservers of boubou.me can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @boubou.me 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 @boubou.me 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
  • sogo.boubou.me
  • sogo.seeboxs.com
  • sogo.tiboxs.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-03-20
Not valid after
2025-06-18
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
2E:A5:71:BA:0A:5A:E4:37:31:55:E3:DD:32:0C:B6:68:B5:EE:8C:3A:00:D0:6F:96:64:B9:70:69:AB:53:03:63
SHA1
DC:DC:B3:B8:3E:E3:C4:28:80:63:C5:F5:2A:31:3A:20:2C:38:9C:2D
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
crlDistributionPoints
  • Full Name:
  • URI:http://r11.c.lencr.org/123.crl
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 20 04:42:43.751 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:B6:2F:7B:72:90:37:9A:0B:93:BF:45:
  • 34:63:09:DE:4A:6E:9C:BB:68:74:59:4E:8F:57:4B:C2:
  • 7C:BB:21:01:5B:02:20:5D:A1:D6:3F:8E:EB:DA:66:6A:
  • 52:30:69:E1:4E:F6:DD:42:97:88:B1:D4:D1:91:27:F8:
  • 85:48:1F:CA:31:B1:05
  • 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 : Mar 20 04:42:45.864 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:B0:97:99:73:19:E9:1C:A4:11:8B:B2:
  • FB:30:2A:56:4C:45:CD:5C:A6:52:66:F0:EC:84:EA:99:
  • 38:42:C0:F7:40:02:21:00:B0:BC:C5:53:F4:AB:70:BB:
  • B0:65:EE:37:5D:D7:F0:6F:A0:33:5A:5A:A2:59:28:E8:
  • 81:30:99:17:62:8E:46:92

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