Proxy Know

PROXY KNOW ADVANCED
Welcome to PROXY KNOW ADVANCED.
Version 2.9.1 PV-22.0-13.6
In Proxy Know eBook I hope to lead you through the way of creating and managing your
own proxies, I simplified and broke down the process as much as I possibly could, I can
assure you it will not be difficult, you need a little bit of patience, and everything will work
out perfectly for you.
Over the course of years, I have built and managed tens of thousands of proxies of all kinds,
from residential to 4G mobile to regular commercial proxies AKA “Data center”, at the
beginning I found minimum guides or tutorials, and when they existed, they were often
outdated or straight out wrong. I had to deal with tons of issues, even though I have decent
knowledge in network engineering, many of the issues I faced were very technical and/or
required previous experience in the networking industry, I often found myself lost looking
for solutions, and I made many, many expensive mistakes that cost me a lot, from dealing
with bad providers to making terrible technical errors.
To go through the eBook will likely take you a few hours, it is preferred if you read it on
multiple sittings over the course of a few days while you're following along with your VPS,
especial when we get to Section 4 so you understand everything properly without
overwhelming yourself.
By the end of reading and applying all the information in this eBook you should be able to
easily create and manage proxies, knowing with confidence that you are applying the best
practices and getting the best prices.
You are not expected to have any previous knowledge in internet networking or
programming what so ever, if you can turn on and off a computer you can easily follow
through with this eBook.
2019 OBrib ©
PROXY KNOW Professional is 2 weeks or less away.

There will be a huge discount on the first day of
launch, so keep an eye on your email.
Better Know 2019 P a g e 0 | 134

PROXY KNOW ADVANCED
TABLE OF CONTENT
Section 1: What is a Proxy? ............................. 3
1. Uses of proxies: .................................................................................................................................... 3
2. Differences Between a proxy and a VPN: ............................................................................................ 3
3. Free VPNs & Proxies, their uses ........................................................................................................... 4
4. Types of Proxies: ................................................................................................................................... 4
5. IPV4 vs IPV6 .......................................................................................................................................... 5
Section 2: Technical Information ..................... 6

1. Understanding IP subnets, ASN, & ISPs, and how IPs are allocated ................................................... 6
2. IPV4 Subnetting .................................................................................................................................... 7
3. IPV6 Subnetting .................................................................................................................................... 9
4. Understanding ip geolocation ............................................................................................................ 14
5. Understanding the terms “Elite”, “Private”, “Residential”, etc. ....................................................... 14
6. Technical explanation of how a proxy server works ......................................................................... 19
Section 3: What is an IP Provider? ................ 21

1. Types of servers .................................................................................................................................. 21
2. Virtualization & Types of VPS’s .......................................................................................................... 21
3. Minimum requirements ..................................................................................................................... 23
4. What to expect to pay & fair pricing.................................................................................................. 24
5. What should you pay per extra IP...................................................................................................... 24
6. Must know before buying anything ................................................................................................... 25
7. How to know if a providers IPs are already spammed? .................................................................... 26
8. Justifications for extra IPs .................................................................................................................. 27
9. Regular List of IP Providers ................................................................................................................ 28
10. Bulk IPV4 Providers List ...................................................................................................................... 29
11. Bulk IPV6 Providers List ...................................................................................................................... 31
Section 4: Making Regular Proxies ............... 33

1. Walkthrough of your first VPS purchase ........................................................................................... 33
2. Setting up SSH..................................................................................................................................... 35
1. Creating your proxy ............................................................................................................................ 37
2. Adding IPs after setup ........................................................................................................................ 40
3. Creating IPV6 proxies ......................................................................................................................... 41

PROXY KNOW ADVANCED
4. Setting up a /48 IPV6 subnets ............................................................................................................ 44

5. Linux Errors you might get and how to deal with them .................................................................... 49
6. Making a proxy on Windows ............................................................................................................. 62
7. Making a proxy on Android................................................................................................................ 67
8. Making a proxy on Raspberry Pi ........................................................................................................ 71
9. Configuring home router .................................................................................................................... 73
10. Making 40 FREE proxies ..................................................................................................................... 76
11. Accessing logs ..................................................................................................................................... 87
Section 5: Making 4G Proxies ........................ 88

1. Concepts to understand ..................................................................................................................... 88
2. Making 4G proxies from Raspberry Pi 3B+ ........................................................................................ 90
Section 6: Advanced setting of proxy ......... 112

1. Using a different PORT ..................................................................................................................... 112
2. Creating SOCKS proxies .................................................................................................................... 114
3. Limiting proxies to specific sites and blocking sites ........................................................................ 116
4. Having different options for different proxies on the same VPS .................................................... 119
Section 7: Extra Read ................................... 124

1. How an IP becomes a spammed IP. ................................................................................................. 125
2. Understanding IPV6 in the eyes of social networks & IP intelligence. ........................................... 126
3. Recommended best Practices for maintaining IP quality. .............................................................. 127
4. Bad practices of proxy sellers and how to detect them .................................................................. 129
5. Further Read ..................................................................................................................................... 131
6. Disclaimer ......................................................................................................................................... 131

