SSL-Tools

SSL check results of 3haber.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for 3haber.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 Sat, 28 Feb 2026 01:32:53 +0000

We can not guarantee a secure connection to the mailservers of 3haber.net!

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

/mailservers/3haber.net

Servers

Incoming Mails

These servers are responsible for incoming mails to @3haber.net addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.3haber.net
2a01:4f9:3100:4190::2
Results incomplete
5 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
mail.3haber.net
157.180.54.108
 5
supported
3haber.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

We have not received any emails from a @3haber.net address so far. Test mail delivery

Certificates

First seen at:

CN=3haber.net

Certificate chain
  • 3haber.net
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch
      • R12
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • 3haber.net
Alternative Names
  • 3haber.net
  • www.3haber.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R12
validity period
Not valid before
2026-02-15
Not valid after
2026-05-16
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
Fingerprints
SHA256
8D:BF:71:4D:B2:EF:8E:52:5A:28:B9:72:BE:8E:C9:4B:AB:47:82:67:D7:4A:37:9F:E8:FD:51:07:7D:99:1D:81
SHA1
A0:0C:66:76:1E:CD:0C:21:17:10:E8:4C:CF:78:5D:71:2B:3B:26:2D
X509v3 extensions
subjectKeyIdentifier
  • BB:1E:B3:C0:7A:E4:C5:52:BA:71:92:6F:3E:7D:B2:D3:4C:43:9C:2F
authorityKeyIdentifier
  • keyid:00:B5:29:F2:2D:8E:6F:31:E8:9B:4C:AD:78:3E:FA:DC:E9:0C:D1:D2
authorityInfoAccess
  • CA Issuers - URI:http://r12.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r12.c.lencr.org/37.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 96:97:64:BF:55:58:97:AD:F7:43:87:68:37:08:42:77:
  • E9:F0:3A:D5:F6:A4:F3:36:6E:46:A4:3F:0F:CA:A9:C6
  • Timestamp : Feb 15 08:03:10.798 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:79:38:DF:A9:32:71:3E:6F:47:74:7C:1A:
  • 77:BF:41:15:7A:96:04:C2:69:C6:05:92:91:75:9A:22:
  • 44:E8:15:DD:02:21:00:FA:9A:BD:10:D5:41:38:BD:B6:
  • 76:33:21:3C:93:86:28:C3:1B:FA:06:BF:D2:C5:57:C0:
  • C8:40:3B:50:2F:2E:4A
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 71:7E:95:F3:C2:38:8A:6D:B1:E3:84:49:3D:31:E1:5A:
  • A9:62:08:76:2D:42:00:E0:05:0C:D0:67:B5:A6:61:E2
  • Timestamp : Feb 15 08:03:11.008 2026 GMT
  • Extensions: 00:00:05:00:09:80:7D:BB
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:25:D6:04:4B:5D:D3:EC:F4:E4:54:A0:5B:
  • C6:4C:76:7F:35:13:E9:28:5B:7F:8B:73:CD:BB:CD:8E:
  • 4A:51:8F:0B:02:21:00:EE:7C:45:10:79:A5:7E:A3:1F:
  • 40:1F:30:4B:31:9C:6F:C6:B1:E6:D3:C0:02:08:FD:2D:
  • 27:E1:1B:74:8A:8C:B1