Onchain TLDs and car makers: what to check

An automotive group’s name is rarely just a name. It anchors a marque, spreads across model lines, travels through a dealer network in many countries, and lives more and more inside the vehicles it sells. When the same string exists as an onchain top-level domain (TLD), a namespace recorded on a public blockchain outside the ICANN domain name system, the exposure is not generic brand risk. It touches the retail network, the financing arm, the software in the vehicle, and the payment flows that run through all of them.

This guide is written for the head of trademarks at an automotive group, or for whoever on the legal and brand protection team owns the meeting point of IP and digital infrastructure. It does not explain what an onchain TLD is in any depth: that background is on the page for brands and legal teams. What follows covers what is particular to this sector, the functions where the exposure sits, and a checklist that can be assigned to the right people the same day.

The general picture fits in a few lines. Take Freename as the reference registry: there, a TLD such as .yourbrand is a token recorded onchain and held in a wallet. Freename charges no annual renewal fee on that TLD, and issuing names under it is reserved to whoever holds it. Its record is public, and a block explorer lets anyone check it, a trademark team included. Because these names are resolved outside the ICANN DNS root, a buyer’s or dealer’s ordinary browser does not open them without support, and the coverage that wallets and browsers offer is partial and changes. The UDRP, the dispute procedure that binds registrants of DNS domains through their registration contracts, does not reach these names. A useful first measure is the Namespace Exposure Score, a free tool that scores how exposed a brand is onchain.

Why automotive is different from a generic brand

Most brand protection teams treat domain risk as a second-level problem: someone registers a domain containing the brand and you pursue it. The onchain TLD changes the structure, because the extension itself is the asset. Whoever holds .yourbrand decides every name under that string. A name such as finance.yourbrand, dealer.yourbrand or service.yourbrand is issued by that holder, whoever it is.

Automotive makes this structural point heavier for reasons that do not apply to most sectors.

Number of touchpoints. A consumer goods brand may run a handful of official web properties. An automotive group runs a very large number: dealers, importers, national sales companies, financing portals, fleet platforms, owner apps and the vehicle’s own connected systems. Each of those touchpoints corresponds to a plausible name under the TLD. The wider the legitimate footprint, the more a namespace outside the group’s control can be mistaken for part of it.

Transaction size and financing. A vehicle purchase is large, often financed, and involves a transfer of legal title. A buyer shown a payment name or a contract portal that ends in the marque has little reason to ask who issued it. The trust placed in the marque passes to any name under the matching TLD, and the customer does not see that passage happen.

The dealer channel. Dealers are independent businesses that trade under the marque by contract. The manufacturer sets standards for signage and websites but cannot inspect every digital tool a dealer adopts. Dealers are therefore the population most likely to meet a name under the TLD in an ordinary business process, and the least equipped to know who issued it.

Rules on vehicle sales. In most markets the sale and financing of a vehicle is regulated more closely than general retail, with rules on distance selling, finance disclosure and advertising that vary by country. A name that appears to come from the manufacturer and leads a consumer into a transaction raises questions that a look-alike site for an inexpensive product does not.

Connected vehicles. The vehicle is a networked device. Software updates, remote diagnostics and in-vehicle purchases all rely on named endpoints. This layer has no parallel in most other sectors and is examined on its own below.

Marques, model names and dealer networks: three layers of names

The exposure does not sit at a single point. It spans three naming layers, each with its own profile and its own internal owner.

The marque

The house brand, the word that appears on the car, is the primary exposure. A TLD matching that string can carry names for every function: pay.yourbrand, update.yourbrand, recall.yourbrand. A group with several marques has this layer once per marque, and the group’s corporate name is one more string to add. The trademark team owns this layer, with the chief information security officer (CISO) alongside for anything that touches systems.

Model names

Model names are sub-brands, and many are registered as trademarks in their own right. A TLD matching a model name is a narrower namespace but not a trivial one, because owners identify with the model as much as with the marque. The sensitive uses are the ones tied to safety and ownership: recall notices, software update notices and invitations to an owner portal.

Model names also behave differently from the marque as trademarks. Some are ordinary words, place names or numbers and letters, which are harder to claim across every class and every country. Some are shared with unrelated businesses in other industries. Heritage models that left production long ago keep a following among collectors and clubs, and a name that the group no longer uses commercially may be the one that enthusiasts use most. The review therefore needs a ranking of model names: current volume models first, then names planned for coming launches (handled with the confidentiality a launch requires), then heritage names. Product and brand teams own this layer, and the trademark team supplies the registration position for each name.