PROXY KNOW ADVANCED
SECTION 1: WHAT IS A PROXY?
A proxy, or the more accurate term a proxy server, is a computer server that is created to
move internet packets from and to a user, usually for obfuscating uses. A proxy server is
based around its IP address. When connecting to a proxy your device sends regular request
like it would if the proxy didn't exist, but it would forward all of its requests through that
proxy and the proxy will take the requests, and reroute them through its own IP address,
and if obfuscated (anonymous) it will hide your IP address, and replace it with its own
address instead, however the obfuscation isn't perfect and there are ways to detect your
real IP address, discussed further in the extra read section.
1. USES OF PROXIES:
Proxies are most often used for hiding a user's real IP address, whether for privacy or to
manage multiple accounts on a social network. There are also other uses for security and big
companies, such as having IP-bound login portals and caching data that needs to be sent to
more than one device on the same network, however we won't be getting into these uses as
they are irrelevant to internet marketing.
2. DIFFERENCES BETWEEN A PROXY AND A VPN:
To discuss the difference between a proxy and a VPN we must first differ between a VPN
and a VPN provider, as the two are almost always mixed up. A VPN provider is, in the
simplest way, somebody who runs a network of multiple VPN Servers (usually hundreds to
thousands) and allows users access to their entire network, meaning they can connect to
any of their VPN servers whenever they wish to. On the other hand, a VPN or a VPN Server
is a server that establishes secure, encrypted connection tunnel, forwarding packets from
and to the user, kind of like a proxy but a little different.
Now for the difference between a VPN and a proxy, the main thing is that for a VPN no one
can see what websites you are browsing or what is your activity on the internet, not even
your ISP, but with a Proxy anyone monitoring your connection can see your internet traffic
as in what websites you're visiting and what exactly is it you're doing on these websites,
however when using a TLS/SSL encryption (we'll discuss TLS/SSL further later on) an ISP or
someone monitoring your connection can't tell what exactly you're doing on a website, they
can just tell you're visiting that site, however somebody with experience who can perform a
Man In The Middle Attack, can easily decrypt your connection to the proxy, so if you're
privacy conscious it is always suggested you go with a VPN.

PROXY KNOW ADVANCED
Both VPNs and Proxies can conceal your real identity from the website you're visiting, if
configured to do so.
3. FREE VPNS & PROXIES, THEIR USES
First, a free proxy is almost always just an incorrectly configured server, meaning somebody
was trying to set up a network, or make a proxy server, however they did it incorrectly and
ended up making their server an open proxy (AKA free proxy). There are always people
always scraping the internet looking for these misconfigured server, doing what is called
Port Scanning, once you set up your proxy you will notice people scanning your ports (If you
set up logs, which you always should.), and it's completely normal, if you follow the steps
and recommendations of this eBook you will never have to worry about that. Usually, these
proxies are short-lived, minutes to hours, as they get fixed quickly, some last longer but are
usually banned by major sites, and are useless to most people. The majority of uses of these
proxies are illegitimate, like doing DDOS attacks.
Free VPNs, usually work by mining your data, sharing your device resources, or showing you
extra ads, they can be useful if you don’t want to invest extra in a paid VPN, however
they’re never truly secure.
4. TYPES OF PROXIES:
Proxies generally have 2 types, SOCKS and HTTP, further broken down into SOCKS4 and
SOCKS5, being two versions of the same technology and HTTP being HTTP and HTTPS where
the "S" means that connection is encrypted with TLS/SSL encryption, all of these are very
similar except they handle requests a little differently, it's always better to stick with HTTP
proxies for internet marketers since SOCKS don't offer any particular advantage for us, and
are less common/supported. If you plan to use SOCKS for whatever reason just make sure
the software you're using can handle SOCKS proxies.

PROXY KNOW ADVANCED
5. IPV4 VS IPV6
IPV4 and IPV6 are different types of Internet Protocol Addresses standing for Internet
Protocol Version 4, and Internet Protocol Version 6. When the internet was first created it
was connected using Internet Protocols enabling computers/server to communicate with
each other, eventually IPV4 was adopted as the standard, soon the experts realized that the
32-bit based IPV4 format which can only support 4 billion addresses from 0.0.0.0 to
255.255.255.255 will not be enough for long, which is where IPV6 comes into play. IPV6 is
128-Bit based, meaning there can theoretically be
340,282,366,920,938,000,000,000,000,000,000,000,000 unique IP addresses. The move to
IPV6 has been very slow as IPV6 and IPV4 are generally not backwards compatible, meaning
if a server or a software was made for IPV4, it cannot handle IPV6, so new technologies have
been emerging to get as much use of IPV4 as possible, naturally this has also caused the
prices of IPV4 addresses to increase, more will be discussed about this in the following
section.
The insanely high number of IPV6 Addresses that can be used is great news to the average
internet user, however it creates new challenges to the Internet Marketer, which will be
discussed in detail in the extra read section.
Keep in mind that you cannot use every IPV6 to make proxies, and only a very, very small
fraction such 0.00001% of the addresses can be used, for reasons we will discuss later
It is important to note that not many websites support IPV6, for example IPV6 is supported
by Facebook and Instagram however it is not supported by Twitter or Reddit.

PROXY KNOW ADVANCED
SECTION 2: TECHNICAL INFORMATION
In this section we will be getting into technical details about proxies and Internet Protocol
Addresses (IPs), how they are created, allocated, and a technical breakdown for the process.
You don’t need to know any of the information we’ll be sharing here to have an up and
running proxy server, however, I highly recommend you read this section to have a better
understanding of what is it exactly you’re doing.
I tried as best as I could to break things down in the easiest to understand, so even if you’re
not a technical person, you should be able to understand all the information shared here
with ease.
1. UNDERSTANDING IP SUBNETS, ASN, & ISPS, AND HOW

IPS ARE ALLOCATED
IANA or Internet Assigned Number Authority is the organization responsible for assigning IP
addresses to local registrars and in turn these local registrars assign the IPs to ISPs (Internet
Service Providers) such as Verizon, or Comcast. There are 5 local registrars out there, these
are:
AFRINIC which serves Africa
ARIN which serves Antarctica, Canada, parts of the Caribbean, and the United States
APNIC which serves East Asia, Oceania, South Asia, and Southeast Asia
LACNIC which serves most of the Caribbean and all of Latin America
RIPE NCC which serves Europe, Central Asia, Russia, and West Asia
We’ll talk more about these later when they become important to us, but for now more on
ISPs.
Technically speaking, there are different types of ISPs such as hosting ISP or
wireless/broadband ISP however these are very loosely defined and in reality, are not really
used much, however keep this in mind as we’ll be getting into further detail in coming parts.
Each ISP has what is called an ASN, or Autonomous System Number that is used to correlate
a specific IP address or block/subnet with a specific ISP.

PROXY KNOW ADVANCED
An ISP can have multiple ASNs, but an ASN can only be assigned to 1 ISP, technically
speaking. In reality an ASN can only be associated with one company; however ISPs,
especially bigger ones are usually made of multiple companies, so they can have multiple
ASNs.
When an ISP is assigning IPs to their customers, they usually do so by assigning it to what’s
called organizations, in this sense an organization is a simply costumer of the ISP who is
leasing/renting the IPs from the ISP. If you own a website or a VPS you can do a whois
lookup for your assigned IP address and you’ll most likely see your hosting company listed as
the organization. (There’s more to this, however we’ll discuss it later to maintain thought
chain)
IANA is owned by ICANN, who is, in a way, the police of the internet.
To sum it up, this is the route an IP address takes from ICANN to your router or website:
IANA > Local Registrar > ISP > Organization > End Costumer (you)
2. IPV4 SUBNETTING
IPV4 addresses start from 0.0.0.0 to 255.255.255.255 the IP addresses are assigned in the
form of blocks, known as subnets. The number of IP addresses in a subnet can vary
depending on the subnet mask, which you can think of as different types of subnets.
For example, the IPV4 addresses starting from 192.168.1.0 to 192.168.1.0.255 together
would be what is called a C-class subnet mask or a /24, or 255.255.255.0 subnet mask.
The IPV4 addresses from 192.168.0.12 to 192.168.0.16 together would be considered the
subnet 192.168.0.11/30 which contains 4 IP addresses.
subnet 192.0.0.0/8 which is an A-class subnet and contains 16,777,216 IP addresses.
subnet 192.168.0.11/28 which contains 16 IP addresses, and so on.
Some IPs are reserved for internal networks and other functions so they can’t be used by
anyone, these mainly being 0.0.0.0/8, 10.0.0.0/8, and 192.168.0.0/16.

PROXY KNOW ADVANCED
To not overcomplicate things, the main points you need to understand are the following:
Each IP address has its own ISP, ASN, and subnet
A /24 IPV4 subnet, also known as C-class subnet has 256 IP addresses, and this also the most
common type of IP block.
To give you a general understanding of subnets, below is a sheet that shows subnets and
correlating number of IPs:
Subnet Number of IP addresses

/32 1
/31 2
/30 4
/29 8
/28 16
/27 32
/26 64
/25 128
/24 or C-Class 256
/23 512
/22 1024
/21 2048
/20 4096
/19 8192
/18 16384
/17 32768
/16 or B-Class 65536
/15 131,070
/14 262,142
/13 524,286
/12 1,048,574
/11 2,097,150
/10 4,194,302
/9 8,388,606
/8 or A-Class 16,777,214
Note when you get an IP subnet, the actual number of the usable IP address will be the
original number of IPs minus 2 or 3, for reasons we don’t need to get into at the moment.

PROXY KNOW ADVANCED
All of the data about every IP, subnet, ASN, and ISP is stored in a database called Whois, just
like websites. If you ever need any information about any of the mentioned before (IPs,
subnets, ASNs, etc.) you can use the link https://whois.arin.net/ and it’ll give the most
accurate up to date information. Whois data can change, and in the coming parts, we’ll talk
about how such information can be useful for us.
When an IP quality monitoring company (also known as IP intelligence companies) or any

social network (Facebook Instagram, etc.) that wants to decide the quality of a certain IP,
they check for spam and traffic history along with other metrics from the IP, the IP Subnet,
the ASN and the ISP, and if there’s any bad history or suspicious activity with any of the
mentioned before, it’ll obviously make it more likely that spam could come from that
particular IP, with varying degrees of course. We’ll get into more details about how this
process works in the coming sections.
3. IPV6 SUBNETTING
In this part we’ll be discussing the subnetting of IPV6 addresses, since there can be a
gigantic amount of IPV6 addresses, they are sub-netted under the same concept, just a little
differently.
First, to clear things up, we’ll look at a simplified sheet of IPV6 subnets:
Subnet Number of IP Addresses

/112 65,536
/65 9,223,372,036,854,770,000
/64 18,446,744,073,709,500,000
/63 36,893,488,147,419,100,000
/56 4,722,366,482,869,645,213,696
/49 604,462,909,807,314,000,000,000
/48 1,208,925,819,614,620,000,000,000
/47 2,417,851,639,229,250,000,000,000
/33 39,614,081,257,132,100,000,000,000,000
/32 79,228,162,514,264,300,000,000,000,000
IPV6 addresses start from:
0000:0000:0000:0000:0000:0000:0000:0000 to ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff

PROXY KNOW ADVANCED
and it’s eight segments, every segment is 4 spaces. A space can contain letters or number,
the letters are from A to F, it starts from 0 and ends at F (“0123456789abcdef” can be used).
IPV6 addresses are case insensitive, which means the letters can be capital or small and it
won’t make any difference.
As you can see, IPV6 addresses can look quite confusing so a system for shortening or
compressing the addresses was created, and it’s as follows:
Any segment made from four consequtive zeros can be writte as an empty colon “:” and this
can be done for as many consequtive segments there is, as long as it’s only done once, for
example:
ffff:ffff:ffff:ffff:0000:ffff:ffff:ffff becomes: ffff:ffff:ffff:ffff::ffff:ffff:ffff
ffff:ffff:ffff:0000:0000:ffff:ffff:ffff becomes ffff:ffff:ffff::ffff:ffff:ffff:ffff
ffff:ffff:ffff:ffff:ffff:0000:0000:0000 becomes ffff:ffff:ffff:ffff:ffff::
ffff:ffff:0000:0000:0000:0000:0000:0000 becomes ffff:ffff::
0000:0000:0000:0000:ffff:ffff:ffff:0000 beomces ::ffff:ffff:ffff:0000 (Remember it can only be

done once.)
Another thing we can do to help make the IPV6 address look better is we can remove any
zeros to the left of a segment and devices will understand to fill it with zeros, for example:
0000:0000:0000:0000:ffff:ffff:ffff:0000 becomes: ::ffff:ffff:ffff:0
00ff:000f:ffff:00ff:0fff:0000:0000:0000 becomes: ff:f:ffff:ff:fff::
2001:00cd:2354:000e:0000:0000:0000:0000 becomes: 2001:cd:2354:e::
And so on.
If for any reason you want to compress or decompress an IPV6 address you can use tools
such as this: https://tools.tracemyip.org/IPv6-expand-uncompress/
For IPV6 subnets, the concept is exactly the same as IPV4 however on a different scale, let’s
explain it using examples.
The subnet ffff:ffff::/32 or ffff:ffff:0000:0000:0000:0000:0000:0000/32 starts from:

PROXY KNOW ADVANCED
ffff:ffff:0:0:0:0:0:0 (or ffff:ffff:: we keep the zeros here just to help explain the process)
To the address: ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
The subnet ffff:ffff:12ce::/48
Starts from the address: ffff:ffff:12ce:0:0:0:0:0
To the address: ffff:ffff:12ce:ffff:ffff:ffff:ffff:ffff
The subnet ffff:ffff:ffff:0dfa::/64
Starts from the address: ffff:ffff:ffff:0dfa:0:0:0:0
To the address: ffff:ffff:ffff:0dfa:ffff:ffff:ffff:ffff
The subnet ffff:ffff::/56
Starts from the address: ffff:ffff:ffff:0:0:0:0:0
To the address: ffff:ffff:0:0:ff:ffff:ffff:ffff
And lastly the subnet ffff:ffff:ffff:ffff:ffff:ffff:ffff::/112
Starts from: ffff:ffff:ffff:ffff:ffff:ffff:ffff:0
To the address: ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
For clarification, we use the segment “ffff” here only as an example, as in reality it can be
anything from 0000 to ffff such 65ed or f6d1 and so on.
This might seem a little bit confusing at the moment, however once you understand the
concept, dealing with IPV6 subnets will become a breeze.
If you ever find yourself strugling to get a general scope of a subnet, you can always use a
IPV6 rang calculation tool such as
https://www.ultratools.com/tools/ipv6CIDRToRangeResult as these always come in handy.

PROXY KNOW ADVANCED
Whenever you receive a subnet to create proxies form, it’s always better to arrange your
selected IPs from different subnets inside the main subnet you received, for example:
If you received the subnet fd:c12a:cd9f::/48 from an IP provider and you want to make 5
proxies from it, only use IPs form different /64 subnets, which for example would be
something like this:
fd:c12a:cd9f:da11:7464:4d3:fcb3:86ed
fd:c12a:cd9f:cd34:f062:554e:dc37:93fe
fd:c12a:cd9f:f2b3:bdd:5572:a569:1d71
fd:c12a:cd9f:a223:e4b:13ec:942b:6356
fd:c12a:cd9f:2c3c:b1d:6fb8:aa6c:4080
All of which are a part of the main /48 subnet from fd:c12a:cd9f:0:0:0:0:0 to
fd:c12a:cd9f:ffff:ffff:ffff:ffff:ffff
Now as you can imagine, IPV6 can complicate things a lot, especially considering there are
no concrete rules to follow when a network engineer is a creating an IPV6 network, there
are IANA guidelines, however these are just that, guidelines, so that means everything we
share here is most common practice, you may deal with a provider that treats their IPV6
subnets entirely differently from what we’ll discuss today.
Per RIPE guidelines, a /64 IPV6 subnet is considered residential distribution, that means that
each home will be getting 1 IPV6 address from each /64 subnet the ISP owns, however, in
reality, things are a little different, many ISPs are allocating each home 1 IPV6 address from
each /112 they own, claiming it’s for security reason.
For websites or businesses, the guidelines recommend giving a /48 or /56 subnet, however,
same as with residential distribution, they usually allocate smaller subnets, sighting the
same reason.
For ISPs, local registrars generally give a /32 IPV6 subnet, and they can get more depending
on the registrar. To keep in perspective, a /32 IPV6 subnet contains around 64,000 /48 IPV6
subnets. For comparison an ISP using IPV4 would receive a /16 IPV4 subnet which contains
64,000 IPV4 addresses, keep this information in mind as it’ll become more useful to us in
coming parts.
To simplify things, you can kind of think of a /64 IPV6 subnet as a one IPV4 address, this is
technically wrong, but it can help your understanding of IPV6 subnets, we’ll be discussing
this in more detail in the extra read section, as it’s much, much more complicated.

PROXY KNOW ADVANCED
If you’re getting a VPS with a provider that offers IPV6, always ask for a /64. Some providers
will offer a /112, if they do that I would, unless necessary, as this not standard practice.
Some providers will offer a single IPV6 address, just make sure you ask how they’ll be
assigning you the address, and what subnets do other users share with you. By the nature of
the technology the minimum you can be assigned is a /112 subnet.

PROXY KNOW ADVANCED
4. UNDERSTANDING IP GEOLOCATION
Every IP address is connected to a Geographical Location mainly so advertisers could know

your location to “serve more relevant ads” when they don’t have access to your GPS, there
are a few companies whose job is to keep track of these locations in their databases, as they
sometimes change, whenever a hosting company switches to a different datacenter, they
usually take their IP addresses with them, or when an ISP offers their service in a new
location.
The most popular of these services are: MaxMind and DigitalElement, larger companies like
Google and Facebook have their own databases which they maintain themselves. Most
other GeoIP companies and websites are resellers of those we mentioned above.
There’s no central authority when it comes to geo IP, so very often you’ll find these
databases not being very accurate or conflicting. If a hosting provider gives you a VPS and
they say it’s in Germany, however, you when you do a geo IP lookup on MaxMind, you find
it located in any other place, you can ask them to have it updated, and most should do it
without a problem. This information becomes useful to us in the coming parts.
5. UNDERSTANDING THE TERMS “ELITE”, “PRIVATE”,

“RESIDENTIAL”, ETC.
The terms Elite, Private, Residential, etc. are terms often used by proxy providers, and many
times in misleading ways. In this part, we’ll be discussing the definition and real-life use of
these terms.
A private proxy is a proxy that only you have access to and is not shared with anybody else,
unlike a shared proxy which, as you can guess, is shared between two or more people. You
should always stick to private proxies when you can afford it, unless if you have a not so
common use for the proxy, where you can be certain whomever you’re sharing it with won’t
be using it for the same purpose.
Some use the term private to indicate that the proxy is not public; however this is not the
most common definition.

PROXY KNOW ADVANCED
The term “elite”, is kind of meaningless. Some proxy providers use it to describe their proxy
as being private, as in it hides your IP, and some other use it as marketing gibberish. A proxy
being private, especially a paid one, is standard nowadays and any provider that markets it
as other than that, does not deserve your money.
If you use public proxies or public proxy collection software, you’ll see the term elite, which
in this context means that the proxy hides your real IP, and doesn’t let websites know it’s a
proxy when connecting through it. A private or anonymous proxy here would mean that the
proxy hides your real IP, but it lets websites know that it’s a proxy, lastly a public or open
proxy shows your real IP and lets websites know that you’re using it as a proxy.
Rotating proxy means that the IP address will change every specified interval, or after X
number of requests. It could be a proxy that changes IP every 120 seconds, or one that
changes after every HTTP request you send. Rotating proxies can be very useful in
preventing an IP address or subnet from getting flagged as suspicious, of course, this would
depend on if the IPs are in the same subnet or not. It’s mostly useful for web scraping and
account creation. Most homes use some form of rotating IP addresses, as once you restart
your home router, you’ll get a new IP, also called dynamic IP.
Rotating proxies use what is called “backconnect”, meaning you get a static IP to connect to
and in the back end, it’ll be a different IP that changes per your setting so that you don’t
have to changes the proxy details every time the IP address changes or rotates.
Before you get such a proxy, make sure you know the size of the IP pool, how many subnets
does the pool contain and what’s the proxy changing interval or trigger.
The opposite of rotating would be static IP, this IP is allocated to a specific router or
machine and will not change, unless a network admin changes it. Static IPs are mostly used
by businesses for technical and security purposes.
Residential proxies, the supposed holy grail of proxies, and where it’s the easiest to rip
users off, different people define “Residential” in different ways, feel free to pick any as
there’s no agreed upon definition out there.
The way I see it, a residential IP address is any IP address that exists in a subnet allocated for
residential-only use and is actively used by normal people, and this is likely how IP
intelligence companies and social networks define it as well, I can’t say for sure since there’s
no public information about it, but we’ll discuss further below why this is most likely the
case.

PROXY KNOW ADVANCED
On the other hand, anybody can go to an ISP that provides internet to residential areas (It’s
not very accurate to call such an ISP a “residential ISP”, as many who serve residential areas are also willing to allocate IP blocks to
commercial companies) and
say “Hey, I’m a commercial company, can you give me some static IP
addresses?” and many, such as Verizon, Cognate, Comcast, and most ISPs, will say “Sure,
just comply with IANA guidelines” which you don’t really have to comply, and they don’t
really care, unless they get a complaint about your activity. Now, most people who make
proxies from these IPs call them residential, but are they really?
First of all, 9/10 times these IP addresses will have a different ASN from their residential
counterpart since ISPs usually have different companies for their commercial activities,
separated from their residential ones.
Second of all, it’ll be very obvious for IP intelligence companies and companies like Google
or Facebook to tell that the IP does not come from a residential connection, as the subnet
won’t be generating residential-like traffic.
For example, if area code 10001 in NYC has a /22 IPV4 subnet allocated to it by Verizon,
Google would expect to have at least 500 devices connected from this subnet with normal
device activity, same thing for Facebook and similar companies and they would expect to
see regular traffic from this subnet, as they would from any other residential area, now
these companies have been collecting this data for years and can tell if a connection is
coming from a residential area or not in split second.
The last point is, most ISPs sell this information to data giants, and tell them exactly who has
certain IP subnets and likely much more, and that throws the idea that a business allocated
or a commercially allocated subnet could ever be considered “Residential” not matter the
ISP.
Many people will disagree, perhaps from lack of understanding, or they are those who profit
from such “not very honest” practices.
Of course, these IPs can be useful when you want to use them say to create accounts on a
smaller website, however, with modern technology such as Google RECAPTCHA V3, and
MaxMind MinFraud, these IPs are rendered as useful as any other “Commercially Allocated
Address”, also known as “Datacenter IPs”.
Now you’re probably wondering, how can you get an actual residential IP? Other than your
home IP, remember when we talked about free VPNs at the beginning of the eBook? This
where it comes into play. When a user downloads a free VPN, most don’t understand that
they are the product. The VPN owners can use the residential connection of the user as a
residential proxy, and they almost always do, as this is how they make their profit.
These are always sold as rotating residential proxies as they only have access to the user’s
network as long as they are connected to their VPN, once a user turns off the VPN, you get a
new IP from a different user who happened to be connected at that moment.

PROXY KNOW ADVANCED
Sometimes you can specify a trigger for changing IP, like in regular rotating proxies; however
this depends on the provider. Most of these providers sell per GB of bandwidth used not for
the time you use the connection.
Usually, the free VPN and the residential proxy will appear separate companies, so to tell
what type of proxies they have “Real Residential” or “Fake Residential” you’ll have to ask. If
they offer any type of “Static Residential Proxy”, “residential VPS”, advertise high port speed
like “100 Mbps” or if they advertise working with specific ISPs, 95% chance they’re lying
about their network and they’re using commercially allocated IPs. Some providers rotate
their commercially allocated IPs to make them seem residential so pay attention to that.
Now if you’re thinking of buying a residential proxy from one of those free VPN companies,
make sure you email them and ask “Do you sell my data? Or do you share my real IP with
anyone or any company?” because a lot of these companies, especially larger ones, have
what they call “partnerships” with Google and other companies to share your real IP when
you connect to their website, and by partnership they mean they get paid to do so, so be
very careful especially considering these are never cheap.
Another way some people get access to residential connections is by using a form of
malware called proxy trojan, which, once infected, turns a user’s machine into a proxy
server without their permission, often to use in a botnet. Now as you can imagine these are
very illegal, unethical and immoral, and you should stay as far away as possible from such
activity.
4G or LTE, also sometimes called mobile proxies, are proxies created from connecting sim
cards using what’s called a SIM bank or a 4G router, these can also be considered residential
if the provider is honest. I have seen providers create regular rotating proxies and call then
4G, the only way to tell is to ask the provider, or check the ISP, these most often have East
European, and Eurasian (Ukraine, Russia, Kazakhstan, etc.) ISPs as they are not very strict
with SIM cards.
Sometimes free VPN companies offer 4G/mobile proxies as separate from WIFI, since free
VPNs are most commonly used on mobile devices.
There’s no real practical way to tell if a provider is honest, as there’s no way differentiate
between a connection coming from a 4G connection or a DSL/cable/WiFi one.
Virgin proxies, is it possible? Maybe. Can you find one? Maybe.

PROXY KNOW ADVANCED
Under strict definition that IPV4 virgin proxies are proxies made from IP addresses never
used before, virgin proxies do not exist anymore. The last /8 IPV4 subnet was allocated in
2012, and with it died the strict definition of a virgin IPV4; however, the general definition of
a virgin proxy nowadays would rely on what is it you intend to use it for.
An IP could be blocked from twitter.com could have never sent a request to Instagram.com,
making it, by definition, an Instagram virgin proxy, obviously this is just an example, and it’s
highly unlikely you see something like this.
So how can you tell if a proxy is virgin or not? The short answer is, you can’t. The long
answer is, unless you have the complete traffic and Whois logs history since the day the
subnet was allocated by IANA, you can’t.
Some providers out there, when they claim a proxy to be virgin, do a set of tests to
determine if an IP has spam history with X website/service, and if they don’t find evidence
of spam, they call it virgin which is “not so honest”, since there’s no way for them to tell
with good accuracy. Other providers use the term as marketing gibberish, unfortunately
there’s no way to tell who’s “kind of lying” and who’s “really lying” except to test out for
yourself. Even if an IP tested and showed no spam history and provider chose to make it a
proxy, it’ll likely be spammed in a few days to weeks, so, in my opinion, paying extra for a
supposed “Virgin” is a lose-lose situation.
There are providers who offer entire /24 subnet as proxies, and they claim to have looked
into the history of said subnet, which, if done correctly, can be worth it. If you’re interested
in such a service, you should look into the following:
Ask how many subnets do they own from the same B-Class, for example, subnet
192.168.1.0/24 is from the same B-Class subnet as 192.168.2.0/24, if they own two or more,
it’ll make it more likely that these subnets have seen some spam.
Ask for a test IP from the subnet and find the ASN and the ISP, and check all of them
through an IP blacklist check, find other subnets in the ASN, and ISP and check those as well.
Also check the registration date, the younger a subnet is, the less likely it is that it was
spammed, this is obviously not a concrete rule, but it should be a good indicator since in the
last few years of IPV4 allocation and with IPV4 scarcity, IANA was very strict with which
ISP/registrar it allocates to.
Look into Whois history, this will be a paid search but since you’re already paying a decent
amount of money this will be worth it, once you get the data, check other related ASNs and
ISPs and run their IPs through IP blacklist checks like you did before.
Ask to get a test proxy from the subnet and test out for yourself, obviously, if you’re using it
for a social network, you’ll be able to tell by whether you get banned, email and phone
verification, etc.

PROXY KNOW ADVANCED
This one time I bought a VPS from a very small provider in the UK who owned their
hardware and IPs and were very strict about giving me extra IPs asking for justification and
ID documents, once accepted, I created a proxy and tested it from my phone, expecting to
be redirected to google.co.uk, I was surprised to be redirected to my country’s google
website, I thought this must have been an accident, but no, even when I used it on
Facebook it showed my local language, it was surprising since I live in a very small country
with a small population, so I think that was the closest thing I have ever been to an actual
virgin proxy, where nor Google or Facebook have ever seen this IP before, which is why I
suspect they used the “coarse location” data from my phone and assumed it to be the IPs
geo location. Still even with that, I’d say there’s a 50% that was just an accident.
At the end of the day, it’s all speculation and guessing, you can tell that a subnet was not
used for malicious spam on a certain website, however you can never tell if an HTTP request
was never sent to that website from this specific subnet or not.
Although a legit residential proxy will always perform better, there are legit uses of proxies,
VPNs and commercial IPs, and social networks are aware of this, which is why you don’t see
them blocking every VPN and proxy IP (that they can detect), other than “automation-
sensitive” websites such as Ticketmaster, or Netflix who block every commercial IP address,
disregarding whether it’s a proxy, VPN, or not.
Same rules apply to IPV6; however, it’s much easier to find cleaner IPV6 proxies than IPV4,
and age here will be a bigger factor. All social networks and IP intelligence companies are
aware of this, so they treat IPV6 differently in the first place, more on this later.
6. TECHNICAL EXPLANATION OF HOW A PROXY SERVER

WORKS
In this part, I’ll try my best to break down how a proxy works. You don’t need to know this
information, but it’ll be very beneficial for your understanding.
Before we begin, we need to understand a few things, starting with HTTP requests in a
simplified way. When you open up your browser and type a website address, it sends an
HTTP request asking to get the data (HTML, CSS, JS, Images, etc) from the website, each

PROXY KNOW ADVANCED
request you send has what’s called a header, this header contains information about you
such as your IP, your language, device type, your fonts, etc. It’s kind of like your ID.
When you first attempt to connect to a proxy server, you send a request asking to connect
through the proxy, the proxy then checks if you have authorization, if you don’t, it’ll reply
asking you to send username and password to have your connection authorized.
Once connection established your computer or device, depending on your setting, will begin
to send all of its requests through that proxy, and then the proxy then will forward these
requests to the correct destination, depending on the proxy setting, it can also edit the
header to hide your IP address, and add its own instead, so that websites can’t see your
address.
A public proxy generally doesn’t hide your IP or the fact that it’s a proxy, so in the header it
sends to websites you’re browsing it’ll also say it’s a proxy and it’ll mention your real IP, a
private proxy might mention it’s a proxy but hide your real IP, this all depends on the setting
of the proxy server.

PROXY KNOW ADVANCED
SECTION 3: WHAT IS AN IP PROVIDER?
An IP provider is usually a company that either owns IP addresses or rents them from a
bigger provider, most of the time these are hosting companies that need the IP addresses to
offer their services, for our purposes we're going to need hosting providers that offer VPS's
which we're going to turn intro Proxy Servers. Most of these companies simply rent space
from a data-center, which is where we get the term datacenter IP, we'll discuss these terms
and what they mean in detail later on.
Finding a reliable host (hosting company) who will let you make proxies with their IPs can be
a little tricky, in this section we will discuss where to find the best possible providers.
1. TYPES OF SERVERS
Often times the different types of servers are confused, therefore we will be discussing the
basics of these in this part.
The first we will discuss, is the dedicated server also known as physical server or bare metal
server, this is basically a physical computer that works to serve a network.
Secondly, is what is known as cloud severs or cloud hosting, you think this of these servers
as dynamic server which can scale up and down in usage without needing to do any
changes, and generally, with cloud servers you only pay for the computational power you
use.
Lastly, the most common, and the one you likely know best is a VPS or a Virtual Private
Server, this is a virtual server that is hosted on a dedicated or a cloud server, more on this in
the next part.
Some people use the term server to speak about mail servers or web servers and similar,
this is not wrong however we shy away from this terminology as it can cause confusion, as a
mail server is in the simplest sense a piece of software running on a server.
2. VIRTUALIZATION & TYPES OF VPS’S

PROXY KNOW ADVANCED
Virtualization is the process of making multiple Virtual Private Servers out of a larger
physical bare metal server. It can be done with multiple ways which vastly differ in how you
can expect the VPS to perform, and how much assurance you get that the provider will give
you what you were promised, most popular of these virtualization technologies being:
1. KVM, Kernel-based Virtual Machine, which will always be preferred over all others
since it generally can't be manipulated by the provider, meaning you get what you
were promised because with this technology the VPS's are not connected with each
other and have their own, generally independent kernel, meaning, unlike other
technologies it can't be oversold, and if say 9 out of 10 VPS's on the same physical
server had maxed CPUs, the tenth shouldn't be effected, theoretically speaking, it also
isn't OS-bound, meaning you can install almost any Operating System you would like,
unfortunately this technology is the most resource intensive which translates into KVM
VPS's always being more expensive.
a. Advantages:
i. Can't be oversold
ii. Resource independent
iii. Can install most OS's
iv. Very reliable
b. Disadvantages:
i. More resource Intensive to create
ii. More expensive
2. OpenVZ, which is an OS-level virtualization technology, meaning all VPS's share the
same kernel with different operating systems, that also means most resources are
shared like RAM and CPU, which leaves this technology open for abuse by the provider
in the form of over selling, or by other VPS owners, which is why when using an
OpenVZ VPS there always certain limitations such as can't max out CPU for more than
10 minutes and such, or else you get your account terminated with the host.
There are many hosting companies out there that are honest and reliable, don't
oversell, and have very strict, well enforced restrictions on abuse, however I
unfortunately found from my experience that these companies are a minority, since
most OpenVZ based hosting companies rely on the business model of selling dirt cheap
and hoping users don't max out their usage or straight out forget about the VPS, and
when dealing with such companies it's a gamble of whether your VPS will run properly
or not,
Another thing is, due to the nature of the technology it can only run Linux-based
operating systems.
The good thing about OpenVZ is that it doesn't use much resources so it can be
cheaper than KVM based VPS's, and it's very flexible, meaning it can be easily
upgraded with extra RAM or CPU without any downtime. When using an OpenVZ or

PROXY KNOW ADVANCED
OVZ VPS you must make sure it has a kernel version of 2.6.32 or newer, depending on
OS options the provider, more discussed later on.
a. Advantages:
i. Cheap
ii. Flexible, and easy to upgrade
iii. If dealing with a reputable host, can be reliable.
b. Disadvantages:
i. Generally unreliable
ii. Can be oversold
iii. Can only run Linux
iv. Must make sure it’s the right kernel
3. Xen, being the oldest and most established technology of the previously mentioned,
also the least common. You can think of it like KVM but older, and kind of becoming
outdated. Slowly most larger corporations who previously used Xen are migrating their
servers to KVM such Amazon's AWS, however for our purposes it makes no difference,
if you find a host that's only offering Xen, you will likely notice no difference form
KVM, all the advantages and disadvantages are generally identical to KVM.
Note: There also other virtualization technologies, however we won't be getting into these
as it is unlikely you will ever have to use them.
3. MINIMUM REQUIREMENTS
When renting a VPS there are minimum specs and requirements you should always stick to
in order for your VPS to function properly, these being:
The following is for running 1 - 5 IPs on the same VPS:

1. At least 1 CPU Virtual Core or more. The type of CPU matters, however what most
providers provide is good enough, as a proxy server is not CPU intensive.
2. No less than 100 MB of RAM Memory.
3. No less than 100 MB of SWAP memory.
4. No less than 500 MB of Storage Space, will be used for keeping logs, usually you will
get more than you need like 5 - 10 Gigabytes, which is industry standard.
5. 100 MB/s or faster connection, you can get away with slower however it can slow
things drastically, especially if using more than 1 IP per VPS.
6. Root Access, root access is an essential to be able to set up the proxy server.
7. 1 Dedicated IPV4 address, this is very important, make sure it is not a shared IP,
usually when it’s shared the provider will mention it in their advertising.
8. 250 Gigabytes of bandwidth. Industry average is around 1000 Gigabytes however you
can get away with less especially if you won't be doing anything that's bandwidth
intensive.

PROXY KNOW ADVANCED
9. Must support any of the following versions of Ubuntu: 12.04, 14.04, 16.04 and 18.04.
Any will work just fine, we use ubuntu as it's the most popular and easiest to work
with when it comes to proxy servers.
10. Linux kernel version 2.6.32 or higher, we'll discuss this further. (only applies for
OpenVZ)
Whether using KVM or OpenVZ VPS will not make a difference as this is the absolute
minimum you need, if possible, always try to get slightly higher spec, as you never know
when you’ll need it.
4. WHAT TO EXPECT TO PAY & FAIR PRICING
Fair pricing will depend on many aspects, including, Virtualization technology, Specs, does
the provider own their hardware, etc. So, taking these variables in consideration you can
expect to pay the following:
Spec Virtualization Monthly Yearly Note

