Our rules

UAS Rules

Before you start using our service we strongly recommend you to read the rules of our service.

The users are allowed to:

  • Use our SOCKS for surfing in the Internet and for their application in the software which does not produce a large load on the server.
  • Use a single account by multiple users or group of users simultaneously.
  • Use absolutely any software on RDP-servers.

The users are prohibited from:

  • Using our SOCKS/SSH for spamming and other activity, due to which the SOCKS can get into the blacklist of Spamhaus.
  • Using the software which gives access to SOCKS/SSH/RDP to third parties, as well as multi-threaded software which can produce a large load on the server.
  • Making attempts to hack the service, as well as from launching Metasploit, Nmap, Acunetix and other scanners.
  • Publishing SOCKS/SSH/RDP purchased in the public domain.


Violation of the rules of our service entails a ban with no refund of the deposit!

Privacy Policy

  1. We do not disclose our customer information.
  2. We do not keep logs of connections, and do not charge the traffic from SOCKS/SSH/RDP.
  3. We do not save IP addresses, which you use when connecting to SOCKS/SSH/RDP.



  • Our service provides two options for buying SOCKS at a base price:
  1. Buying of SOCKS5 for 24-hour period – 0.25 USD (just click on “BUY”)
  2. Full buy-out of SOCKS5 for 24-hour period – 0.80 USD (just click on “BUY OUT”) – please select this option if you do not want to have "neighbors" on the server.
  • Appreciation of SOCKS is possible for the following reasons:
  1. Price for the SOCKS added less than 5 hours ago – 0.15 USD
  2. Price for the SOCKS, the ProxyScore of which is below 1 – 0.20 USD
  • Discounts for the SOCKS, which are in the Blacklist:
  1. Socks Blacklisted (Spamhaus XBL, SBL) – 50%
  2. Socks Low Risk (Spamhaus PBL) – 25%
  • After the purchase of SOCKS (the access to SOCKS will be active for 24 hours), you get the IP address of our server, which can be different from the IP addresses of the purchased SOCKS, but during the operation your outbound IP address is the one you have bought. Sometimes, IP address and port may change – you can see your current IP address and port in the purchase history.
  • Be aware that when you buy SOCKS by the first option (the “BUY” button), the same SOCKS can be bought by someone else in addition to you, so if you do not want to have "neighbors" on the server, you can buy out the SOCKS completely by clicking on “BUY OUT”. Thus, you will be able to use the SOCKS individually for 24 hours.


  • Our service sells RDP servers at the following prices:



Windows XP - 3 USD

Windows Vista - 5 USD

Windows 7 - 8 USD

Windows 8 - 9 USD

Windows 10 - 9 USD

Windows 2003 server - 3 USD

Windows 2008 server - 7 USD

Windows 2012 server - 8 USD




Windows XP - 5 USD

Windows Vista - 7 USD

Windows 7 - 8 USD

Windows 8 - 10 USD

Windows 10 - 10 USD

Windows 2003 server - 5 USD

Windows 2008 server - 7 USD

Windows 2012 server - 9 USD




Windows XP - 5 USD

Windows Vista - 6 USD

Windows 7 - 7 USD

Windows 8 - 9 USD

Windows 10 - 9 USD

Windows 2003 server - 3 USD

Windows 2008 server - 6 USD

Windows 2012 server - 6 USD




Windows XP - 5 USD

Windows Vista - 6 USD

Windows 7 - 7 USD

Windows 8 - 9 USD

Windows 10 - 8 USD

Windows 2003 server - 3 USD

Windows 2008 server - 6 USD

Windows 2012 server - 7 USD


  • Appreciation of RDP server is possible for the following reasons:
  1. Price for the RDP server added less than 5 hours ago – 1 USD
  2. Price for the RDP server, the ProxyScore of which is below 1 – 1 USD
  3. Price for the RDP server registered accounts less than 7 - 1 USD
  4. Price for the RDP server with Direct IP - 1 USD
  5. Price for the RDP server with opened port 25 - 1 USD


