Host mapper

App Cloner 2.1 comes with a new networking option called Host mapper, which allows redirecting requests made with a specific host to a different host name or IP address and/or port number.

This can be useful for monitoring, intercepting, analyzing or modifying network traffic.

The option allows specifying one or more pairs of hosts in the form of AB, where requests to host A are redirected to host B. For A and B you may use host names or IP addresses. You may also use wildcards, for example, while entering www​.​ would match this exact host name, writing * would match any sub-domain.

If no port number is specified for A, it will match any port number, otherwise you may restrict the mapping to a host with a specific port number, e.g. www​.​

If no port number is specified for B, it will keep and use the request’s original port number, otherwise you may override and change the port number, e.g. www​.​ → You may need to create two separate mapping rules to separate SSL from non-SSL traffic when using custom port numbers.

When forwarding SSL traffic to your own interceptor, you may need to enable the networking option Trust all certificates, as otherwise the SSL negotiation will likely fail.

By default a notification is shown for every request to a new host, whether mapped or not. By checking Silent you can disable these notifications.

The Host mapper option works at socket level, not at HTTP level. The HTTP Host header is not changed to the new host, so if the target server relies on this header for handling the HTTP request, the request may fail.

The Host mapper option is not compatible with the Hosts blocker option, meaning the two options cannot be enabled the same time. However, using the Host mapper option you may also ‘block’ requests by redirecting them to an invalid host, e.g. localhost or

Like with the Hosts blocker option, the Host mapper option does not work with native network connections as used by most web browsers, web views and audio/video streaming apps.

The Host mapper option is available for users with the medium donation.

Hosts blocker

The Hosts blocker networking option is a very powerful privacy tool to monitor and block individual hosts or entire domains a clone accesses.

In case you accidentally blocked a host, you may configure blocked hosts using Manage blocked hosts from the pop-up menu under the Cloned apps tab.

This option doesn’t work with native network connections as used by most web browsers, web views and audio/video streaming apps.

SOCKS proxy

The SOCKS proxy option allows routing the app’s network traffic via a SOCKS5 compatible proxy server. This can be used to bypass firewalls, prevent traffic throttling or to anonymize network traffic.

Using a SOCKS proxy also helps to prevent an app from finding your approximate location using your IP address. Your IP address will be hidden. Unlike HTTP proxies, which often include the original IP address inside the HTTP header, SOCKS proxies operate at a lower layer and do not send your IP address to the target server, nor will the target server know that a request has been proxied.

You can find many free (open) SOCKS proxies on the internet but these are often very slow and unreliable. You can use the Test button to test the proxy connection before cloning the app. It’s much better to use a private, password-protected proxy server. Do not use HTTP or SOCK4 proxies.

If you want to change the proxy server without recloning the app, you should considering using the Runtime modding options add-on.