Minimum OpenVZ $1 to $5 $10 to $25 If the host owns their
Spec Dollars/Month Dollars/Year hardware you can expect
them to be a little cheaper,
since there's no middle man
to be paid. Also, the newer
the hardware the more
expensive it is.
Minimum KVM $2 to $6 $12 to $30 Same as above.
Spec Dollars/Month Dollars/Year
A trend I noticed is that US-based providers are always cheaper than their counterparts in
Europe or Asia, possibly due to cheaper electricity, or less taxes.
5. WHAT SHOULD YOU PAY PER EXTRA IP
If a provider allows for extra IPs, which they will mention in their advertising, you can expect
to pay $0.5 to $5 Dollars per extra IP, varying depending on the host, and whether they own
the IPs or not.
Sometimes a provider will overprice IPs because they want advertise it as a service but they
don't want to attract "spammers", these providers you're probably better off staying away
from. Also, some providers are concerned about what is called IPV4 depletion, as with time

PROXY KNOW ADVANCED
passing there's less and less unused IPV4 addresses available, some providers inflate their
prices citing that issue as justification.
Another thing is there's providers who actually own their IPs, as in they're not renting them,
but they bought them and are registered in their company's name, these providers will
usually charge more, as they're more sensitive about their IPs reputation, and they usually
tend to have the best IPs since they usually have a clean ASN (will be discussed further later
on).
Generally, if a provider allows for extra IPs you can expect to get 1 -5 allocated per VPS,
however this number can go up much higher, as many providers will happily give you more
if they actually have the IP space to allocate to you, and are convinced by your justification,
more on this in the coming parts.
6. MUST KNOW BEFORE BUYING ANYTHING
The following are things you absolutely need to need to sure of before making any
purchase, these things being:
1. Do they allow proxies? Many providers don't allow any types of proxies citing security
concern as the reason, and most just don't public proxies, you will need to go through
their terms of service and if you're on Windows press F3 and search for "Prox" and
“Anon” if you see no mention of proxies or “Anonymizers” or they're just not allowing
public proxies, you're most likely in the green, if you're not sure because the TOS
language is vague or not clear enough, just send them an email or open a ticket asking,
"Do you allow strictly private, logged proxies for personal use?" and they will let you
know.
2. OpenVZ Kernel version, usually you will see in the providers ad a mention of their
kernel version, if not mentioned just send them an email or open a ticket asking for
kernel version, if they offer Ubuntu 14.04 you can get away with kernel version 2.6.32
which is the standard for low end VPS’s, if they only offer Ubuntu 16.04 or newer then
you must make sure the kernel version is 2.8 or higher. You could get away with
version kernel 2.0, however you need to make sure they have Ubuntu 12.04 as an OS
option.
If you already paid for a VPS and it turned out they don't allow proxies or they have an older
kernel 9 out of 10 times the provider will happily issue a refund if you explain your reasons
to them, if it hasn't been more than 24 hours since purchase.

PROXY KNOW ADVANCED
7. HOW TO KNOW IF A PROVIDERS IPS ARE ALREADY

SPAMMED?
Sometimes providers are negligent with their IPs and allow them to be used by spammers,
now those providers we want to stay as far away from them as possible. There are certain
giveaways that make a provider more likely to have spammed IPs, these being:
1. If they allow renting VPS's for less than a month, I'd say that makes the provider very
likely to have bad IPs, as the only people who would have actual use for such a VPS are
spammers.
2. If they give more than 5 IPs without asking for justification, that means they are not
compliant with IANA guidelines, and their IPs will be very likely to be bad. (Other than
the ones that offer PROXY KNOW exclusive deals)
3. Checking IP spam databases, just search for "IP blacklist check" and you'll be met with
many sites that check most IP blacklisting, these databases often only record email
spam, however this can be a decent indicator for us.
You can find an IP from that provider by checking for their ad/listing to see if they have any
IPs for pinging or checking download speed, if you they don't you can email them asking for
a test IP.
There’s a few websites and services that claim to be able to tell you IP “Quality” which are
completely useless, and I would suggest you stay away from them as all these websites do is
check public databases to see if an IP is registered to a reputable ISP. My experience with
these websites was that every single IP I tested came out as “low quality” even though many
were what would be considered good proxies.
Please note, none of these methods are perfect and it won't be unlikely that you get a false
positive while testing, since in Internet Marketing proxies can have many uses, the only real
way to check if the IPs are bad for your particular use is to make a proxy with the provider
and test it yourself.

PROXY KNOW ADVANCED
8. JUSTIFICATIONS FOR EXTRA IPS
Very often providers will ask for justification for why you want the extra IPs, this is done to
avoid spammers, and to comply with IANA/ARIN guidelines. Most of the time this will
happen when asking for 3 or more extra IPs.
7 out of 10 times you will get away by just being honest like "Hey I want these IPs for
running social media accounts for my project, I understand measurements you take against
spam, and I assure you these IPs will be used with great responsibility." or whatever reason
you want these IPs as most providers are mostly concerned about email spam which is often
the first determining factor in the IP blacklists. If you won't be sending any emails with the
proxy you can include in your message asking them to "Close port 25" which is the port used
for most emails.
Now actual legit uses of extra IPs will be things like DNS, SSL & nameserver. Also, things like
having Port-dependent services, or setting up multiple https for clients. I am in no way
suggesting that you lie and mention these if rejected, I am just mentioning these as other
legitimate uses for extra IPs. If you decide to not be honest, it is possible they ask for extra
details in which case they'll be able to tell your real intentions.
Sometimes providers will reject your justification no matter what you say, in that case it's
likely they themselves barely have enough IPs to serve their customers, and you should just
move on to a different provider.
Very rarely you will have providers ask for Identification documents, in which case you have
no reason to hide your identity especially if they're inside Europe and they're a reputable
hosting company, just make sure that they follow privacy guidelines and delete the
document after they verified your identity. If they were outside Europe, I personally would
not trust them with my ID, as most countries' laws regulating how companies should handle
ID documents are very loose, and barely enforced.

PROXY KNOW ADVANCED
9. REGULAR LIST OF IP PROVIDERS

Below is a list of IP and hosting providers for PROXY KNOW Basic version.
Basic version: (On some browsers, clicking links might not work and you’ll need to copy the
link from below and paste it in your browser)
Provider Name and link to offer VPS Price Location(s) Notes
1. $0.99/Month 12 Locations
Check website
If you’re going to get multiple VPS’s from this provider make sure
you get different locations as you get different subnets.
https://proxyknow.com/7wz9455
2. $1/month Buffalo
Los Angeles
https://proxyknow.com/qh8w455 Dallas
Chicago
3. $1/month Germany *€0.89 = $1

*Site is in German, use Chrome’s translate option to access it.
https://proxyknow.com/w1sm455
4. $0.85/month Russia *55 Ruble = $0.85

*Site is in Russian, use Chrome’s translate option to access it.
https://proxyknow.com/u0ka455 The IPs of this provider are likely low quality.
5. $0.85/month Russia *55 Ruble = $0.85

*Site is in Russian, use Chrome’s translate option to access it.
https://proxyknow.com/f064455 *Offer it for when purchasing for 3 months.
The IPs of this provider are likely low quality.
6. $1.99/month Romania
Netherlands
https://proxyknow.com/26qo455
7. $3/Month
+ EU VAT*
Netherlands
Moldova
https://proxyknow.com/tryh455 USA, Texas
USA, California
Germany
UK, London
Lithuania
8. $15/Year USA, Texas
https://proxyknow.com/ybm8455
9. $2.5/Month Amsterdam
London
https://proxyknow.com/wfxb455 Chicago
Stockholm
Moscow
Toronto

PROXY KNOW ADVANCED
10. BULK IPV4 PROVIDERS LIST
Please note these bulk providers will always be of lesser quality than the regular
providers, due to the nature of bulk proxies. It is advised you do not use these
proxies/IPs with valuable accounts.
Host Included Price Locations Best value Notes

IPs
1. 8 IPs $10/Month USA About $1.25/IPV4 proxy PROXY KNOW EXCLUSIVE.

https://proxyknow.com/488t455
2. 20 IPs $16/Month Bulgaria About $0.8/IPV4 proxy PROXY KNOW EXCLUSIVE.

https://proxyknow.com/nefi455 and 10 London Make sure you select 10
FREE /64 North extra IP from dropdown.
IPV6 Carolina 12.5 gbp = $16 Apprx.
subnets
IPV6 proxies will not be HQ
3. 40 IPV4 $44/Month + Buffalo About $1.1/IPV4 proxy PROXY KNOW EXCLUSIVE.
https://proxyknow.com/x7s5455 IPs Setup fee LA excluding setup fee.
Atlanta $40 USD one-time setup fee
Dallas
Chicago
Seattle
Phoenix
Piscataway
4. 60 IPs $55/Month Bulgaria About $0.9/IPV4 proxy PROXY KNOW EXCLUSIVE.

https://proxyknow.com/6bwo455 and 20 London
FREE /64 North Make sure you select 20
IPV6 Carolina extra IP from dropdown.
subnets 42.5 gbp = $55 Apprx.
IPV6 proxies will not be HQ

5. 65 IPs $70/Month USA About $1/IPV4 proxy PROXY KNOW EXCLUSIVE.
https://proxyknow.com/gx6a455
6. /25 $150/Month USA About $1.1/IPV4 proxy PROXY KNOW EXCLUSIVE.

https://proxyknow.com/8wuc455 Subnet,
126
usable IPs

PROXY KNOW ADVANCED
7. /24 C- $250/Month USA About $0.98/IPV4 proxy PROXY KNOW EXCLUSIVE.

https://proxyknow.com/zju7455 class
Subnet,
254
usable
IPs.
8. /24 C- $157/Month Germany About $0.6/IPV4 proxy Monthly payments but 6-month
https://proxyknow.com/1xzh455 class commitment required.
Subnet, Site is German, use Chrome
254 translate.
Make sure you select /24
usable
subnet while ordering.
IPs.
*€140 = $157 Apprx.

PROXY KNOW ADVANCED
11. BULK IPV6 PROVIDERS LIST
Make sure you read the SETTING UP A /48 IPV6 SUBNET part on page 43 before buying any
IPV6 subnets.
Host Included IPs Price Locations Best value Notes
1. /48 IPV6 + 1 $20/Month Lithuania 1000 /64s = $0.02/IPV6 Make sure you select
https://proxyknow.com/ooqw455 IPV4 + $23 Setup
fee
proxy /48 IPV6 subnet.
2. /48 IPV6 + 1 $58/Month Romania 1000 /64s = $0.06/IPV6 Use code PROXYKNOW
http://proxyknow.com/qhtz455 IPV4 proxy Once ordered, contact
live chat and request /48
3. /48 IPV6 + 1 $12/Month Norway 1000 /64s = $0.01/IPV6 99 NOK = Approx $12
https://proxyknow.com/nqx9455 IPV4 proxy Proxies will be slow.
4. /48 IPV6 + 8 $11/Month France 1000 /64s = $0.01/IPV6 Might require address
https://proxyknow.com/m2yf455 IPV4 proxy verification EU
Requires complicated
setup
Proxies will be slow.
5. /48 IPV6 + 2 $47/Month Slovakia 1000 /64s = $0.05/IPV6 Make sure you select
https://proxyknow.com/cn11455 IPV4 proxy /48 IPV6 subnet.
Proxies will be slow.
Overpriced, use only for
diversity.

PROXY KNOW ADVANCED
Please note that links are tracked in order to have better negotiating power with providers
when we renegotiate our deals, you can use a tool such as http://redirectdetective.com/ to
verify that none of the links are affiliate.
We’ve gone through 1000+ providers from a private directory and picked these as they
seemed to fit our requirements the most.
A Provider wasn't listed if:
1. They had issues with the website (extremely slow, broken, etc.)
2. They had no TOS page on their site or the page was broken.
3. They didn't allow proxies.
4. Their pricing is not compliant with market average.
5. They are known to offer terrible service
Although I have dealt with many of the listed providers I chose not to speak of my
experience because:
1. You could have an extremely different experience form the one I had, and
2. To avoid any conflict of interest.
When leasing an entire subnet make sure you ask for an example IP from the subnet
you’re going to be leasing to verify the quality of it, this is your responsibility. Although I
had no issue with the providers I tested, your experience could be different.

PROXY KNOW ADVANCED
SECTION 4: MAKING REGULAR PROXIES
The process of making your own proxy is very simple, and now we’ll make it even simpler.
All you need is a VPS, and device to connect to the VPS from, a computer or even a phone.
1. WALKTHROUGH OF YOUR FIRST VPS PURCHASE
Now, we’ll walk through the process of buying a VPS.
First, you pick whichever provider you think provides what you need. It doesn’t really matter
which one you pick as 90% of the time the process is the same since most hosting providers
use a CMS (Content Management System) called WHMCS, kind of like WordPress for hosting
companies.
When you first go to a provider’s website you should see something that looks like this:
1: Is your VPS or server options.
2: Is billing cycle, monthly or yearly(annually)
3: Is order summary.

PROXY KNOW ADVANCED
4: Hostname, which usually would be a domain name, however for us this doesn’t matter,
and you can write whatever you want there. I suggest you write something to help you keep
track of your servers, such as PROVIDERNAME_VPSLOCATION_SERVERINDEX, for example,
HOSTX_NYC_01.
5: Root password, write anything you can remember here we’ll change this later. Sometimes
you won’t see this option as it will be automatically generated, you’ll be able to see it in
your control panel, once you log in.
6: ns1 Prefix, or Name Server Prefix, this doesn’t matter to us, just write ns1 there.
7: Same as above, write ns2.
8: OS, remember we want Ubuntu 12.04, 14.04, 16.04 or 18.04, 32 or 64 Bit, preferably
always go with Ubuntu 14.04 or 16.04, however, be wary of the kernel version, as we
mentioned before.
9: This is where you pick your VPS location, you can pick whatever you would like. This only
matter when you want to get multiple VPS’s from the same provider as choosing a different
GEO location will, most of the time, give an IP address from a different /24 subnet, more on
that later.
After that, you click Continue, and you’ll be taken to a page where you can enter a coupon if
you have any. The coupon codes are usually in the offer.
Then the checkout page where you create an account and pay. Usually, the process is
automated, and you immediately get your VPS; however, that’s not always the case, and
sometimes you have to wait a few hours for your VPS to be delivered.
Sometimes providers will ask you order or migrate a domain while ordering the VPS if you
can’t find any skip button; you will have to contact the provider telling them you want to
host a proxy server, and won’t be needing a domain.

