Contact directory IPV4 LEASING CONTACT

A legitimate use before an allocation.

Prospective lessees should explain the use, ASN or hosting relationship, geography, duration, and abuse-response capability before discussing a prefix.

BOUNDARIES / 01

A form starts review. It does not issue an LOA.

No public document upload. Identity, authority, registry, and routing evidence needs a controlled channel and access log.

No automatic acceptance. Prefix history, RIR records, signer authority, route origin, policy, and counterparties require review.

No single-signal suspension. Monitoring creates evidence and a case; it does not replace investigation or contractual process.

No unauthorized sublease. A seller must have an explicit right to make the exact resource available for the intended use.

LESSEE INTAKE / 02

Describe the need and how you will operate it.

Do not place private documents or personally identifying registry evidence in this first message.

RENANT LIMITED will store these details for review. Do not include passwords, API keys, personal documents, or full IP-holder evidence. Read the working privacy notice before submitting; it has not yet been adopted as an effective notice.

Want to understand the verification, LOA, monitoring, and return workflow first?

Explore the IPv4 exchange model