SSL-Tools

SSL check results of make24.io

NEW You can also bulk check multiple servers.

Discover if the mail servers for make24.io 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 Wed, 10 Mar 2021 07:49:55 +0000

The mailservers of make24.io can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @make24.io addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.make24.io
2a03:4000:52:d74::1
 10
supported
make24.io
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
mail.make24.io
202.61.243.230
 10
supported
make24.io
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

We have received emails from these servers with @make24.io sender addresses. Test mail delivery

Host TLS Version & Cipher
mail.make24.io (IPv6:2a03:4000:52:d74::1)
TLSv1.3 TLS_AES_256_GCM_SHA384
mail.make24.io (202.61.243.230)
TLSv1.3 TLS_AES_256_GCM_SHA384

Certificates

First seen at:

CN=make24.io

Certificate chain
  • make24.io
    • 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)
  • make24.io
Alternative Names
  • *.make24.io
  • make24.io
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-02-22
Not valid after
2021-05-23
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
F5:7F:5A:F3:C7:4B:DC:87:23:AA:07:07:52:D3:AC:49:17:65:13:0F:92:DE:F4:78:82:78:18:34:AB:F3:7A:06
SHA1
A9:7C:1B:5B:57:3E:D2:88:44:43:BF:9F:AC:D3:C7:34:E3:D5:FC:11
X509v3 extensions
subjectKeyIdentifier
  • 9F:2E:B7:22:72:ED:F2:27:B6:55:B6:5F:EB:6C:53:FC:D0:A2:08:AE
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 : Feb 22 23:01:39.280 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:B7:FA:2F:C6:24:83:5C:FC:42:A8:4E:
  • C6:C3:69:07:3F:A5:AD:F4:D2:60:74:20:BA:6F:2B:35:
  • 7F:9A:14:B6:19:02:21:00:9C:EC:CA:B8:8C:6C:96:FF:
  • FB:30:94:E5:D1:4C:3F:DE:03:56:98:00:42:F0:A9:08:
  • 11:CA:D2:71:57:DF:0B:C0
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
  • 79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
  • Timestamp : Feb 22 23:01:39.336 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:8F:7F:C2:12:5F:CC:E3:D2:C2:BA:E8:
  • 2E:F5:19:CE:04:84:EB:2D:2C:C9:30:97:12:D3:F1:B7:
  • D4:9E:62:B7:4A:02:21:00:FA:C9:F1:33:C8:1C:91:BC:
  • 56:34:B4:F3:20:32:F7:61:B8:6E:AD:74:F4:04:2B:11:
  • 0D:DD:EB:D3:06:7C:BD:CC