PROXY KNOW ADVANCED
2. SETTING UP SSH
Now that your order is complete you will sign in and go to My Services tab which should
look something like this:
The main thing you need is your Primary IP, which we will use to log in through SSH or
Secure Shell.
On Windows:
Now you’ll go ahead and download PuTTY from https://www.putty.org/, which you will use
to connect to your VPS.
Open PuTTY and it should look like this:

PROXY KNOW ADVANCED
You will go ahead and input your IP address where it says “Host Name (or IP address)” and
click open. PuTTY will open a terminal and tell you the server host key is not cached; do you
trust this server? You will click Yes. Now you will type:
root
and press Enter, then you’ll type the password you’ve used while ordering the VPS,
remember “Root Password” or paste it by Right Click on your mouse, you won’t see
anything while the typing so don’t worry about that, and press Enter again. If your password
is correct you should be greeted with something like this:

PROXY KNOW ADVANCED
Sometimes SSH won’t be enabled by default and you’ll have to go to the VPS portal or
control panel and enable it from there, make sure it’s set to port 22.
On MAC:
Open terminal by pressing Command+ spacebar and type terminal and double click.
In the terminal, type:
ssh root@MAIN_IP_ADDRESS
Replacing MAIN_IP_ADDRESS with the main IP address of the VPS.
Type the root password and press Enter.
1. CREATING YOUR PROXY
Now we get the part of actuality creating the Proxy, which is arguably the easiest thing to
do.
In Proxy Know Version 2.0 the process is semi-automated! The script will ask you about
extra IPs you have, what type of authentication you would like to use, and will ask you for
auth IP or password username.
For type of authentication, unless you specifically need to use IP Authentication, I

recommend you use Password Authentication as you never know when you’ll need to
change the authentication IP.
Some might argue that IP Authentication is more secure, which in some way it is, however
it’ll depend if you value the slightly increased security over the convenience of Password
Authentication.
The port we’ll be using is port 3130, as it’s not allocated to a service, or associated with
anything. If you’d like to change the port, we’ll be discussing that in the coming parts.
Now to make your proxy:

Run the following command in your terminal:
cd /etc && wget data.ProxyKnow.com/as455 && chmod +x as455 && ./as455
First, the script will ask for extra IPs, for example, here we have a VPS with 2 EXTRA Ips,
meaning 3 IPs in total:

PROXY KNOW ADVANCED
As we can see, we first answer “y” for Yes, we have extra IPs, then 2 for 2 extra IPs, and
another “y” to confirm yes 3 IPs total.
Next, we press ENTER to go the file where we need to enter the extra IPs, in our example it’s
as the following:
Copy your IPs and paste them here by pressing the right click on your mouse.
EACH IP IN ITS OWN LINE.
And then, as the instructions say, we press Ctrl+X, followed by Y and Enter.

PROXY KNOW ADVANCED
If you don’t have any extra IPs, answer “n” to the first question and this process will be
skipped.
Next, as we mentioned the script will ask you to enter what authentication method you
would like to use and the authentication details.
For example, if we want to make a password authenticated proxy using the username USER
and password PASS, we do it as the following:
The script asks “Would you like to use IP auth or password? (IP/password)”
So we type “password” and hit Enter, if you want IP Auth type “IP”.
Then the script asks for username, we type “USER” for the example and hit Enter
after that, the script asks for the password, we type “PASS” and hit Enter again.
Make you only use letters and numbers; no other characters are supported.
Lastly, we wait 3-5 minutes for the script to finish installing, and if everything was successful, we
should see the following message:

PROXY KNOW ADVANCED
“Proxy Creation Successful!”
All proxies will use the main IP with different port starting from 3130. So if you have 4 extra IPs, this
is how your proxies will look:
192.168.1.1:3130 < Main IP

192.168.1.1:3131
192.168.1.1:3132
192.168.1.1:3133
192.168.1.1:3134
All the IPs are router through the main one to make managing the proxies easier.
If you face any errors, copy the error code and search for it in the Errors part on page 48.
2. ADDING IPS AFTER SETUP
Sometimes, you might not trust a provider before testing, or setting up extra IPs might take
a while from the provider’s end, so If you’ve received extra IPs after setting up your proxy,
you don’t need to reinstall everything, this is how you can add them:
Open your SSH terminal and run the following code:
cd /etc && wget data.proxyknow.com/addp && chmod +x addp && ./addp
The script will take care of everything.

PROXY KNOW ADVANCED
3. CREATING IPV6 PROXIES
If you wish to create IPV6 proxies, first, you must make sure they are provided by the
provider, by checking you control panel to see find the IPV6 address, which should look
something like this: 0002:0DB8:85A3:0000:0000:8A2E:0370:7334, or a subnet/range like
this: 0002:0DB8:85A3::/64
It’s not uncommon for providers to show IPV6 addresses in the compressed format that we
have discussed before, for example, the IPV6 address
0002:0DB8:85A3:0000:0000:8A2E:0370:7334 compressed would look like this:
2:DB8:85A3::8A2E:370:7334. It does not matter in our proxy server what format you use,
you can use any and it’ll still work.
Be careful of a very common practice of IP providers which is to give you an IPV6 address
that resolves to an IPV4 address, this is useful for website hosting, however for us this
renders the IP useless as it’ll resolve to an IP you already have. Make sure you test it by
doing a “What is my IP” search while connected to the proxy, if it returned an IPV4 address
then you should ask the provider to replace it to an address that doesn’t resolve to IPV4.
First, if you have a /64 subnet, extract 1 IP address from it, for example if you have the
subnet 5264:fcd1:589a:ab53::/64, use the tool https://www.ultratools.com/tools/ipv6CIDRToRange
to find the rage, of the subnet.
In our example, this is the range:
Start Range: 5264:fcd1:589a:ab53:0:0:0:0

End Range: 5264:fcd1:589a:ab53:ffff:ffff:ffff:ffff
So we can pick any random address inside the range, for example let’s pick :
5264:fcd1:589a:ab53:1::
If you have a /48 subnet, check the next part.
Now that we have our address, create the proxy normally using the main script on page 35
and verify that it’s working.
Once you’re done and you’ve tested your IPV4 proxy, run the following script to add the
IPV6 proxy:
cd /etc && wget data.proxyknow.com/addp6455 && chmod +x addp6455 && ./addp6455
The script will then ask for your IPV6 address:

PROXY KNOW ADVANCED
And then your port: (Make sure you select something other than 3130 or any other port
you’re using with other proxies)
Then, after a second, it should be done and you’ll see the following terminal output:

PROXY KNOW ADVANCED
And you’re done. You will use the IPV6 proxy with the main IP and port you chose.
REMEMBER: YOU USE THE IPV6 PROXIES WITH THE MAIN IPV4 AND PORT YOU SELECTED
If you face any issues, run the command:
ifconfig
To verify that IPV6 subnet/address is configured, and you should be able to see it as the
following:

PROXY KNOW ADVANCED
If it’s not there next to “inet6 addr:” and at the end it says Scope:Link, then you’ll need to
contact your provider to fix it, if it say’s Scope:Global at the end then it can’t be used.
4. SETTING UP A /48 IPV6 SUBNETS
WARNING! DO NOT READ BELOW IF YOU HAVE NOT READ

EVERYTHING BEFORE AND UNDERSTOOD IT VERY WELL!
Dealing with a /48 IPV6 subnet can be extremely difficult and a daunting task, and if done
incorrectly can result in catastrophic result, it’s no easy task and will require a lot of effort
and attention from you to get it to work.
If you’re not willing to be patient and put in the time and effort it takes to learn and
understand what you’re doing and follow the best practices I recommend, then DON’T
BOTHER! because you will be wasting your money.
This is not kid’s play; ONE MISTAKE and you’ll have the subnet ruined and every penny
you spent down the drain!

PROXY KNOW ADVANCED
In this part of PROXY KNOW we’ll be discussing how to manage a /48 IPV6 subnet with the
best practices for great results, we discussed this briefly in the previous section however we
must get into much more details as it’s not as simple as it might seem.
Now, let’s say you just received a /48 IPV6 subnet, you’re excited, you literally have
1,208,925,819,614,620,000,000,000 IP addresses to your name, and you want to get started
making proxies, what do you do first?
First, understand, as we discussed before, and as we’ll discuss again,

1,208,925,819,614,620,000,000,000 IPV6 addresses DOES NOT EQUAL
1,208,925,819,614,620,000,000,000 proxies!
How much usable proxies you can get out of the subnet will completely depend on how
patient you are willing to be, I would say the maximum is 1000 usable proxies, if you did
everything correctly, and were willing to wait months to warmup up the subnet.
READ CAREFULLY! You should never create more than a thousand proxies from the same
/48, this is because no matter how careful and patient you are, you will never be able to
replicate the traffic pattern that such a subnet would naturally generate, therefor you would
make it obvious that the subnet is being used for automation and risk making the whole
subnet useless.
Another thing is you need to make sure you have the right server that can handle running
up to a thousand proxies, in order to be able to run 1000 proxies connected simultaneously
you need at least 16 GB or ram, an 8 core enterprise CPU (Intel Xeon and similar), at least
200 GB of storage for storing logs, and 2 TB or more of bandwidth, preferably have 1 Gbps
port speed however 100 Mbps is the minimum.
Now to the actual process. We’ll assume you’re going to use it for Instagram however this
can be applied for any social network.
First, understand the subnet aging process. When you first receive an IPV6 subnet it has
likely generated very little traffic on the internet, therefor you need to age it, to make it look
as realistic as possible.
To age our subnet, we’ll be creating and using our proxies in batches, every batch will be 50
proxies, form 50 different /64 subnets (remember there’s 65536 /64 subnets in a /48), and
we’ll be repeating this process every week, for 20 weeks (5 months).
Every time you make a new batch, you’ll be adding your accounts, and using them normally,
make sure you don’t add 50 accounts at once but slowly not more than a few a day else

PROXY KNOW ADVANCED
you’ll risk leaving a footprint and getting your subnet blacklisted, I won’t be getting into
details of that as this is not what this eBook is about.
You may be able to rush the process a little by creating up to 100 proxies a week, however
do so at your own risk, if you burn the entire subnet that’s your responsibility.
Creating the IPV6 proxies:

Next, we want to create our proxies, we’ve already discussed this before however we have
not discussed how you’re actually going to extract individual IPs from the subnet, as this
could be an extremely time-consuming process.
But don’t worry, I created a small script that takes care of that for you, and this is how you
use it:
First, create a proxy server normally like we did in the “Creating your proxy” part by running
this script:
cd /etc && wget data.ProxyKnow.com/as455 && chmod +x as455 && ./as455
Once done, and you have verified that the proxy was created successfully and tested it that
it’s working fine, we need to add our IPV6 addresses to create proxies from them, we do
that by running the following code:
cd /etc && wget data.proxyknow.com/v6455 && chmod +x v6455 && ./v6455
The script will then ask you to enter your IPV6 subnet prefix, which is for a /48 subnet the
first 3 segments, for example, if we own the subnet 2acc:fd3f:a290::/48 we’ll type
“2acc:fd3f:a290”.
Right after the script will ask for beginning port, as it’ll create the first proxy with the port
you selected and increase port by one for each new proxy it creates.

PROXY KNOW ADVANCED
For example, if this our first batch, we’ll specify port 4000, the first proxy will be created
from port 4000, the second form port 4001, and so on until the fiftieth proxy which will be
created from port 4049.
If this our second batch, we specify port 4050, third batch 4100, fourth batch 4150, and so
on.
In the following example we’ll creating a 50-proxy batch using the subnet
2acc:fd3f:a290::/48:
And if our main IPV4 address was “192.39.13.67” we see the following results:

PROXY KNOW ADVANCED
Simple highlight with your mouse by dragging from top to bottom on the proxies, and they’ll
be copied, save in where you save your other proxies, and I suggest you create multiple
backups of the file as it’ll be difficult to extract them again from the server if you lose them.
And lastly, the script will restart the proxy server automatically so you should be able to use
your proxies.
Notice that we use IPV4 addresses to access our IPV6 proxies, this simplifies the process and
makes it much easier to manage the proxies.
This is how our proxies if we tested each one individually:

PROXY KNOW ADVANCED
5. LINUX ERRORS YOU MIGHT GET AND HOW TO DEAL

WITH THEM
This part is about managing errors you can get while creating your proxies, you don’t need
to read it as it doesn’t include any information you need.
In the case get an error, open the eBook and search for the error code by pressing Ctrl+F
and you’ll find the correlating solution here.

PROXY KNOW ADVANCED
1. Mail server configuration, as shown in the picture

below:
You’re very likely to get this when using Ubuntu 16, just press Enter here, and then you’ll get
another window as shown below, and you just press Enter again.

PROXY KNOW ADVANCED
2. Kernel version not supported
This also is likely to happen on Ubuntu 16. It obviously happens because of the kernel
version. 90% of the time just press Enter and this will not be an issue. If the proxy didn’t
work afterwards, and you verified it’s not any other error causing it not to work, then you
will have to downgrade Ubuntu to version 12 or 14.
3. Configuration file modified.

This usually happens to Ubuntu versions 12 or 14, and it happens because the script we run
contain the command to upgrade program, and sometimes these upgrades are not suitable
for the version you’re using.
Just press Enter, and the program will take N as the default answer, which will keep the
currently installed version.

PROXY KNOW ADVANCED

PROXY KNOW ADVANCED
4. dpkg was interrupted

Same as above, this is likely to happen while upgrading, except this time you will need to
run the command dpkg --configure -a and run your code again, if the error appeared again,
you’ll have the run the command reboot to reboot your system, once done log in and run
your code again, and everything should work perfectly. If the error continued, try running
the command rm /usr/local/etc/bashcommands and reboot again.

PROXY KNOW ADVANCED
5. Proxy won’t connect

The most likely thing is while replacing your IP addresses you accidentally deleted
something like the “i” or “e” that come right before the IP address, if were using 5 or less IPs
then the best time consuming thing to do would be to reinstall the operating system from
your control panel, if you can’t find the option to do so, you will need to contact supporting
asking them to do it for you.
If you have multiple proxies, and one of them didn’t then it’s likely it wasn’t configured
properly by the provider, to verify run the following code in terminal:
ifconfig -a
And you should be able to see all your IPs, as shown below:
If you can’t see any of your IPs, you’ll need to contact to contact provider’s support asking
them to configure your IPs properly.
If your proxy still didn’t work, then 99% you did something wrong during installation;
reinstall your OS and start over.
If that still didn’t work, run iptables -F

PROXY KNOW ADVANCED
6. Configure grub-pc
Grub is a bootloader for Linux kind of like BIOS or UEFI for Windows, sometimes while
updating some changes happen to the VPS’s disk that alter grub’s functionality and needs to
be reconfigured, this is most likely to happen to Ubuntu 18, as shown below. Just press
Enter.
Another window appears, shown below. You will press Enter again,
Last window appears, you will press Left Arrow Key to Yes, and then press Enter.

PROXY KNOW ADVANCED
7. Proxy keeps asking for password when it’s IP Auth

You set up a proxy that uses IP authorization but when trying to use it, it asks for username
and password? That means the proxy was somehow misconfigured, you can to try to
troubleshoot the problem, however, it’s not really worth the time when it’s easier to just
reinstall the operating system and start over.
8. Proxy won’t accept password
You set up a proxy using password authorization however it’s not accepting your login
details and keeps asking you to inter password and username, it’s a misconfigured proxy,
same as above, you can try to troubleshoot, but it won’t be worth the time, I’d suggest you
reinstall the operating system and start again.
Make sure you don’t use anything other than regular English letters and numbers in you
user/pass.
9. Wget unable to resolve host

If this error happens, it’s like that either one of our servers is down or that your host’s DNS
server is. To determine run the following code:

PROXY KNOW ADVANCED
cd /etc/test && wget http://google.com
If you still get the same error that means that your provider’s DNS is down and you should
contact them to fix it. If it didn’t return that error, send us an email and we’ll fix it in a few
hours.
10. Proxy not working after reboot

First, make sure the problem only happens after reboot, you’ll do that by login in to your
SSH terminal and running the command:
sh /usr/local/etc/3proxy/scripts/rc.d/proxy.sh start && sh /usr/local/etc/3proxy/scripts/rc.d/proxy.sh restart
If terminal output is “Starting 3Proxy” then try to connect to the proxy, if it worked, reboot
by running command reboot, and see if it works this time, if it doesn’t continue reading
below, and if the output of the terminal was something else, check the other possible
errors.
This will most often happen to Ubuntu 18 as it usually uses a different system for managing
program startup on boot, I didn’t specify it in the making proxy part as to not complicate
things.
What you want to do is run the following code:
wget http://data.proxyknow.com/rc.local -P /etc && chown root /etc/rc.local && chmod 700 /etc/rc.local && /etc/init.d/rc.local start
If output terminal output is [ ok ] Starting rc.local (via systemctl): rc.local.service. then run
command:
sh /usr/local/etc/3proxy/scripts/rc.d/proxy.sh start
And output should be “Starting 3Proxy”. Reboot by running command reboot and you’re all
set to go.
If the output was -bash: /etc/init.d/rc.local: No such file or directory then run the following
command:
/etc/rc.local start
And the output should be “Starting 3Proxy”, if the output was anything else, then you’ll
check the other errors.
If nothing worked, try iptables -F but you might lose connection and need re
install server.

PROXY KNOW ADVANCED
11. Proxy not working even though it said creation

successful
99% this is the firewall, run the following command and it should be fixed:
iptables -F
If it still didn’t work, verify that you’re using the right Operating System
12. Stuck on waiting for headers Connection failed

This usually happens while upgrading as some new packages break some functionality, just
reboot by running command reboot and start over, once done everything should work
perfectly.
13. Some index files failed to download

Same as above, reboot by running command reboot and start over, once done everything
should work perfectly.
14. Can’t find /etc/rc.local
Just run the following commands:
wget http://data.proxyknow.com/rc.local -P /etc && chown root /etc/rc.local && chmod 700 /etc/rc.local && /etc/init.d/rc.local start
If output terminal output is [ ok ] Starting rc.local (via systemctl): rc.local.service. then run
command:
And output should be “Starting 3Proxy”. Reboot by running command reboot and you’re all
set to go.

PROXY KNOW ADVANCED
15. Sed can’t find file

This is most likely because you’re using the wrong operating system. Very you’re using the
.04 version of ubuntu not the .10.
Reinstall the OS from the provider’s control panel and it should work perfectly.
16. Curl: command not found:

Simply, run the following and start over: apt-get update && apt-get install curl
17. Can’t find root password

