SSL check results of webnames.ru

NEW You can also bulk check multiple servers.

Discover if the mail servers for webnames.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

Report created Thu, 16 Mar 2023 07:20:25 +0000

We can not guarantee a secure connection to the mailservers of webnames.ru!

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

/mailservers/webnames.ru

Servers

Incoming Mails

These servers are responsible for incoming mails to @webnames.ru addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
ns1.regtime.net
87.229.239.234
0
supported
*.regtime.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
39 s
ns2.regtime.net
87.242.76.153
99
supported
*.regtime.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
10 s
il.regtime.net
217.79.22.229
Results incomplete
999 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 @webnames.ru address so far. Test mail delivery

Certificates

First seen at:

CN=*.regtime.net

Certificate chain
  • *.regtime.net
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
    • Unknown Authority

      R3
Subject
Common Name (CN)
  • *.regtime.net
Alternative Names
  • *.regtime.net
  • regtime.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2023-02-15
Not valid after
2023-05-16
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
6B:0F:56:FD:00:0D:92:DF:6B:29:32:5D:C3:6E:8D:4B:D1:BB:6C:6A:87:BE:2B:54:D0:3A:5D:E3:4E:63:71:02
SHA1
1F:1C:1D:7D:2D:47:CA:B8:DE:20:E2:C6:08:0A:29:E4:1B:7D:32:BC
X509v3 extensions
subjectKeyIdentifier
  • 12:71:C7:9E:BF:1E:9E:8B:C0:CE:75:9B:52:76:B2:FE:85:85:DE:CC
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
  • 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 : 7A:32:8C:54:D8:B7:2D:B6:20:EA:38:E0:52:1E:E9:84:
  • 16:70:32:13:85:4D:3B:D2:2B:C1:3A:57:A3:52:EB:52
  • Timestamp : Feb 15 05:31:00.199 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:AB:74:4E:30:E9:65:42:1E:1C:AD:6A:
  • 81:B0:96:05:3E:7B:CC:5A:D4:C1:5D:C9:7A:3B:53:65:
  • 21:01:91:AE:EE:02:20:46:05:FD:EA:B3:FB:E9:08:8F:
  • 64:99:DD:3F:B1:64:E2:F4:D7:F6:A1:4B:2E:75:D8:C8:
  • 67:8E:47:C3:D8:B3:7F
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : AD:F7:BE:FA:7C:FF:10:C8:8B:9D:3D:9C:1E:3E:18:6A:
  • B4:67:29:5D:CF:B1:0C:24:CA:85:86:34:EB:DC:82:8A
  • Timestamp : Feb 15 05:31:00.225 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:04:09:F9:A8:1D:57:05:F7:34:2E:EB:B0:
  • 5E:53:51:88:C3:45:3C:64:3E:D2:1C:53:37:32:21:25:
  • 87:C2:D4:63:02:20:34:FD:C2:F1:81:BB:A0:02:5C:E0:
  • D5:DC:D6:F3:18:34:65:81:48:09:C3:61:02:CD:0B:B0:
  • B6:69:27:36:03:E6