SSL-Tools

SSL check results of ttc-net.ru

NEW You can also bulk check multiple servers.

Discover if the mail servers for ttc-net.ru 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, 14 Apr 2021 14:05:18 +0000

We can not guarantee a secure connection to the mailservers of ttc-net.ru!

Please contact the operator of ttc-net.ru and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/ttc-net.ru

Servers

Incoming Mails

These servers are responsible for incoming mails to @ttc-net.ru addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx.ttc-net.ru
217.21.208.234
 10
supported
titan.ttc-net.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
5 s
relay.ttc-net.ru
217.21.210.13
Results incomplete
20
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
relay.ttc-net.ru
217.21.210.18
 20
supported
demon.ttc-net.ru
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
5 s

Outgoing Mails

We have not received any emails from a @ttc-net.ru address so far. Test mail delivery

Certificates

First seen at:

emailAddress=support@ttc-net.ru,CN=titan.ttc-net.ru,OU=IT,O=AO Transtelecom,L=Moscow,ST=Russian Federation,C=RU

Certificate chain
  • titan.ttc-net.ru (Certificate is self-signed.)
    • remaining
    • 1024 bit
    • md5WithRSAEncryption
    • Hostname Mismatch
    • Unknown Authority
Subject
Country (C)
  • RU
State (ST)
  • Russian Federation
Locality (L)
  • Moscow
Organization (O)
  • AO Transtelecom
Organizational Unit (OU)
  • IT
Common Name (CN)
  • titan.ttc-net.ru
Email
  • support@ttc-net.ru
Issuer

Certificate is self-signed.

validity period
Not valid before
2018-12-13
Not valid after
2023-12-12
Fingerprints
SHA256
21:47:75:0E:92:77:A9:0D:0C:27:24:6F:49:45:D7:FC:22:B3:90:A3:DF:E7:42:38:C9:D8:C9:BF:D2:6A:35:0C
SHA1
60:0F:FA:86:5A:B9:8E:89:EF:F9:28:3D:E2:05:C3:16:2F:DC:3F:C4
X509v3 extensions
subjectKeyIdentifier
  • 66:7D:98:89:89:98:F6:FF:B7:8C:41:9E:BB:31:32:4F:F9:04:4D:B7
authorityKeyIdentifier
  • keyid:66:7D:98:89:89:98:F6:FF:B7:8C:41:9E:BB:31:32:4F:F9:04:4D:B7
  • DirName:/C=RU/ST=Russian Federation/L=Moscow/O=AO Transtelecom/OU=IT/CN=titan.ttc-net.ru/emailAddress=support@ttc-net.ru
  • serial:84:2B:48:75:C8:5E:59:F9
First seen at:

CN=demon.ttc-net.ru

Certificate chain
  • demon.ttc-net.ru (Certificate is self-signed.)
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch
    • Unknown Authority
Subject
Common Name (CN)
  • demon.ttc-net.ru
Alternative Names
  • demon.ttc-net.ru
Issuer

Certificate is self-signed.

validity period
Not valid before
2019-04-29
Not valid after
2029-04-26
Fingerprints
SHA256
62:EE:4F:ED:08:52:7B:9E:6C:E1:D2:B0:C2:DF:AB:7C:F7:91:AE:9C:BB:31:3B:54:5F:55:6B:3D:0C:93:75:AC
SHA1
F3:22:B7:99:68:6D:AC:E3:D8:8D:C8:CB:92:FF:82:9F:AB:AE:8F:BD