What Is an IPv4 Transfer Agreement?
An IPv4 transfer agreement is a legally binding contract between the seller (transferor) and the buyer (transferee) of IPv4 address space. It defines the terms, responsibilities, and conditions under which IP addresses change hands. Without a proper agreement, both parties face significant legal and operational risks.
Why You Need a Formal Transfer Agreement
IPv4 addresses are valuable digital assets, with /24 blocks worth thousands of dollars. A well-drafted transfer agreement protects both parties by:
- Clearly defining the IP resources being transferred (prefix, size, RIR registration)
- Establishing the purchase price and payment schedule
- Setting timelines for the RIR transfer process
- Defining representations and warranties (clean title, no encumbrances, no blacklisting)
- Specifying what happens if the RIR rejects the transfer
Essential Clauses in an IPv4 Transfer Agreement
1. Identification of the Parties
Both buyer and seller must be clearly identified with their legal entity names, registration numbers, addresses, and authorized signatories. For RIR transfers, include the RIR member/organization IDs (e.g., RIPE ORG-handle or ARIN Org-ID).
2. Description of the IP Resources
Specify the exact IP address block being transferred:
- Network address and CIDR notation (e.g., 185.100.200.0/22)
- Total number of IP addresses
- Current RIR registration details
- Resource type: PA (Provider Aggregatable), PI (Provider Independent), or Legacy
3. Purchase Price and Payment Terms
Define the total price, currency, payment method (wire transfer, escrow, cryptocurrency), and payment schedule. Many agreements use escrow to protect both parties: the buyer deposits funds, and they are released to the seller only after the RIR confirms the transfer.
4. Transfer Process and Timeline
Outline who initiates the RIR transfer request, expected processing time, and each party's obligations during the process. For RIPE intra-RIR transfers, expect 5-10 business days. Inter-RIR transfers (e.g., RIPE to ARIN) can take 4-8 weeks.
5. Representations and Warranties
The seller should warrant that:
- They are the legitimate holder of the IP addresses
- The addresses are free from liens, encumbrances, or third-party claims
- The addresses are not blacklisted on major DNS blacklists
- There are no pending abuse complaints or legal disputes
6. Conditions Precedent
List conditions that must be met before the transfer is final, such as RIR approval, completion of due diligence, and successful payment processing.
7. Indemnification and Liability
Define each party's liability in case of breach, failed transfers, or misrepresentation. Include indemnification clauses to protect against third-party claims.
8. Termination and Refund Policy
Specify under what conditions the agreement can be terminated and how refunds are handled if the transfer fails or is rejected by the RIR.
Intra-RIR vs Inter-RIR Transfer Agreements
Intra-RIR Transfers (e.g., RIPE to RIPE)
These are simpler because both parties operate under the same RIR policy. The agreement references a single set of transfer rules, and the process is handled by one registry.
Inter-RIR Transfers (e.g., RIPE to ARIN)
These require compliance with both RIR policies. The agreement must address:
- Which RIR's policy takes precedence for specific matters
- ARIN's needs assessment requirement (if applicable)
- Coordination between both RIRs
- Longer processing timelines
Common Mistakes to Avoid
- Vague resource description: Always use exact CIDR notation, not just "approximately 1,000 IPs"
- No escrow protection: Never send payment directly without escrow for large transactions
- Missing blacklist warranty: Always require the seller to warrant clean IP reputation
- Ignoring holding periods: Some RIRs impose holding periods before re-transfer (e.g., RIPE's 24-month rule)
- No dispute resolution clause: Specify arbitration or jurisdiction in case of disputes
Generate Your Transfer Agreement Automatically
Drafting an IPv4 transfer agreement from scratch is time-consuming and error-prone. Our Transfer Contract Generator creates professionally formatted, RIR-compliant transfer agreements in seconds. Simply select the transfer type, enter buyer and seller details, and download a ready-to-sign PDF.
The generator supports all five RIRs (RIPE, ARIN, APNIC, LACNIC, AFRINIC) and handles both intra-RIR and inter-RIR transfer scenarios.
Ready to buy or sell IPv4 addresses? Start your purchase or list your addresses for sale on our platform.