SSL-Tools

SSL check results of promt.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for promt.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 Sun, 04 Oct 2026 12:06:32 +0000

We can not guarantee a secure connection to the mailservers of promt.com!

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

/mailservers/promt.com

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
relayfe.promt.ru
178.238.31.139
 10
supported
relayfe.promt.ru
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
supported
  • SSL_RSA_WITH_RC4_128_SHA
  • SSL_RSA_EXPORT_WITH_RC4_40_MD5
  • TLSv1.0
  • SSLv3
2 s
mxbnl.promt.ru
185.130.226.79
Results incomplete
20 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
mail.promt.ru
178.238.31.171
Results incomplete
50 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s

Outgoing Mails

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

Certificates

First seen at:

CN=relayfe.promt.ru

Certificate chain
Subject
Common Name (CN)
  • relayfe.promt.ru
Alternative Names
  • relayfe.promt.ru
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2020-05-27
Not valid after
2020-08-25
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
7A:C0:73:F5:91:85:26:B6:D5:3E:DF:D0:2C:92:D9:8C:26:DF:03:A4:EB:FA:4D:CF:3F:11:72:93:38:73:0A:5D
SHA1
1F:49:15:75:50:D0:B1:C1:EF:DC:D6:79:08:BE:7F:49:E1:F8:63:05
X509v3 extensions
subjectKeyIdentifier
  • 3C:8C:12:DE:36:56:20:25:06:34:67:CF:0D:26:B2:0E:C2:EA:A6:41
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 : 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 : May 27 12:21:19.788 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:2A:6F:F4:E3:66:7E:FC:6B:E0:D4:E8:FD:
  • 75:91:A4:5D:F3:09:EF:09:99:25:50:3B:48:3E:F7:67:
  • 6A:28:65:5D:02:21:00:C4:09:00:3A:D2:EC:1C:3E:99:
  • AB:ED:61:1B:4C:44:B3:87:A6:F8:69:08:FA:68:F9:4E:
  • 63:6C:8A:A7:C6:2A:B6
  • 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 27 12:21:19.740 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:4C:E8:92:E2:F7:5A:3C:EB:CD:2F:1D:77:
  • 47:57:89:87:DF:C1:C8:60:43:C5:B6:77:9A:40:5D:D8:
  • 8A:08:9F:8B:02:20:38:C3:F1:0B:C8:B5:5C:81:A3:D0:
  • 31:40:08:0D:29:B1:53:D2:AD:A8:6F:29:7C:34:F7:CC:
  • 80:1E:7D:5D:44:05