
Curated IPv4 blocklist of malicious addresses, refreshed every 6 hours for firewall and WAF ingestion, with split lists and CTI-ready formats for threat intelligence platforms.
Two complete lists. Clear choices. Controlled updates.
Data-Shield provides maintained IPv4 blocklists for inbound filtering on firewalls, gateways and web application firewalls. Choose the policy that fits your environment, import its raw URL, and review its effect on legitimate traffic.
Download standard · Download critical · Report a false positive
| Profile | Intended use | File |
|---|---|---|
| Standard | The starting point for Internet-facing services, with reviewed exceptions to reduce avoidable blocking. | prod_data-shield_ipv4_blocklist.txt |
| Critical | A broader blocking policy for environments that accept stricter ingress filtering. Review the impact before deployment. | prod_critical_data-shield_ipv4_blocklist.txt |
Each file is complete and can be used on its own. Applying both lists combines their blocking decisions and may override the exceptions of the profile you intended to use.
The entry count changes over time. Check your product's capacity against the actual file, including whether it silently truncates oversized imports. There is no fixed 100,000-entry cap.
For devices with per-list entry limits, import every part of one profile as a separate feed and include them all in the same inbound policy. Each part contains up to 30,000 addresses. The publisher commits both complete files and all their parts together. Concatenating the parts of one profile in suffix order reproduces its complete file from the same commit.
| Part | Standard | Critical |
|---|---|---|
| aa | Raw Standard aa | Raw Critical aa |
| ab | Raw Standard ab | Raw Critical ab |
| ac | Raw Standard ac | Raw Critical ac |
| ad | Raw Standard ad | Raw Critical ad |
The table covers the four parts per profile at rollout. When a profile exceeds 120,000 entries, its next part is ae. Check the repository file listing for the current suffixes when updating your firewall configuration.
| Destination | Standard | Critical |
|---|---|---|
| GitHub | Raw file | Raw file |
| GitLab | Raw file | Raw file |
| Codeberg | Raw file | Raw file |
| Bitbucket | Raw file | Raw file |
| jsDelivr CDN | Raw file | Raw file |
These are the existing download URLs used by SYSwarden. The two filenames and their paths remain unchanged. GitLab manages repository mirroring to Codeberg and Bitbucket. jsDelivr serves a cached copy from GitHub, so CDN refreshes can lag behind publication.
Use a raw file URL in your firewall's feed configuration. A repository or preview-page URL returns a web page, not the blocklist.