SSL-Tools

SSL check results of proxyshield.io

NEW You can also bulk check multiple servers.

Discover if the mail servers for proxyshield.io 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, 05 Aug 2026 14:31:10 +0000

The mailservers of proxyshield.io can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @proxyshield.io addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx-public.relayproxy.io
193.135.8.80
 10
supported
*.relayproxy.io
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
7 s
mx-spare.relayproxy.io
193.135.8.89
 50
supported
*.relayproxy.io
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
7 s

Outgoing Mails

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

Certificates

First seen at:

CN=*.relayproxy.io

Certificate chain
  • *.relayproxy.io
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R12
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • *.relayproxy.io
Alternative Names
  • *.relayproxy.io
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R12
validity period
Not valid before
2026-05-17
Not valid after
2026-08-15
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
Fingerprints
SHA256
E5:75:2D:DF:22:D8:CA:60:91:D7:42:C1:15:1A:28:37:01:8C:A4:2B:99:D1:C3:62:C0:13:60:A3:43:BC:F7:52
SHA1
2C:10:7B:C7:CF:92:D7:81:CE:0D:CA:2D:9F:87:67:18:FD:CE:55:9D
X509v3 extensions
subjectKeyIdentifier
  • D2:23:1A:6D:68:9F:62:17:F9:5A:20:7D:9A:60:E7:55:08:DC:23:08
authorityKeyIdentifier
  • keyid:00:B5:29:F2:2D:8E:6F:31:E8:9B:4C:AD:78:3E:FA:DC:E9:0C:D1:D2
authorityInfoAccess
  • CA Issuers - URI:http://r12.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r12.c.lencr.org/105.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : D8:09:55:3B:94:4F:7A:FF:C8:16:19:6F:94:4F:85:AB:
  • B0:F8:FC:5E:87:55:26:0F:15:D1:2E:72:BB:45:4B:14
  • Timestamp : May 17 01:16:49.361 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:13:1B:3E:BB:A9:6F:2F:8E:F0:69:E8:11:
  • 87:FE:5E:87:42:CB:BC:AE:7C:9A:60:7D:D8:06:17:A2:
  • 67:C7:E0:AC:02:21:00:C4:EA:BC:D2:85:4D:FE:EB:FB:
  • D3:30:9A:07:EF:16:E4:DB:5E:7B:33:AD:6B:A9:35:B2:
  • C3:A0:44:BB:C2:9E:32
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 26:E3:64:6E:58:69:21:23:BC:34:3F:47:24:35:9B:37:
  • 92:CD:24:5A:88:D8:15:D3:93:33:FD:99:18:AB:47:23
  • Timestamp : May 17 01:16:49.262 2026 GMT
  • Extensions: 00:00:05:00:12:06:8B:6B
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:94:56:8A:D4:E3:63:15:6E:D1:FD:0D:
  • 80:8E:5C:E7:36:67:AE:4C:D1:00:E7:B8:AB:2B:A4:4F:
  • BF:F2:92:83:0F:02:20:74:C9:74:32:66:07:BD:DE:81:
  • A3:CE:B7:6D:6F:74:24:15:D2:91:FE:58:CA:6C:E2:C2:
  • D5:12:C3:F4:B9:DB:66