<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: ipwhoisnet</title>
    <description>The latest articles on DEV Community by ipwhoisnet (@ipwhoisnet).</description>
    <link>https://dev.to/ipwhoisnet</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4253916%2Fc8f53bac-bc34-4ddf-9baf-e2ab5e1ca0df.png</url>
      <title>DEV Community: ipwhoisnet</title>
      <link>https://dev.to/ipwhoisnet</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ipwhoisnet"/>
    <language>en</language>
    <item>
      <title>How we tell a residential proxy from a real home connection</title>
      <dc:creator>ipwhoisnet</dc:creator>
      <pubDate>Thu, 19 Nov 2026 13:29:18 +0000</pubDate>
      <link>https://dev.to/ipwhoisnet/how-we-tell-a-residential-proxy-from-a-real-home-connection-1d0f</link>
      <guid>https://dev.to/ipwhoisnet/how-we-tell-a-residential-proxy-from-a-real-home-connection-1d0f</guid>
      <description>&lt;p&gt;For a while our server logs made no sense. On a normal day we'd get over thirty thousand page views from more than twenty-one thousand different IP addresses. Every address made one or two requests and never came back. Look any of them up and you'd find exactly what you'd expect from a real person: a home broadband line in Brazil, a mobile network in Pakistan, a cable ISP in Mexico.&lt;/p&gt;

&lt;p&gt;None of them were people. It was one scraper renting a residential proxy pool, and every request went out through somebody's home router or phone.&lt;/p&gt;

&lt;p&gt;I run an IP lookup site, so "is this address a real household or a proxy?" is a question we get asked every day, and one we had to answer for ourselves. The short version: the address alone usually can't tell you. Here is what can, roughly in the order we check it.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Where the address claims to be versus where it can physically be
&lt;/h2&gt;

&lt;p&gt;Light in fibre covers about 100 km per millisecond of round trip, give or take. So if a "residential IP in Zagreb" answers a ping from a probe in Frankfurt in 2 ms, it isn't in Zagreb. It is sitting in a data centre a few hundred kilometres from Frankfurt, wearing a Zagreb label.&lt;/p&gt;

&lt;p&gt;We use that rule a lot, but carefully. RTT can rule a city out; it can almost never prove one. 3 ms can't tell a suburb from the city next to it, and we learned that the hard way when an automated pass "confirmed" a batch of suburbs as their neighbouring big city and we had to undo it. Now a row only moves when the ping makes the claimed place impossible, not merely unlikely.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Geofeeds that are too pretty
&lt;/h2&gt;

&lt;p&gt;Network operators can publish a geofeed: a CSV that says which of their prefixes sits in which city. Honest ones are boring. A cable company's feed lists the towns it actually serves, in one country.&lt;/p&gt;

&lt;p&gt;The fake ones look like a geography quiz. One feed we rejected mapped hundreds of /24s from a single block to small places in Denmark, Cambodia, Albania and Nigeria. Nobody has a broadband footprint like that. Somebody selling proxies does.&lt;/p&gt;

&lt;p&gt;Even feeds that look sane get checked against the regional registries before we trust a country change. Out of 332 geofeed country claims that passed our other filters in one round, the registry agreed with exactly one. That number still surprises me.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Two databases agreeing is not proof
&lt;/h2&gt;

&lt;p&gt;It's tempting to think that if two well-known IP databases put an address in the same country, it must be right. We tried that on 3,373 rows. When we pinged a sample, about one in five of the agreed locations was physically impossible. Both sources had fallen back to the same thing: the headquarters address in the registry record. A big carrier's HQ city ends up on addresses it uses on another continent.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Reverse DNS still says a lot
&lt;/h2&gt;

&lt;p&gt;Real ISPs name their customer addresses, and they're boringly consistent about it. A home DSL line in Slovenia comes back as something like &lt;code&gt;bsn-61-98-230.dynamic.siol.net&lt;/code&gt;. Pools of proxies on rented hosting space often have no reverse DNS at all, or names that clearly belong to a data centre while the geolocation claims a living room.&lt;/p&gt;

&lt;p&gt;It's not proof on its own. Some small ISPs never set PTR records. But a "residential" range with no PTRs, announced by a hosting network, is a strong hint.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Who announces it, and who it's registered to
&lt;/h2&gt;

