SSL-Tools

SSL check results of relayforliferossendale.co.uk

NEW You can also bulk check multiple servers.

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

JSON Refresh

Report created Tue, 01 Oct 2024 21:04:15 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.relayforliferossendale.co.uk
86.48.6.108
 5
supported
relayforliferossendale.co.uk
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=relayforliferossendale.co.uk

Certificate chain
  • relayforliferossendale.co.uk
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • relayforliferossendale.co.uk
Alternative Names
  • admin.relayforliferossendale.co.uk
  • mail.relayforliferossendale.co.uk
  • mta-sts.relayforliferossendale.co.uk
  • relayforliferossendale.co.uk
  • webmail.relayforliferossendale.co.uk
  • www.relayforliferossendale.co.uk
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2024-09-30
Not valid after
2024-12-29
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
08:FD:6F:C2:B8:C0:59:35:82:ED:92:1B:D7:26:D9:21:F0:0B:1A:AA:0D:E4:B7:5E:66:6F:91:BE:44:EE:FA:24
SHA1
BE:0E:DE:4E:18:76:18:51:07:2A:EB:82:8A:D6:AB:E0:79:10:F6:26
X509v3 extensions
subjectKeyIdentifier
  • 34:E2:6E:3D:B6:32:7C:98:AD:5C:FB:E5:12:8F:29:42:B4:7C:A9:74
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Sep 30 11:18:39.343 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:8B:EB:B9:AB:EF:93:5A:E1:7B:41:79:
  • D6:9A:72:CE:5B:7B:43:69:65:4F:E3:27:A0:02:73:F2:
  • 06:6E:AE:43:F8:02:20:42:82:1A:BC:A1:BD:23:97:C4:
  • A0:8A:92:A9:8A:B8:F6:03:7E:4E:D9:78:D4:C6:8B:09:
  • 2D:01:C1:18:4B:74:D2
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 19:98:10:71:09:F0:D6:52:2E:30:80:D2:9E:3F:64:BB:
  • 83:6E:28:CC:F9:0F:52:8E:EE:DF:CE:4A:3F:16:B4:CA
  • Timestamp : Sep 30 11:18:39.366 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:A2:22:15:B6:40:B0:DA:A2:A1:5B:2F:
  • 06:13:E6:0E:0A:B4:80:E1:BE:78:0D:A4:3D:57:84:67:
  • 78:65:7A:B7:55:02:21:00:AF:38:E6:84:B3:BA:5B:17:
  • F9:B5:E9:8D:21:73:8B:04:34:36:A7:AA:F4:73:43:AA:
  • 16:68:F7:6B:22:EA:F6:21