ListIPs: from a shared IP list to a published artifact

Imagine a firewall allowlist that lives in a shared document, with three servers pulling a copy on a cron job. It works until a typo slips in, a vendor’s published ranges change, or someone pastes a hostname where an address should be. The firewall then does whatever it does with malformed input, and nobody notices until traffic is blocked or let through.

The list is the product

ListIPs treats that list as a small piece of infrastructure. You create a named list, add IPv4 and IPv6 addresses, CIDR ranges and comments, and optionally attach approved upstream text sources from a supported set of hosts. ListIPs validates every line, reports anything malformed instead of publishing it quietly, and serves the result as plain line-oriented text at a stable HTTPS URL. Your script or configuration management job fetches that URL the way it fetched the old file.

Source-enabled lists refresh in the background on a schedule, so your servers read a cached, validated copy rather than calling the provider directly. The output stays plain on purpose: addresses, CIDRs and comment lines, nothing tool-specific, so scripts and configuration workflows for HestiaCP, iptables, UFW or Nginx can consume it. The documentation covers the workflow and format.

Where ListIPs stops

ListIPs is not a firewall and does not apply rules. The consuming system remains responsible for staging a change, keeping a tested rollback, and watching for fetch failures before it discards its last known-good copy. ListIPs also does not vet upstream sources. It accepts text from approved hosts and validates the lines. Whether a source is trustworthy and correctly scoped is still your call.

Private lists use a token in the URL. Treat that URL as a credential: keep it out of source control, screenshots, analytics and logs, and rotate it if it leaks. A private URL only limits who can read the list. It is not a security boundary around your firewall.

Its place in the portfolio

ListIPs is owned by VMCSoft Digital and published and operated by ViWeb Technology. It is open source, with its code in a public GitHub repository, and it sits alongside HeaderSec, Pingeko and DiagEZ as a focused product that does one bounded job and hands the result to systems you already run. In the scenario above, publishing the list through ListIPs is a smaller change than redesigning the firewall, and it makes the list visible enough to be maintained.

Read the about page for scope, then move one existing list and point a single consumer at it before migrating the rest.