&lt;p&gt;The organisation in the registry record and the network that actually announces the range in BGP should usually be the same, or obviously related. When a block registered to a home broadband company is announced by a small hosting AS, it's often been leased out, and leased ranges are where a lot of proxy and VPN capacity lives. We keep over 110,000 VPN and proxy ranges flagged in the database, and leased blocks are one of the most common places they turn up.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. The part network data can't see
&lt;/h2&gt;

&lt;p&gt;Here's the honest bit. The worst residential proxies are real home connections: an SDK in a free app or a "bandwidth sharing" program on someone's PC routes other people's traffic through their line. Location, ASN and reverse DNS are all genuinely residential, because the line is. No lookup will flag that address, and anyone who claims otherwise is guessing.&lt;/p&gt;

&lt;p&gt;What gives those away is behaviour, not the address. The scraper I started with gave itself away in the request headers. Every request claimed to be desktop Chrome, yet none sent the &lt;code&gt;Accept-Language&lt;/code&gt; header every real Chrome sends, and the Chrome client hints were missing or contradicted the user agent. A later fleet used ten fixed user agents with the same time zone and screen size on every request, spread over a long list of addresses. One address does nothing suspicious. Ten thousand addresses that share a fingerprint do.&lt;/p&gt;

&lt;p&gt;So our labels try to stay honest: an address on a home ISP gets the ISP label, even when we suspect it's being rented out, and the proxy flag goes on ranges where the network evidence holds up.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'd check, if you're deciding about one address
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Does the location survive a ping from somewhere nearby?&lt;/li&gt;
&lt;li&gt;Does the reverse DNS look like that ISP's customers, or like a server?&lt;/li&gt;
&lt;li&gt;Is the announcing network the one the range is registered to?&lt;/li&gt;
&lt;li&gt;Is the address part of a block that's been carved into many countries?&lt;/li&gt;
&lt;li&gt;And if you have the traffic: do the headers look like the browser they claim to be?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You can run the first four on any address with our &lt;a href="https://ipwhois.net/ip-lookup" rel="noopener noreferrer"&gt;IP lookup&lt;/a&gt;. It shows the registry owner, the announcing network, reverse DNS and the network type side by side. The fifth one needs your own logs, and in my experience that's where the interesting answers are.&lt;/p&gt;

</description>
      <category>networking</category>
      <category>security</category>
      <category>webdev</category>
      <category>privacy</category>
    </item>
    <item>
      <title>Make fail2ban report its bans to a community blacklist</title>
      <dc:creator>ipwhoisnet</dc:creator>
      <pubDate>Thu, 19 Nov 2026 13:29:10 +0000</pubDate>
      <link>https://dev.to/ipwhoisnet/make-fail2ban-report-its-bans-to-a-community-blacklist-5ka</link>
      <guid>https://dev.to/ipwhoisnet/make-fail2ban-report-its-bans-to-a-community-blacklist-5ka</guid>
      <description>&lt;p&gt;Check the auth log on any server with port 22 open and it's always the same story: endless login attempts from IPs that have clearly done this before. fail2ban bans them, the bantime runs out, and that's it. Nothing learned, nothing shared.&lt;/p&gt;

&lt;p&gt;A while ago I started sending those bans to a shared blacklist instead of letting them disappear. I use the one on bl.ipwhois.net, mostly because it needs no signup and no API key. You get 500 requests a day per source IP, which is plenty for a normal server.&lt;/p&gt;

