SSL-Tools

SSL check results of smack.email

NEW You can also bulk check multiple servers.

Discover if the mail servers for smack.email 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, 30 Oct 2025 01:30:08 +0000

We can not guarantee a secure connection to the mailservers of smack.email!

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

/mailservers/smack.email

Servers

Incoming Mails

These servers are responsible for incoming mails to @smack.email addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
use4.bumpemail.com
5.161.193.72
Results incomplete
0
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
4 s
usw4.bumpemail.com
49.13.117.11
 10
supported
usw4.bumpemail.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
23 s

Outgoing Mails

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

Certificates

First seen at:

CN=usw4.bumpemail.com

Certificate chain
  • usw4.bumpemail.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R13
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • usw4.bumpemail.com
Alternative Names
  • usw4.bumpemail.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R13
validity period
Not valid before
2025-09-01
Not valid after
2025-11-30
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
DB:FC:C9:19:28:4E:04:C3:32:C9:DD:67:BE:98:55:61:63:B9:DB:01:EF:48:DF:1B:A5:7D:20:5B:72:CC:C5:83
SHA1
70:ED:61:7F:24:77:85:E1:21:B8:64:51:3F:D1:D9:5E:B7:99:EF:D7
X509v3 extensions
subjectKeyIdentifier
  • 6C:67:A8:8C:7D:10:5E:4F:31:FB:CD:1D:ED:62:AC:7B:E4:CC:CC:98
authorityKeyIdentifier
  • keyid:E7:AB:9F:0F:2C:33:A0:53:D3:5E:4F:78:C8:B2:84:0E:3B:D6:92:33
authorityInfoAccess
  • CA Issuers - URI:http://r13.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r13.c.lencr.org/7.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 : Sep 1 09:17:01.751 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:34:40:48:A9:03:C3:0A:F0:6F:29:C6:F3:
  • 54:D0:1B:32:D6:32:CE:22:19:FE:E4:BE:67:A4:29:4E:
  • 97:57:79:E4:02:20:29:62:3B:A4:B9:FA:33:FD:23:F0:
  • AC:88:73:32:3F:28:A3:CE:27:88:37:BD:C1:76:F6:7E:
  • E5:55:AC:0D:C7:90
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 1A:04:FF:49:D0:54:1D:40:AF:F6:A0:C3:BF:F1:D8:C4:
  • 67:2F:4E:EC:EE:23:40:68:98:6B:17:40:2E:DC:89:7D
  • Timestamp : Sep 1 09:17:01.690 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:B4:22:EB:EC:3C:9F:BB:B9:76:36:31:
  • BB:D7:A5:B2:B3:84:8F:B4:F1:C9:E2:B5:C8:5A:05:3C:
  • EF:9A:8C:33:0B:02:20:07:AC:18:D4:02:09:67:5A:EF:
  • C3:2D:40:1F:B5:5D:AD:23:48:76:0B:C9:27:74:41:B1:
  • 68:E5:C8:93:5E:35:63