SSL-Tools

SSL check results of mail.infomarine.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.infomarine.net 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 Sun, 07 Jun 2026 00:30:45 +0000

The mailservers of mail.infomarine.net can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @mail.infomarine.net addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.infomarine.net
185.194.218.135
 -
supported
www.infomarine.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
3 s

Outgoing Mails

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

Certificates

First seen at:

CN=www.infomarine.net

Certificate chain
  • www.infomarine.net
    • remaining
    • 256 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)
  • www.infomarine.net
Alternative Names
  • cpanel.infomarine.net
  • ftp.infomarine.net
  • infomarine.net
  • mail.infomarine.net
  • webmail.infomarine.net
  • www.infomarine.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • YE2
validity period
Not valid before
2026-06-02
Not valid after
2026-08-31
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
Fingerprints
SHA256
2C:F6:70:E5:4F:E7:E7:01:6E:44:0D:D2:F0:69:14:53:9F:6B:44:C3:19:57:0B:32:0D:EB:95:90:B1:F7:5F:0B
SHA1
E3:B0:5F:C1:90:38:5E:01:15:82:D8:66:59:94:C1:CC:D5:96:71:FE
X509v3 extensions
subjectKeyIdentifier
  • 92:63:87:19:65:12:88:0F:7A:93:FE:27:57:66:19:4A:E4:BE:ED:2E
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/34.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : D7:6D:7D:10:D1:A7:F5:77:C2:C7:E9:5F:D7:00:BF:F9:
  • 82:C9:33:5A:65:E1:D0:B3:01:73:17:C0:C8:C5:69:77
  • Timestamp : Jun 2 11:41:36.359 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:47:69:0C:6B:50:8D:6A:DD:E8:50:19:87:
  • 15:7F:30:11:D1:50:A3:96:B3:BE:60:E9:81:9F:C0:2D:
  • 7C:C6:31:0F:02:20:66:28:A4:37:AC:77:6B:8D:01:6D:
  • F4:99:A8:BB:E8:7D:E1:98:44:CA:1A:E2:29:55:E8:41:
  • 32:A0:40:98:E4:FA
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 1A:8B:9D:6B:0F:FE:BF:81:B4:79:39:C6:D2:31:0A:86:
  • D6:D1:02:D4:F0:46:E2:18:2C:9D:E3:5F:5E:26:25:EF
  • Timestamp : Jun 2 11:41:36.701 2026 GMT
  • Extensions: 00:00:05:00:19:9E:60:97
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:58:1A:A8:0D:EB:25:8C:E0:91:6B:59:0B:
  • DF:6D:CA:88:91:4E:C5:E1:4F:B3:9D:37:4D:58:28:73:
  • 61:A3:18:BB:02:20:18:97:EF:FE:B6:B1:D4:15:F9:DE:
  • DF:1B:1D:50:D2:98:90:1F:E0:B4:23:03:CC:26:F0:8C:
  • 26:CF:05:73:70:46