SSL check results of datadrivesports.com

NEW You can also bulk check multiple servers.

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

Report created Fri, 05 Mar 2021 14:39:13 +0000

We can not guarantee a secure connection to the mailservers of datadrivesports.com!

Please contact the operator of datadrivesports.com and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/datadrivesports.com

Servers

Incoming Mails

These servers are responsible for incoming mails to @datadrivesports.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx3.sandstonesourcing.com
2a01:4f8:171:d19::2
Results incomplete
20 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
mx3.sandstonesourcing.com
136.243.104.26
20
supported
sandstonesourcing.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
supported
  • ECDHE_RSA_WITH_RC4_128_SHA
  • SSL_RSA_WITH_RC4_128_SHA
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
12 s

Outgoing Mails

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

Certificates

First seen at:

CN=sandstonesourcing.com

Certificate chain
  • sandstonesourcing.com
    • 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)
  • sandstonesourcing.com
Alternative Names
  • *.sandstonesourcing.com
  • sandstonesourcing.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2020-12-10
Not valid after
2021-03-10
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
DD:1B:30:05:2C:0A:75:47:FD:A6:1F:0D:FF:4D:70:12:41:D0:31:39:4A:82:04:1B:A5:A1:3C:B2:21:64:33:4E
SHA1
27:4E:6B:9C:08:48:3F:15:8C:07:FB:36:B5:C5:67:D9:6E:7C:0C:FB
X509v3 extensions
subjectKeyIdentifier
  • 2E:7B:CE:90:3A:F8:D3:38:EC:36:F7:B0:E4:C2:57:5C:85:3E:76:DE
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 : Dec 10 19:09:47.082 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:E2:5C:A0:45:8C:2C:F1:DA:60:EE:06:
  • 0E:10:71:FE:09:8E:59:59:F0:73:71:F7:4A:DB:32:87:
  • 45:5D:5C:73:94:02:20:3E:B1:72:07:96:DF:67:BB:84:
  • 86:95:53:62:3F:48:0F:24:F8:A8:61:DC:03:E7:71:3C:
  • B9:D5:0F:AC:E8:23:F1
  • 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 : Dec 10 19:09:47.117 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:AD:66:5C:D5:EF:FE:7C:19:3E:DE:1F:
  • 37:03:F3:BB:6C:EC:6A:61:41:CA:3C:75:A1:E4:45:68:
  • 01:55:6B:A6:32:02:21:00:F9:64:26:DE:C7:AE:5F:97:
  • 03:1A:6B:1E:F7:84:D0:3D:4A:10:8B:6F:7F:96:50:59:
  • EB:5C:C9:25:FC:00:97:78