SSL-Tools

SSL check results of smartftp.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for smartftp.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 Wed, 17 Apr 2024 23:32:40 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.smartftp.com
2a01:4f8:192:40d4::6
 10
supported
mail.smartftp.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
mail.smartftp.com
148.251.142.76
 10
supported
mail.smartftp.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.smartftp.com

Certificate chain
  • mail.smartftp.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.smartftp.com
Alternative Names
  • mail.smartftp.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-15
Not valid after
2024-07-14
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
AF:45:BD:4A:44:95:57:32:89:D0:79:CD:58:F7:D6:3B:1F:59:5C:2D:76:2F:30:D3:0E:08:F7:AF:00:9D:E9:F4
SHA1
AA:6A:5D:08:75:8B:8B:4F:E7:14:FF:21:9F:15:23:67:50:6D:66:83
X509v3 extensions
subjectKeyIdentifier
  • 83:14:72:98:4A:63:8E:82:7F:68:1D:0F:DC:71:58:25:A4:6F:CB:6D
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
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Apr 16 00:24:04.141 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:0B:AC:EF:A4:29:A3:DD:CC:F8:03:2F:B0:
  • 28:49:7A:7A:60:1F:5F:BC:CD:36:49:69:B6:77:CC:E2:
  • 06:C8:1A:CE:02:20:52:08:51:5B:86:EF:F7:76:14:C3:
  • 2F:31:55:E1:00:0C:7C:DA:FF:FB:54:12:B7:19:A7:E7:
  • 08:98:6C:28:4B:70
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 19:98:10:71:09:F0:D6:52:2E:30:80:D2:9E:3F:64:BB:
  • 83:6E:28:CC:F9:0F:52:8E:EE:DF:CE:4A:3F:16:B4:CA
  • Timestamp : Apr 16 00:24:04.205 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:E7:70:50:95:4E:AC:EE:31:C4:C8:42:
  • E9:4A:F0:77:71:58:5E:5C:8E:58:AD:4B:B3:74:B6:7E:
  • DB:A1:D2:3B:76:02:21:00:82:55:9E:6B:98:53:60:4B:
  • 07:0E:12:84:E6:13:EF:D5:04:20:23:A8:86:9F:C2:32:
  • BA:FF:30:1E:A1:B8:AB:9C