SSL-Tools

SSL check results of greenshine.fr

NEW You can also bulk check multiple servers.

Discover if the mail servers for greenshine.fr 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 Wed, 08 May 2024 20:41:13 +0000

The mailservers of greenshine.fr can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @greenshine.fr addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.greenshine.fr
2001:41d0:304:200::23d1
 1
supported
mail.greenshine.fr
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
8 s
mail.greenshine.fr
54.37.40.181
 1
supported
mail.greenshine.fr
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
5 s

Outgoing Mails

We have not received any emails from a @greenshine.fr address so far. Test mail delivery

Certificates

First seen at:

CN=mail.greenshine.fr

Certificate chain
  • mail.greenshine.fr
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.greenshine.fr
Alternative Names
  • autoconfig.greenshine.fr
  • autodiscover.greenshine.fr
  • mail.greenshine.fr
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-05-08
Not valid after
2024-08-06
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
2B:94:83:BF:60:36:0D:CB:4F:A4:D3:CA:63:40:E0:5E:D5:9D:C1:A6:92:F2:34:05:E9:63:BE:4F:FE:5D:99:0A
SHA1
51:BE:ED:38:D9:CE:67:B2:60:3D:57:76:37:78:8F:4C:F3:AB:74:8F
X509v3 extensions
subjectKeyIdentifier
  • B8:7F:2A:63:D9:82:25:19:79:C5:C3:98:86:10:3B:01:3F:3A:C3:69
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 : 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 : May 8 16:29:29.320 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:37:0A:2E:E5:66:74:9E:69:FF:43:EB:2E:
  • A9:21:95:A9:A0:D0:5E:22:C5:23:5D:FE:E6:67:5D:C4:
  • DE:1B:24:F7:02:21:00:F7:2D:94:C3:1B:2C:9C:56:07:
  • 4E:86:ED:18:E5:E2:CA:86:2E:45:1E:01:A0:90:8C:4A:
  • EF:35:C0:F0:D9:E1:13
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DF:E1:56:EB:AA:05:AF:B5:9C:0F:86:71:8D:A8:C0:32:
  • 4E:AE:56:D9:6E:A7:F5:A5:6A:01:D1:C1:3B:BE:52:5C
  • Timestamp : May 8 16:29:29.514 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:AA:C0:37:CB:1B:88:2C:31:16:A2:6A:
  • 96:95:EB:59:33:97:FD:E7:8E:CC:32:FC:02:4A:E4:30:
  • 33:DD:6C:3A:80:02:21:00:C0:3D:6E:A5:67:84:6D:D9:
  • D6:49:00:BE:99:09:C9:6A:BC:43:15:B3:29:02:EA:D0:
  • A8:03:6B:4D:E9:90:76:D5