> ## Content Index
> Fetch the complete content index at: https://blog.financely.io/llms.txt
> Use this file to discover other available public pages before exploring further.

# Perfecting a Security Interest in a Domain Name
- URL: https://blog.financely.io/perfecting-a-security-interest-in-a-domain-name/
- Published: 2026-11-13T22:13:53.000Z
- Updated: 2026-11-13T22:13:53.000Z
- Description: Two different jobs get mixed together in domain-backed loans. One is legal perfection: putting the lender's interest in the right place so that it has priority against other creditors, to the extent the law allows. The other is practical control: making it hard for the name to.
- Author: Financely Debt Advisors
- Tags: Specialty Finance, Structured Finance

Two different jobs get mixed together in domain-backed loans. One is legal perfection: putting the lender's interest in the right place so that it has priority against other creditors, to the extent the law allows. The other is practical control: making it hard for the name to be transferred, updated, or allowed to expire while the facility is outstanding.

A file needs both. One does not replace the other. This article goes deeper than the registrar-control section on the live [loans against domain names](https://blog.financely.io/loans-against-domain-names-and-domain-finance-advisory/) page. It is general information, not legal advice. Financely is an advisor and arranger, not counsel. The right steps depend on the debtor, the registrar, the TLD, and the governing law.

## The U.S. filing example

In the United States, Article 9 of the Uniform Commercial Code governs many security interests in personal property. Section 9-102(42) defines a general intangible as any personal property, including things in action, other than a list of more specific categories such as accounts, goods, instruments, and deposit accounts. The term includes payment intangibles and software. Counsel often document a domain-name pledge in this residual category, or in another Article 9 category that fits the facts. Courts and commentators have not always described a domain name in the same way, which is one reason a generic phrase in a filing is not a do-it-yourself project.

Section 9-310(a) states the general rule: except as otherwise provided in subsection (b) and Section 9-312(b), a financing statement must be filed to perfect all security interests and agricultural liens. There are exceptions, and they have to be checked. The point for this cluster is simpler. A U.S. lender will usually expect a financing statement, filed in the right place, with a collateral description that actually reaches the name. The ICANN registrar system is not a financing-statement office. You cannot perfect an Article 9 interest by "recording" a pledge only at the registrar.

Where the debtor is not a U.S. person, or the governing law is not a U.S. state law, a different statute may apply. Do not copy a UCC-1 routine into another country and assume it works.

## Registrar status codes are control tools

ICANN's EPP status guidance describes `clientTransferProhibited` as a status that tells the registry to reject requests to transfer the domain from the current registrar to another, which can help prevent unauthorized transfers from hijacking or fraud. The same page notes that `clientUpdateProhibited` and `clientDeleteProhibited` can help prevent unauthorized updates or deletions. `serverTransferProhibited` also blocks a transfer, and ICANN notes that removing it can take longer because the registrar has to ask the registry to lift the restriction.

Those tools matter. They are still not perfection by themselves. They also have limits. Under section 5 of the ICANN Transfer Policy, as updated on 21 February 2024, a registrar may only set `ClientTransferProhibited` on registration or at the registered name holder's subsequent request, and must include the terms in the registration agreement. If the registrar does not give the holder a way to remove the status or manage the AuthInfo code, the registrar must remove the status and, in the AuthInfo case, provide the unique code within five calendar days of the holder's initial request. The registrar may not use a more restrictive process for that request than it uses for contact or name-server changes, and it may not refuse solely because of a payment dispute with the holder.

The credit implication is direct. A lock that the borrower, as registered name holder, can have removed on that timetable can help against some third-party threats. It is a weak sole control if the borrower itself is the person the lender is worried about. A serious control plan usually needs contract rights, account access arrangements, escrow, or other steps counsel designs, sometimes including a stronger registry-level lock where the registry offers one.

## What a lender-ready control outline usually covers

- Who is the registered name holder today, and who will be the holder at closing.
- Where a financing statement or equivalent filing will be made, and how the name will be described.
- Who holds registrar logins, AuthInfo or transfer codes, and recovery emails.
- Which EPP statuses will be in place, and who can ask the registrar or registry to change them.
- How renewals will be paid so the name does not expire during the facility.
- What happens on default, in practical terms, not only in a legal paragraph.

That outline belongs in the credit file described in [documents for a domain-backed loan file](https://blog.financely.io/documents-for-a-domain-backed-loan-file/) and in the underwriting walk-through, [how lenders underwrite loans against domain names](https://blog.financely.io/how-lenders-underwrite-loans-against-domain-names/). For placement, use [specialty finance against domain name collateral](https://www.financely.io/specialty-finance-against-domain-name-collateral?ref=blog.financely.io). Submit the file through [deal submission](https://www.financely.io/deal-submission?ref=blog.financely.io). Financely will not file a financing statement for you, and a tidy control memo is not an approval.

## Frequently asked questions

### Is a registrar lock enough to perfect a security interest?

Usually no, and this page is not legal advice. In the United States, Article 9 generally requires a financing statement to perfect a security interest, subject to listed exceptions. A registrar lock can be an important control tool. It is not a UCC filing system.

### What is ClientTransferProhibited?

ICANN's EPP status guidance says this status tells the registry to reject requests to transfer the domain from the current registrar to another, which can help prevent unauthorized transfers. The Transfer Policy also sets rules for when a registrar must remove that status or issue an AuthInfo code, including a five-calendar-day timing rule in defined cases.

### Does every country use the UCC for domain pledges?

No. This article uses United States Article 9 as a worked example because it is a common reference point. The right filing, court, and characterization depend on the debtor, the registrar, and the governing law. Counsel has to confirm that.

### Will Financely perfect the security interest?

No. Financely is an advisor and arranger only. Counsel and the parties document and file the security. A complete file still does not guarantee that a lender will offer a facility, and Financely does not make those filings or act as the borrower's counsel.

Financely is an advisor and arranger, not a lender and not counsel. If you need a domain-backed file prepared, including a control outline for counsel to finish, submit it through the intake form.

[Submit your deal](https://www.financely.io/deal-submission?ref=blog.financely.io)

Sources and references

1. Uniform Commercial Code § 9-102(42), definition of general intangible, Cornell LII: [https://www.law.cornell.edu/ucc/9/9-102](https://www.law.cornell.edu/ucc/9/9-102?ref=blog.financely.io)
2. Uniform Commercial Code § 9-310(a), perfection by filing, Cornell LII: [https://www.law.cornell.edu/ucc/9/9-310](https://www.law.cornell.edu/ucc/9/9-310?ref=blog.financely.io)
3. ICANN Transfer Policy, updated 21 February 2024, sections 5.1 to 5.4: [https://www.icann.org/en/contracted-parties/accredited-registrars/resources/domain-name-transfers/policy](https://www.icann.org/en/contracted-parties/accredited-registrars/resources/domain-name-transfers/policy?ref=blog.financely.io)
4. ICANN, EPP Status Codes, including clientTransferProhibited and serverTransferProhibited: [https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en](https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en?ref=blog.financely.io)
5. Financely deal submission: [https://www.financely.io/deal-submission](https://www.financely.io/deal-submission?ref=blog.financely.io)