Enter All IP Iran

Overview

IP Range Helper is a focused operational tool built for a very practical problem: handling IP ranges cleanly when you need to separate Iranian traffic from non-Iranian traffic, validate whether domains or IPs match your allowlists, and move those ranges into real infrastructure without turning the workflow into copy-paste chaos. The project is especially useful for Iranian IP range scenarios, where range files need to stay structured, validated, and ready for deployment into real systems such as MikroTik, Windscribe, firewalls, proxies, and custom routing or filtering workflows. IP Range Helper start screen

Why I built it

In practice, working with IP ranges becomes messy very quickly. Teams often need to:

check whether a domain resolves into an expected range,
verify if a direct IP is inside or outside a maintained CIDR list,
keep a reliable source file of ranges,
and then push those results into another system in exactly the input format that system expects.

That combination sounds simple until you do it repeatedly. This project exists to remove that friction.

Core capabilities

1. Range validation

IP Range Helper result when an address is inside the maintained ranges

The tool can validate whether an IP belongs to the maintained range set. That makes it useful for quickly deciding whether an address should be treated as local, routed differently, proxied, allowed, or blocked.

2. Domain checking

IP Range Helper result when an address is outside the maintained ranges

When a domain resolves to one or more IP addresses, the tool can help determine whether those addresses match the stored CIDR ranges. That is useful for policy checks and traffic-routing decisions.

3. CIDR range management

The maintained range list is not treated like throwaway text. The project is built around managing CIDR ranges as a real data source so they can be checked, updated, and reused confidently.

4. Automation-friendly output

IP Range Helper preparing ranges for another operational tool

One of the most useful parts of the tool is that it helps prepare the output for real-world systems. Instead of manually retyping or reshaping data, the generated content can be moved into tools and environments such as:

MikroTik address lists
Windscribe or similar routing configurations
firewalls and ACL-style workflows
proxies and split-routing tools
custom scripts and operational tooling

Operational value

This is not a vanity project. It is the kind of utility that becomes valuable because it saves time in the boring but important layer of infrastructure work. Small operational tools like this often prevent mistakes, reduce repetitive manual work, and make the final system more reliable.

Example workflow

Operational flow (Docker Compose / Linux, macOS, Windows)

# conceptual workflow
# 1) load and maintain CIDR source file
# 2) check a domain or IP against the ranges
# 3) generate output for the target system
# 4) paste or import the result into MikroTik / firewall / proxy tooling

Where it fits best

IP Range Helper is a strong fit for workflows where you repeatedly need confidence, speed, and repeatability while dealing with regional routing, traffic separation, or policy enforcement based on IP ownership and location. It is especially valuable when the target systems are operational tools that do not forgive formatting mistakes.

Outcome

The result is a practical bridge between range intelligence and real deployment actions. Instead of maintaining Iranian IP ranges in a passive text file, the project turns them into something you can validate, reuse, and operationalize.