SSL-Tools

SSL check results of oci.mx4me.nl

NEW You can also bulk check multiple servers.

Discover if the mail servers for oci.mx4me.nl 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 Wed, 17 Apr 2024 15:26:56 +0000

The mailservers of oci.mx4me.nl can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @oci.mx4me.nl addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
oci.mx4me.nl
141.148.243.70
 -
supported
mx4me.nl
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
61 s
oci.mx4me.nl
2603:c022:c006:400:1ab6:1407:edc2:510a
 -
supported
mx4me.nl
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 @oci.mx4me.nl address so far. Test mail delivery

Certificates

First seen at:

CN=mx4me.nl

Certificate chain
  • mx4me.nl
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mx4me.nl
Alternative Names
  • *.mx4me.nl
  • mx4me.nl
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-02-25
Not valid after
2024-05-25
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
22:0B:46:1D:2C:46:12:0B:72:D2:95:44:40:09:F1:C5:33:2C:36:C2:8B:AA:2D:C9:B0:B7:94:E4:E7:9E:9D:DF
SHA1
B2:C1:33:59:90:BF:DA:E8:22:9C:C8:E3:14:62:71:60:CD:FE:28:60
X509v3 extensions
subjectKeyIdentifier
  • D1:80:02:3D:C6:B1:96:6D:70:21:2F:9D:75:0E:37:C7:7D:C1:77:FB
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 : Feb 25 05:25:04.912 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:E6:8A:BC:C0:C8:A1:26:9D:C5:F8:80:
  • E3:54:BE:D6:CE:42:11:B7:0A:24:A3:1E:F2:80:ED:0D:
  • 71:C6:CB:5B:44:02:21:00:B1:10:81:51:24:50:1C:52:
  • 19:04:D9:86:13:04:B1:23:38:D8:75:43:A5:08:B3:C9:
  • 68:2A:DA:B4:C3:0F:4E:DB
  • 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 : Feb 25 05:25:04.962 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:EF:55:9C:F6:B5:05:52:81:89:28:28:
  • C1:56:AD:FF:61:BC:7A:EB:89:E7:C6:3D:14:7A:5D:29:
  • 65:70:45:C1:8F:02:21:00:81:79:E4:4C:69:F8:2A:05:
  • 1B:F4:56:DB:7A:78:A8:32:5E:FF:5C:5A:83:5A:F0:4F:
  • E8:31:1F:B9:85:81:39:8F

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.oci.mx4me.nl
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid