SSL-Tools

SSL check results of resilio-solutions.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for resilio-solutions.com 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 Fri, 21 Feb 2025 14:14:14 +0000

The mailservers of resilio-solutions.com can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @resilio-solutions.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail1.dgtz.fr
2a02:c207:2066:9834::1
 10
supported
mail1.dgtz.fr
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
8 s
mail1.dgtz.fr
173.212.201.71
 10
supported
mail1.dgtz.fr
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
7 s

Outgoing Mails

We have not received any emails from a @resilio-solutions.com address so far. Test mail delivery

Certificates

First seen at:

CN=mail1.dgtz.fr

Certificate chain
  • mail1.dgtz.fr
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail1.dgtz.fr
Alternative Names
  • mail1.dgtz.fr
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-01-03
Not valid after
2025-04-03
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
DD:01:3C:F6:A6:A5:6F:8D:52:70:61:A6:81:D4:3F:1B:0C:59:39:94:9D:46:8B:71:21:02:27:A1:5F:84:A1:7C
SHA1
E3:16:82:E5:E2:D6:F2:37:78:F1:EB:FC:54:73:15:ED:E4:F0:28:1A
X509v3 extensions
subjectKeyIdentifier
  • 18:BF:3D:E8:AD:05:6D:A6:2F:37:34:6B:EA:86:E4:F2:8B:74:A2:15
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 : 73:20:22:0F:08:16:8A:F9:F3:C4:A6:8B:0A:B2:6A:9A:
  • 4A:00:EE:F5:77:85:8A:08:4D:05:00:D4:A5:42:44:59
  • Timestamp : Jan 3 18:23:15.861 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:D9:6C:74:9B:A4:1D:BE:39:35:74:63:
  • 7D:99:12:1A:F1:15:FB:F0:51:B7:9C:DE:A8:2E:02:1E:
  • FA:78:37:5C:BC:02:21:00:AD:43:94:0A:B5:C5:84:F5:
  • 0C:54:73:7C:AF:B0:61:ED:A8:C2:C5:AE:6A:DA:79:DF:
  • 18:94:CE:03:D0:3D:7A:8F
  • 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 : Jan 3 18:23:15.857 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:F8:FE:EF:0C:C8:1D:53:C4:1D:74:9A:
  • 0D:90:55:EC:16:D3:40:96:32:06:7D:73:3A:44:52:FC:
  • 81:27:CA:0B:D0:02:21:00:9A:9D:7C:98:59:C6:E3:31:
  • DA:32:A1:F1:62:CA:E0:1B:28:79:CD:F3:70:EA:5D:2C:
  • 67:5F:02:F6:BF:3C:7C:08