Download the Iran IP List for FortiGate, including a dedicated GeoIP override configuration, IPv4 address objects, IPv6 address objects and a combined configuration. The files are generated from the coverage-audited RIPE registry set to help network administrators maintain Iran-associated IP ranges for security and network-policy workflows.
Each download serves a different purpose. Select the format that matches your configuration workflow rather than importing every file indiscriminately. All links below point to the generated files published with this page.
A custom GeoIP override configuration for Iranian IPv4 ranges. Use this when you specifically need the GeoIP override mechanism and have confirmed that your FortiOS version supports its syntax, country identifier and range requirements.
Generated IPv4 address objects for workflows that use explicit IP addresses and subnets. These objects are separate from the GeoIP override and can be referenced only after they have been imported and checked.
Generated IPv6 address6 objects for IPv6-aware environments. The presence of this file does not mean the separate GeoIP override format accepts IPv6 ranges. Confirm the features supported by your target FortiOS release.
A single file containing both generated IPv4 and IPv6 address-object configuration. Review existing object names and compatibility before importing it into an established firewall configuration.
The Iran GeoIP override file is intended for the FortiOS GeoIP override mechanism. This is not the same thing as creating a normal firewall address object for every subnet. A GeoIP override changes how supported FortiOS versions associate configured IP ranges with a geographic country entry.
Do not assume that every FortiGate model or FortiOS version accepts the same GeoIP override format. Validate the downloaded configuration against the official documentation for your release and test before production use. The country identifier shown in a file is configuration data, not a guarantee that every firmware release will accept it.
Use this checklist before deploying a FortiGate Iran GeoIP configuration. The exact import and activation procedure depends on the capabilities and syntax of your FortiOS version.
Confirm that the target release supports the GeoIP override feature and the configuration structure used by the downloaded file. Do not assume support based only on the hardware model.
Review the country identifier, configured object name, IP ranges and command structure. Compare them with the official FortiOS documentation and your current configuration.
Save a recoverable backup before making changes. If possible, validate the configuration in a lab or non-production environment first.
Use the import or CLI procedure documented for your release. Do not paste an unverified configuration into production or assume a file can be imported unchanged across different FortiOS versions.
Confirm that the configuration was accepted and that the intended geographic match is visible and behaves correctly. Review policy order, logs and representative traffic before relying on the result.
The standard IPv4, IPv6 and combined downloads contain address-object configuration. These objects are different from a GeoIP override. After importing and verifying the objects, administrators can reference supported objects in relevant firewall policies and groups according to their network design.
Decide whether the list should be used for matching, allowing, restricting or logging traffic based on your security requirements. Check object-name conflicts, policy order, logging and the effect on existing sessions. Review the data before every production change.
The published prefix set follows the coverage-audited RIPE Database-derived
public dataset. RIPE NCC alloclist.txt provides LIR metadata.
The same retained prefix set is rendered in FortiGate and other supported
network-list formats.
The website does not currently refresh this dataset on a daily schedule. Check version.json for its generation time and verify the downloaded configuration before applying it.
No. Registry allocation data describes address-space assignments and is a useful reference, but it does not guarantee the physical location of a user, device or service. Reassignments, hosting providers, VPNs, proxies and routing changes can affect how an address is used. Treat the list as one input to network policy, not as definitive geolocation evidence.
Source provenance: RIPE Database and RIPE NCC allocation metadata. Published output: Iran IP List. Validate the published configuration before using it in a production environment.
Use the GeoIP Override download near the top of this page. Separate downloads are also available for IPv4 address objects, IPv6 address objects and a combined IPv4/IPv6 configuration.
A GeoIP override is intended for the supported GeoIP mapping mechanism. Standard IPv4 and IPv6 files define address objects. Their syntax and use are different, so select the file that matches your intended workflow.
The website does not currently refresh the dataset on a daily schedule. Check version.json for the generation time.
Compatibility depends on the FortiOS release and the features, syntax and limits it supports. Verify the specific release and test before deployment.
The IPv6 address-object download is separate. Its availability does not establish that the GeoIP override format supports IPv6. Verify the capability and syntax of your FortiOS release.
No. Allocation records are not definitive physical geolocation data. Reassignment, hosting, VPNs, proxies and routing can affect the actual use and apparent location of an address.
Review the file, confirm compatibility, back up the current configuration and test first. Object-name conflicts, syntax differences and policy behavior should be checked before production deployment.