Title: IP lists
Last modified: August 14, 2025

---

# IP lists

 *  Resolved [Vineeth Mohan](https://wordpress.org/support/users/vineethmp/)
 * (@vineethmp)
 * [8 months ago](https://wordpress.org/support/topic/ip-lists/)
 * Is there a way to upload IP addresses in bulk, for eg Cloudflare IPs, for the
   white list or black list?

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Author [IniLerm](https://wordpress.org/support/users/inilerm/)
 * (@inilerm)
 * [8 months ago](https://wordpress.org/support/topic/ip-lists/#post-18599292)
 * Hi Vineeth, [@vineethmp](https://wordpress.org/support/users/vineethmp/)
 * That’s an excellent question and a very valid feature request. Thank you for 
   asking!
 * You are absolutely right that managing large IP lists like Cloudflare’s is a 
   common need. The good news is that the plugin fully supports **IP ranges in CIDR
   format** (like 103.21.244.0/22), which makes managing services like Cloudflare
   much easier. Instead of adding thousands of individual IPs, you can add their
   official ranges directly to the Whitelist or Manual Blocklist tabs.
 * However, for importing a list in bulk, the most efficient method currently is
   via **WP-CLI**, which is perfect for these kinds of operations.
 * **Here’s how you can do it:**
    1. **Create a text file** (e.g., cloudflare_ips.txt) containing the list of IP 
       ranges, one per line. You can get the official list from [Cloudflare’s website](https://www.google.com/url?sa=E&q=https%3A%2F%2Fwww.cloudflare.com%2Fips%2F).
       For example:codeCode`103.21.244.0/22 103.22.200.0/22 103.31.4.0/22 ...`
    2. **Use a command to add them to the whitelist:**
       From your server’s command line,
       in your WordPress root directory, you can run this command to add all ranges
       from the file to the whitelist:codeBash`cat cloudflare_ips.txt | xargs -n 1 
       wp advaipbl whitelist add`
    3. **To add them to the manual blocklist instead:**
       You would use the block command:
       codeBash`cat your_blocklist_file.txt | xargs -n 1 wp advaipbl block --reason
       ="Custom Blocklist Import"`
 * That being said, we absolutely agree that having a simple “Import from file” 
   button directly in the **IP Management > Whitelist** and **Blocked IPs** tabs
   would be a fantastic usability improvement. We’ve added this to our feature roadmap
   for a future release, as it would make managing large lists much more accessible
   for everyone.
 * Thank you again for the great suggestion! Let us know if you have any other questions.
 * Best regards.
 *  Thread Starter [Vineeth Mohan](https://wordpress.org/support/users/vineethmp/)
 * (@vineethmp)
 * [8 months ago](https://wordpress.org/support/topic/ip-lists/#post-18599605)
 * That’s interesting! Thanks a lot 🙂
 *  Plugin Author [IniLerm](https://wordpress.org/support/users/inilerm/)
 * (@inilerm)
 * [6 months, 3 weeks ago](https://wordpress.org/support/topic/ip-lists/#post-18648877)
 * Hi,
 * I’m marking this thread as resolved. Feel free to open a new topic if you have
   further questions.
 * Thanks.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘IP lists’ is closed to new replies.

 * ![](https://ps.w.org/advanced-ip-blocker/assets/icon-256x256.png?rev=3320247)
 * [Advanced IP Blocker](https://wordpress.org/plugins/advanced-ip-blocker/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/advanced-ip-blocker/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/advanced-ip-blocker/)
 * [Active Topics](https://wordpress.org/support/plugin/advanced-ip-blocker/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/advanced-ip-blocker/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/advanced-ip-blocker/reviews/)

## Tags

 * [IP](https://wordpress.org/support/topic-tag/ip/)
 * [list](https://wordpress.org/support/topic-tag/list/)

 * 4 replies
 * 2 participants
 * Last reply from: [IniLerm](https://wordpress.org/support/users/inilerm/)
 * Last activity: [6 months, 3 weeks ago](https://wordpress.org/support/topic/ip-lists/#post-18648877)
 * Status: resolved