SSL check results of xpezdigital.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for xpezdigital.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 Sat, 06 Mar 2021 07:17:15 +0000

The mailservers of xpezdigital.com can be reached through a secure connection.

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.xpezdigital.com
162.241.218.25
0
supported
cpcontacts.xpezdigital.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
43 s

Outgoing Mails

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

Certificates

First seen at:

CN=cpcontacts.xpezdigital.com

Certificate chain
  • cpcontacts.xpezdigital.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)
  • cpcontacts.xpezdigital.com
Alternative Names
  • autodiscover.xpezdigital.com
  • cpanel.xpezdigital.com
  • cpcalendars.xpezdigital.com
  • cpcontacts.xpezdigital.com
  • mail.xpezdigital.com
  • webdisk.xpezdigital.com
  • webmail.xpezdigital.com
  • www.xpezdigital.com
  • xpezdigital.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-02-14
Not valid after
2021-05-15
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
11:EC:B0:EE:7B:F3:F6:59:7A:E6:61:1D:DC:E6:2B:30:24:15:95:56:67:03:18:99:12:E6:84:8E:3E:78:F5:47
SHA1
17:7C:4C:94:46:A6:82:7C:BE:F9:AB:09:ED:38:32:26:3C:EE:8B:91
X509v3 extensions
subjectKeyIdentifier
  • 56:4C:FE:8A:18:C9:58:F7:D0:79:B6:48:78:86:B0:F9:58:49:2C:BA
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 : Feb 14 04:38:01.634 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:07:2D:38:8D:9F:45:A0:44:DF:D9:BE:57:
  • BE:9F:AE:A6:60:A2:42:AA:D7:65:AC:32:09:23:29:C7:
  • 9D:18:C9:39:02:21:00:E4:D8:2F:16:FB:C8:B3:55:AE:
  • FB:46:46:70:8B:84:A0:6A:D8:20:DC:D2:2D:2C:36:38:
  • A4:D1:37:44:65:7B:9F
  • 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 : Feb 14 04:38:01.619 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:FE:C2:74:BC:D4:ED:03:DB:96:03:78:
  • 46:C9:E7:30:D5:1E:85:C9:17:46:5E:39:28:5E:9C:D0:
  • 93:19:D3:01:60:02:20:43:42:F7:69:F9:FC:0A:89:CB:
  • 66:41:F1:4D:BB:BA:D1:67:BC:03:1D:14:2B:CE:B7:0F:
  • 20:97:7B:30:C4:BC:23