<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>VPS on Jack Taylor</title><link>https://jacktaylor.tech/tags/vps/</link><description>Recent content in VPS on Jack Taylor</description><generator>Hugo</generator><language>en</language><managingEditor>jack@jacktaylor.tech (Jack Taylor)</managingEditor><webMaster>jack@jacktaylor.tech (Jack Taylor)</webMaster><lastBuildDate>Sat, 02 Apr 2022 11:45:00 +0900</lastBuildDate><atom:link href="https://jacktaylor.tech/tags/vps/index.xml" rel="self" type="application/rss+xml"/><item><title>Proxy OWASP ZAP through a VPS</title><link>https://jacktaylor.tech/2022/04/proxy-owasp-zap-through-a-vps/</link><pubDate>Sat, 02 Apr 2022 11:45:00 +0900</pubDate><author>jack@jacktaylor.tech (Jack Taylor)</author><guid>https://jacktaylor.tech/2022/04/proxy-owasp-zap-through-a-vps/</guid><description>&lt;p&gt;If you do any kind of penetration testing or bug bounty hunting from your home
PC, then as a necessity you will be sending malicious-looking traffic to your
target. If your target happens to be protected by Akamai or CloudFlare, and you
don&amp;rsquo;t take any special precautions, then unfortunate things may happen.
Unfortunate, as in your home IP gets &lt;a href="https://www.doyler.net/security-not-included/akamai-internet-banned"&gt;blocked from half the sites on the
internet&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;To avoid this, you need to make your web traffic look like it came from a
different IP address than it actually did. This means using some kind of proxy
server. There are a few different ways you can do this, but my preferred way is
to use a virtual private server (VPS) rented out from a cloud provider.&lt;/p&gt;</description></item></channel></rss>