SSL-Tools

SSL check results of lin-mail.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for lin-mail.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

JSON Refresh

Report created Fri, 16 Apr 2021 07:42:38 +0000

The mailservers of lin-mail.com can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @lin-mail.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
lin-mail-com.mail.cloud.nospamproxy.com
193.37.132.131
 10
supported
*.mail.cloud.nospamproxy.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
lin-mail-com.mail.cloud.nospamproxy.com
193.37.132.171
 10
supported
*.mail.cloud.nospamproxy.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=*.mail.cloud.nospamproxy.com

Certificate chain
  • *.mail.cloud.nospamproxy.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption
Subject
Common Name (CN)
  • *.mail.cloud.nospamproxy.com
Alternative Names
  • *.mail.cloud.nospamproxy.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-03-28
Not valid after
2021-06-26
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
5C:07:A1:52:D8:0C:A8:89:18:C6:4E:97:17:24:59:56:70:B4:A3:21:B8:F1:AF:83:13:1B:64:F4:58:7C:AA:22
SHA1
F2:2B:B3:A8:68:88:61:57:88:A1:69:3D:0A:E6:1A:28:B6:90:A4:8A
X509v3 extensions
subjectKeyIdentifier
  • F4:61:56:EA:CA:57:A2:70:51:66:B0:AE:2A:5E:8E:A6:F5:87:2D:87
authorityKeyIdentifier
  • keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
authorityInfoAccess
  • OCSP - URI:http://r3.o.lencr.org
  • CA Issuers - URI:http://r3.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
  • 15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
  • Timestamp : Mar 28 07:19:16.989 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:B3:EA:4E:81:EC:AE:77:03:48:34:03:
  • 1B:14:46:F5:3E:6D:FC:7D:8B:8D:67:90:47:00:2F:54:
  • 2E:7A:5C:7D:A0:02:21:00:D5:CE:D6:05:15:C2:24:71:
  • C6:88:A0:1D:CC:EE:EC:FF:A4:BA:85:8E:46:9A:EF:0D:
  • 52:C3:5B:AB:9F:C8:AD:FD
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
  • E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
  • Timestamp : Mar 28 07:19:16.931 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:40:7E:30:87:11:CC:0C:1F:5D:CA:55:8A:
  • 0D:AF:8A:40:DD:5B:0B:D0:48:C5:F4:0B:EA:00:9E:D2:
  • 3E:34:3C:F7:02:21:00:A3:7A:10:97:89:26:AC:5A:F0:
  • 2E:AA:77:B4:F7:15:21:31:76:D7:55:3D:2F:42:76:23:
  • F8:63:A1:91:7A:4A:7A