SSL check results of eumx.net

NEW You can also bulk check multiple servers.

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

Report created Tue, 16 Apr 2024 08:40:05 +0000

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

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

/mailservers/eumx.net

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
eumx.net
161.97.154.251
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
bmx1.eumx.net
2a02:c206:2101:8953::70
Results incomplete
50 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
bmx1.eumx.net
37.48.73.248
50
supported
bmx2.eumx.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
bmx2.eumx.net
37.48.73.248
90
supported
bmx2.eumx.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 @eumx.net address so far. Test mail delivery

Certificates

First seen at:

CN=bmx2.eumx.net

Certificate chain
  • bmx2.eumx.net
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption

Subject
Common Name (CN)
  • bmx2.eumx.net
Alternative Names
  • bmx2.eumx.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-11
Not valid after
2024-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
4E:1B:7D:61:93:33:54:F5:E2:A8:82:8B:24:D0:8C:40:B3:19:57:80:6E:46:D5:7E:43:10:F7:20:D8:E9:DA:B3
SHA1
23:3F:C6:BB:E9:51:DC:FB:0D:86:8D:27:E5:8C:0F:EF:E9:A6:24:F1
X509v3 extensions
subjectKeyIdentifier
  • F4:BB:67:C4:59:89:F9:47:6B:D9:2D:0A:E5:7E:BB:86:BA:35:A1:23
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
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3B:53:77:75:3E:2D:B9:80:4E:8B:30:5B:06:FE:40:3B:
  • 67:D8:4F:C3:F4:C7:BD:00:0D:2D:72:6F:E1:FA:D4:17
  • Timestamp : Mar 11 19:37:49.356 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:41:20:10:6C:28:04:1D:54:0A:20:CA:0F:
  • 3E:97:C8:5A:93:3F:B0:E7:C8:99:73:60:2C:FF:C8:5E:
  • E8:BC:34:54:02:20:3A:51:B2:9C:05:30:5D:32:FE:25:
  • 6C:72:C7:51:D9:9A:03:1D:07:F1:94:EB:63:0A:C6:BE:
  • CE:FC:42:DF:96:8D
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E2:BF:D6:1E:DE:2F:2F:07:A0:D6:4E:6D:37:A7:DC:
  • 65:43:B0:C6:B5:2E:A2:DA:B7:8A:F8:9A:6D:F5:17:D8
  • Timestamp : Mar 11 19:37:49.373 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:D8:C1:EB:B2:3B:42:1A:BD:12:4C:14:
  • 60:87:ED:AD:ED:51:A2:09:C9:F2:AB:A7:AF:0D:0D:B0:
  • 45:B8:C7:9A:65:02:21:00:CA:9B:10:5C:4C:FA:4C:C9:
  • E2:A3:29:7D:B7:C6:4C:57:FD:DC:E2:2B:9F:00:4C:3F:
  • BC:72:E7:56:EA:DF:78:3F