SSL-Tools

SSL check results of ailant.org

NEW You can also bulk check multiple servers.

Discover if the mail servers for ailant.org 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, 17 Jun 2020 00:30:45 +0000

The mailservers of ailant.org can be reached through an encrypted connection.

However, we found problems that may affect the security.

Servers

Incoming Mails

These servers are responsible for incoming mails to @ailant.org addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx.ailant.org
213.234.27.36
 10
supported
mail.ailant.org
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
supported
  • ECDHE_RSA_WITH_RC4_128_SHA
  • SSL_RSA_WITH_RC4_128_SHA
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
14 s
mx.ailant.com.ru
213.234.27.36
 30
supported
mail.ailant.org
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
supported
  • ECDHE_RSA_WITH_RC4_128_SHA
  • SSL_RSA_WITH_RC4_128_SHA
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
14 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.ailant.org

Certificate chain
Subject
Common Name (CN)
  • mail.ailant.org
Alternative Names
  • mail.ailant.com.ru
  • mail.ailant.org
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2020-05-17
Not valid after
2020-08-15
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
25:9F:6C:B6:8C:5D:F3:D9:B7:E4:3F:D1:2B:86:FE:AA:52:99:CA:D0:54:EF:2B:38:F2:9B:AB:5B:80:C8:82:A6
SHA1
46:E2:70:19:C8:4E:11:31:7E:B4:F5:50:93:CB:7E:41:CD:A5:B8:42
X509v3 extensions
subjectKeyIdentifier
  • 70:0D:B6:19:5F:35:01:DD:7A:69:4A:6D:43:19:28:F6:90:11:B5:33
authorityKeyIdentifier
  • keyid:A8:4A:6A:63:04:7D:DD:BA:E6:D1:39:B7:A6:45:65:EF:F3:A8:EC:A1
authorityInfoAccess
  • OCSP - URI:http://ocsp.int-x3.letsencrypt.org
  • CA Issuers - URI:http://cert.int-x3.letsencrypt.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 : E7:12:F2:B0:37:7E:1A:62:FB:8E:C9:0C:61:84:F1:EA:
  • 7B:37:CB:56:1D:11:26:5B:F3:E0:F3:4B:F2:41:54:6E
  • Timestamp : May 17 08:17:11.575 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:C1:2F:31:F5:A2:EA:23:90:B0:A8:BF:
  • AD:43:CF:14:A0:AD:D6:14:C3:2A:E2:88:39:20:67:47:
  • 56:CB:45:09:33:02:20:48:E4:E2:7E:82:E1:1B:CE:78:
  • D1:DE:9B:CC:68:00:A5:6B:DE:52:40:E5:B5:EE:4B:6D:
  • 02:6F:51:B8:6B:F9:EC
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : B2:1E:05:CC:8B:A2:CD:8A:20:4E:87:66:F9:2B:B9:8A:
  • 25:20:67:6B:DA:FA:70:E7:B2:49:53:2D:EF:8B:90:5E
  • Timestamp : May 17 08:17:11.576 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:65:1A:5A:A8:62:40:E5:C6:17:B0:32:49:
  • 53:42:CB:CA:A7:4D:66:13:CA:73:C1:11:16:14:5C:81:
  • 22:B8:EB:42:02:21:00:C5:EF:A5:65:C6:AB:72:A8:90:
  • B3:AA:86:31:34:14:D7:45:F0:C8:BE:76:66:AB:55:E4:
  • 40:90:E1:A2:0E:1D:DD