&lt;p&gt;Checking an address looks like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="s2"&gt;"https://bl.ipwhois.net/api/check?ip=203.0.113.5"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="nl"&gt;"ip"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="s2"&gt;"203.0.113.5"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="nl"&gt;"listed"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="kc"&gt;false&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="nl"&gt;"message"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="s2"&gt;"Not found in IPWhois Blacklist"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="nl"&gt;"rate_limit"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="nl"&gt;"limit"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="mi"&gt;500&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="nl"&gt;"remaining"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="mi"&gt;499&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Reporting is a POST to the same API. To make fail2ban do it on every ban, drop this into &lt;code&gt;/etc/fail2ban/action.d/ipwhois-report.conf&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight ini"&gt;&lt;code&gt;&lt;span class="k"&gt;[Definition]&lt;/span&gt;
&lt;span class="na"&gt;actionstart&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt;
&lt;span class="na"&gt;actionstop&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt;
&lt;span class="na"&gt;actioncheck&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt;
&lt;span class="na"&gt;actionban&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;curl&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;s&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="no"&gt;X&lt;/span&gt; &lt;span class="no"&gt;POST&lt;/span&gt; &lt;span class="s2"&gt;"https://bl.ipwhois.net/api/report"&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;d&lt;/span&gt; &lt;span class="s2"&gt;"ip=&amp;lt;ip&amp;gt;"&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;d&lt;/span&gt; &lt;span class="s2"&gt;"type=&amp;lt;name&amp;gt;"&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;d&lt;/span&gt; &lt;span class="s2"&gt;"comment=fail2ban &amp;lt;name&amp;gt; ban"&lt;/span&gt;
&lt;span class="na"&gt;actionunban&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;and add the action to whatever jails you want in &lt;code&gt;jail.local&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight ini"&gt;&lt;code&gt;&lt;span class="k"&gt;[sshd]&lt;/span&gt;
&lt;span class="na"&gt;enabled&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;
&lt;span class="na"&gt;action&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;iptables&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;multiport&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="n"&gt;sshd&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;port&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"22"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
         &lt;span class="na"&gt;ipwhois-report[name&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="n"&gt;sshd&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Reload fail2ban and that's it. The &lt;code&gt;&amp;lt;ip&amp;gt;&lt;/code&gt; and &lt;code&gt;&amp;lt;name&amp;gt;&lt;/code&gt; tags get filled in by fail2ban itself, so the jail name ends up as the threat type.&lt;/p&gt;

&lt;p&gt;The other direction is more useful. There's a plain text feed of everything the community reported (only direct reports, fail2ban setups like this one, and honeypots, they don't mix in other people's feeds). One IPv4 per line, refreshed every 30 minutes. I load it into an ipset once an hour:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl -s https://bl.ipwhois.net/feed.txt &lt;span class="o"&gt;|&lt;/span&gt; grep -v &lt;span class="s1"&gt;'^#'&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; /tmp/ipwhois_bl.txt
ipset create ipwhois_bl hash:ip -exist
ipset flush ipwhois_bl
&lt;span class="k"&gt;while&lt;/span&gt; &lt;span class="nb"&gt;read&lt;/span&gt; -r ip&lt;span class="o"&gt;;&lt;/span&gt; &lt;span class="k"&gt;do&lt;/span&gt; ipset add ipwhois_bl &lt;span class="s2"&gt;"$ip"&lt;/span&gt; -exist&lt;span class="o"&gt;;&lt;/span&gt; &lt;span class="k"&gt;done&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;&lt;/span&gt; /tmp/ipwhois_bl.txt
iptables -I INPUT -m &lt;span class="nb"&gt;set&lt;/span&gt; --match-set ipwhois_bl src -j DROP
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;It's around a thousand entries, the whole refresh takes under a second.&lt;/p&gt;

&lt;p&gt;Two warnings from experience. Whitelist your own IPs above the DROP rule, because sooner or later you'll be connecting from a network somebody reported. And run the rule with &lt;code&gt;-j LOG&lt;/code&gt; instead of &lt;code&gt;DROP&lt;/code&gt; for a day first, just to see what it would have caught.&lt;/p&gt;

&lt;p&gt;One more habit that stuck: when a banned IP keeps coming back, I run it through an &lt;a href="https://ipwhois.net/ip-lookup" rel="noopener noreferrer"&gt;IP lookup&lt;/a&gt; to see who actually owns it. Half the time it's some cheap VPS provider, and a quick &lt;a href="https://ipwhois.net" rel="noopener noreferrer"&gt;IP whois&lt;/a&gt; check turns up the abuse contact. Forwarding a chunk of auth.log to that address works more often than you'd think, especially with smaller hosters.&lt;/p&gt;

</description>
      <category>linux</category>
      <category>security</category>
      <category>devops</category>
      <category>tutorial</category>
    </item>
  </channel>
</rss>