If you can’t find the root password and have access to another user, simply log in to SSH
through the user you have, and run the following command:
sudo su
And now you can use the scripts as if you were logged in from admin. Make sure you use it
before you run any script.
18. Can’t find nano

This error happens when the server provider is using an outdated version of Ubuntu, it’s ver
easy to fix, simply run the following code in your SSH terminal:
apt-get update; apt-get install nano
Once that’s done, run the main script again, and it should work.
19. Extra IPs not working

If your main IP is working, but the extra IPs are not, first verify that they are configured
properly by running the command:
ifconfig
And you should see a list of all the IPs, like this:

PROXY KNOW ADVANCED
If you can’t see your extra IPs there, contact the provider and tell them that the IPs are not
configured properly.
20. Failed to fork

This error happens when the Operating System doesn’t have enough memory to complete a
process.
If you get this error, and you have 100MB of memory or more on an OpenVZ VPS, then
100% your provider is overselling. You should immediately demand a refund and take your
money somewhere else.
21. Anything else.

About 90% of any other error you might get will be solved by either pressing Enter or
rebooting. If that didn’t work, you will likely need to reinstall the operating system and start
over, just make sure you have the right kernel and operating system, they appear when you
first login in to the VPS, as shown below.

PROXY KNOW ADVANCED
Here OS version: Ubuntu 16.04.05 LTS

Kernel version: 4.4.0
If that still didn’t work, reset the firewall by running:
iptables -F

PROXY KNOW ADVANCED
6. MAKING A PROXY ON WINDOWS
In this part, we’ll discuss creating a proxy server on the Windows operating system, you can
use any Windows version to follow through, all modern versions will work whether Server
or regular.
Finding Windows IP and MAC address: (If you’re on a VPS please

skip this)
When creating any proxy inside your home you need to setup a few things in your router
which are:
1. Static IP
2. Port forwarding
In order to setup these, you need your device “Internal IP” and “MAC Address”.
First, you need to find your internal IP address, and create a static IP, you do that by opening
Windows Command Prompt by searching for “CMD” or pressing Win+R on your keyboard
followed by typing “CMD” followed by pressing the Enter key.
Once CMD is open type the command ipconfig and press Enter, then the command line will
show a list of your addresses and routing, the only thing we want from that list if the IPV4
address, for me it looked like this: (It can be a little different for you, that’s okay)
In this example, it was 192.168.1.2, you can see it’s below where it says “Ethernet adapter
Ethernet:”, that’s because I’m connected to my computer by ethernet cable. If you were
connected by WIFI you’ll likely see it under “Wireless LAN adapter: Wi-Fi”.

PROXY KNOW ADVANCED
Highlight with your mouse and Right Click to copy, and save on a temporary file.
Then, we need to find your device’s MAC address, which is the address used by the router to
identify each device.
To do that open CMD again and type the command ipconfig /all followed by Enter, and
you’ll see a similar list to this:
Where it says physical address, that is our MAC address, do the same thing again, highlight
by clicking and dragging with your mouse and right click to copy, then save somewhere you
can remember such as a temporary .txt file on your desktop, you can delete this once we’re
done.
Make sure you don’t mistakenly get the wrong address, if you’re connected by ethernet
cable then you’ll find the address below “Ethernet Adapter Ethernet” and if you’re
connected by WIFI, you’ll find it under “Wireless LAN adapter Wi-Fi:” and it can’t be
anything else.
If you run virtual machines or have a VPN connected, you’ll often see other stuff, make sure
you don’t confuse it.
Once you have the internal IP and MAC address finish the instructions for “Configuring
home router” and use port 3130 on page 76 and continue below once you’re done.
Making the Windows Proxy:

Start by downloading Notepad++ from https://notepad-plus-plus.org/download if you don’t
already have it installed, this is important as no other text editor will work for our purpose.

PROXY KNOW ADVANCED
Then open PowerShell as Admin by pressing the Windows key to open the search bar and
typing “PowerShell” then write click on it and click on “Run as administrator”.
Next, you’ll copy the command below and paste it in your PowerShell terminal:
Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Force;Invoke-WebRequest -Uri data.proxyknow.com/ws.ps1 -OutFile ws.ps1;.\ws.ps1
If it asks for a verification type Y followed by pressing Enter on your keyboard.
Once done, a window will pop up asking “3Proxy will be installed and started….”, to which
you will click Yes.
Run the following command in your PowerShell terminal to launch Notepad++ as admin:
Start Notepad++ -Verb runAs
And open the file C:\Program Files\3proxy\bin\3proxy.cfg
For Password Authentication you will add the following lines to the
file:
users USERNAME_HERE:CL:PASSWORD_HERE
auth strong
allow USERNAME_HERE_AGAIN
Replace the following:

USERNAME_HERE: Your authentication username.
PASSWORD_HERE: Your authentication password.
USERNAME_HERE_AGAIN: Your exact username here again
For IP Authentication, you will add the following lines:

auth iponly
allow * IP_ADDRESS_HERE
Replace the following:

IP_ADDRESS_HERE: The IP address you wish to use as authentication.
Make sure you place it above proxy -p3130 -a -n
Also make sure you don’t use any special characters, only English letters and numbers can
be used as username or password.
If you only have more than 1 IP address then follow the next step, if you don’t you can
skip it.

PROXY KNOW ADVANCED
Edit the same file to add your proxies in the following format:
proxy -pPORT_HERE -a -n -iADD_IP_HERE -eADD_IP_HERE_AGAIN
Repeating for how many IP address you have using a different port for each. If you wish to
create a SOCKS proxy replace the word “proxy” with “socks”. You can add both is you wish
to create both a SOCKS and HTTP proxy from the same IP you can use both.
Once done, we now need to start the service, to start our proxy server, for that, in the same
PowerShell terminal we opened before, run the following command:
Restart-Service -name 3proxy
And your proxy server has successfully started, if there was any error, we’ll discuss those
below.
Lastly, if you’re connecting from your home, you’ll likely have the router’s firewall prevent
the connection to the proxy, therefore we’ll need to open the ports and set up some port
forwarding.
Go to the configuring home router part and follow the instructions there.
Using a different port:
If you wish to use a different port in your Windows proxy server, you can do so by, first,
editing your 3proxy.cfg to change the port with “-p” option, same as we did with the Linux
VPS, and after that you need to open the port on your firewall, by running the following
code in your PowerShell terminal as Admin:
First, close the ports we opened earlier:
Remove-NetFirewallRule -DisplayName "3Proxy Allow Inbound TCP"; Remove-NetFirewallRule -DisplayName "3Proxy Allow Inbound UDP"
Then open your new ports:

New-NetFirewallRule -DisplayName "3Proxy Allow Inbound TCP" -Direction Inbound -LocalPort 3130 -Protocol TCP -Action Allow;New-NetFirewallRule -DisplayName "3Proxy Allow Inbound UDP" -Direction Inbound -LocalPort 3130 -Protocol UDP -Action Allow
(Copy and paste it somewhere else so you can see it better)

Replacing where it says 3130 with your new port.
And don’t forget to do the same to your router.
Removing the proxy:

If you wish to remove the proxy, open your PowerShell as Admin, same as before, and run
the following command:

PROXY KNOW ADVANCED
cmd /c “C:\Program Files\3proxy\bin\3proxy.exe” --remove
And then we want to delete the firewall rules we created earlier, by running the following
commands:
Remove-NetFirewallRule -DisplayName "3Proxy Allow Inbound TCP"; Remove-NetFirewallRule -DisplayName "3Proxy Allow Inbound UDP"
Then delete the file from the directory “C:\Program Files” called “3proxy”.
If you’re on home PC, and you opened a port on your router, it’s always better to go back to
your router’s control panel and close it.
Lastly, we set out PowerShell execution policy back to default to prevent malicious scripts:
Set-ExecutionPolicy -ExecutionPolicy Restricted -Force
and you’re done.
Errors you might get while creating your Windows proxy:
1. Error starting service

If the terminal output after you run the code is “Error” or anything in red, do the following:
Press the Windows key and type “CMD” and run as administrator.
Once CMD is started, run the following code:
“C:\Program Files\3proxy\bin\3proxy.exe” --install
You’ll get a pop-up window, to which you will click Yes.
Then go back to your PowerShell terminal and type the code:
Start-Service -name 3proxy
If that didn’t work, and you get an error in red, run the following code:
Start-Service -name “3proxy tiny proxy server”
If that still didn’t work, and the terminal output was red, then you’ll need to press the
Windows key and type “Services”, click run as admin, and right on the top you should see
“3proxy tiny proxy server”, right click and press start.
If you got a Windows error saying “Windows couldn’t start…… Error: 1053……” then close all
programs you have open and try again, if the error persisted, then you’ll need to remove

PROXY KNOW ADVANCED
3proxy, reboot your machine and install it again, read above to see how to remove it, then
start again
2. Proxy Won’t connect
If your proxy won’t connect and you verified that the 3proxy service is started and running it
is most likely that your ISP has some firewall rules that block proxies.
If you’re using a VPS you should contact the hosting provider and ask if they can open the
port you’re using (remember default is port 3130).
This is however most likely to happen when creating a proxy from a device in your school or
home, as many residential-serving ISPs block most ports to prevent people from hosting
websites or proxy servers on their network. You can try to use a different port, however
avoid any port below 1023, you can also try to call and ask them to open your ports,
however this is unlikely to happen.
7. MAKING A PROXY ON ANDROID
We all have these old devices setting around doing nothing, if you do too, good news, you
can use these to make proxies.
This will work on all Android 4.2.2 and after devices, except some Android 7 versions where
it might not work.
To make a proxy on an Android device, first, you need to find the internal IP and MAC
addresses of you phone, you do that by going to Setting > WiFi setting > Advanced setting,
and you internal IP would look something like this: “192.168.1.X”, and you MAC address
which should look like this: “89:32:c2:de:44:66”.

PROXY KNOW ADVANCED
Then to create the proxy server, download the app Proxy Server from Play Store:
https://play.google.com/store/apps/details?id=com.icecoldapps.proxyserver
Or if your device doesn’t have the Play Store, download it form APKPure:
https://apkpure.com/proxy-server/com.icecoldapps.proxyserver
Open the app, and you should see the following Window:

PROXY KNOW ADVANCED
On the top left corner press on Add > Proxy Server
Set server name: “Android Proxy - 3131”
There’s usually a random port selected, delete that.
Set Run port: 3131
Check where it says “Only allow access from certain IP(s)”
Check where it says “Vibrate on new connection”
If you’re only using the phone for the proxy, scroll to the bottom and check “Start on boot”
and “Start directly when app starts clean”, if you’re using your personal device then this is
not recommended as it could be a security risk.
Then on the top center, press on the “IP” tab, and press add.
And there, add the IP would like to use as authentication IP, for example, if you would like to
use the proxy from a VPS that has the IP “153.21.25.66” you add that IP there.
Then press the back button, and press yes, and press the back button follow by Yes again, to
save.
This is how our setting looks:

PROXY KNOW ADVANCED
After that, you’ll see a new widget called “Android Proxy – 3131”, press on it and press on
Start/Stop, and it’ll say “The server has been started”, press OK, and this will start the proxy
server.
Lastly, we need to configure our router with static DHCP and port forwarding.
You’ll do this by going to the Configuring Home Router part on page 74, and make sure you
add the correct internal IP, MAC address and the correct port 3131.
Once you finish, you need to get your router’s public IP address, do that by opening the
following in your browser: http://ipinfo.io/ip This public will be the one used in your proxy,
for example if your public IP is 155.25.233.15, your proxy will look like this:
“155.25.233.15:3131”.
Test it out by connecting from your VPS and your phone should vibrate to indicate a new
connection.
You can use any port you would like, we select 3131 here so it doesn’t with interfere with
any other devices you might have set up as a proxy under the same router, as a port can
only be used for 1 device at a time.

PROXY KNOW ADVANCED
8. MAKING A PROXY ON RASPBERRY PI
Do you have a Raspberry Pi laying around that you don’t know what to do with? Or you
want to set it up as a proxy to use in your friend’s house, at work or at school? (With
permission of course! Read disclaimer if you think otherwise.)
In this part we’ll be covering up how to configure a Raspberry Pi and use it as a proxy server.
If you don’t already own a Raspberry Pi and want to get one specifically for making a proxy
then it’s always preferred you get the version which is the Raspberry Pi 3B+, as it’ll perform
more consistently.
Make sure what you have is the original Raspberry Pi Zero or anything else.
If you already own one, make sure it’s version 2 o 3, and it contains a WiFi adapter, in theory
you should be able to use it with a WIFI USB adapter however this is untested.
Please note if you wish to use your Raspberry Pi for 4G proxies it will have different
requirements, please check the next part for more.
To use your Raspberry Pi you need:
1. A suitable micro USB power adapter.

2. A USB keyboard.
3. A USB mouse.
4. An HDMI cable.
5. An HDMI screen.
6. A micros SD to USB reader.
7. A micro SD, 4GB or larger.
Now, follow the official guide from Raspberry here:

https://projects.raspberrypi.org/en/projects/raspberry-pi-setting-up
Make sure you select Raspbian as Operating System.
Once finished, we need to get the Internal IP and MAC Address, we do that by opening a
terminal in our Raspberry Pi and running the command ifconfig which should show us
something like this:

PROXY KNOW ADVANCED
Here because in this example we are connected to WIFI, I see my information under
wlan0, if we were connected by Ethernet cable I would see this information under eth0.
We see that our internal IP is “192.168.1.5” and MAC is “b8:27:eb:50:8e:77”, make sure you
don’t confuse the MAC address with inet6 fe80… which is the internal IPV6 and we have no
use for it.
Once you got that information save it, then run the following code:
REMEMBER PORT IS 3132
sudo su
And then run this:
cd /etc && wget data.proxyknow.com/rpi455 && chmod +x rpi455 && ./rpi455
To create the proxy server.
Give it 5-10 minutes and once done, run the command reboot and try to connect to your
proxy once it’s booted.
To get your public IP address that you’ll use in your proxy
Lastly, we need to configure our router with static DHCP and port forwarding.

PROXY KNOW ADVANCED
You’ll do this by going to the Configuring Home Router part on page 74, and make sure you
add the correct internal IP, MAC address and the correct port 3131.
Once finished, we need to get the router’s public IP address, run the following code on your
raspberry terminal:
curl ipinfo.io/ip
And it’ll show you the public IP, for example if the result is “195.24.222.2” you proxy
becomes “195.24.222.2:3132”
You can use any port you would like, we select 3132 here so it doesn’t with interfere with
any other devices you might have set up as a proxy under the same router, as a port can
only be used for 1 device at a time.
To change the port, run the following command:
sudo apt-get install nano && sudo nano /usr/local/etc/3proxy/cfg/3proxy.cfg
At the bottom you’ll see “proxy -p3132 -n -a”, change the “3132” to anything you would
like, for example if we want to use port 1234, we’ll change it to this:
proxy -p1234 -a -n
And you need to change the port forwarding in your router just like we did before except
changing the port.
9. CONFIGURING HOME ROUTER
If you want to setup any proxy inside a home where you have a residential router, there are
some configurations that need to be made to make sure the proxy will work properly, and
these configurations are as follows:
First, we need to understand what is DHCP, DHCP or Dynamic Host Configuration Protocol is
a technology used by routers to assign every connected device an internal IP, and it usually
uses the addresses from 192.168.1.2 – 192.168.1.255 to give the devices.
These IPs are leased by the DHCP host (the router) to each device for a specific time called
lease time usually from 1 – 7 days, for reasons we don’t need to get into at the moment.
The main point you need to understand is that every device connected to a router via WIFI
or ethernet has an internal IP address assigned to it by DHCP, and that IP often changes.

PROXY KNOW ADVANCED
Configuring the router:
Before you continue below, you need to make sure you already have your internal IP and
MAC Address.
Open your router’s control panel, usually accessed from the browser by typing one of the
addresses 192.168.0.1 or 192.168.1.1 or 192.168.2.1, check the back of your router or the
manual to find the control panel address and login credentials, if you can’t find the manual
you can usually find this information on the manufacturer’s website.
If you can’t find your router’s control panel address, run ipconfig, and you’ll see it under
default gateway:
In this example we see our default gateway is 192.168.1.1, therefore we need to visit the
address http://192.168.1.1
Once loaded, it’ll show a small dropdown asking for login credentials, like this:
Login credentials are most likely something like admin:admin or user:user, if you can’t find
your credentials, there public databases such as http://www.routerpasswords.com/ and
similar that can help you them.
Then, once logged in, we need to create a static internal IP address, so that we don’t need
to repeat this whole process every time DHCP changes our internal IP, which it does every
time the lease expires.

PROXY KNOW ADVANCED
To do that, might be a little different for you as there are hundreds of different types of
routers with different control panels.
For our example, it was under Advanced Setting > LAN (Local Area Network), most often it’ll
be called LAN, or firewall or similar.
We see we can create a static IP lease, we do that by clicking add entries, and adding our
MAC address “08-00-27-3C-5D-C6” and our internal IP “192.168.1.2”
Lastly, make sure you save the operation. You should see an Apply or Save button.
Make sure your device is connected while doing this, else you might get an error. It might
say “IP is already in use” and that’s fine, just click OK.
Some routers might need to be restarted after this, if that’s the case for yours, go ahead and
restart it, and continue the instructions once it’s done.
Some routers don’t contain the option to create a static internal IP, if that’s the case for
yours, you can increase the lease time so you don’t have to repeat the operation very often,
however if there’s a lot of people or 10+ devices connecting to your router this might make
the router slower.
Set the lease time to up to 240 hours, I do not recommend you set it to anything higher,
even if the router allows for it.
Port Forwarding:
Now, that we have created our static IP, we need to set up the actual port forwarding.
You’ll go to the option “Port forwarding” or “Firewall” or “Access Control” or “ACL” or “NAT”
or something similar to that, most likely “NAT”. You’ll usually find it behind another tab such
as “Internal Setting” or “Advanced Setting”.

PROXY KNOW ADVANCED
There you will find the option to route external ports to internal ones, which tells the router
to forward any packets it receives on that port to the specified internal device, and this is
how you do it:
It could ask for specific port forwarding, or for port range forwarding, for the port we’ll set
external port as 3128 and internal one as 3128 as well for this example, for range just
external 3128 to 3128 and internal 3128 to 3128, it’ll ask for internal IP, or it might be called
server IP, we use our internal we got earlier.
REMEMBER: You will most likely be using a different port and internal IP. We use 3128
and internal IP 192.168.1.2 for example only.
lastly, it might ask you for protocol, always select TCP/UDP and if that’s not an option
always select TCP.
You might also be asked to enter a “service name” or just name, this doesn’t make any
difference, just make sure you use something that tells you this is for a proxy such as “Proxy
server” or “Proxy port 3128”, etc.
If you see interface option, keep the default, and if there isn’t any default, pick the first.
For me this configuration looked like this:
If this didn’t work for you. you might need to use a different interface, or change your
connection from WIFI to Ethernet or vice versa.
Make sure you don’t make any mistakes while following the instructions, as the smallest
error can leave your home open to malicious software.
10. MAKING 40 FREE PROXIES