Dealer and importer names

Dealers often trade under names that combine the marque with a place or with the dealer’s own business name. Under a TLD, the equivalent is a name such as cityname.yourbrand or dealername.yourbrand. Because only the holder of the TLD can issue names under it, a TLD held outside the group means those names can be issued to anyone, including a business with no franchise agreement.

The manufacturer rarely holds every dealer agreement from one legal entity. National sales companies and independent importers carry those relationships, market by market. The review of this layer therefore includes network operations and the regional legal teams, not the central trademark function alone.

Connected vehicles and software agents that act for the owner or the manufacturer

A connected vehicle accepts over-the-air (OTA) software updates, sends telemetry to the manufacturer, lets the owner reach vehicle functions through an app, and in some cases supports purchases from the dashboard. Each of these functions has a named endpoint somewhere in the stack.

It is worth being exact about where things stand. Vehicle systems of this kind run on the DNS and on private infrastructure, with certificates and access controls built for that purpose. For safety-related communication the DNS is simply the better tool, and nothing about onchain naming changes that. The matching onchain TLD becomes an infrastructure question only if the group’s architecture roadmap brings onchain names into owner services, payments or machine-to-machine exchanges. The question to put to the CISO is therefore about the roadmap, not about the present stack.

The second subject is software agents. ERC-8004, titled “Trustless Agents”, is a draft Ethereum standard that defines three registries: identity (each agent is an ERC-721 token pointing to its agent card), reputation (feedback from those it worked with) and validation (independent checks of its work). The standard is not final: as a draft it may change, and how naming registries plug into it is still evolving. Its direction is that an agent acting for a person or an organization carries an identity that others can check.

Automotive gives that idea concrete shapes. An agent could act for the owner: booking a service slot, paying for charging or parking, or settling a toll. An agent could act for the manufacturer: answering an owner’s question about a service campaign, or confirming that a part is genuine. An agent could act for a fleet operator across many vehicles. In each case the other party needs to know whose agent it is dealing with. If agents of this kind are ever named, a name ending in the marque will be read as the manufacturer’s. A group that plans to operate such agents has an interest in doing so under a namespace it controls, and the page on identities for AI agents under a TLD sets out what works and within which limits. The CISO and the product team should follow this subject themselves instead of waiting for the trademark team to raise it.

Dealers and importers who trade under the marque

Dealers speak to customers with the manufacturer’s brand, and customers treat a dealer’s message as carrying the manufacturer’s authority. That is the purpose of a franchise. It also means that a name under .yourbrand, used by a dealer or by someone presenting themselves as one, borrows that authority whether or not the manufacturer had any part in issuing it.

The risk to recognize runs in two directions. In the first, a third party obtains a name under a TLD the group does not hold and presents a consumer-facing site or a payment name that looks like a franchised dealer. In the second, a genuine dealer meets such a name in a business process, in a document, a payment instruction or a supplier message, and treats it as coming from the manufacturer.

Importers add a variation. In markets served by an independent importer, the importer is the face of the marque: it runs the national website, appoints dealers and often handles homologation paperwork and parts supply. An importer that adopts new payment or identity tools does so under its own governance, and the manufacturer may learn of it late. The importer agreement is the place where the use of the marque in names of any kind is governed, and it is worth reading that clause again with onchain names in mind. Whether it covers them is a question for your own counsel in each market.

Two limits keep this in proportion. Onchain names do not open in an ordinary browser without support, so the audience that can reach such a name is narrower than the audience of a website. And a dealer who never uses a wallet or an onchain payment tool is unlikely to meet one. The exposure grows with the adoption of those tools in the network, which is why the first task is to find out where they are in use.

The function that owns this line of the review is network operations or the franchise team, working with the regional legal teams that hold the dealer and importer agreements. The trademark team provides the IP analysis, and the commercial team provides the map of the network.

Financing arms and payment flows

Many automotive groups operate a captive finance company that writes loans, leases and insurance products under the group name or a closely related one. It is the function most directly concerned by payments to a name.

