Wikipedia:Open proxies noticeboard/Guide to checking open proxies: Difference between revisions
Content deleted Content added
m →How to confirm open proxies: Typo fixing, replaced: adress → address using AWB |
|||
Line 6:
# Identify the access point. You are hopefully going to use it yourself. Google the IP address. Do [[rDNS]] and [[WHOIS]] lookups. Be creative if you have to, like look at neighbouring IP address. While you're there check if it looks dynamic. The first question to ask is whether it's a web proxy or an HTTP proxy.
## Does it look like a web server? Keywords to look for in search results are PHP-proxy, CGI-proxy, Glype, and NPH, as well as ___domain names. Do the rDNS and WHOIS suggest it's a dedicated server or hosting range? Open the IP address in your browser. Is there a holding page, or even a web proxy there? Find which sites are hosted on it using rDNS and Google. Nmap will almost always say that port 80 is open on webservers, but this does not necessarily mean there is an open proxy there.
## Or does it look like an [[SOCKS#Comparison_to_HTTP_proxying|HTTP/SOCKS proxy]]? Such proxy IPs are always associated with a [[TCP and UDP port|port number]]. The most usual ones are 80, 1080, 3128, 8000, 8080, 8888, but it could be any number up to 65535. These ports are usually displayed in search results following the IP address and a colon, for example 111.282.3.1:3128. They are, in so far as they obfuscate e.g. the user's original IP
## Or is it another type of anonymiser? They are beyond this article's scope, but the same principles apply. For examples see [[:Category:Anonymity networks]].
# Connect to the proxy. If it's a web proxy go to its page in a browser. If it's an HTTP proxy change the network settings in your browser options.
|