SSL check results of spol.org.uk

NEW You can also bulk check multiple servers.

Discover if the mail servers for spol.org.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 Thu, 22 Sep 2022 12:04:05 +0000

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

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

/mailservers/spol.org.uk

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.spol.org.uk
185.222.80.90
Results incomplete
10
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
6 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
  • SSLv3
4 s

Outgoing Mails

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

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
2022-07-09
Not valid after
2022-10-07
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
7E:B0:02:30:3C:C3:00:DE:37:0A:08:F6:65:67:F7:1D:1D:1C:7C:24:39:CB:CB:EF:53:55:19:47:23:98:F0:86
SHA1
17:67:5A:12:28:B3:90:F1:C1:E6:43:25:B8:1D:BF:C6:B9:9D:F9:B3
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
  • 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 : DF:A5:5E:AB:68:82:4F:1F:6C:AD:EE:B8:5F:4E:3E:5A:
  • EA:CD:A2:12:A4:6A:5E:8E:3B:12:C0:20:44:5C:2A:73
  • Timestamp : Jul 9 06:01:34.574 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:E3:D8:6A:D3:E2:5C:42:6D:E3:2A:65:
  • DC:C5:DD:07:D1:85:2E:DC:77:6C:97:45:F2:DD:AD:DC:
  • 5A:0B:99:94:B2:02:20:0A:3C:0C:A8:48:3E:EC:58:A5:
  • EB:93:47:98:E5:66:E6:70:FB:4B:FF:B9:2C:09:04:5C:
  • AD:62:E0:D9:22:3D:08
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 29:79:BE:F0:9E:39:39:21:F0:56:73:9F:63:A5:77:E5:
  • BE:57:7D:9C:60:0A:F8:F9:4D:5D:26:5C:25:5D:C7:84
  • Timestamp : Jul 9 06:01:34.569 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:F3:63:9E:FD:E6:D9:0E:77:CB:32:74:
  • C8:BC:E1:B2:8D:56:AF:2D:2E:63:9D:2F:89:4A:34:A8:
  • 70:07:D8:BE:56:02:20:13:E6:58:0B:7F:4B:7A:7F:EE:
  • 1F:0D:E0:67:D9:27:C7:AF:10:38:41:C8:45:7F:0E:38:
  • 51:CD:10:6B:F4:B8:51