SSL-Tools

SSL check results of evopay.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for evopay.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 Thu, 03 Oct 2024 10:22:18 +0000

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

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

/mailservers/evopay.com

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.evopay.com
2a02:af8:3:600::3326
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
mail.evopay.com
92.48.122.207
 10
supported
mail.evopay.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
47 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.evopay.com

Certificate chain
  • mail.evopay.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.evopay.com
Alternative Names
  • mail.evopay.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2024-10-03
Not valid after
2025-01-01
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
9D:3B:37:62:43:85:84:9F:E6:EA:97:53:A5:39:4E:DC:EE:F3:79:D9:C6:F5:37:B4:F2:D1:05:FC:F9:AF:44:8C
SHA1
2D:17:DA:EA:5D:4B:1A:52:EE:F3:A4:34:ED:78:94:D8:91:59:42:2A
X509v3 extensions
subjectKeyIdentifier
  • 40:6A:D0:07:40:A3:A1:84:C1:69:59:91:51:6F:96:38:15:1D:0B:6C
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 : 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 : Oct 3 10:18:45.696 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:19:A4:C3:38:F9:70:FC:F6:42:9C:F5:A2:
  • 2E:77:A0:00:52:1B:E7:BF:07:46:C4:6D:B2:6C:2D:08:
  • F1:4F:C5:20:02:21:00:97:50:BA:27:A6:A1:85:67:6C:
  • 00:44:71:13:42:02:8E:2D:A6:5D:88:E2:51:EB:F0:45:
  • 86:13:7E:BE:CC:1C:8D
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CF:11:56:EE:D5:2E:7C:AF:F3:87:5B:D9:69:2E:9B:E9:
  • 1A:71:67:4A:B0:17:EC:AC:01:D2:5B:77:CE:CC:3B:08
  • Timestamp : Oct 3 10:18:45.718 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:F3:95:81:D8:87:6E:A8:91:AF:23:00:
  • 22:38:04:68:A9:0F:E0:F1:42:C4:85:9D:D6:02:18:94:
  • 0A:8B:78:C7:A4:02:20:41:A5:6B:E2:DE:18:1F:EB:F2:
  • 62:E6:C0:A9:54:5F:4C:5F:60:E3:8A:68:81:E3:AD:1A:
  • 0F:B8:6C:F5:44:95:13