IP Ranges Per Country

We publish the official IPv4 allocation blocks for every ISO 3166-1 territory — 244 countries and regions — as plain-text CIDR lists. Pull /Ranges/US.txt for the United States, /Ranges/NL.txt for the Netherlands, /Ranges/JP.txt for Japan, and so on. The full mapping uses the standard two-letter codes.

What this data is

Each file contains every IPv4 block that the regional internet registries (ARIN, RIPE NCC, APNIC, LACNIC, AFRINIC) have allocated to networks geolocated in that country. Format is one CIDR per line:

86.48.240.0/20
91.222.132.0/22
103.71.56.0/24
103.101.215.0/24
103.104.244.0/22

Source data is reconciled with MaxMind GeoLite2 and refreshed periodically. The lists are conservative: only ranges that all three sources agree on for a given country are included.

What you can do with it

• Filter your proxy list by country — intersect any of our protocol lists with a country's CIDR file to get only exits in that jurisdiction.
• Geo-block at the firewall — allow or deny inbound traffic per country without paying for commercial GeoIP feeds.
• Geo-target ad campaigns or scrapes — verify that your campaigns hit the right country, or scrape geo-locked content with a matching exit.
• Threat intelligence — quickly classify suspicious traffic by source country for triage.

Country pages

We maintain dedicated landing pages for the most-requested countries with direct downloads, proxy use cases, and cross-links:

Other territories

Every ISO code from AD (Andorra) through ZW (Zimbabwe) has a file. Pattern is /Ranges/CC.txt. If you need a comma-separated combined file or a JSON dump, the maintainer can prepare one.

Pairing ranges with proxies

The classic workflow: grep -F -f Ranges/DE.txt http.txt won't quite work because CIDR isn't a string match, but a quick Python or netaddr-style script intersects the two in under a second. See the protocol comparison for which list to start from.