cidr-ip-ranges-by-country
CIDR IP ranges by country for geolocation, firewall rules, network filtering, and cybersecurity – updated hourly for IPv4 and IPv6. Curated by EbraSha – Abdal Security Group
CIDR IP ranges by country
A curated set of IPv4 and IPv6 CIDR blocks organized by country, updated hourly for geolocation and firewall use.
Coverage and update cadence
The repository collects CIDR IP ranges for both IPv4 and IPv6 for all countries and keeps them in one place. Every country gets its own directory containing two files: an IPv4 range file named with the suffix ipv4-Hackers.Zone.txt and an IPv6 range file named with ipv6-Hackers.Zone.txt. The README states the whole repository is regenerated every hour, so the lists track changes in allocated address space without manual edits. Because the data is plain text with no build step, it can be consumed directly by scripts, firewalls or geolocation lookups.
Intended uses
The project frames the ranges as useful for network management, geolocation services, firewall rules, network filtering and cybersecurity work. A network operator can, for example, pull the IPv4 file for a specific country and feed it into firewall allow or deny lists, or use the IPv6 file for similar policy decisions. The README presents the dataset as comprehensive and up to date rather than as a one off snapshot, which is what the hourly refresh is meant to support. No aggregation logic or tooling is included; the value is the curated, country keyed lists themselves.
Localization and maintenance
The README is translated into more than ten languages, including English, Chinese, Russian, Spanish, Japanese, Persian, Arabic, Turkish, German and Hindi, with translation files kept under a docs/i18n directory. The repository is maintained by Ebrahim Shafiei, who goes by EbraSha and is associated with the Abdal Security Group, and contact is offered through email and Telegram as well as GitHub or GitLab issues. The combination of frequent updates and multilingual documentation suggests the dataset is intended for a broad operational audience rather than a single team.
Editorial conclusion
The repository carries no code or build pipeline and is consumed as two text files per country, refreshed hourly and maintained by Ebrahim Shafiei (EbraSha).
Community notes