Deposit Refund


  1. Refund of the amount used for the purchase of SOCKS/SSH/RDP, can be made on the user account balance only.
  2. Refund on the account balance is possible if the purchased RDP/SOCKS has worked less than 2 hours from the time of purchase.
  3. Refund on the account balance is possible only in case of a real malfunction of RDP or identification of duplicate (one server can be accessed across multiple IP addresses).
  4. Refund is possible in case of discrepancy with the description (for example, if the checker has not found the use of PayPal/Ebay/other system on RDP, but, when checking, you have found that the purchased RDP has been used on those resources). The main thing is to provide a detailed description of the problem in a support ticket.
  • Carefully check the description of RDP server before you buy! If the server has been tested for more than seven days before, the information about it is most likely not actual and in this case the refund of the money spent on the purchase of RDP server is impossible!
  1. Refund on the account balance is possible only in case of malfunction of the browser on the purchased RDP.
  2. Refund of the funds contributed to the account, back to your wallet is impossible. Create tickets if you have made a mistake in the amount when replenishing your account balance.
  3. Refund for the purchased SSH/RDP is impossible. All SSH/RDP are automatically checked by our system immediately prior to the sale. Exceptions are RDP on which a locker has been installed. In this case, the refund for the purchased RDP on the account balance can be made within 30 minutes after the purchase.
  4. Refund is impossible if you use SOCKS5 in the software which is not designed to work with this protocol. We guarantee the work of SOCKS only in the software which works with the protocol (e.g. Proxifier).
  5. Refund is impossible if geo location of RPD or Socks is different with results of third-parties checkers because we use our own GeoIP Database which we believe is the most accurate. To avoid conflicts we created a feature of pre-purchasing IP address of RDP or Socks for all clients that uploaded their balances for $20 or more. So if you don't believe our GeoIP database you have to buy IP address and check it on your Geo Checker and then decide to buy a product or not.
  6. Refund is impossible if the DNS of SOCKS does not coincide with its country.
  7. Refund for the SOCKS, which changed the IP address and/or port while working, is impossible.
  8. We check the IP addresses of our SOCKS/SSH/RDP only in the Spamhaus blacklists. If the IP address has appeared in the blacklist of other services, the refund of the amount spent for the purchase, is impossible. For the refund please log in the history of your purchases and click on "Refund". Our system will automatically check the status of SOCKS/SSH/RDP and make a refund on your account balance.
  9. Refund is impossible if you have changed the login/password, blocked the user account, etc. on the purchased RDP.
  10. Refund is impossible if any of your software does not work on the purchased RDP server.
  11. Refund is impossible if you have used the purchased RDP server and it has the traces of your presence.
  12. Refund is not available for RDP servers that have been added on sell less than 12 hours ago.
  13. Refund is impossible if you have no connection to RDP. Our checker automatically checks for the availability of RDP connection and accuracy of login and password, so you have to check the problem independently. The problem may lie in your provider/VPN/SOCKS. To connect to RDP, we recommend using the utility of RDP plug-in for Google Chrome, download link.
  14. Refund is impossible if RDP works in RDP Plugin for Google Chrome.
  15. In case of violation of the rules, your account shall be blocked automatically or by the administrator. Unlocking of the account is only possible after reviewing your violation by the service administration and/or payment of a fine. The fine shall be set by the service administration.


If you put RDP on resell it will be checked. If RDP is alive and valid it will be placed on sell.

You may change your mind and remove RDP from resale only at the checking stage. After RDP is checked and put on the sell, it can not be returned back.

After someone bought your RDP, you will receive 30% of the price of which RDP was purchased by you. If the new RDP owner makes a return for it due to the inoperability of RDP or its main systems, then in this case, the fee will be charged off (30% of the price)

Your RDP will not be shown to you in the general RDP list.

These rules may be supplemented and updated by the service administration – you can read about the updates of the service rules in the news.




  • Below you can find some of the answers to frequently asked questions when connecting to SOCKS/SSH/RDP:


A) There is no connection, and you get an error that the server is offline – the problem is about your provider which blocks the connection to the network, wherein the purchased RDP is located. It can be connected to the other servers, but there’s no connection to this RDP because of blocking. Try to change your SOCKS/VPN and then try to connect to RDP once again.

B) There is no connection, and you get an error that the server is offline – the problem may lie in connecting to the wrong RDP port. See the detailed information about RDP and check the connection port (3390 or 3391), enter the necessary port in the RDP IP address input field (e.g.

C) Not suitable login/password – the reason may lie in entering an incorrect login. If, when purchasing, you have received the login of ‘seller/admin’ type, then insert it as it is, without separation.