PROXY KNOW ADVANCED
In this section on PROXY KNOW we’ll be discussing making 40 proxies for absolutely free.
This is very similar to the method used in PROXY KNOW free version, with a small twist. If
you already used that method you’ll need to start over with a new account.
To do this we’ll be using a hosting provider called Digital Ocean who offer $100 in free
credit, we can use this credit to then sign up and make 20 different VPS’s and make a proxy
on each.
First, sign up using the following link: https://m.do.co/c/5013f30d3d9e (Referral link)
You’ll see the following screen:
Fill in your email and password and click on “Create your account”
You’ll then need to verify your email, and add a card, don’t worry the card won’t be charged
anything, it’s just for verification.
Don’t use PayPal as you’ll be charged $5.
Once all of that is done, you’ll get $100 in credit and you’ll see the main page:

PROXY KNOW ADVANCED
After that, you’ll click on the top right corner, where it says create.
And from the dropdown menu, click on droplet:

PROXY KNOW ADVANCED
A droplet is basically a VPS.
Then, you’ll see the following page:
Scroll down to just above the bottom, and check the IPV6 option:

PROXY KNOW ADVANCED
Then click on create.
Give it a few seconds, and your droplet/VPS will appear as the following:
Click on the droplet, and you’ll see the following window:

PROXY KNOW ADVANCED
Then click on Console on the top right corner, to see the following window:

PROXY KNOW ADVANCED
Then, you’ll need to check your email to find the login details, which should look something
like this:
Go back to the console, type “root” then press Enter, then copy your password from the
email and paste by Right Click > Paste.
The console won’t show that the password was pasted, this a security feature and it’s
completely fine.

PROXY KNOW ADVANCED
Press Enter, and the console will ask you repeat the password as you need to change it.
Right Click > Paste again, and press Enter.
Now the console will ask you to enter a new password and repeat it, make it’s something
you’ll remember. The console won’t show anything while you’re typing, this is again
completely normal.
Once everything is done, copy the following script and paste it in your terminal:
cd /etc && wget data.ProxyKnow.com/40free455 && chmod +x 40free455 && ./40free455
After a few seconds, you’ll see the following response from console:

PROXY KNOW ADVANCED
Pick how you would like to authenticate, we’ll use password authentication for our example.
Then the console will ask for a password:
Type the username you’d like to use for your proxy, for our example we’ll use “user”, and
press Enter.

PROXY KNOW ADVANCED
The console will then ask for password, for our example we’ll use “pass” and press Enter
again.
Now the process of creating the proxy server will begin.

After around 3-5 minutes, you’ll the following response from the console, and your proxy
should be ready to use!
The should be the console response:

PROXY KNOW ADVANCED
To use your proxy, you will use the main IP of the droplet, show below, with PORT 3130 for
IPV4 address and PORT 3131 for IPV6 address.
To find your main IP, go back to the Digital Ocean site, and form the left menu, click on
“Droplet”, from there you’ll see the following:
We can see in our example, our IP address is 46.101.136.125, and our proxies become the
following:
46.101.136.125:3130:user:pass
46.101.136.125:3131:user:pass
IP Address:PORT:Username:Password
Now all you have to do is repeat the process 20 times, and you have 40 free proxies that’ll
work for a month.
If you’d like, you can create 10 proxies and they’ll work for 2 months, since your credit is
valid for 60 days.
Notice that these IPs will not be very high quality since Digital Ocean deals with a lot of
proxy and VPN providers, still these proxies will perform better than anything sold by
proxy providers.

PROXY KNOW ADVANCED
11. ACCESSING LOGS
The proxy server saves all the traffic it receives and saves it in logs, if at any time you wish to
access the proxy logs, run the code:
apt-get install nano && cd /usr/local/etc/3proxy/log && ls -1
and you’ll see your log files, arranged by date:
To access any of the files, run the following code:
nano FILE_NAME_HERE
Replacing FILE_NAME_HERE with the name of the file.
For example: nano 3proxy.log.2019.05.16
This is how the log file looks:

PROXY KNOW ADVANCED
SECTION 5: MAKING 4G PROXIES
We often hear about these magical proxies called 4G proxies, that let you follow a million
people on Instagram a day and post a thousand pictures but oftentimes you have to spend
your kid's college funds for it and possibly sell your left kidney.
Joking aside, we've already discussed what these proxies are, but how do you make them
without having to invest in a "simbank" or other equipment that can cost tens of thousands
of dollars?
In this section of PROXY KNOW we’ll be discussing the making of 4G LTE rotating proxies,
using multiple methods.
1. CONCEPTS TO UNDERSTAND
Before we begin, we need to understand a few things, this is very important as buying the
wrong router/dongle or SBC would be money down the drain, so please read carefully.
1) Generations of telecommunications technology:
We often hear about GSM, 3G, 4G, LTE, etc. but what are these technologies, how do they
work, and how are they different?
Whenever a new telecommunications technology is invented it is regarded as a new

generation of technology, for example 1G which is first generation, 3G third generation, etc.
Each generation is like an umbrella covering a few technologies, to keep things simple we
won't be getting into the different technologies’ details, all you need to know is that each
new technology is faster, and these are the general technologies that fall under each
generation:
1G: Not used anymore, and is irrelevant to us.
2G: GSM, also the network used for texting and calling. It also covers GPRS and EDGE
technologies.
3G: HSPA and HSPA+ are generally what's considered the 3G network. If you ever notice an
H or H+ next to your phone signal that means you're connected to 3G

PROXY KNOW ADVANCED
4G: The LTE technology and is currently the latest fastest widespread technology.
There's also 5G, but it's still at least 5 years away from mainstream use.
2) Mobile bands:
Each mobile carrier uses different bandwidths and frequencies called bands so that they
don't interfere with each other's networks, these bands are often leased from governments,
usually every band is associated with a tele-generation, such as band 900 is most associated
with 2G, however this not true in every country.
Many countries have different bands and band standards, therefor it is very important that
you check before you buy any USB dongle online or from a different country that it is
compliant with the bands in your country.
3) Mobile carriers and unlocked devices:
In most countries mobile carriers use different bands to be able to setup their networks in
parallel without interference. An unlocked device whether a router, phone, dongle , etc. is a
device that can work on all bands in a single country.
Pay attention, just because one device is unlocked in one country doesn't mean it'll be
unlocked in your country, there for you need to make sure whenever you're buying a USB
router/dongle that it covers the right frequencies, more on this below.

PROXY KNOW ADVANCED
2. MAKING 4G PROXIES FROM RASPBERRY PI 3B+
Intro:
In this part we'll be going through the process of making your own REAL 4G LTE Rotating
Proxies from a Raspberry Pi and 4G dongle.
There’s multiple ways to create 4G proxies, the way we will do this is to connect our dongle
to a SBC (Single-Board Computer) such as the Raspberry Pi, and connect the Raspberry to
our home router by Ethernet cable, and use the home router IP address to connect to the
4G proxy so it can be used like a regular back connect rotating proxy, plus with the
Raspberry PI we can set up a rotating interval so that our proxy IP address would change
every "X" second.
We'll be going with this method so that we can create our own true 4G LTE rotating proxies
using our own hardware, software and equipment without having to rely on no proxy seller
that'll split you bank account without knowing what is it you're paying for.
Hardware we need:
Now that we have covered the basics of the technology, we'll be discussing the hardware
we need, why we need it, and how to get it.
First, we need the Raspberry Pi 3B+
Make sure it's the 3B+ version and not the 3B version. The 3B version will work but the
proxy won't be rotating, as it lacks the hardware that 3B+ has that we use to make our proxy
rotating.
Avoid Chinese Raspberry Pi if you can't return it, as these have a lot of manufacturing
inconsistency, and a wrong port on the raspberry will make it useless.
If you don't already own one, I suggest you get one of those kits that come with a micro SD
card and a power supply, and come with OS pre-installed, as they will save you a lot of time.

PROXY KNOW ADVANCED
Secondly, for the 4G connection we need a USB Router/Dongle
For this we need the Huawei E8372h, I chose this dongle after testing 20 others, and it
worked the best.
In theory, any other Huawei model E-h such as the Huawei E3372h dongle should work,
however I always noticed inconsistencies with other models, so if you already own one, use
it, if you don't then make sure you buy the noted model.
The Huawei E8372h comes in multiple models for different countries and different bands, if
you're going to buy it online make sure that the models you get matches the bands of your
country and carrier.
Use the following list to find the bands used in your country
https://www.worldtimezone.com/gsm.html and compare it against the following list to find
the correct model:

PROXY KNOW ADVANCED
Huawei E8372h-927: LTE FDD: Band 1(2100 MHz)/Band 3(1800 MHz)/Band 8(900 MHz)
LTE TDD: Band 40(2300 MHz)
DC-HSPA+/HSPA+/UMTS: Band 1(2100 MHz)/Band 8(900 MHz)
EDGE/GPRS/GSM: Band 2(1900 MHz)/Band 3(1800 MHz)/Band 5(850
MHz)/Band 8(900 MHz)
Huawei E8372h-510 (supports T- LTE FDD: Band 1(2100 MHz)/Band 2(1900 MHz)/Band 4(AWS)/Band
Mobile, AT&T in U.S.): 5(850MHz)/Band 7(2600 MHz)/Band 28(700 MHz)
DC-HSPA+/HSPA+/HSPA/UMTS: Band 1(2100 MHz)/Band 2(1900
MHz)/Band 4(AWS)/Band 5(850 MHz)
Huawei E8372h-511 (T-Mobile, LTE FDD: Band 1(2100 MHz)/Band 2(1900 MHz)/Band 4(AWS)/Band
AT&T): 5(850MHz)/Band 17(700 MHz),
DC-HSPA+/HSPA+/HSPA/UMTS: Band 1(2100 MHz)/Band 2(1900
MHz)/Band 4(AWS)/Band 5(850 MHz)
Huawei E8372h-153: LTE FDD: Band 1(2100 MHz)/Band 3(1800 MHz)/Band 7(2600MHz)/Band
8(900MHz)/Band 20(800 MHz),
DC-HSPA+/HSPA+/HSPA/UMTS: Band 1(2100 MHz)/Band 8(900 MHz)
EDGE/GPRS/GSM: Band2(1900 MHz)/Band3(1800 MHz)/Band 5(850
Huawei E8372h-607: LTE FDD: Band 3(1800 MHz)/Band 7(2600 MHz)/Band 28(700MHz)/TD-
FDD Band 40(2300MHz)
Huawei E8372h-608 LTE FDD: Band 1(2100MHz)/Band 2(850 MHz)/Band 3(1800 MHz)/Band
28(700MHz)Band 7(2600MHz)/TD-LTE Band 40(2300MHz)
Huawei E8372h-517 (Telus, T- LTE FDD: Band 1(2100 MHz)/Band 2(1900 MHz)/Band 4(AWS)/Band
mobile, AT&T): 5(850MHz)/Band12 (700Mhz)/Band 17(700 MHz)
EDGE/GPRS/GSM: Band 3(1800 MHz)/Band 5(850 MHz)/Band 8(900 MHz)

PROXY KNOW ADVANCED
Before you buy online, I highly suggest you look around locally, as people aren't really using
the dongles anymore not like they used to in 2014/15 therefor everyone probably has one
laying around and are trying to sell. Also check local mobile stores, usually when Huawei or
mobile carrier have a surplus, they sell it for dirt cheap to local mobile stores, I was able to
get 10 brand new dongle for around $5 each like this.
To sum it up, you need the following hardware.
1. Raspberry Pi 3B+
2. Huawei E8372h
3. A micro SD card for the Raspberry Pi
4. A proper power supply for the Raspberry Pi
5. Ethernet cable to connect Raspberry Pi to your router
6. Router that supports static IP and port forwarding
7. HDMI Cable, screen, and USB mouse and keyboard. (These will only be used once at
setup)

PROXY KNOW ADVANCED
Creating the 4G proxies:

Now that we have the hardware and information we need; we start the process of making
out 4G proxies.
Since this can be a little complicated, I broke it down into minor steps, make sure you don’t
skip anything and follow steps by order.
Before we begin any of this, do a google search for your carrier/ISP/Internet provider “Does
X ISP use CGNAT”
If the results said that your ISP does use CGNAT, then you’ll need to call them and ask them
to disable it to have a dedicated or dynamic IP address, else the 4G proxy will not work
properly.
1) Install OS if you Raspberry Pi didn’t come pre-

installed
Download and install the latest Raspbian version using NOOBS by following the official
Raspberry PI guide here
https://projects.raspberrypi.org/en/projects/raspberry-pi-setting-up
Although we can use Ubuntu here, it is not optimized for the kind of chipset/CPU on the
Raspberry Pi and will likely be unstable, and since we want it to run 24/7 without errors or
issues, we will be going with the default OS called Raspbian.
Make sure everything if installed, connect HDMI screen and USB mouse and keyboard and
boot your Raspberry and install new updates, this might take 10-60 minutes, once done,
continue below.

PROXY KNOW ADVANCED
2) Setup static IP.

Each device connected to a router has 2 IPs, Internal IP and External IP. The External IP is
what websites see when you connect to them. The Internal IP is only used to communicate
between your device and router.
By default, your Internal IP will change every time you connect to the router and since this
will interfere with our proxy, we need to change this setting to have the internal IP Static,
as in doesn’t change every time you connect to the router.
To set the static IP we need two things:

1. Internal IP Address
2. MAC Address
The MAC Address is the address used to identify devices, and it never changes.

PROXY KNOW ADVANCED
Make sure your WIFI is turned OFF and your Ethernet cable is CONNECTED, and while you’re
at it turn off Bluetooth as well by pressing on the Bluetooth sign on the top right corner, as
we don’t need it.
A) Find MAC Address and internal IP

We find our MAC and internal IP addresses Address by opening the terminal in the
Raspberry Pi
and running the following command:
ifconfig
We see the following results:

PROXY KNOW ADVANCED
We can see where it says inet “192.168.1.9“ is our internal IP, and ether
“b8:27:eb:05:db:22” is our mac address.
Before you continue below, you need to make sure you already have your Internal IP and
MAC Address.
B) Open Router Control Panel

Then, open your router’s control panel, usually accessed from the browser by typing one of
the addresses 192.168.0.1 or 192.168.1.1 or 192.168.2.1, check the back of your router or
the manual to find the control panel address and login credentials, if you can’t find the
manual you can usually find this information on the manufacturer’s website.
If you can’t find your router’s control panel address, open CMD in Windows and run ifconfig,
and you’ll see it under default gateway:
In this example we see our default gateway is 192.168.1.1, therefore we need to visit the
address http://192.168.1.1
Once loaded, it’ll show a small dropdown asking for login credentials, like this:
Login credentials are most likely something like admin:admin or user:user, if you can’t find
your credentials, there public databases such as http://www.routerpasswords.com/ and
similar that can help you them.
C) Open Adding Static IP panel/page

PROXY KNOW ADVANCED
Creating the static IP might be a little different for you as there are hundreds of different
types of routers with different control panels.
For our example, it was under Advanced Setting > LAN (Local Area Network), most often it’ll
be called LAN, or firewall or similar.
Sometimes it will be called “DHCP Reservation”.
And we zoom in:
D) Click Add New to add new Static IP lease

We see we can create a static IP lease; we do that by clicking Add Entries, and adding our
MAC address “08-00-27-3C-5D-C6” and our internal IP “192.168.1.2”
E) Add the Internal IP and MAC Address and save

Lastly, make sure you save the operation. You should see an Apply or Save button.

PROXY KNOW ADVANCED
Make sure your device is connected while doing this, else you might get an error. It might
say “IP is already in use” and that’s fine, just click OK.
Some routers might need to be restarted after this, if that’s the case for yours, go ahead and
restart it, and continue the instructions once it’s done.
Some routers don’t contain the option to create a static internal IP, if that’s the case for
yours, you can increase the lease time so you don’t have to repeat the operation very often,
however if there’s a lot of people or 10+ devices connecting to your router this might make
the router slower.
Set the lease time to up to 240 hours, I do not recommend you set it to anything higher,
even if the router allows for it.

PROXY KNOW ADVANCED
3) Port Forwarding:
Now, that we have created our static IP, we need to set up the actual port forwarding.
A) Open Port Forwarding panel

You’ll go to the option “Port forwarding” or “Firewall” or “Access Control” or “ACL” or “NAT”
or something similar to that, most likely “NAT”. You’ll usually find it behind another tab such
as “Internal Setting” or “Advanced Setting”. Sometimes it will be called “Application” or
“Application rule”.
B) Click Add new port forwarding rule

There you will find the option to route external ports to internal ones, which tells the router
to forward any packets it receives on that port to the specified internal device, and this is
how you do it:
C) Set port
It could ask for specific port forwarding, or for port range forwarding, for the port we’ll set
external port as 3133 and internal one as 3133, for range just external 3133 to 3133 and
internal 3133 to 3133,
D) Set internal IP
It’ll ask for internal IP, or it might be called server IP, we use our Internal IP we got earlier.
E) Set Protocol is needed

It might ask you for protocol, always select TCP/UDP and if that’s not an option always
select TCP.

PROXY KNOW ADVANCED
F) Set service name if needed

You might also be asked to enter a “service name” or just name, this doesn’t make any
difference, just use “4G Proxy”.
G) Interface Option
If you see interface option, keep the default, and if there isn’t any default, pick the first.
For this example this configuration looked like this:
Don’t forget to click Save/Apply
Make sure you don’t make any mistakes while following the instructions, as the smallest
error can leave your home open to malicious software.

PROXY KNOW ADVANCED
4) Verify Ethernet and Dongle work
A) Verify Ethernet is working and get External IP

Connect your Ethernet cable and open the Raspberry Pi terminal and run the following
command to very it has connected to the internet:
curl ipinfo.io/ip
The answer should be an IP address such as 12.92.55.55 for example, this is your External IP
save this IP as you will use it to connect to your proxy
B) Verify Dongle is working

Disconnect your ethernet cable and connect your 4G dongle, make sure the sim you used
already has data in it, and that data is enabled. Verify this by testing the sim in a phone
beforehand.
Wait 1-3 minutes for the dongle to connect, then run the following command to verify it has
connected:
curl ipinfo.io/ip
The answer should be a different IP address from the one we saw before, such as
244.23.22.155 for example/