The mechanism is simple to describe. For a finance company, the working example is shaka, an onchain payment router: its payment link can pay out to a name where a raw address would otherwise be used, and the parties’ split is agreed and signed onchain before funds move. It routes funds and does not hold them. The page on payments to a name explains the capability in general. A name is easier to read and to trust than a long string of characters, which is the benefit. The same property means that a name such as finance.yourbrand or lease.yourbrand, issued under a TLD the group does not hold, would carry the visual weight of the financing brand.

The payment flows of a vehicle business are unusually varied, and each is a place to look:

• deposits and reservations taken before delivery, sometimes directly by the manufacturer;
• monthly loan and lease payments collected by the finance company;
• settlements between dealers, importers and the manufacturer for vehicles and parts;
• payments for connected services, charging and subscriptions billed to the owner;
• end-of-lease settlements and buy-backs.

Most of these run on bank transfers and cards, and will continue to. The review does not assume otherwise. It asks the treasury and payments teams whether any onchain payment is in use or under study, in which market, and under which name. The finance company usually has its own compliance function and its own legal entity, so it needs its own line in the review and its own owner.

Exposure by function inside the organization

The table below maps the main internal functions to their exposure and gives each a relative weight. It is a starting point for assigning the checks that follow, and the weights should be adjusted to the group’s own structure.

Two readings of the table matter. The first is that four functions outside the legal department carry a high weight, which is unusual for a naming question and explains why the file cannot stay with the trademark team alone. The second is that the weight for digital infrastructure is conditional: it depends on a roadmap that only the CISO and the product team can describe.

A checklist of nine checks, each with its owner

Run the nine checks in sequence, because each takes as its input what the previous one produced. The first three can be completed by the trademark team alone. The others need an answer from another function, which is why each step names its owner.

1. List every string that carries the group's identityInclude the house brand of each marque, the group name, current and heritage model names, the names of the finance company, and the trading names dealers use with consumers. Add spelling variants in the main languages of the group's markets. Owner: trademark and IP, with marketing and network operations.
2. Measure the exposure of each stringUse the Namespace Exposure Score and the Trademark Name Check on the site, then confirm on the registry which strings exist as TLDs. The result gives the size of the question before any further step. Owner: trademark and IP.
3. Read the registry record of each existing TLDEach record is public, so the team can check it on a block explorer like anyone else. Note the wallet that holds the token and whether names have been issued under the TLD. Draw no conclusion about who the holder is from the wallet address. Owner: trademark and IP, with the CISO's team for the technical reading.
4. Ask about the connected vehicle and agent roadmapAsk the CISO and the product team whether the roadmap brings onchain names into owner services, in-vehicle purchases or agents. If it does, the TLD matching the marque is an infrastructure matter as well as an IP matter. Owner: CISO and product, reporting to group legal.
5. Review the finance company's payment namesAsk treasury and payments whether any onchain payment is in use or planned, and whether names resembling the financing brand appear among the names found in the third check. Owner: finance company legal and treasury.
6. Assess the dealer and importer network by marketStart with the largest markets. Ask each regional legal team whether dealers or importers use onchain names or addresses with customers, and compare the answers with the third check. Owner: network operations and regional legal.
7. Establish the trademark position in each marketConfirm that the marque and the main model names are registered in the classes that cover payments, software and financial services, as well as vehicles. The strength of the position varies by country, and your own counsel decides it. Owner: trademark and IP.
8. Decide on monitoringWhere a TLD exists outside the group and no decision to acquire it has been taken, decide who watches the names of the brand onchain and how often the result is reviewed. Owner: trademark and IP, with the CISO.
9. Assemble the file and restrict itBring the results of the eight previous checks into one document with limited circulation. It is the basis for any later decision. Ask counsel how legal privilege applies to it, since the rules vary by country. Owner: group general counsel.

The options and who should own the file

Once the review is complete, the group has a defined set of options. They are not mutually exclusive.

Acquire the TLD. If the TLD matching the marque exists and the group does not hold it, the most complete answer is to acquire it. Control of the namespace passes to the group, and the uses described in the next section open. An organization can mandate Hush Partners to find and approach the holder: one named partner follows the file from first note to closing, every exchange is covered by a standard mutual NDA, and closing runs through onchain escrow on an aftermarket. The brand namespace recovery page describes the service.

Monitor and wait. If acquisition is not possible for the moment, because the price is not established or no budget has been authorized, namespace watch is the service that monitors the names of a brand onchain while the file progresses. This is a holding position, not a resolution.

