Unique blocked IPv4 addresses
PUBLIC INTELLIGENCE / IPV4 ONLY
Clarity at the
network edge.
Understand what you block.
Explore the global footprint of Data-Shield, from country-level coverage to the addresses protecting your infrastructure.
Published snapshot/21 Oct 2026, 00:05 UTC
Checked 21 Oct 2026, 00:05 UTC
Unique blocked IPv4 addresses
IPv4 addresses covered in both profiles
With addresses in Critical
THE GLOBAL PICTURE
A world of signals.
Every country in view.
Explore blocked addresses and whitelist coverage.
Hover, tap or select a country to see its numbers.
STANDARD / BLOCKED IPV42D COUNTRY ATLAS
Blocked IPv4Low → High
Unique IPv4 addresses, not connection or attack counts. Colors use a logarithmic scale.
Geolocation: DB-IP 2026-10 · Map: Natural Earth
COUNTRY RANKINGS
The Top 50.
Standard countries ranked by unique blocked IPv4 addresses.
| Rank | Country | Blocked IPv4 | Whitelisted IPv4 | Blocked share |
|---|---|---|---|---|
| 01 | USUnited States | 25,464 | 409,960 | |
| 02 | CNPeople's Republic of China | 8,293 | 566,296 | |
| 03 | DEGermany | 5,012 | 30,717 | |
| 04 | BEBelgium | 4,175 | 4,040 | |
| 05 | SGSingapore | 3,883 | 36,483 | |
| 06 | NLNetherlands | 3,801 | 49,894 | |
| 07 | GBUnited Kingdom | 3,556 | 37,536 | |
| 08 | INIndia | 2,521 | 48,941 | |
| 09 | KRSouth Korea | 2,517 | 8,146 | |
| 10 | BRBrazil | 2,304 | 68,432 | |
| 11 | FRFrance | 2,115 | 23,434 | |
| 12 | RURussia | 2,051 | 184,657 | |
| 13 | JPJapan | 1,861 | 22,826 | |
| 14 | HKHong Kong | 1,743 | 28,703 | |
| 15 | CACanada | 1,691 | 1,067,935 | |
| 16 | UAUkraine | 1,676 | 2,845 | |
| 17 | IDIndonesia | 1,421 | 209,202 | |
| 18 | ARArgentina | 1,346 | 9,536 | |
| 19 | TWTaiwan | 1,332 | 5,266 | |
| 20 | PKPakistan | 1,162 | 3,584 | |
| 21 | VNVietnam | 1,118 | 1,788 | |
| 22 | MYMalaysia | 1,087 | 4,927 | |
| 23 | UZUzbekistan | 819 | 864 | |
| 24 | AUAustralia | 722 | 22,301 | |
| 25 | FIFinland | 624 | 5,457 | |
| 26 | SESweden | 608 | 6,371 | |
| 27 | TRTurkey | 594 | 8,644 | |
| 28 | PLPoland | 583 | 325,866 | |
| 29 | IRIran | 581 | 0 | |
| 30 | ITItaly | 544 | 8,342 | |
| 31 | BDBangladesh | 499 | 4,353 | |
| 32 | MXMexico | 473 | 6,148 | |
| 33 | ESSpain | 438 | 9,340 | |
| 34 | AEUnited Arab Emirates | 399 | 2,109 | |
| 35 | COColombia | 393 | 5,917 | |
| 36 | CLChile | 384 | 5,120 | |
| 37 | THThailand | 374 | 5,631 | |
| 38 | ZASouth Africa | 339 | 8,824 | |
| 39 | PHPhilippines | 267 | 6,917 | |
| 40 | CHSwitzerland | 246 | 3,733 | |
| 41 | BGBulgaria | 244 | 3,329 | |
| 42 | EGEgypt | 236 | 1,319 | |
| 43 | KEKenya | 235 | 3,585 | |
| 44 | ILIsrael | 216 | 6,929 | |
| 45 | KZKazakhstan | 198 | 2,164 | |
| 46 | VEVenezuela | 188 | 0 | |
| 47 | ADAndorra | 165 | 256 | |
| 48 | LTLithuania | 163 | 513 | |
| 49 | ECEcuador | 143 | 2,044 | |
| 50 | PEPeru | 123 | 2,561 |
Unknown country is excluded from the ranking and included in totals.
TWO PROFILES. A DELIBERATE CHOICE.
Choose your
protection policy.
Both profiles apply the shared whitelist. Critical adds broader blocking coverage. Each file is complete and can be used on its own.
Compare and download ↗In both lists94,998
Standard only0
Critical only9,854
Unique across both104,852
Shared whitelist exceptions take precedence in both profiles. Whitelist coverage counts unique IPv4 addresses, with overlapping ranges counted once.
READY FOR YOUR NETWORK
Two lists. Five delivery paths.
Plain text. One IPv4 address per line.
Numerically sorted. No duplicates. No IPv6.
Standard
IPV4 / TXTA focused inbound filtering policy with reviewed exceptions.
prod_data-shield_ipv4_blocklist.txt
94,998 addresses1.28 MiB
Verify SHA-256
51447828205fa88bbc64174ec574613806489b5f1a47302c18550d38df8927feCritical
IPV4 / TXTA broader inbound blocking policy for stricter environments.
prod_critical_data-shield_ipv4_blocklist.txt
104,852 addresses1.42 MiB
Verify SHA-256
3a02829a30ae4a9663a05b5910b492d2eb49c7569bc93c631fda699e9114d066Choose your mirror
STANDARD / CRITICAL| Delivery | Standard | Critical | Publication path |
|---|---|---|---|
| GitHub | Standard ↓ | Critical ↓ | Primary publication |
| GitLab | Standard ↓ | Critical ↓ | Direct publication and mirror origin |
| Codeberg | Standard ↓ | Critical ↓ | Mirrored through GitLab |
| Bitbucket | Standard ↓ | Critical ↓ | Mirrored through GitLab |
| CDN | Standard ↓ | Critical ↓ | Cached GitHub delivery |
GitHub and GitLab publish both files together. Codeberg and Bitbucket are mirrored through GitLab. The CDN caches GitHub content; mirrors and caches can lag behind the source.
CHECK BEFORE YOU REPORT
Where does this IP stand?
Check an IPv4 address or CIDR against both published lists. The lookup happens in your browser. The address you enter is never sent in a lookup request.
TRANSPARENCY BY DESIGN
Know what the numbers mean.
Published, then measured.
Statistics refer to one published GitHub commit. Both files are checked against their expected SHA-256 hashes before the site is built.
Freshness you can inspect.
Blocklists are generated every two hours. The site updates after publication and refreshes automatically every hour. Open pages check for updates every minute.
Exceptions stay private.
Whitelist statistics count unique IPv4 addresses covered by the policy, including CIDR ranges. Only aggregate country statistics are public. Internal rules and reasons stay private.
Should I use Standard or Critical?
Start with the profile that fits your inbound filtering policy. Both profiles apply the shared whitelist; Critical adds broader blocking coverage. Both are complete files. Review changes and retain a working local copy before applying updates.
Does a country with more blocked IPs mean it is more dangerous?
No. Rankings are counts in these lists, not population-adjusted or network-size-adjusted risk scores. Hosting infrastructure and address allocation affect the distribution. Geolocation is approximate and does not establish the origin or nationality of an attacker.
What does whitelisted mean here?
The shared whitelist applies to both Standard and Critical. Statistics count unique IPv4 addresses covered by exceptions for the selected profile, with overlapping ranges counted once. It is not the number of benign addresses on the Internet, nor the number of allowed connections. An address absent from a blocklist is not necessarily explicitly whitelisted.
How should I use the blocklists?
Use them for incoming traffic filtering on firewalls, gateways or WAFs. Do not apply them blindly as a blanket outgoing traffic block. SysWarden can consume Data-Shield lists for kernel-level filtering. Follow the integration guides for FortiOS, UniFi, Palo Alto, OPNsense and Stormshield.
What happens if an update fails?
The last verified website snapshot remains available. The page displays its generation time and warns when it is stale. Deployments fail closed if list contents, counts or hashes disagree. Hosting caches and GitHub Pages deployment time can delay visibility of a new snapshot.
Privacy, licensing and data credits
This site uses no analytics, advertising cookies or external font services. Only your theme preference is saved locally. Hosting providers process normal connection information. Created and maintained by duggytuxy (Laurent Minne). Code and blocklists are covered by the project's GPL-3.0 license. Country geolocation is based on DB-IP Country Lite, under CC BY 4.0. Map geometry is from Natural Earth (public domain); the Outfit font uses the SIL Open Font License.
EVIDENCE BEFORE CONCLUSIONS
Context behind every signal.
Investigate blocked IPv4 addresses with optional exposure enrichment, CVSS severity, CISA KEV and FIRST EPSS. Understand the evidence and its limits.
FROM INTELLIGENCE TO ENFORCEMENT
Put the lists to work.
Connect Data-Shield to FortiOS, UniFi, Palo Alto, OPNsense or Stormshield. Follow the setup, copy the commands and verify your coverage.
BETTER DATA. TOGETHER.
A clear signal starts with you.
Found a malicious address or a false positive? Share evidence through the project's dedicated forms. Keep credentials and sensitive logs out of public issues.