SSL check results of msinstruments.co.uk

NEW You can also bulk check multiple servers.

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

Report created Wed, 13 Mar 2024 14:55:37 +0000

The mailservers of msinstruments.co.uk can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @msinstruments.co.uk addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.msinstruments.co.uk
82.68.108.238
Results incomplete
10
supported
not checked
DANE
missing
PFS
not checked
Heartbleed
not vulnerable
Weak ciphers
not checked
1 s
smtp.lymden-lodge.net
82.69.249.98
50
supported
*.lymden-lodge.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
4 s

Outgoing Mails

We have received emails from these servers with @msinstruments.co.uk sender addresses. Test mail delivery

Host TLS Version & Cipher
vpn.msinstruments.net (82.68.108.238)
TLSv1.2 ECDHE-RSA-AES256-SHA384

Certificates

First seen at:

CN=*.lymden-lodge.net

Certificate chain
  • *.lymden-lodge.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)
  • *.lymden-lodge.net
Alternative Names
  • *.lymden-lodge.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-01-05
Not valid after
2024-04-04
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
3C:91:53:AF:45:62:CE:F7:D4:01:69:4A:3C:C1:B6:D6:D6:35:BA:BC:7B:6C:36:46:78:AF:A8:24:E6:49:1E:A0
SHA1
4B:E8:F6:53:CA:4B:F8:F4:07:9C:49:92:04:54:2F:AD:DE:E9:2D:80
X509v3 extensions
subjectKeyIdentifier
  • 86:39:B9:E2:7E:AF:D4:42:BC:C4:E9:2C:3B:68:47:14:77:A4:A9:F4
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 : 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 : Jan 5 07:04:06.358 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:C7:26:4A:5D:89:8A:C3:E7:A2:77:ED:
  • E0:DB:6C:46:3E:E3:A9:BD:C4:57:9D:75:18:4B:63:13:
  • 82:D0:A6:53:91:02:20:43:A6:C7:22:78:BA:08:7E:F4:
  • 52:30:E1:4D:09:89:46:5E:9D:E1:8F:5F:1D:A9:5D:52:
  • 22:F0:15:47:CA:EA:B2
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : Jan 5 07:04:06.370 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:0D:AA:59:63:56:D2:A6:93:E0:8A:02:CF:
  • 3A:C6:1E:4D:3C:C8:E2:E5:92:C0:47:B3:00:BB:7E:6D:
  • 20:D5:7A:61:02:21:00:84:36:50:7A:DF:FA:9E:DD:CE:
  • EB:1E:FA:C6:BF:35:11:0E:51:2C:C5:BF:5A:E2:89:3E:
  • 2C:A3:47:41:DB:79:3B