SSL-Tools

SSL check results of jcu.me.uk

NEW You can also bulk check multiple servers.

Discover if the mail servers for jcu.me.uk 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 Fri, 29 Aug 2025 19:01:10 +0000

The mailservers of jcu.me.uk can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @jcu.me.uk addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
smtp4.vorticity-systems.com
2a01:7e00::f03c:91ff:fe69:d685
Results incomplete
20 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
smtp4.vorticity-systems.com
176.58.119.90
 20
supported
smtp4.vorticity-systems.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

We have not received any emails from a @jcu.me.uk address so far. Test mail delivery

Certificates

First seen at:

CN=smtp4.vorticity-systems.com

Certificate chain
  • smtp4.vorticity-systems.com
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • E5
        • remaining
        • 384 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • smtp4.vorticity-systems.com
Alternative Names
  • smtp4.vorticity-systems.com
  • vorticity-systems.co.uk
  • vorticity-systems.com
  • vorticity-uk.com
  • vorticity-us.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E5
validity period
Not valid before
2025-07-05
Not valid after
2025-10-03
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
5D:8E:FE:F1:36:F0:C0:D0:D9:24:CA:35:70:9F:72:BB:65:5E:A2:B7:B2:54:4D:6C:E8:50:CE:12:61:1E:F3:D2
SHA1
9B:39:F3:0E:8C:AA:83:DB:C0:9C:06:09:8F:C1:40:55:84:13:53:A0
X509v3 extensions
subjectKeyIdentifier
  • B7:37:DA:1C:D8:7D:38:3C:22:BC:8A:D2:77:DE:52:3C:41:D7:AA:64
authorityKeyIdentifier
  • keyid:9F:2B:5F:CF:3C:21:4F:9D:04:B7:ED:2B:2C:C4:C6:70:8B:D2:D7:0D
authorityInfoAccess
  • CA Issuers - URI:http://e5.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://e5.c.lencr.org/48.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 0D:E1:F2:30:2B:D3:0D:C1:40:62:12:09:EA:55:2E:FC:
  • 47:74:7C:B1:D7:E9:30:EF:0E:42:1E:B4:7E:4E:AA:34
  • Timestamp : Jul 5 19:25:06.943 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:FE:04:2A:0C:40:13:EF:F5:AE:AC:32:
  • 23:5F:E4:3B:C3:5B:1B:78:14:FA:43:74:05:8E:9E:36:
  • 7E:A2:89:E3:3F:02:21:00:D9:35:DE:A1:1C:15:12:1E:
  • 42:54:00:C8:54:EE:48:AC:A2:EF:80:F7:5F:25:66:0C:
  • E4:07:E6:0E:8E:7C:EC:08
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A4:42:C5:06:49:60:61:54:8F:0F:D4:EA:9C:FB:7A:2D:
  • 26:45:4D:87:A9:7F:2F:DF:45:59:F6:27:4F:3A:84:54
  • Timestamp : Jul 5 19:25:06.947 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:8C:AC:A1:88:DA:A6:88:23:52:C4:EE:
  • 17:9F:FB:E1:D5:34:72:71:45:AC:14:57:02:07:C6:82:
  • BD:DA:C0:A0:BB:02:20:34:6E:E2:4F:F3:81:89:32:DC:
  • 12:C8:77:36:32:96:49:FE:54:DC:B4:5A:8E:47:03:12:
  • BB:69:13:50:55:D1:82