SSL-Tools

SSL check results of mail.rese.com.mx

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.rese.com.mx 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 Mon, 14 Apr 2025 15:23:02 +0000

The mailservers of mail.rese.com.mx can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @mail.rese.com.mx addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.rese.com.mx
199.231.163.34
 -
supported
mail.rese.com.mx
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
7 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.rese.com.mx

Certificate chain
  • mail.rese.com.mx
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.rese.com.mx
Alternative Names
  • mail.rese.com.mx
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-03-03
Not valid after
2025-06-01
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
D4:E7:E3:F3:9B:35:AE:6F:45:0E:AD:82:41:24:D3:AE:06:1E:2B:6F:3A:CB:05:6E:B0:5C:19:61:57:5F:CA:CE
SHA1
7F:91:4C:DC:7E:48:64:F9:71:71:16:CB:A2:48:AA:0B:8A:30:E0:2C
X509v3 extensions
subjectKeyIdentifier
  • 0E:AE:3D:4A:F8:F6:D1:F4:AB:5E:34:1E:D9:08:A1:FB:F4:B4:F6:72
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : Mar 3 22:40:13.477 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:72:47:01:15:84:16:A2:3B:8A:4D:EF:9B:
  • 29:FC:98:FA:8F:FC:86:C8:55:C2:EC:B7:51:A4:C4:00:
  • B9:B1:4F:69:02:20:7E:97:AD:AB:CC:4D:77:B4:C2:4D:
  • DC:27:50:37:62:BA:EB:8B:B6:20:3D:6A:74:CA:B5:64:
  • 79:F7:9A:2A:90:11
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E6:D2:31:63:40:77:8C:C1:10:41:06:D7:71:B9:CE:C1:
  • D2:40:F6:96:84:86:FB:BA:87:32:1D:FD:1E:37:8E:50
  • Timestamp : Mar 3 22:40:13.482 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:37:42:36:F6:53:4B:62:E9:7C:D2:ED:6F:
  • 03:80:8A:D1:98:EC:ED:30:F8:DB:BF:B1:6A:EA:CA:6D:
  • 12:62:E5:62:02:21:00:B1:6C:1F:A9:DC:47:83:45:8B:
  • 1B:B1:C8:7D:B8:7D:E1:76:17:AA:44:2E:70:14:30:68:
  • 49:5D:AB:B1:90:87:12