An IPv4 transfer audit is, at its core, a systematic verification that both sides of a transaction should run before any money changes hands. Prices have held strong lately, and marketplace activity keeps climbing, which means due diligence now matters more than ever. It’s what separates a smooth transfer from a very expensive headache. This guide walks through each stage of a proper audit, from RIR record verification to abuse history screening, so you can transact with confidence.

What Is an IPv4 Transfer Audit and Why It Matters

An IPv4 transfer audit is a structured review of a block’s legal ownership, registry status, reputation, and eligibility for transfer under the policies of the relevant Regional Internet Registry (RIR). Whether you’re picking up a /24 for network expansion or selling off legacy space, the audit protects both parties from disputes, fraud, and surprises that only surface after the transfer is done.

The stakes are real. A single /24 can be worth tens of thousands of dollars, and problems discovered post-transfer — unresolved ownership claims, blacklistings, bogus pre-use (BPU) listings — can stall routing, wreck sender reputation, and drag you into lengthy RIR investigations. A disciplined audit typically takes one to three weeks. That might sound slow. It isn’t. It’s cheap insurance.

Need IPv4 addresses?

Browse clean, RIPE-verified subnets at $0.50/IP/month.

Browse Subnets →

At IP4 Market, every listing goes through pre-transaction verification. Still, buyers and sellers should understand the underlying audit steps themselves, because at the end of the day you’re the one protecting your own interests.

Step 1: Verify Block Ownership and RIR Registration Records

The foundation of any audit is confirming that the seller actually controls the block. Start with the authoritative sources:

  1. WHOIS lookup: Query the relevant RIR database (ARIN, RIPE NCC, APNIC, LACNIC, or AFRINIC) to confirm the registered organization, administrative contacts, and allocation type.
  2. Registry portal check: In ARIN Online or the RIPE Database, verify that the seller can actually initiate a transfer request. Only the registered holder or an authorized contact can. Nobody else.
  3. Legacy vs. issued space: Legacy blocks (pre-1999, assigned directly by the registries) often lack modern registration agreements. Confirm the block is eligible for transfer and that the seller can sign the necessary RSA or Legacy Registration Services Agreement where required.

What should worry you at this stage? Recent registration changes, organization names that don’t quite match, a seller who can’t produce documentation tying them to the registered entity. For RIPE space, check for conflicting resources or pending transfer flags in the database. And always request corporate documentation — a certificate of incorporation, a letter of authorization — that matches the WHOIS organization name exactly. Not approximately. Exactly.

Step 2: Check for Blacklistings, Hijacking History, and Abuse Reports

A block’s reputation directly affects its value and usability. Blocks with blacklisting history can cause email delivery failures, outbound filtering, and BGP trust issues that stick around long after the transfer closes.

  • Blacklist screening: Run every prefix through the major DNSBLs — Spamhaus (SBL, XBL, PBL), SpamCop, Barracuda, Composite Blocking List. Delisting after transfer is possible, but expect weeks of coordination.
  • Hijacking checks: Review the block’s BGP announcement history with tools like RIPEstat, BGPlay, or RouteViews data. Frequent unauthorized announcements from unexpected ASNs suggest a hijack history that network operators may still have flagged somewhere.
  • Abuse and spam traces: Search abuse databases, SenderScore records, and open archives for complaints tied to the range. A heavy spam velocity history can permanently lower deliverability in the eyes of some providers. Some never forgive.

Practical tip: Document your screening results with dated screenshots or reports. If a delisting turns out to be necessary, negotiate responsibility for cleanup into the purchase agreement — reputable marketplaces like IP4 Market require sellers to disclose known reputation issues before listing, which makes this step considerably less painful.

A clean reputation report at this stage de-risks the rest of the transaction significantly. Small effort upfront. Big payoff later.

Step 3: Review Legal Documentation, LOAs, and Transfer Agreements

Once reputation due diligence is done, move to the legal layer of the deal. Two documents matter here: the Letter of Authorization (LOA) and the transfer agreement itself. The LOA is what authorizes the holder to move the block, and it should reference the prefix range explicitly, plus the RIR of record, the signatory’s name and title, and the destination organization. If an LOA arrives with handwritten edits, a missing signature, or vague prefix notation — a /16 described as a “half” allocation, for instance — walk away from it. No exceptions.

For the transfer agreement, check that it covers each of the following:

  • Consideration and payment terms: escrow arrangements, milestone-based releases, and settlement currency. All of it unambiguous.
  • Warranties of title: the seller confirms unencumbered ownership — no liens, no leases, no pending disputes against the block.
  • RIR compliance representations: both parties acknowledge their obligations under the relevant registry’s transfer policy.
  • Indemnification clauses: who carries liability if a third party contests the transfer, or if undisclosed usage rights surface after the fact.
  • Contingency and refund terms: what happens if the RIR rejects the application, or if the process drags past the agreed timeline.

One practical tip I’d stress: cross-check the signatory against the RIR’s organizational contact record. If the person signing the LOA isn’t listed as the administrative contact, ask for corporate documentation proving their authority. Skipping this step is, frankly, one of the most common routes to post-transfer litigation.

Step 4: Validate Pre-Bid Requirements and RIR Transfer Policies

Last step: confirm both parties actually satisfy the registry’s procedural requirements. Each RIR plays by different rules, and those differences affect feasibility and timing in ways buyers often underestimate. ARIN requires a demonstrated need — the recipient must justify the number of addresses requested, typically within a 24-month utilization horizon. RIPE NCC has no strict need-based test, though both organizations must hold valid membership. APNIC assesses need based on current usage data.

Before you submit any bid or offer, work through this checklist:

  1. Confirm your receiving organization is registered and in good standing with the relevant RIR.
  2. Verify your documented need (ARIN and APNIC) with growth projections and existing utilization data.
  3. Budget for administrative fees — anywhere from a few hundred to several thousand dollars, depending on block size and registry.
  4. Factor in the standard processing window, usually 30 to 90 days, and align deployment plans accordingly.
  5. Check for regional restrictions, such as intra-RIR versus inter-RIR transfer limitations.

Going through a marketplace with in-house compliance expertise, such as ip4 market, cuts friction at this stage considerably — listings are pre-screened against current RIR policies, and sellers get walked through the documentation. That said, don’t outsource your judgment. Registry rules change periodically, and when a transfer gets rejected, responsibility usually lands on the recipient, not anyone else.

Conclusion: Building a Repeatable IPv4 Transfer Audit Process

An IPv4 transfer audit isn’t a one-time formality. It’s a discipline, and it pays off across every acquisition your organization makes. Verify ownership and block status. Assess routing and reputation health. Review the legal documentation. Validate RIR policy compliance. Do this every single time and you’ve built a framework that minimizes financial, legal, and operational risk — one that holds up deal after deal.

Document findings at each stage in a standardized audit template, then revisit it after every transaction to fold in lessons learned. Prices keep climbing as IPv4 scarcity deepens, and scrutiny of block provenance is only getting sharper. Buyers and sellers who treat due diligence as a core competency close faster, pay fair market rates, and stay clear of the costly disputes that plague poorly audited transfers. The others learn the hard way.

Need IPv4 space? Lease RIPE-verified /24–/22 subnets at a flat €0.50/IP per month — LOA + RPKI/ROA in minutes, instant company verification, automatic renewals. Browse available subnets →

Share:
IP4

ip4.market Team

Expert content on IPv4 leasing, IP address management, and network infrastructure from the ip4.market team.