SSL check results of dolphsantorine.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for dolphsantorine.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 Fri, 15 Aug 2025 13:54:30 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.dolphsantorine.com
162.241.252.50
0
supported
cpcalendars.dolphsantorine.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
46 s

Outgoing Mails

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

Certificates

First seen at:

CN=cpcalendars.dolphsantorine.com

Certificate chain
  • cpcalendars.dolphsantorine.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)
  • cpcalendars.dolphsantorine.com
Alternative Names
  • autodiscover.dolphsantorine.com
  • cpanel.dolphsantorine.com
  • cpcalendars.dolphsantorine.com
  • cpcontacts.dolphsantorine.com
  • dolphsantorine.com
  • mail.dolphsantorine.com
  • webdisk.dolphsantorine.com
  • webmail.dolphsantorine.com
  • www.dolphsantorine.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-06-26
Not valid after
2025-09-24
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
AC:ED:86:A8:85:5F:FB:F1:C5:9E:40:CD:99:05:1D:CE:56:A0:64:C4:BC:DD:43:A5:4F:9A:2A:90:AF:1F:D3:1B
SHA1
EE:7A:5F:92:38:1A:89:82:AD:1F:74:2D:9A:DC:6D:D7:60:5D:C4:9C
X509v3 extensions
subjectKeyIdentifier
  • 7A:DB:25:9B:DC:56:A3:F6:9B:51:F6:BD:89:7D:A7:CE:A0:B6:2A:28
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r10.c.lencr.org/7.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7D:59:1E:12:E1:78:2A:7B:1C:61:67:7C:5E:FD:F8:D0:
  • 87:5C:14:A0:4E:95:9E:B9:03:2F:D9:0E:8C:2E:79:B8
  • Timestamp : Jun 27 00:37:25.413 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:D2:DC:56:9A:16:77:2C:55:A2:F7:72:
  • 96:8C:18:82:B3:CE:B3:F5:79:1B:42:AB:C9:11:A4:3F:
  • 73:BA:B7:72:B8:02:21:00:E8:1F:DD:F7:31:09:46:39:
  • 69:EE:52:6B:E9:70:B9:BB:90:19:99:AD:F0:26:7F:0C:
  • 29:14:09:15:46:EC:98:EC
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 0D:E1:F2:30:2B:D3:0D:C1:40:62:12:09:EA:55:2E:FC:
  • 47:74:7C:B1:D7:E9:30:EF:0E:42:1E:B4:7E:4E:AA:34
  • Timestamp : Jun 27 00:37:25.415 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:D1:1A:A4:0E:5D:94:ED:8C:94:33:EE:
  • 4A:5A:E4:D6:98:DF:94:83:F1:03:2F:22:D3:CE:CF:68:
  • 22:F2:E2:59:B3:02:21:00:F9:E6:67:DF:73:E5:5E:81:
  • 2E:84:54:91:66:CF:D8:5F:42:CF:CA:64:4C:18:10:25:
  • F8:98:B7:D2:71:D8:85:81