D) There is no password to the purchased RDP – you have bought a dedicated server without a password. Please enter only the login and leave the password field blank. If there is still no connection, then perhaps your OS uses an outdated connection protocol; if you use Windows 7, try to install this update. The problem may also lie in the licenses on your computer, in this case you should remove MSLicensing folder from the register. If the purchased RDP runs on Windows 2003 and shows the error “Max connections...”, you should connect to it with administrator rights, thus you need to run the command of ‘mstsc.exe/admin’.

E) If you use Windows XP, there is a chance that you will not be able to connect to some RDPs running on Windows 7 or Windows 2008, wherein the security of Network Level Authentication is enabled. To connect to such servers, you need to install this update. After the update is installed, we recommend you to restart your computer.

F) Not suitable login/password (if you connect to the purchased RDP server via ‘mstsc’ command) – another reason may lie in the fact that the checker was unable to get the fully qualified domain name for the login. In this case, download a special plug-in for Google Chrome by this link, then activate it and click on "Start", then enter the login and password for the RDP server, and then a remote desktop will be on, and you will be launched to the purchased RDP. To have an ability to connect to RDP server via ‘mstsc’ command (Remote Desktop Connection), you should do the following:


Once you have successfully connected to a remote desktop by the plugin for Google Chrome, while staying on the connected RDP server, you need to right click on the icon "My Computer" and copy the contents of the field ‘Domain Name’: ‘example.local’ or ‘anygroup’ into the clipboard (Ctrl C). Then substitute the domain name before the login in the format of ‘example.local/administrator’ or ‘anygroup/guest’. Having received a new login (‘example.local/administrator’ or ‘anygroup/guest’), you shall enter it, when connecting via ‘mstsc’ command, along with the password which you have obtained from our automatic service.


  • If you are frequently disconnected from the RDP server, it means that another user is working on the RDP at the moment. In this case, we recommend you to wait a bit until the server owner has finished, otherwise he can suspect any suspicious activity and change the password on the server. Especially, this problem concerns Windows OS of 7, 8, 8.1 and 10 versions. By default, the said operating systems do not support the mode of simultaneous work of multiple users on server, and therefore you need to install a special patch.
  • If there is no Internet access or certain sites cannot be opened on the purchased RDP server, then you need to perform a few checks:
    • Check in your browser settings, whether proxy is enabled or not (if it is enabled, turn it off and try again).
    • Check in the section of "Protocol TCP\IP" of the network connection settings, which DNS address is inscribed there (and whether it is inscribed at all). If there is no DNS, enter the Google DNS address – It is better not to change the settings of the IP address, mask and gateway.
    • Launch a command prompt in the administrator mode and type the command: ipconfig/flushdns. Next, enter the following command: netsh winsock reset. After completing these steps, restart the RDP and check the Internet.
    • If none of the methods does not work, it means that the operation with the network is limited by the established router.
  • If you have got any RDP server with the login of Administrator/Root/Admin, we strongly do not recommend you to work under this account, since the chance that the real owner of the server suspects that something is wrong, increases several times.
  • Before buying RDP server, pay attention to its configuration – it is very important to pay attention to the connection speed and the size of RAM. If the connection speed is below 2 Mbps, the operation speed can be rather low.
  • Balance replenishment via Bitcoin occurs within 30-40 minutes after the first confirmation in BlockChain network.
  • Balance replenishment via WebMoney only occurs when sending money with a unique commentary and without a protection code!
  • A tag on the availability of direct IP address indicates that the RDP server is directly connected to the Internet without any routers, and the address of its network adapter corresponds to its IP address.
  • If the desktop fails to load when connecting to RDP server, try pressing the key combination of CTRL ALT END, then go to the ‘Applications’ tab, click on "New Task", enter (without quotes) "explorer.exe" and click on "Ok". Desktop may fail to boot on the servers without administrator rights, so start the browser in the same way.
  • To work with the purchased SOCKS5, we recommend using the time-tested software:
    • Proxifier (Windows, Mac)
    • FreeCap
    • Proxychains (linux)
    • Permeo
    • ProxyDroid (android)
  • Not all SOCKS support ‘Remote DNS’ mode, so be sure to pay attention to this before buying. When working with such SOCKS, set the ‘Name Resolution’ parameter in ‘Local’ mode in the Proxifier settings.