Register what does not yet exist. A model name or a secondary string that does not exist as a TLD can be registered by the group itself. There is no annual renewal fee on a Freename TLD, so a string registered once does not create a recurring cost line. What a TLD of this kind is, the group’s team can read on the page on trademark TLDs. For a group with a long list of model names, the ranking made in the review decides where to start.

Take advice on the legal position. The trademark analysis and an acquisition are separate tasks. The position in each market is a matter for your own counsel. Nothing in this guide is legal advice, and the desk does not give any.

The file is best owned by the group general counsel, with the CISO as co-owner for the infrastructure questions and the head of trademarks running it day to day. The finance company and network operations are informed at each stage. They do not need to take part in a negotiation, and keeping them out of it shortens the list of people who know that one is under way.

What a car maker could do with its own TLD

Acquiring the TLD is not only defensive. A group that holds .yourbrand controls the namespace, because only the holder can issue names under it. That has uses specific to a vehicle business. Each of them is bounded by the fact that resolution is partial.

Payment names for the finance company and the network. With a payment router, finance.yourbrand or dealername.yourbrand can be the destination of a payment, with the split between parties agreed onchain before funds move. A settlement between a dealer and the manufacturer, or a deposit shared between a dealer and the finance company, is the kind of flow where an agreed split is the point.

Names for franchised dealers. The group can issue dealername.yourbrand to each franchised dealer, under terms it sets in the dealer agreement. Since no one else can issue a name under the TLD, a name ending in .yourbrand tells the customer that the group stands behind it. That statement is only as good as the group’s own process for issuing names, which becomes a task for network operations.

Names that resolve in wallets. Freename names are supported in Bitcoin.com Wallet, in MetaMask through Freename’s resolver, and in desktop browsers through the Freename Web3 extension. Coverage is partial and changes, and it is not a substitute for the DNS. For owners who pay for a service from a wallet, a readable name is easier to check than a raw address.

Identities for the group’s agents. If the group comes to operate agents for service booking, charging or fleet management, it can name them under the namespace it controls, for example agent.yourbrand. ERC-8004 is a draft and may change, and the link between its identity registry and naming registries is still evolving, so this is a subject to follow and not a plan to commit to.

Names under a model TLD. A group that holds a TLD matching a model name can issue names under it to owners’ clubs or model communities it chooses to recognize. Under Freename’s royalty program, each registration fee paid for a name registered under such a model TLD returns a share to the TLD’s holder, a share advertised at up to half and subject to the registry’s current terms and activation conditions. The program itself carries an annual cost set by the registry, unless the TLD was registered under earlier terms that include it for life, and whether those terms pass to a buyer is to be confirmed with the registry before closing. For a manufacturer the revenue is secondary. The interest is in giving a heritage name a use under the group’s control.

Putting a TLD to work after the transfer is a project of its own, described on the post-transfer activation page. The practical next step is smaller: assign the first three checks to the trademark team, and book the conversation with the CISO about the roadmap. Those two actions tell you whether this is a file for the trademark team or one for the group.

Questions people ask

Does the onchain TLD affect the group’s existing DNS domains?

No. Onchain TLDs and DNS domains are separate systems, and an onchain .yourbrand has no effect on the group’s DNS domains, its websites or its email. The exposure is confined to the places where onchain names are used: wallets, payment routers, supporting browsers and anything the group itself builds on onchain naming.

Is a trademark registration enough to compel a transfer?

Not by itself. The UDRP applies to DNS domains because registrants accept it in their registration contracts, and that mechanism does not extend to onchain TLDs. A trademark may support a claim before the courts of a relevant country, but the outcome and the time it takes depend on local law, on where the holder is and on how the name is used. Your own counsel assesses that position. A negotiated acquisition is a separate route that does not depend on it.

What if the group holds an ICANN dotBrand and does not hold the onchain TLD?

The two do not substitute for each other. A dotBrand is delegated in the DNS under a contract with ICANN, after an application process, and it opens in every browser. An onchain TLD is recorded on a blockchain without ICANN’s involvement and resolves only where it is supported. Holding the first gives no control over the second. The comparison of a dotBrand and an onchain TLD sets out the differences side by side.

Should dealers be told about the review?

Not during the review itself. Dealers are numerous and independent, and a message to the network is in practice a public message. Once the group has decided its position, a short instruction on which names the group issues and which it does not is more useful to a dealer than an explanation of the technology.