SSL-Tools

SSL check results of smartsoftserv.ro

NEW You can also bulk check multiple servers.

Discover if the mail servers for smartsoftserv.ro 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 Mon, 28 Apr 2025 15:05:28 +0000

We can not guarantee a secure connection to the mailservers of smartsoftserv.ro!

Please contact the operator of smartsoftserv.ro and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/smartsoftserv.ro

Servers

Incoming Mails

These servers are responsible for incoming mails to @smartsoftserv.ro addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.smartsoftserv.ro
5.2.229.238
 10
supported
mail.smartsoftserv.ro
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
mail.blackseasuppliers.ro
5.2.229.242
Results incomplete
20
supported
not checked
DANE
missing
PFS
unsupported
Heartbleed
not vulnerable
Weak ciphers
supported
  • SSL_RSA_WITH_RC4_128_SHA
  • TLSv1.0
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.smartsoftserv.ro

Certificate chain
  • mail.smartsoftserv.ro
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.smartsoftserv.ro
Alternative Names
  • mail.smartsoftserv.ro
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-04-04
Not valid after
2025-07-03
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
4B:E9:20:45:84:E6:32:66:F9:55:1C:C5:74:A6:26:63:AF:CD:7E:61:04:76:49:74:26:F4:F0:F6:7F:F3:29:D1
SHA1
92:27:BB:DC:87:76:EE:C3:72:A8:8D:B9:65:D2:D1:47:4F:24:3A:7C
X509v3 extensions
subjectKeyIdentifier
  • 24:1C:9C:D9:F9:C5:AC:37:0D:15:98:FC:29:8F:F3:DC:1B:05:07:A5
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r10.c.lencr.org/127.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 0D:E1:F2:30:2B:D3:0D:C1:40:62:12:09:EA:55:2E:FC:
  • 47:74:7C:B1:D7:E9:30:EF:0E:42:1E:B4:7E:4E:AA:34
  • Timestamp : Apr 4 21:00:47.898 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:BC:49:58:E8:11:17:FE:BA:56:13:79:
  • E8:D2:27:C3:AB:FF:0E:13:0D:98:FA:B1:43:BC:FA:97:
  • 59:B8:77:A1:1B:02:20:2F:92:18:68:F9:1F:67:E2:73:
  • 00:33:35:21:FA:2B:91:A0:14:AE:9F:33:28:1E:FC:2D:
  • C3:FB:B7:6B:0A:1E:F7
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A4:42:C5:06:49:60:61:54:8F:0F:D4:EA:9C:FB:7A:2D:
  • 26:45:4D:87:A9:7F:2F:DF:45:59:F6:27:4F:3A:84:54
  • Timestamp : Apr 4 21:00:47.899 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:84:49:4B:1B:F3:29:10:6E:DE:24:EE:
  • 5F:30:64:C6:0D:56:45:82:1F:34:E0:07:A6:08:B6:A3:
  • 8D:BA:EE:2B:6B:02:21:00:86:5B:0D:48:61:80:36:BA:
  • DF:A5:3E:43:31:C5:1C:C5:8B:1A:77:91:B8:63:3C:9C:
  • AC:A0:A1:08:3F:CA:40:2F