SSL check results of fxopen.org

NEW You can also bulk check multiple servers.

Discover if the mail servers for fxopen.org 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

Report created Fri, 07 Feb 2025 01:31:07 +0000

We can not guarantee a secure connection to the mailservers of fxopen.org!

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

/mailservers/fxopen.org

Servers

Incoming Mails

These servers are responsible for incoming mails to @fxopen.org addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
fe01.mx.fxopen.net
159.69.231.195
Results incomplete
10
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
fe02.mx.fxopen.net
212.83.161.67
20
supported
fe01.mx.fxopen.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
supported
  • ECDHE_RSA_WITH_RC4_128_SHA
  • SSL_RSA_WITH_RC4_128_SHA
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
12 s

Outgoing Mails

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

Certificates

First seen at:

CN=fe01.mx.fxopen.net

Certificate chain
  • fe01.mx.fxopen.net
    • remaining
    • 3072 bit
    • sha256WithRSAEncryption
    • Expired
    • Unknown Authority

      R3
Subject
Common Name (CN)
  • fe01.mx.fxopen.net
Alternative Names
  • fe01.mx.fxopen.net
  • fe02.mx.fxopen.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-09-06
Not valid after
2021-12-05
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
39:40:31:19:CD:3F:29:7C:C8:D8:6C:6A:4E:AE:2F:B9:55:C4:8C:CE:CB:E6:E8:53:9B:24:3B:BD:A5:39:2E:E4
SHA1
94:3B:0E:73:BA:1D:14:61:6A:5A:BE:9E:DE:80:E0:CB:FF:3C:58:4B
X509v3 extensions
subjectKeyIdentifier
  • 09:81:11:AD:E2:AD:E9:78:A5:0B:FB:75:0F:D7:87:53:AE:6D:4B:86
authorityKeyIdentifier
  • keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
authorityInfoAccess
  • OCSP - URI:http://r3.o.lencr.org
  • CA Issuers - URI:http://r3.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 94:20:BC:1E:8E:D5:8D:6C:88:73:1F:82:8B:22:2C:0D:
  • D1:DA:4D:5E:6C:4F:94:3D:61:DB:4E:2F:58:4D:A2:C2
  • Timestamp : Sep 6 10:52:34.711 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:BC:D0:20:83:03:C0:F1:11:57:99:F2:
  • 5F:7A:2B:67:A9:44:1C:4B:1E:11:B3:4C:DE:D0:CE:93:
  • C3:7E:00:C6:69:02:20:40:EB:40:76:9E:C3:DF:20:A7:
  • CA:4F:EC:99:22:60:9D:AD:4C:42:8C:32:8E:CF:04:BC:
  • 39:6A:C7:03:27:1A:45
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
  • 79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
  • Timestamp : Sep 6 10:52:34.749 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:EA:A0:E4:E3:CD:BD:3D:6E:9C:0D:06:
  • E5:1F:2B:E9:08:DF:D9:90:6D:34:5C:63:58:0F:A9:A3:
  • 99:4A:90:DC:5D:02:21:00:D4:E7:C8:6E:EE:8E:76:F2:
  • 26:85:35:BE:14:42:9D:DD:88:13:DD:9A:7A:56:46:25:
  • C0:F6:68:82:AA:F5:87:E0