> ## 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.

# Domain Names in a Project Finance Security Package
- URL: https://blog.financely.io/domain-names-in-a-project-finance-security-package/
- Published: 2026-11-13T22:13:58.000Z
- Updated: 2026-11-13T22:13:58.000Z
- Description: Project companies own domain names all the time. The site is how customers find the service, how an offtaker is billed, or how the project presents itself to regulators and lenders. That does not turn the financing into a loan against a domain name, and it does not make the.
- Author: Financely Debt Advisors
- Tags: Project Finance, Specialty Finance

Project companies own domain names all the time. The site is how customers find the service, how an offtaker is billed, or how the project presents itself to regulators and lenders. That does not turn the financing into a loan against a domain name, and it does not make the project non-recourse just because the name is valuable.

This article sits between two live product paths. If the mandate is project debt, start with [project finance advisory](https://www.financely.io/projectfinance?ref=blog.financely.io) and [non-recourse project finance advisory](https://www.financely.io/nonrecourse-projectfunding?ref=blog.financely.io). If the mandate is liquidity against a name, start with [specialty finance against domain name collateral](https://www.financely.io/specialty-finance-against-domain-name-collateral?ref=blog.financely.io). Financely is an advisor and arranger only.

## The domain is usually an operating asset, not the repayment engine

In the project finance sense described by a World Bank policy note, nonrecourse lenders have recourse only to the project's cash flows and assets. In practice, many facilities are limited recourse, with some sponsor or government support. The cash flows that matter are still the project's: an offtake, a concession, a regulated tariff, or another bankable revenue path. A domain might be part of the asset base that has to be secured. It is rarely the reason a committee believes those cash flows will appear.

That is why this piece does not retarget the live guides on [eligibility tests lenders use](https://blog.financely.io/nonrecourse-project-finance-eligibility-tests-lenders-use/) or [non-recourse project financing](https://blog.financely.io/non-recourse-project-financing/). Those pages already explain when a project can support that debt. The only incremental question here is what to do with the name.

## When the name belongs in the project package

| Situation                                                                                                | Typical treatment in a project file                                                                                                                        |
| -------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The project cannot operate, bill, or reach users without the name                                        | Include it in the security schedule, take control of the registrar account, and treat loss or hijacking of the name as a project risk                      |
| The name is a modest operating URL with little stand-alone sale value                                    | Still pledge and control it if the project uses it. Do not build the credit story around a sale of the name                                                |
| The sponsor owns a premium name that is not used by the project                                          | Leave it outside the vehicle unless there is a real commercial reason to contribute it. A trophy domain does not fix a weak offtake                        |
| The sponsor wants to move a valuable name into the SPV to claim non-recourse treatment for a domain loan | That is the wrong structure. See [when a domain-backed loan is not non-recourse](https://blog.financely.io/when-a-domain-backed-loan-is-not-non-recourse/) |

If the name is in the package, the same control issues arise as in a specialty domain facility. A transfer lock can help, but ICANN's Transfer Policy also describes cases where a registrar must remove `ClientTransferProhibited` or issue an AuthInfo code within five calendar days of the registered name holder's request. Project lenders will want a control arrangement that does not depend on a single person at the sponsor being able to unlock the name. The mechanics are in [perfecting a security interest in a domain name](https://blog.financely.io/perfecting-a-security-interest-in-a-domain-name/).

## Do not mix the two credit stories

A project file should still be a project file: contracts, model, permits, construction, accounts, and a cash waterfall. Mention the domain in the security and insurance discussion, and in operations if the customer channel depends on it. Do not replace a missing offtake with a domain appraisal.

A domain-collateral file should still be a domain-collateral file: title, control, dispute risk, value evidence, and borrower repayment. Do not call it project finance because the borrower created a new company and transferred the name in. [Choosing a structure](https://blog.financely.io/specialty-finance-vs-project-finance-choosing-a-structure/) is the decision guide. [Why the two markets treat recourse differently](https://blog.financely.io/why-specialty-finance-and-project-finance-treat-recourse-differently/) explains the support logic.

## Keep the name, the vehicle, and the sponsor in the right places

A practical issue appears when the project uses a name that the sponsor wants to keep, or when several projects share a brand domain. Shared names create shared risk. If one project defaults, a lender that controls the shared name can interfere with another project or with the sponsor's broader business. If the name stays with the sponsor and the project only has a license, the project file has to show that the license survives default and change of control, and that a successor operator can still use the URL. Those points belong in the security review and in counsel's work, not in a footnote on the last page of a model.

Cyber and hijacking risk belongs in the same discussion. A project that invoices through a single domain, or that depends on email at that domain for offtake notices, can be hurt by a loss of control even if the physical plant is fine. Renewal dates, registrar access, and a named person who can act if the name is moved or locked, should be part of the operations plan. That is project administration, not a reason to re-label the debt as a domain loan.

If you are preparing a real project mandate, submit it through [deal submission](https://www.financely.io/deal-submission?ref=blog.financely.io) as a project file. If the live owner you need is the lender-facing project page, use [non-recourse project finance lenders](https://www.financely-group.com/non-recourse-project-finance-lenders?ref=blog.financely.io) as the group reference, and keep the work on financely.io and the blog for this cluster.

## Frequently asked questions

### Can a premium domain make a project bankable on a non-recourse basis?

No, not by itself. Non-recourse or limited-recourse project debt is underwritten on the project's cash flows, contracts, construction, and project assets. A valuable domain can be additional collateral or an operating asset. It does not replace bankability tests, and it does not turn the financing into a domain-backed loan.

### Should every project company domain be pledged?

If the project needs the name to operate, bill, or reach customers, lenders will usually want it in the security package and under control. A sponsor trophy name that has nothing to do with the project should not be dropped into the vehicle just to decorate the file.

### If the project company owns a domain, is this a domain-backed loan?

Usually not. The product is still project finance. The domain is one asset in the package. A domain-backed specialty loan is a different mandate, described on the specialty finance against domain name collateral page. Do not recast a project file as a loan against the project's name.

### Where do I start if the mandate is a project, not a domain loan?

Use Financely's project finance advisory and non-recourse project finance advisory pages, and the eligibility-tests guide. Submit the project file through the deal submission form, not a list of names. A project file still needs the contracts, the model, permits, construction, accounts, and a cash waterfall.

Financely is an advisor and arranger, not a lender. If you have a project finance file, or a question about assets inside the security package, submit it through the intake form. No approval is promised.

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

Sources and references

1. World Bank, Public Policy for the Private Sector, Note No. 56 (October 1995), on nonrecourse versus limited recourse project finance: [https://documents1.worldbank.org/curated/en/434831468763784861/pdf/16916-Replacement-file-056LAMEC.pdf](https://documents1.worldbank.org/curated/en/434831468763784861/pdf/16916-Replacement-file-056LAMEC.pdf?ref=blog.financely.io)
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](https://www.icann.org/en/contracted-parties/accredited-registrars/resources/domain-name-transfers/policy?ref=blog.financely.io)
3. Financely deal submission: [https://www.financely.io/deal-submission](https://www.financely.io/deal-submission?ref=blog.financely.io)