SSL check results of jaimeayala.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for jaimeayala.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 Sun, 19 Jul 2026 00:31:12 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mx1.secria.me
2a02:c207:2247:9170::1
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
4 s
mx1.secria.me
173.212.225.151
10
supported
mx1.secria.me
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
mx2.secria.me
173.212.225.151
20
supported
mx1.secria.me
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=mx1.secria.me

Certificate chain
  • mx1.secria.me
    • remaining
    • 384 bit
    • ecdsa-with-SHA384

      • YE2
        • remaining
        • 384 bit
        • ecdsa-with-SHA384

          • Root YE
            • remaining
            • 384 bit
            • ecdsa-with-SHA384

              • ISRG Root X2 (Certificate is self-signed.)
                • remaining
                • 384 bit
                • ecdsa-with-SHA384

Subject
Common Name (CN)
  • mx1.secria.me
Alternative Names
  • mx1.secria.me
  • mx2.secria.me
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • YE2
validity period
Not valid before
2026-07-14
Not valid after
2026-10-12
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
Fingerprints
SHA256
E5:58:EB:AD:23:BB:10:7B:7C:92:F7:5D:6C:47:D9:E6:50:A7:69:36:0A:38:C2:C4:1A:AA:A0:6C:7B:97:57:5F
SHA1
E3:78:34:BE:FE:E4:31:DF:29:1C:FD:E2:C5:F1:AE:3B:20:C8:33:FA
X509v3 extensions
subjectKeyIdentifier
  • 19:ED:CA:FF:10:69:65:5C:45:7A:46:43:E0:17:F3:91:08:D1:00:76
authorityKeyIdentifier
  • keyid:B9:59:F2:8E:CF:22:F0:86:D3:37:48:FF:76:14:18:BA:82:D8:55:87
authorityInfoAccess
  • CA Issuers - URI:http://ye2.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://ye2.c.lencr.org/108.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : C8:A3:C4:7F:C7:B3:AD:B9:35:6B:01:3F:6A:7A:12:6D:
  • E3:3A:4E:43:A5:C6:46:F9:97:AD:39:75:99:1D:CF:9A
  • Timestamp : Jul 14 13:28:28.739 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:9C:BA:A8:5D:5B:11:55:E8:E5:2E:D3:
  • CC:B9:F7:4B:29:E8:EB:59:A6:A4:B9:10:45:7F:C4:94:
  • 8B:C5:37:E2:45:02:20:2D:E0:DF:85:FE:6D:F1:D5:CE:
  • D8:BD:94:35:FE:89:C4:C6:BF:B3:73:52:B9:C7:1C:1B:
  • 41:5F:0C:09:BC:B8:76
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 46:AF:86:3D:3B:3E:E5:9F:A5:77:DE:A8:24:5D:36:B0:
  • D9:ED:22:A2:23:F4:61:77:41:22:94:52:EE:95:50:5F
  • Timestamp : Jul 14 13:28:28.844 2026 GMT
  • Extensions: 00:00:05:00:0C:F1:46:6B
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:C7:20:6E:ED:78:47:D0:85:85:81:DD:
  • D0:00:25:CC:49:9D:E9:82:EC:53:05:9A:26:9D:91:FB:
  • B1:D8:01:EC:4A:02:21:00:E1:55:16:37:FF:D3:0B:57:
  • 61:4B:BB:1E:AE:7A:87:08:77:68:5C:4E:50:78:4A:A2:
  • DB:82:1A:22:EF:40:5C:FB