Additional information

Additional Information


What is ProxyScore?

Scammers and hackers often use anonymous proxy servers in order to hide their real geographical location. According to the estimates by MinFraud service of MaxMind, about 41% of fraudulent transactions, which pass through their service, come from open proxies. The estimate of ProxyScore 1 or 2 indicates an average risk of fraud, while the estimate of ProxyScore 3 or higher – a high risk.

What is RiskScore?

The estimation by Risk Score determines the likelihood of fraud during the transaction. The estimate is given as a percentage, ranging from 0.01% to 100%. The higher the indicator is, the more thoroughly every online operation with money will be checked.

What is direct IP address?

Direct IP address means that a remote server is directly connected to the Internet with no routers, and the network adapter address is the same as the address of RDP server. Any software for ‘back-connect’ can be installed on such servers – for example, you can make your own VPN/Proxy/SOCKS from a RDP server.

  1. How to connect to RDP?

Click on "Start" -> "Run" and then type ‘mstsc.exe’ command. When a window for entering IP address appears, enter the IP address of the previously-purchased RDP server and press "Connect". After entering your Login and Password in the following fields, you will get the desktop of the remote computer.

To connect to RDP, we recommend to use the utility of MremoteNG.

You can also download a plug-in for Google Chrome by this link.

How to create an account on the dedicated server

You need to run the command line of "cmd" and enter the following commands:

net user Uas 12345 /add

net localgroup Administrators Uas /add

In this case, it will be created the user account Uas with the password 12345

Administrators’ group is called ‘Administrators’ only on the English-speaking dedicated servers, while on the other linguistic varieties of Windows – the group is called differently.

You can see the name of the Administrators’ group in ‘compmgmt.msc’




Press ‘Start’ --> The account icon appears, thus you go to ‘User Accounts’

Press the link "Manage another account"

Next – "Create a new account"

Here write the name of your new account, put a tick in the "Administrator" line and click on "Create Account"

Select the newly created account

Press "Create a password"

Enter the password twice and click on "Create Password"

That’s all, the new account has been created.
Now you can log in to the server with the new data.

The advantage of this method is that you can easily and quickly create an account regardless of the system language, all links and buttons can be found in their places.

Do not still forget to hide your account for a comfortable and safe operation.




  1. Go to the system registry – you can get there through ‘Start’ --> ‘Run’ --> regedit

    If you are already there, then go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon – here you shall create a section of ‘SpecialAccounts’ – then go to it, and there you shall also create a section but titled ‘UserList’.
    If the ‘UserList’ section already exists, you shall skip the first point.

    2. Then, in the ‘UserList’ section, you shall create a parameter of ‘DWORD(32bit)’ – its name is the name of the account we wish to hide: For example, we are to hide the account named ‘user’, then we shall create a parameter of ‘DWORD(32bit)’ named ‘user’.


Windows ХР/Vista/Win7 (by default) is a single-user system, thus, upon login by a different user, the previous user’s session (e.g. your) is closed with an appropriate warning to the incoming user.
To avoid this, you need to install the patch.

Message: "terminal exeeded the maximum connections"

In this case, in 99% of cases, there can help the so-called console connection or the connection through a zero session. To do this, in the menu of ‘Start-Run’, you shall type: mstsc /v: /admin and press ENTER, or: mstsc /v: /f -console (instead of zeros you shall enter the IP of the RDP server)

When connecting, you do not see your desktop

Press the key combination ‘Ctrl Alt End’, this will bring the Task Manager, then go to the ‘File’ menu, New Task, and type ‘explorer.exe’, and then click OK.

Clipboard is not working on the dedicated server!

First option:
Go to the Task Manager, cancel the process of ‘rdpclip.exe’, and then run it once again through the ‘File -> New Task (Run)’.

Second option:
Log off and then log in to the RDP once again.

Can I remove the locker from the dedicated server?

In most cases, you can easily do this:

How to Install RDP Plugin for Google Chrome
  • Run Chrome Browser and paste link:
  • Click to the button “ADD TO CHROME”:

  • Click to the button “Add App”:

  • After Plugin installed you will see “Apps” tab, just click to the icon “CHROME RDP”:

  • Enter IP:PORT of remote server you bought;
  • Enter only login name without domain name and password and you will see desktop.