SSL check results of coastwebsolutions.co.uk

NEW You can also bulk check multiple servers.

Discover if the mail servers for coastwebsolutions.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 Tue, 04 May 2021 15:02:06 +0000

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

Servers

Incoming Mails

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

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

Outgoing Mails

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

Certificates

First seen at:

CN=coastwebsolutions.co.uk

Certificate chain
  • coastwebsolutions.co.uk
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption

Subject
Common Name (CN)
  • coastwebsolutions.co.uk
Alternative Names
  • autoconfig.coastwebsolutions.co.uk
  • autodiscover.coastwebsolutions.co.uk
  • coastwebsolutions.co.uk
  • hosting.coastwebsolutions.co.uk
  • mail.coastwebsolutions.co.uk
  • ns2.coastwebsolutions.co.uk
  • www.coastwebsolutions.co.uk
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-05-04
Not valid after
2021-08-02
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
7D:B5:D1:AF:95:29:B3:B8:5B:A2:F5:58:BE:D3:96:8C:72:9E:C0:94:EE:92:06:BF:ED:2C:8F:40:FA:A7:D0:91
SHA1
E0:B8:5E:47:E6:6A:BF:C0:D7:E8:5E:E4:72:84:5C:1C:F0:F0:9D:EF
X509v3 extensions
subjectKeyIdentifier
  • 87:ED:0F:A6:BA:C0:48:7B:AB:9B:32:03:61:DC:E1:A3:72:A2:F2:29
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 : 94:20:BC:1E:8E:D5:8D:6C:88:73:1F:82:8B:22:2C:0D:
  • D1:DA:4D:5E:6C:4F:94:3D:61:DB:4E:2F:58:4D:A2:C2
  • Timestamp : May 4 14:50:51.178 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:EA:EF:FC:6A:9C:EA:02:65:B9:0D:08:
  • 61:8B:06:F2:D6:56:9A:5B:FD:43:24:93:E0:D9:A5:3C:
  • FB:95:97:C9:3D:02:20:01:B3:61:8C:3B:5D:D9:8B:4F:
  • 09:8B:01:26:7D:6F:18:22:25:28:CC:F5:FB:04:D8:D3:
  • AD:91:E7:89:2C:4C:2B
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
  • E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
  • Timestamp : May 4 14:50:51.210 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:A9:E3:2E:1F:55:9B:C6:1E:B6:D5:4A:
  • 4D:16:ED:5B:CA:36:0A:5A:B0:10:CF:2B:A8:DE:88:A5:
  • B3:C2:CC:E4:90:02:21:00:97:E1:1A:AC:F4:51:CA:98:
  • 6C:C9:20:98:C8:F6:93:B7:2A:D8:9C:FA:1F:78:F2:E5:
  • 0B:32:6C:D2:0A:03:20:AC