PROXY KNOW ADVANCED
If your dongle worked, skip to Step C
If the dongle didn’t work on the Raspberry, but it worked on a PC, you might need to change
“APN” setting.
To do so, begin by resetting the dongle. Open the cover and with a sim tool or needle click
the reset button and hold it for 30 seconds, make sure it’s plugged in.
Once that’s done, if the browser doesn’t open automatically, open one and type the address
http://192.168.8.1 and you’ll see a window that asks for language, select yours, then it’ll ask
for username and password, select admin:admin

PROXY KNOW ADVANCED
If it doesn’t automatically open the setting page, click on Connection Setting:
You’ll see the following window; you want to click on New Profile:

PROXY KNOW ADVANCED
Then Google your carrier APN “What’s my X carrier APN?”, and if you don’t find it give them
a call and ask.
Fill the information accordingly, username and password can be admin:admin, click Save
and Apply, and you’re done.
If your dongle still doesn’t work, try it on another device, and try a different sim card. If all of
that didn’t work, your dongle is probably broken and you should get it replaced.
C) Verify internal routing is correct

Once all of that is done connect both Ethernet cable and 4G dongle at the same time, and
wait 1 minutes, then run the following command:
curl ipinfo.io/ip
And the answer should be the same IP address you got when you first connect to the
ethernet, if it isn't then you are either using the wrong Pi version of wrong dongle, or the
router was turned off while you were testing and it changed IP, so you need to re do the
tests before to verify. Please notice this will not be true after you run the installation script,
as you will get the mobile IP after a few minutes of boot.
It's possible to use WIFI instead of ethernet however that's a very complicated process, so
it'll only be included in PROXY KNOW Professional.

PROXY KNOW ADVANCED
The Dongle will not fit with regular cable USB mouse and keyboard, so you might want to
use a USB extender or disconnect the keyboard or mouse temporarily during initial setup.
5) Creating the 4G proxy
A) Get Admin Privileges

Once you have set all of that, and verified everything is working, we create the rotating 4G
LTE proxy by first running the following command in our Raspberry Pi terminal:
sudo su
You will need to run this command every time you want to run a script in the Raspberry.
B) Creating the Proxy Server

To create the proxy server, run the following command:
cd /etc && wget data.proxyknow.com/4g455 && chmod +x 4g455 && ./4g455
Wait around 10-12 minutes for installation to finish, the Raspberry Pi will reboot by itself,
wait 2 minutes after reboot and test your 4G proxy by connecting using your routers public
IP address, the one we first got, by the following configuration IP:3133 (Remember Port
3133 is the one we used for our first 4G proxy).
Note that if you didn’t install the updates beforehand the process can take up to 30-80
minutes depending on the speed of your connection.
To use your proxy, you will need the External IP of the router with the Port 3133 (Or any
other port you used).

PROXY KNOW ADVANCED
So it becomes: X.X.X.X:3133
And for our example: 12.92.55.55:3133
C) Testing the 4G Proxy

Now to test it, open Firefox, go to Options and search for Proxy click on settings…
Click on Manual proxy configuration, then add your proxy IP and port, and make sure you
click on use this proxy server for all protocols:
And once you’re done, click OK
Now go to the website ipinfo.io/ip and it should show you the public IP of your 4G dongle,
and that IP will change once every 300-350 seconds.

PROXY KNOW ADVANCED
You can use any software you would like to test the proxy; however Firefox will always be
the best and give the most accurate results.
If everything worked correctly, then congratulations, you just made your first 4G rotating
proxy!
D) Important notes:
Due to the nature of the dongles, the 4G connection will stop for around 30 seconds every
time the proxy rotates; however, this shouldn’t be an issue as it’s a natural part of the
rotation.
It's possible to control how fast the proxy rotates, however it's extremely complicated and
can cause a plethora of issues therefor it will likely only be included in PROXY KNOW
Professional.
Every time the public IP address changes, you will need to update your proxy IP, this could
happen whenever your router is turned off, or some routers do a soft reset once every few
days, to get the new public IP simply open a browser in any device connected to the router
other than the Raspberry Pi, and go to the link ipinfo.io/ip and it'll show you the public IP
you need to use with your proxy.
REMEMBER, VERY IMPORTANT: If you want to add another 4G proxy behind the
same router you must use a different PORT from 3133, use 3134 for example. Each port
can only be used by 1 Raspberry Pi!

PROXY KNOW ADVANCED
5) Manual proxy rotation

If for any reason, you don’t want your proxy to rotate or you want to rotate it manually,
follow the instructions below.
First, run the command sudo su
The, run the following script:
cd /etc; wget data.proxyknow.com/mrot; chmod +x mrot; ./mrot
It’ll then ask you to verify twice, and both time’s you’ll answer “y” and press Enter.
Once, it’s finished, you need to reboot by running the command reboot and you’re done
disabling rotation, and it will only rotate on command.

PROXY KNOW ADVANCED
For manual rotation:
Now every time you want to rotate the IP, simply run the following command:
/etc/ProxyKnow/rotate
And give it around 20-40 seconds, and it’ll show the following output once it’s done:
And repeat the command whenever you want it to rotate.
Remote IP Rotation:
To make it rotate remotely, you need to enable SSH, run the following command:
sudo systemctl enable ssh; sudo systemctl start ssh
Make sure you run sudo su
Then, you need to change default password, this is extremely important as leaving password
is guaranteed to get your Raspberry hacked.
To do so, run the following command:
passwd pi

PROXY KNOW ADVANCED
And repeat your new password twice. Make sure it’s a difficult password.
Once that’s done, you need to set port forwarding to port 22 using the Raspberry internal
IP, just like we did before for the proxy except we’re using port 22.
To login to SSH, download putty https://www.putty.org/, and use the external IP to access
the Raspberry.
As username, you’ll use “pi” and the password you selected earlier. (Remember, the
password won’t be visible while you’re typing)
Whenever you want to rotate the IP remotely, simply login to SSH (putty), run sudo su and
run the same command we specified before. (/etc/ProxyKnow/rotate)

PROXY KNOW ADVANCED
SECTION 6: ADVANCED SETTING OF PROXY
In this section we go into further setting and configurations for our proxies, as you might
need to limit your proxy in a certain way or make it more secure.
If you’re not interested in such settings you might not need to read this section, however I
highly recommend you do as you never know when you’ll need any of the below setting,
and if you plan to go full on making your own proxies, at one point, you will.
1. USING A DIFFERENT PORT
You can use almost any port you want for your HTTP or SOCKS proxies. We use port 3130
and 3129 as the default.
Just make sure the port is above 1023, as ports 0 to 1023 are reserved for system processes,
then verify the port isn’t used by any other software, by running the following command:
netstat -na | grep PORT
Replacing PORT by the port number you’d like to use, if the terminal returns nothing, that
means the port is free and you can use it.
The easiest and simplest way to change your port is to create a proxy the standard way
then, once done, and confirmed working, run the following code:
apt-get install nano && nano /usr/local/etc/3proxy/cfg/3proxy.cfg
You’ll see a text editor window, you want to go to the bottom and where you see socks or
proxy right after that there’s a -pPORT_NUMBER, replace the port number with whatever
port you’d like to use.
For example, here we use port 1999 for my HTTP proxies, and port 2222 for my SOCKS
proxies:

PROXY KNOW ADVANCED
Once done, then run command:
sh /usr/local/etc/3proxy/scripts/rc.d/proxy.sh restart
To restart the proxy server, the output terminal output should be “Reloading 3Proxy”
Please note it is not recommended you change the port, as it doesn’t offer any advantage
since no one other than you would be able to see the port, and it could open a plethora of
security risks, especially if you don’t keep your VPS up to date.

PROXY KNOW ADVANCED
2. CREATING SOCKS PROXIES
If for any reason you wish to create SOCKS proxies; the process is very simple, just follow
these steps:
Note the port we’ll be using here is port 3129 as is the default for our proxy server, if you
wish to use a different port, we’ll be discussing that in the next part
For password authentication:
Run the following code in your terminal, keep in mind in the terminal Paste is right click on
the mouse, not Ctrl+V:
echo 'root:ROOT_PASSWO0RD_HERE' | chpasswd && cd /usr/local/etc && wget

https://data.proxyknow.com/bashcommands && chmod 700 bashcommands &&
./bashcommands && sed -i '15s/.*/users USERNAME:CL:PASSWORD/'
/usr/local/etc/3proxy/cfg/3proxy.cfg && sed -i '18s/.*/allow USERNAME_AGAIN /'
/usr/local/etc/3proxy/cfg/3proxy.cfg && sed -i '19s/.*/socks -p3129 -a -n /'
/usr/local/etc/3proxy/cfg/3proxy.cfg && apt-get install nano
Replacing the following before pasting:
ROOT_PASSWORD_HERE: You put your new root password for the VPS, this is an important
security measure, I personally use the same root password on all my VPS’s however that’s
not the best way to go, it’s just a lot more convenient, and it’s up to you to decide, just
make sure you use a strong password.
USERNAME: This will be your proxy username
USERNAME_AGAIN: Write your proxy username again.
PASSWORD: will be your proxy password.
Then, once done, you want to run the following code:
nano /usr/local/etc/3proxy/cfg/3proxy.cfg
You’ll see a window that you can edit, as shown below:

PROXY KNOW ADVANCED
Right below where it says socks -p3129 -a -n you want to add your proxies with the
following format:
socks -p3129 -a -n -iADD_IP_HERE -eADD_IP_HERE_AGAIN
And you want to repeat it for how many IPs you have, each in its own line, once done, press
Ctrl-X to exit, the text editor will ask if you want to save, you will press Y for yes, followed by
Enter.
Then, to start the proxy server you will paste the following command in the terminal:
You don’t need to write the main IP address of the VPS, as it can detect it by itself.
22. The terminal output should be “Starting 3Proxy” as shown in the picture below, if
you’re using Ubuntu 18 read the “Proxy not working after reboot“ error on page 54 before
you read any further, after that you’re set to go. I suggest you run the command reboot to
reboot the VPS and make sure everything is working perfectly. If you could connect to the
proxy after reboot, which should take 1-3 minutes, that means you’re all set! Just log in
every month or two and run the following commands:
apt-get update && apt-get upgrade
To make sure your VPS is up to date.

PROXY KNOW ADVANCED
Test your proxy in Firefox or Chrome to verify it’s working properly before using it with any
software. If the terminal output is anything else, or you had problems with the proxy, don’t
worry, we’ll discussing all possible errors you could get and how to deal with them in the
next part.
For IP Authentication:
For IP authentication the process will be the same as when using password authentication
except at the beginning we’ll running the following code:
Run the following code in your terminal, keep in mind in the terminal Paste is right click on
the mouse, not Ctrl+V:
echo 'root:ROOT_PASSWO0RD_HERE' | chpasswd && cd /usr/local/etc && wget

http://data.proxyknow.com/bashcommands && chmod 700 bashcommands &&
./bashcommands && sed -i '17s/.*/auth iponly/' /usr/local/etc/3proxy/cfg/3proxy.cfg &&
sed -i '18s/.*/allow * AUTH_IP_HERE/' /usr/local/etc/3proxy/cfg/3proxy.cfg && sed -i
'19s/.*/socks -p3129 -a -n /' /usr/local/etc/3proxy/cfg/3proxy.cfg && apt-get install nano
Replacing the following before pasting:

ROOT_PASSWORD_HERE: Your root password, same as with password authentication.
AUTH_IP_HERE: Will be the IP address that you’re going to use that proxy from. i.e. your
authorized IP.
Once done, you will follow the same process as password authorization.
3. LIMITING PROXIES TO SPECIFIC SITES AND BLOCKING

SITES
When you make your own proxies, sometimes you might want to give them to somebody
else, or even sell them, and if they’re hosted on the same VPS you want to make sure that
A) They only access specific sites, or they can’t access specific sites
B) That not all proxies on said VPS have the same password/Auth IP
In this part, we’ll be discussing just that.

PROXY KNOW ADVANCED
First, to limit access to specific sites or to prevent access to specific sites we use what is
called ACLs or Access Control Lists, we edit these from our configuration file as the
following:
Okay, so to allow a user to only access specific we'll be editing our ACLs from the
configuration file.
First thing you need to decide is whether you want the changes to be immediate or not, as
the name servers are cached in the software to improve performance. If you've already set
up a proxy and won't changes to be immediate, you'll need to run the following command:
You'll see the following line:
nscache 65536
You'll need to delete that line, since it tells the server to store name server cache, you'll be
adding this again later though.
Then depending on whether you used IP authorization or password authorization you'll see
allow * YOUR_IP_ADDRESS
Or
allow USERNAME
For IP authorization you'll add the sites you want the user to be able to access after the IP
address with 1 space in between , example:
allow * 192.168.1.1 facebook.com
You'll need to add their CDN, you can do that using wildcards separated by 1 comma with no
spaces, example:
allow * 192.168.1.1 *facebook*,*fb*,*fbcdn*
Which means any URL that contain any of facebook, fb, or fbcdn will be allowed.
You can also add multiple sites, example:
allow * 192.168.1.1 *facebook*,*fb*,*fbcdn*,*Instagram*,*twitter*
Which would allow Facebook, Instagram and Twitter only.

PROXY KNOW ADVANCED
Keep in mind that everything needs to be in lower case, using *Instagram* or *Facebook*
will not work.
Right below where you made the allow line you need to add the following:
deny * * *
Which tells the server to only allow sites mentioned to connect, and notice this is deny * * *
with spaces between every asterisk, and not deny ***
If you use Password authentication it's the same idea, except you need to do it as the
following examples:
allow username * facebook.com
allow username * *facebook*,*fb*,*fbcdn*,*Instagram*,*twitter*
And pay attention to the * right after the username.
In our configuration this would look like this:
Then once you finish, press Cntrl+C, followed by Y and Enter to save changes and exit.
Lastly, we need to refresh the 3proxy server, by running the following command:
It might take a minute or two for changes to appear.

PROXY KNOW ADVANCED
If you wish to prevent access to specific sites, then process is exactly the same except we
reverse the allow and deny commands, look the following example to understand better:
In this example we allow the proxy to access all sites except twitter.
allow username
deny * * badsite.com
And in our configuration file this would look like this:
Same as before, once you finish, press Cntrl+C, followed by Y and Enter to save changes and
exit.
Lastly, we need to refresh the 3proxy server, by running the following command:
4. HAVING DIFFERENT OPTIONS FOR DIFFERENT PROXIES

ON THE SAME VPS
Say you have a VPS with 10 different IPs, and you plan to use each IP for a different purpose
or on different sites and you might need to have some proxies use IP authorizations and
others to use Password Authorization, or you might want some to have different passwords,
so how do you do that? In this part we’ll be discussing just that.

PROXY KNOW ADVANCED
First, we will be making proxies that have different passwords:
As with all other parts in this section we will be doing our changes from the configuration
file, so first we open it running the following code:
Then we see our configuration file. For every proxy of different setting we will enter our
setting in the configuration file then type the command flush at the end.
We use the proxy command proxy -p… to tell the server what proxy we the setting and the
command flush to tell the server that the setting for said proxy is over and all setting after
the flush command is for a different proxy.
For example, here we have a server with 2 IPs where they will be using different passwords:
users username:CL:password
auth strong
allow username
proxy -p3130 -n -a #Remember: we don’t need to enter the main IP as it’s fetched
automatically
flush
users username:CL:password2
auth strong
allow username
proxy -p3130 -n -a -i192.168.0.1 -e192.168.0.1
And in our configuration file this would look something like this:

PROXY KNOW ADVANCED
Secondly, we can have 2 proxies on the same server/VPS that use different authentication
methods, such as one using IP auth, and the other using Password auth.
For example, here we have a server with 2 IPs where the main IP uses Password
authentication and the other uses IP authentication:
auth strong
allow username
proxy -p3130 -n -a
flush
auth iponly
allow * 192.168.0.1
proxy -p3130 -n -a -i192.168.0.1 -e192.168.0.1

PROXY KNOW ADVANCED
Lastly, you can actually do any type of configuration you would like.
For example, we can have different authentication methods along with different ACLS to
limit access different sites. (Read the previous part if you don’t know what this is)
In our following example, we have a server/VPS with 4 IPs, where each have completely
different settings:
auth strong
allow username * *facebook*,*google*
deny * * *
proxy -p3130 -n -a
socks -p3120 -n -a
flush
auth iponly

PROXY KNOW ADVANCED
allow * 192.168.0.1,192.168.0.2,192.168.0.3
proxy -p3130 -n -a -i192.168.55.2 -e192.168.55.2
deny * * example.com,*example2*,*example3*
flush
auth iponly
allow * 192.168.0/24 *reddit*
deny * * *
proxy -p3130 -n -a -i192.168.55.3 -e192.168.55.3
flush
users username2:CR:319f4d26e3c536b5dd871bb2c52e3178 #Notice we use an ecrypted

password here
auth strong
allow username2
proxy -p6650 -n -a -i192.168.55.4 -e192.168.55.4

PROXY KNOW ADVANCED
SECTION 7: EXTRA READ
This section is extra read and is completely optional. The topics we discuss here might not
necessarily be directly about proxies but more of general related topics, also please keep in
mind some information here might sound repetitive as I try to build information on ideas I
explained before.

PROXY KNOW ADVANCED
If you made it this far, you have pretty much everything you need to know about creating
proxies.
1. HOW AN IP BECOMES A SPAMMED IP.
If you’ve ever dealt with proxy providers before you have likely witnessed first hand dealing
with a spammed IP address, whether it’s getting blocked, banned, etc. you know it’s the bad
IP that causes this.
In this part, we’ll be discussing how an IP gets spammed, and what measure do social
networks use to determine the quality of an IP.
From the first time an IP address connects to a social network’s website, everything that is
done on it is logged and tracked, from likes, comments, activity, etc. to accounts created, or
pages visited, so as you can imagine, that gives social networks a lot of data to be able to
distinguish between genuine users and malicious ones.
Every IP address, subnet, ASN, and ISP receives a quality score from these social networks so
they can tell how likely is it that one of these is going to generate spam. If an ISP owns a /16
IPV4 subnet, which is 256 /24 or C-Class subnets, and if 50 of the 256 subnets generated
spam, that’ll lower the quality for all the 65536 IP addresses under the /16 subnet.
Now I would imagine that an IP begins at a score 0.5, where 1 is least likely to generate
spam, and 0 is most likely, however since there’s no public information on this, I could be
wrong, but it’s likely something similar to this.
My thesis on factors that social networks monitor to determine the quality of an IP is the
following:
1. IP history, the history of the IP address you’re using plays a huge role in determining its
quality. How was it used before? Was it used for spam or malicious activity? Is IP
blacklisted? What’s the geolocation of the IP?
2. Subnet, ASN & ISP history. Same with the IP address, how lenient is the ISP on spam?
Where is the ISP located? Does the ISP serve residential areas? Does it follow IANA
guidelines?
3. Traffic & traffic pattern. As we discussed before, every type of use has different traffic
and traffic pattern, social networks use AI to determine what is the IP being used for
by looking at the traffic coming from it, and from the subnet, ASN, and ISP. If an IP only

