How Lenders Underwrite Loans Against Domain Names

A loan against a domain name is underwritten as a credit file, not as a marketplace listing. The underwriter has to answer a simple question: if the borrower does not repay, can the lender take and realize the name in an orderly way, and was there always another way to get.

Share

A loan against a domain name is underwritten as a credit file, not as a marketplace listing. The underwriter has to answer a simple question: if the borrower does not repay, can the lender take and realize the name in an orderly way, and was there always another way to get repaid that did not depend on a perfect sale?

This article is the underwriting walk-through. It is not a second service page. The live overview of loans against domain names and domain finance advisory already owns that head term. If the product you want is specialty credit secured by the name, use the financely.io page on specialty finance against domain name collateral. Financely is an advisor and arranger only. It does not lend and it does not approve facilities.

Start with the borrower, then the name

Domain collateral does not erase borrower credit. A committee still wants to know who is borrowing, why the proceeds are needed, how interest and principal will be paid, and what happens at maturity. A strong name attached to a borrower who cannot service the facility is still a weak file. A weaker name attached to a borrower with clear cash flow and a conservative request may be easier to discuss, although the collateral still has to be real.

Use of proceeds should be specific. Refinancing a purchase, funding a related operating need, or releasing equity from a held portfolio are different stories. "I want as much as the name is worth" is not a credit story.

Title and control come before valuation

The underwriter will try to match the registered name holder, the proposed pledgor, and the borrower. If the name sits in a personal account, an old registrar login, or an entity that is not in the facility, that gap has to be fixed before anyone talks about value. Prior transfers should be documented. A current WHOIS or RDAP record is not a chain of title.

Control of the registration is part of underwriting, not a closing detail. ICANN describes clientTransferProhibited as a status that tells the registry to reject transfer requests, which can help prevent an unauthorized move. The Transfer Policy also requires, in defined cases, that a registrar remove that status or issue the AuthInfo code within five calendar days of the registered name holder's request. A lock the borrower can have lifted on that timetable can help, and it is not a complete security package on its own. The deeper mechanics are in perfecting a security interest in a domain name.

Dispute and trademark risk can end the review

A name that is identical or confusingly similar to someone else's mark can lose its value quickly if a complaint is filed. Under the UDRP, a complainant must prove three elements: the domain is identical or confusingly similar to a trademark or service mark in which the complainant has rights, the registrant has no rights or legitimate interests in the name, and the name has been registered and is being used in bad faith. An underwriter does not need to be a panelist to care about that test. Open disputes, a pattern of typo or brand-adjacent registrations, or a name whose only value is proximity to a famous mark, are credit issues.

This is not a full legal opinion and it is not a clearance search. Counsel should review the specific string. The underwriter's job is to see whether the file already shows a problem that a buyer, a lender, or a later purchaser would also see.

Valuation evidence has to survive a committee

Automated appraisals are easy to produce and easy to attack. A credit memo that rests on one score, with no comparable sales, no discussion of liquidity, and no explanation of why that name would actually sell, is a weak memo. Better evidence looks like a set of relevant comparable transactions, a clear description of how the name is used, and a conservative view of exit time and buyer depth. The underwriter should also separate the value of the string from the value of a business that happens to sit on it. If the website is the business, the credit may belong in a different product, or the security package may need more than the domain.

Financely does not publish, invent, or guarantee loan-to-value ratios, advance rates, or appraisal haircuts. Those figures, if they appear at all, come from the capital provider after it reviews the file.

Cash flow, concentration, and portfolios

If the borrower claims parking income, a lease, a redirect fee, or operating revenue tied to the name, that cash flow has to be evidenced and should be capable of continuing after a transfer of control. Informal or easily cancelled arrangements add little. For a portfolio, the underwriter looks at concentration. A book that is really one trophy name plus a long tail of weak names is underwritten as a single-name risk, not as a diversified pool.

Portfolio files also need a consistent registrar and ownership map. A collection spread across many logins, expired names, or entities is slower and weaker than a clean, centralised list. The document list for either a single name or a book is in documents for a domain-backed loan file.

Structure and recourse are part of underwriting

The underwriter will ask whether the facility is a loan to an operating company, a loan to a holding vehicle that owns the names, or something the borrower is calling "non-recourse." Labels are not the analysis. In project finance, non-recourse language has a specific meaning tied to project cash flows and assets. A domain-backed specialty loan is usually a different product. How to read that difference is in when a domain-backed loan is not non-recourse and in why specialty finance and project finance treat recourse differently.

If you are preparing a file, also compare the name with other intangibles in domain name collateral versus patents, trademarks and royalties. Then submit a complete package through deal submission. A teaser without title, control, and repayment will not get a serious review.

Frequently asked questions

Do lenders accept an automated domain appraisal as the credit value?

Not as a stand-alone figure. Automated scores can be a starting point, but a credit review looks for evidence a committee can test, such as comparable sales, contracted use, or other market support. Financely does not assign a value or promise an advance against any appraisal.

Can a domain with no traffic still be underwritten?

It can be reviewed. The file then depends even more on the quality of the string, clean title, control of the registration, dispute risk, and a repayment plan that does not rely on a perfect sale. Lack of use is not automatically fatal, and it is not a strength.

Is underwriting the same as approving the loan?

No. Underwriting is the review. Approval, if it happens, comes from the capital provider. Financely is an advisor and arranger only. It does not lend and it does not approve credit. A complete file lets a provider start that review. It does not create a right to funding.

Where should I start if I want to borrow against a domain?

Read the live overview on loans against domain names and domain finance advisory, then use the document checklist and, if the product is specialty credit, the financely.io page on specialty finance against domain name collateral. Submit a complete file through deal submission.

Financely is an advisor and arranger, not a lender. If you have a real domain-backed file and want it prepared for a credit review, submit it through the intake form. No approval is promised.

Submit your deal

Sources and references

  1. ICANN, Uniform Domain Name Dispute Resolution Policy, paragraph 4(a): https://www.icann.org/en/contracted-parties/consensus-policies/uniform-domain-name-dispute-resolution-policy/uniform-domain-name-dispute-resolution-policy-25-02-2012-en
  2. 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
  3. ICANN, EPP Status Codes: https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en
  4. Financely deal submission: https://www.financely.io/deal-submission