SSL-Tools

SSL check results of granvillecliffestate.co.uk

NEW You can also bulk check multiple servers.

Discover if the mail servers for granvillecliffestate.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 Mon, 23 Sep 2024 00:30:35 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
teal.dogssrv.com
2a01:7e00:e000:86d::2
 10
supported
teal.dogssrv.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
teal.dogssrv.com
109.74.195.240
 10
supported
teal.dogssrv.com
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 @granvillecliffestate.co.uk address so far. Test mail delivery

Certificates

First seen at:

CN=teal.dogssrv.com

Certificate chain
  • teal.dogssrv.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • teal.dogssrv.com
Alternative Names
  • teal.dogssrv.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2024-08-24
Not valid after
2024-11-22
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
70:3D:03:57:38:C8:37:43:E7:FC:90:BF:79:F4:1C:EF:84:F9:EA:27:8A:8A:81:06:AB:AC:DA:1B:7C:9C:FD:6D
SHA1
7C:F8:2D:9B:39:5C:D0:C8:31:CE:63:39:FF:5D:27:65:F6:9B:F9:33
X509v3 extensions
subjectKeyIdentifier
  • 45:AA:A2:B1:2F:41:3E:90:05:7F:C4:FC:8C:2B:B6:B5:5A:F1:F2:CD
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
  • ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
  • Timestamp : Aug 24 22:56:09.221 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:E2:61:36:21:BF:D7:4F:C1:D2:4F:DC:
  • AC:B1:B4:41:6B:47:FF:CF:F1:CD:77:2E:43:BE:66:FD:
  • 67:4D:35:A1:16:02:20:4D:2C:17:8E:7D:16:86:C9:3C:
  • B9:DA:51:9E:92:F5:3F:1D:48:EB:E0:29:EF:50:8E:D0:
  • EE:34:A6:0E:97:60:3B
  • 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 : Aug 24 22:56:09.218 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:02:33:CE:C4:71:03:F8:C2:66:18:B7:8A:
  • 15:3F:27:A3:08:95:CC:44:26:6C:99:FF:75:B1:F3:2F:
  • 8D:7C:B2:21:02:21:00:9C:02:C3:88:42:5E:EB:6C:7D:
  • F2:4E:73:65:F3:20:37:C7:1B:70:43:63:D4:99:0E:D8:
  • 51:E9:95:34:49:A7:62