Publish firewall IP lists as clean raw text.

Workflow

Create, validate, and publish

1. Create a named list.Choose a URL slug, description, and public or private visibility.
2. Add entries and sources.Enter IP addresses, CIDR ranges, full-line comments, and optional approved source URLs.
3. Save validated output.Invalid lines are reported instead of being silently published.
4. Consume the raw URL.Fetch the resulting text file from your firewall workflow or configuration management system.

Input and output

Supported list format

Published output contains only blank-free, line-oriented values in these categories:

• IPv4 addresses such as 192.0.2.10
• IPv4 CIDR ranges such as 198.51.100.0/24
• IPv6 addresses and CIDR ranges such as 2001:db8::/32
• Full-line comments beginning with #

# Office and VPN ranges
192.0.2.10
198.51.100.0/24
2001:db8::/32

Comments and addresses count toward the account's configured output-line limit. Validation keeps malformed or mixed-content lines out of the published artifact.

Delivery

Public and private raw URLs

A public list uses a stable path:

https://listips.com/u/username/list-slug

A private list adds a secret token to the URL:

https://listips.com/u/username/list-slug?token=sec_...

Treat a private URL like a credential: keep it out of source control, screenshots, analytics, and logs. Rotate the token if it is exposed.

Raw responses include cache and validation headers, including an ETag. A basic download can use conditional HTTP behavior provided by your client:

curl --fail --silent --show-error \
  https://listips.com/u/username/list-slug \
  --output /path/to/firewall-list.txt

ListIPs publishes the file; the consuming firewall or script remains responsible for applying it safely.

Synchronization

Approved external sources

Lists can combine manual entries with text sources from supported Cloudflare, GitHub raw-content, and Amazon AWS hosts. Source responses pass through the same validation and output limits as manual content.

Saving a source-enabled list queues background synchronization. Scheduled refreshes keep healthy configured lists current without making raw clients fetch upstream providers directly.

Operations

Use lists safely

• Stage firewall changes and keep a tested rollback path.
• Review upstream ownership and scope before trusting an external range.
• Use private URLs for sensitive list membership and rotate exposed tokens.
• Monitor fetch failures before removing the last known-good local copy.
• Validate the consuming tool's expected syntax; ListIPs serves addresses and CIDRs, not tool-specific commands.