IPv4 ↔ Decimal — Addresses as Single Integers
An IPv4 address is a 32-bit number that is conventionally written as four decimal octets. Some systems store the integer instead, because comparing and range-checking integers is far cheaper than parsing strings — and the result is a column full of large numbers that mean nothing at a glance.
When it helps
Mostly to read data you did not design. Geolocation databases, allow-list tables and older logging systems commonly store addresses this way, and a query against them requires converting your address into their form. The reverse conversion is what makes a row of integers legible when you are investigating something. Range checks are the other case: whether an address falls inside a block is trivial arithmetic in integer form and fiddly in dotted notation.
Worth running automatically
Where addresses appear in more than one representation across a system, normalising them is a code-level fix rather than a tool. What is worth checking continuously is the consequence: an allow-list that silently stops matching because one side stores integers and the other strings fails open or closed with no error. Verifying that access rules still behave as intended, from outside, is what notices.
What you get out of it
Makes integer-stored addresses readable and makes range comparisons straightforward. Small, and it removes a real obstacle when working with data whose format you did not choose.