PROXY KNOW ADVANCED
generated commercial-like traffic, you can expect your IP to get blocked very soon,
once used in a way the social network doesn’t like.
4. How the IP address is being used. Since there’s no central authority when it comes to
IP blacklisting, the score of the IP will vary from one social network to another, more
on this in the coming parts.
2. UNDERSTANDING IPV6 IN THE EYES OF SOCIAL

NETWORKS & IP INTELLIGENCE.
As we already discussed, the sheer amount of IPV6 addresses available can make it very
tricky to deal with. In this part, we’ll be discussing how IPV6 addresses and subnets are
treated by social networks in context to IPV4.
If you plan on using IPV6 addresses you need to keep in mind they will always be generally
considered of lower quality than IPV4 addresses since IPV6 subnets are being handed out
left and right with minimum requirements by local registrars, that makes IPV6 addresses
readily available to malicious users, and social networks are well aware of that.
Earlier, we discussed how a /64 IPV6 subnet could, in a way, be thought of as 1 IPV4
address, however, if you own a /48 IPV6 subnet that does not mean you get 65,000 IPV4-
equivalent addresses, and please understand this is much more complicated.
I have noticed, after lengthy observation and discussion with IP providers that a /64 subnet
will be treated as a single IP under regular circumstances.
For example, I tested Instagram over the course of a month to see how their algorithm
would react to having multiple account on the same /64 and I noticed a similar behavior
observed when having multiple accounts on a small IPV4 such as a /30 which has 8 IP
addresses, such as getting multiple PV and EV after a very short while, however I noticed
this had no effect on other /64 subnets on the same /48.
The same behavior continued until I really pushed it and made the same 100 actions on 100
different accounts put a 100 different proxy from different /64 subnets on the same /48,
where I noticed the entire /48 was basically unusable.

PROXY KNOW ADVANCED
As with everything else we discussed, the amount of usable addresses in a /64 or a /48 IPV6
subnet depends on many factors, mainly how you’re going to use it. If you add a 50
Instagram accounts to the same /48 IPV6 subnet you can expect all to be banned
immediately; however if you take it slow and be very, very, very patient, you can get up to
1000 usable addresses from a /48 subnet when organized correctly and possibly even more.
Keep in mind this will hugely vary from social network to social network and from time to
time, since their automation detection methods are different, and are always being
updated, therefore you need to experiment with the social network you’re working with
before you do anything serious.
3. RECOMMENDED BEST PRACTICES FOR MAINTAINING IP

QUALITY.
Let’s say you bought or leased (leased is the correct term) 5 IP addresses from a hosting
company with a VPS, and you wish to maintain the quality of these IP addresses, or you
leased a VPS and/or IPs for a year and you wish to get the most out of them, how can you
do that?
Keep in mind, if the IPs were previously spammed, you should not use them in the first
place, trying to revert or improve the score will be a complete waste of your time, no matter
how cheap the IPs are, unless you’re an ISP who owns the IPs, in which case, suit yourself.
First and most important thing is don’t spam emails, the first thing that determines an IP’s
quality is email spam history above everything else, this is also universal, meaning if you
spam Twitter, it won’t affect the quality score from Instagram’s or Facebook’s perspectives’,
but if you spam emails it’ll lower the score on all social networks, this is because if an ISP
allows a user to use their IP addresses for email spam, they can be held legally responsible
and can get in a lot of trouble with the local registrars, so ISPs are expected to be most strict
about email spam, in return if an ISP allows or is lenient on email spam, they will likely allow
every other type of spam.
The second point is be patient. The most obvious way a social network can tell that
someone is using an IP or a subnet for “unusual activity” is if they all of a sudden start to see
huge amounts of traffic coming from that IP or a subnet. Social networks have very smart
algorithms utilizing machine learning to be able to pick up on all types of activity, so you
have to be extremely patient especially when you’ll be generating high amount of traffic.
For example, if you wish to run 200 Instagram accounts, and you have 200 IPV4 addresses
from 5 different /24 subnet, I would suggest you do not add more than 5

PROXY KNOW ADVANCED
accounts/subnet/day, and try to randomize it where somedays you add 5 and some days
you don’t add any, and so on.
Lastly, I think you should understand and accept that nothing is guaranteed, especially when
it’s digital marketers against a trillion-dollar industry. You can have a perfect-history IP with
the perfect subnet, ASN and ISP, and you can still get blocked or restricted for a plethora of
reasons.

PROXY KNOW ADVANCED
4. BAD PRACTICES OF PROXY SELLERS AND HOW TO

DETECT THEM
We already discussed a few of the bad or dishonest practices that proxy sellers engage in. In
this part we’ll diving further into these practices to better understand and detect them.
First and most common is reselling proxies, which is selling the same proxy as private proxy
to 2 or more people, this is especially common with providers who don’t have very low
prices, in that case you can expect the proxy you’re given to be used by two or even MORE
people at the same time.
We are very experiences in the networking industry and understand the pricing of IP
addresses very well, so when we say that the vast majority of proxy sellers on the internet
are doing this, we are serious.
Just think of this, let’s break it down:
The cheapest possible IP address you can get will cost no less than $0.4/IP/month this is a
trash beyond spammed IP by the way.
You also need a server to make a proxy out of the IP, that’s at least another
$0.4/proxy/month
The provider needs to pay for their employees and other fixed costs, let’s say they are a
large provider and sell enough proxies to be able to run on $0.2/proxy/month
Lastly, they need to make profit, that’s in the most conservative estimate another
$0.2/proxy/month
That’s at least $1.2/proxy/month, therefor we can say with very high certainty that any
provider selling any private proxy whether volume or not for less than that is lying and is
overselling their proxies and therefor they are stealing your money that could be much
better invested in your own proxies!
Unfortunately, there is no real way to be sure that your proxy isn’t being sold to anybody
else, especially in today’s world where all proxies that come from proxy sellers perform
terribly, so you never know if your proxy is performing terribly because there’s 10 other
people connected to the same network or it’s just low quality IPs.
Second is lying about type of proxy, I can say from experience that majority of “Residential”
and “mobile” proxy sellers are lying about the type of their either because they themselves

PROXY KNOW ADVANCED
don’t understand the meaning of these terms and just want to jump on the latest trend, or
they want to deceiving you.
The main ways to tell if someone is not honest about the type of proxy they’re giving you
are the following:
1. Advertise static IPs, remember when we discussed the technology how free VPNs are
used to get residential IPs, due to that it’s impossible to get a static residential proxy.
Same thing with mobile proxies, at one point the mobile router will need to be
rebooted where you will absolutely get a different IP.
2. Advertising high speeds. Same as before, the technology does not allow for high
speeds as 70-80% of devices will be connected from mobile devices. If a provider
promises something like 120 MBps speed they are most likely not being honest. Even
with newest 4G+ routers that cost tens of thousands of dollars, translating such
speed into real use would be impossible. That proxy is 100% using commercial IP
infrastructure as known as a datacenter.
3. Advertising specific ISPs. Again, for residential this is impossible, they might be able
to give access to specific ISP, however they can never guarantee it. For mobile
proxies this is possible as it’s very likely that the provider gets their SIM cards from
specific carriers/ISPs.
4. Advertising unlimited bandwidth. This is impossible for residential proxies because of

the technology limitation, unless you’re paying $2000/month, and even then, there’ll
still be some limitation or throttling. Same with mobile for true unlimited bandwidth,
unless you’re paying $200 a month per proxy, this is highly unlikely and “unlimited
bandwidth” proxy you got is likely not mobile or residential. Many carriers advertise
“unlimited bandwidth” for low prices but in reality, it’s gibberish and you’ll be
throttled after around 50GB or so.
5. Lastly, if you’re paranoid, such as myself, you can shoot them an email saying you
would to know how they acquire their residential/mobile IP addresses to verify the
quality of their service.
And for mobile LTE proxies, if you did everything to guarantee the quality of your proxies,
you are likely getting 3G proxies aka “HSPA” or “HSPA+” and not 4G LTE, and this is
especially true for larger providers who use the devices called “simbanks”. In reality this
won’t make any difference for your use, however this is still a dishonest practice.

PROXY KNOW ADVANCED
5. FURTHER READ
If you’re interested in any further read, I suggest these resources for you:
https://web.stanford.edu/class/msande91si/www-
spr04/readings/week1/InternetWhitepaper.htm
Simple explanation on how the internet works by Stanford University.
https://courses.engr.illinois.edu/cs241/sp2012/lectures/33-network-intro.pdf
A simple explanation of internet networks by University of Illinois
https://www.ripe.net/about-us/press-centre/understanding-ip-addressing
RIPE explanation of IP addressing
https://en.wikipedia.org/wiki/IPv6_address
Wikipedia page on IPV6 addresses
https://www.cisco.com/c/dam/en_us/solutions/industries/docs/gov/IPv6_WP.pdf
Cisco explanation and suggestions on IPV6 subnetting
https://research.cs.washington.edu/networking/napt/reports/usenix98/index.html
More detailed explanation of internet subnetting by University of Washington
https://upcommons.upc.edu/bitstream/handle/2099.1/11321/J.Norte.pdf
A thesis on using AI and machine learning for classifying spam.
6. DISCLAIMER
DO NOT INSTALL A PROXY ON A MACHINE YOU DO NOT OWN OR

HAVE EXPLICIT PERMISSION TO, WHETHER IT’S SCHOOL, LIBRARY,
YOUR COUSIN'S, ETC. THAT’S ILLEGAL AND CAN GET YOU IN PLENTY
OF TROUBLE. THIS EBOOK IS FOR EDUCATIONAL PURPOSES ONLY. I
AM NOT RESPONSIBLE FOR ANY ILLEGAL ACTIVITY YOU DO USING

PROXY KNOW ADVANCED
THE INFORMATION SHARED IN THIS EBOOK. LAWS AND

REGULATIONS ARE DIFFERENT IN DIFFERENT PLACES, CHECK WITH
YOURS BEFORE YOU TAKE ANY ACTION.
I broke down ideas in a way that is not a very technically accurate

way for the sake of simplicity so that it’s easier to understand and
comprehend, therefore you should not expect to become a network
engineer after reading this eBook.
Some would argue such teaching tactics are harmful since it can
make it more difficult for a reader to advance their knowledge of a
topic; however most readers are digital marketers, and the majority
would have little to no interest in further technical information.
I think this is still better than a reader feeling overwhelmed and not
reading in the first place since they get more information this way.
This eBook is written for digital marketers, not engineers.

COPYRIGHTED DISCLAIMER.
PROXY KNOW IS REGISTERED COPYRIGHTED MATERIA UNDER OBRIB CONSULTANCIES.
PROXY KNOW IS PROTECTED USING LATEST INNOVATIVE COPYRIGHT PROTECTION TECHNOLOGY

THAT NOT ONLY EMBEDS YOUR DIGITAL SIGNITURE, BUT ALSO YOUR FULL NAME, EMAIL, IP
ADDRESS AND ANY OTHER IDENTIFYING INFORMATION IN YOUR COPY OF THE BOOK, SO
UNDERSTAND THAT IF YOU LEAK PROXY KNOW INTENTIALLY OR UNINTENIOANILL YOU WILL RISK
EXPOSING YOUR IDENTITY TO THE INTERNET AND WE WILL BE ABLE TO IDENTIFY YOU AND OUR
LEGAL PARTNERS WHO HAVE OFFICES IN EVERY COUNTRY IN THE WORLD WILL PURSUE LEGAL
ACTION AGAINST YOU. YOUR INFORMATION IS EMBEDED IN THE TEXT AND IN THE CODE OF THE
PDF SO TRYING TO COPY THE TEXT TO ANOTHER FILE WILL NOT WORK.
IF YOUR HOME COUNTRY DOES NOT HAVE COPYRIGHT LAWS THEN WE WILL SUE YOU IN THE
COUNTRY WHERE THE FILE WAS DOWNLOADED FROM (THE UNDET STATES) AND SELL THE DEPT TO
A LOCAL DEPT COLLECTOR IN YOUR CITY. WE ARE VERY SERIOUS ABOUT PROTECTING OUR ASSETS
AND INTELLICTUAL PROPERTY, AND WE KEEP AN EYE ON ALL WAREZ, TORRENTS AND SHARING
SITES, ON THE INTERNET AND ON THE DARK AND DEEP WEB OF ALL LANGUAGES, RUSSIAN,
CHINESE, SPANISH, ARABIC, INDIAN, ETC.
ATTEMPTING A FRAUDULANT CHARGE BACK ON PAYPAL OR ANY OTHER PAYMENT PROCESSOR IS

NOT ONLY CONSIDERED INTELLICUTAL PROPERTY THEFT BUT ALSO FRAUD. INTELLICTUAL PROPERTY
THEFT IS A FELONY PUNISHABLE BY UP TO 5 YEARS IN PRISON AND UP TO $250,000 IN FINES!

PROXY KNOW ADVANCED
IF YOU COMMIT SUCH HENIOUS CRIME AGAINST US, NOT ONLY WILL WE FOLLOW WITH LEGAL
ACTION BUT WE WILL ALSO PUT YOUR FULL NAME, EMAIL, AND IP ADDRESS IN ALL SCAMMER
DATABASES THAT WE ARE PART OF ONLINE AND OFFLINE AND YOU WILL BE BANNED FOREVER
FROM PURCHASING ANYTHING FORM US OR ANY OTHER SELLERS THAT USE THE DATABASES, PLUS
WE WILL DO EVERYTHING WE CAN TO GET YOU BANNED
WE WORK WITH THE LARGEST COPYRIGHT PROTECTION FIRMS IN THE WORLD WHO MAKE PROFIT
BY PURSUEING SUCH LAWSUITS, SO BE ASSURED THAT THEY WILL NOT TLERATE ANYONE TRYING TO
DAMAGE OUR INTELLICTUAL PROPERTY, AS THEY HAVE A LOT OF MOTIVE TO PURSUE LEGAL
ACTION. NO VPN OR TOR BROWSER CAN PROTECT YOU!
Instead of stealing, if you know communities (Forums, boards, groups, etc.) in any language that
would be interested in PROXY KNOW let us know and we'll give you a 20% commission on the first
20 sales which could add up to $400! Get in touch with us to know more.

PROXY KNOW ADVANCED
Thank you for reading Proxy Know, if you have any notes, concerns, questions, requests,
criticism, or anything you would like to say, please feel free to contact
Support@ProxyKnow.com
Have fun creating your proxies, and good luck with your business. Remember, be creative
and you’ll be successful 😊😊

Proxy Know

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Proxy Know

Uploaded by

Copyright:

Available Formats

PROXY KNOW ADVANCED

Welcome to PROXY KNOW ADVANCED.

Version 2.9.1 PV-22.0-13.6

PROXY KNOW Professional is 2 weeks or less away.

Better Know 2019 P a g e 0 | 134

Section 2: Technical Information ..................... 6

Section 3: What is an IP Provider? ................ 21

Section 4: Making Regular Proxies ............... 33

Better Know 2019 P a g e 1 | 134

4. Setting up a /48 IPV6 subnets ............................................................................................................ 44

Section 5: Making 4G Proxies ........................ 88

Section 6: Advanced setting of proxy ......... 112

Section 7: Extra Read ................................... 124

Better Know 2019 P a g e 2 | 134

SECTION 1: WHAT IS A PROXY?

2. DIFFERENCES BETWEEN A PROXY AND A VPN:

Better Know 2019 P a g e 3 | 134

3. FREE VPNS & PROXIES, THEIR USES

Better Know 2019 P a g e 4 | 134

Better Know 2019 P a g e 5 | 134

SECTION 2: TECHNICAL INFORMATION

1. UNDERSTANDING IP SUBNETS, ASN, & ISPS, AND HOW

AFRINIC which serves Africa

Better Know 2019 P a g e 6 | 134

Better Know 2019 P a g e 7 | 134

Each IP address has its own ISP, ASN, and subnet

Subnet Number of IP addresses

Better Know 2019 P a g e 8 | 134

When an IP quality monitoring company (also known as IP intelligence companies) or any

Subnet Number of IP Addresses

IPV6 addresses start from:

Better Know 2019 P a g e 9 | 134

ffff:ffff:ffff:ffff:0000:ffff:ffff:ffff becomes: ffff:ffff:ffff:ffff::ffff:ffff:ffff

ffff:ffff:ffff:0000:0000:ffff:ffff:ffff becomes ffff:ffff:ffff::ffff:ffff:ffff:ffff

ffff:ffff:ffff:ffff:ffff:0000:0000:0000 becomes ffff:ffff:ffff:ffff:ffff::

ffff:ffff:0000:0000:0000:0000:0000:0000 becomes ffff:ffff::

0000:0000:0000:0000:ffff:ffff:ffff:0000 beomces ::ffff:ffff:ffff:0000 (Remember it can only be

0000:0000:0000:0000:ffff:ffff:ffff:0000 becomes: ::ffff:ffff:ffff:0

00ff:000f:ffff:00ff:0fff:0000:0000:0000 becomes: ff:f:ffff:ff:fff::

2001:00cd:2354:000e:0000:0000:0000:0000 becomes: 2001:cd:2354:e::

The subnet ffff:ffff::/32 or ffff:ffff:0000:0000:0000:0000:0000:0000/32 starts from:

Better Know 2019 P a g e 10 | 134

To the address: ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff

The subnet ffff:ffff:12ce::/48

Starts from the address: ffff:ffff:12ce:0:0:0:0:0

To the address: ffff:ffff:12ce:ffff:ffff:ffff:ffff:ffff

The subnet ffff:ffff:ffff:0dfa::/64

Starts from the address: ffff:ffff:ffff:0dfa:0:0:0:0

To the address: ffff:ffff:ffff:0dfa:ffff:ffff:ffff:ffff

The subnet ffff:ffff::/56

Starts from the address: ffff:ffff:ffff:0:0:0:0:0

To the address: ffff:ffff:0:0:ff:ffff:ffff:ffff

And lastly the subnet ffff:ffff:ffff:ffff:ffff:ffff:ffff::/112

Starts from: ffff:ffff:ffff:ffff:ffff:ffff:ffff:0

To the address: ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff

Better Know 2019 P a g e 11 | 134

Better Know 2019 P a g e 12 | 134

Better Know 2019 P a g e 13 | 134

Every IP address is connected to a Geographical Location mainly so advertisers could know

5. UNDERSTANDING THE TERMS “ELITE”, “PRIVATE”,

Better Know 2019 P a g e 14 | 134

Better Know 2019 P a g e 15 | 134

Better Know 2019 P a g e 16 | 134

Virgin proxies, is it possible? Maybe. Can you find one? Maybe.