Skip to content
REAL DESTINATIONS. PRACTICAL IDEAS.

Brand TLDs in Action

These public examples show Brand TLDs supporting campaign destinations, customer services, dealer networks and enterprise technology. Each illustrates a practical application, not a verified financial return that will differ based on your situation.

Use Cases: Marketing, Customer, Channel and Service.

Explore how established brands are using their namespaces and consider where similar approaches may be relevant to your business.

10 showing

01 / Amazon Web Services · .aws

A consistent naming structure for cloud services

Service
Amazon Web Services .aws
  • ec2.us-west-2.api.aws Compute · regional API
  • lambda.us-east-1.api.aws Serverless · regional API
  • sqs.us-east-1.api.aws Messaging · regional API
  • iam.global.api.aws Identity · global scope

One documented regional pattern

ec2
Service
us-west-2
Region
api
Namespace
aws
Brand TLD

A documented pattern is service.region.api.aws. Check each service’s regional availability and naming rules.

  • Service naming

Official infrastructure documentation

What is deployed

AWS documents regional API addresses such as ec2.us-west-2.api.aws, lambda.us-east-1.api.aws and sqs.us-east-1.api.aws. The hierarchy identifies the service, region and API namespace. Global services can use a different scope: IAM documents iam.global.api.aws.

Potential value

  • A predictable naming pattern could simplify service inventories, configuration and endpoint governance as infrastructure expands.
  • AWS documents dual-stack support for these services. That capability comes from the implementation and service support, rather than the suffix alone.

What to measure Configuration errors, time to onboard a service and coverage of the approved endpoint inventory.

02 / Google · .google

A destination that reinforces the campaign

Marketing
Google .google
  • grow.google Skills and learning
  • safety.google Safety education
  • sustainability.google Environmental programmes

Purpose before the dot. Brand after the dot.

  • Campaigns

Public programme destinations reviewed

What is deployed

Google gives major programmes descriptive destinations: grow.google for skills and training, safety.google for safety education, and sustainability.google for environmental initiatives and reporting. Each name introduces the purpose before the visitor reaches the page.

Potential value

  • A short programme-and-brand pairing could make links easier to recognise, communicate and reuse across channels.
  • Distinct programme destinations can support focused audience journeys while retaining a visible relationship to the masterbrand.

What to measure Unaided address recall, direct visits, journey completion and consistency across campaign materials.

03 / Audi · .audi

A consistent brand identity across dealers

Channel
Audi .audi
  • audi-zentrum-muenchen-hochstrasse.audi Munich · sales and service
  • audi-zentrum-baden-baden.audi Baden-Baden · local appointments
  • audi-zentrum-essen.audi Essen · vehicles and servicing

The local business name changes. The brand namespace stays consistent. The reviewed sites use a www prefix.

  • Dealer networks

Three dealer destinations reviewed

What is deployed

Audi dealers in Munich, Baden-Baden and Essen use individual .audi hostnames. The reviewed destinations combine local contact details and opening hours with vehicle sales, servicing and appointment routes. The dealer identity varies while the brand ending remains consistent.

Potential value

  • A recognisable dealer-name pattern could help customers connect local service with the manufacturer’s brand.
  • A governed naming model could make dealer onboarding, changes and retirement more consistent across the network.

What to measure Dealer adoption, local lead completion, naming consistency and time to update or retire dealer destinations.

04 / DVAG / Allfinanz · .dvag + .allfinanz

Connecting advisers to a national brand

Channel
DVAG / Allfinanz .dvag + .allfinanz
  • jpeters.dvag Redirects to Jürgen Peters’ adviser profile
  • patrickschmidt.allfinanz Redirects to Patrick Schmidt’s adviser profile
  • kundenportal.dvag Customer portal entrance

The adviser aliases route to existing profiles. The reviewed profiles are not hosted on the brand-TLD addresses.

  • Agent networks
  • Customer portals

Current adviser redirects verified

What is deployed

jpeters.dvag and patrickschmidt.allfinanz redirect to the named advisers’ current profiles on dvag.de and allfinanz-dvag.de. Those profiles offer contact and appointment routes and link to the DVAG customer portal. The brand-TLD address works as a personal entrance to an existing platform.

Potential value

  • A personal adviser address could be easier to share on a business card, in a conversation or in a local campaign.
  • Separating the public address from the destination platform could preserve continuity when profiles or systems change.

What to measure Use of adviser links, qualified enquiries, redirect accuracy and time to update an adviser’s destination.

05 / BNP Paribas · .bnpparibas

Branded destinations for sponsorship programmes

Marketing
BNP Paribas .bnpparibas
  • welovecinema.bnpparibas Cinema community
  • wearetennis.bnpparibas Tennis content and engagement
  • mabanque.bnpparibas Related retail banking destination

A shared brand ending connects different audience experiences.

  • Campaigns

Public sponsorship destinations reviewed

What is deployed

BNP Paribas uses welovecinema.bnpparibas for its cinema community and wearetennis.bnpparibas for tennis content and engagement. The same TLD also supports retail banking, corporate communications and specialist businesses, giving sponsorship activity an explicit connection to the group.

Potential value

  • An interest-led address could extend a sponsorship beyond an event and give audiences a destination they can return to.
  • Consistent brand ownership in the address could connect editorial, community and commercial touchpoints without giving every initiative the same website structure.

What to measure Returning visitors, community participation, campaign-to-site journeys and audience recognition of the sponsor.

06 / E.Leclerc · .leclerc

A recognizable family of trusted customer services

Customer
E.Leclerc .leclerc
  • voyages.leclerc Travel
  • location.leclerc Vehicle rental and agencies
  • traiteur.leclerc Catering and local pickup
  • quiestlemoinscher.leclerc Price-comparison proposition

Several distinct services, expressed through one brand vocabulary.

  • Campaigns
  • Customer portals

Service pages and account guide reviewed

What is deployed

E.Leclerc uses descriptive .leclerc destinations for travel, vehicle rental, catering and price comparison. The rental site combines agency selection with booking fields; catering connects online ordering with local pickup. An official account guide describes shared E.Leclerc credentials across participating services.

Potential value

  • Service names could help customers discover the breadth of an offer while retaining the retail brand relationship.
  • A coordinated address and account model could reduce friction between services, provided the underlying account experience is implemented consistently.

What to measure Cross-service discovery, account reuse, completed bookings and online-to-store journey completion.

07 / Sharp · .sharp

Supporting the customer relationship after purchase

Customer
Sharp .sharp
  • cocoroplus.jp.sharp Connected-appliance service family
  • cocoromembers.jp.sharp Membership and product ownership
  • cocorostore.jp.sharp Related official store and account terms

A customer-facing view of a connected-product ecosystem.

  • Customer portals
  • Connected ecosystems

Official connected-service descriptions

What is deployed

Sharp presents its COCORO+ connected-appliance services at cocoroplus.jp.sharp. COCORO HOME describes connecting appliances, usage information, notifications and remote controls. COCORO MEMBERS provides product registration, appliance management, support and member benefits; the related store documents COCORO ID use.

Potential value

  • A connected set of service and account destinations could help customers find ongoing support and get more use from products they already own.
  • A consistent branded service family could support discovery of complementary appliances, content and services.

What to measure Product registrations, active service use, support completion and adoption across compatible devices.

08 / Microsoft · .microsoft

A brand consistent namespace for enterprise applications

Service
Microsoft .microsoft
  • m365.cloud.microsoft Microsoft 365 Copilot entrance
  • teams.cloud.microsoft Teams application entrance
  • outlook.cloud.microsoft Outlook web application

The published first-party restriction applies specifically to *.cloud.microsoft.

  • Customer portals
  • Service naming
  • Connected ecosystems

Published policy and public app entrances

What is deployed

Microsoft groups application destinations under cloud.microsoft, including m365.cloud.microsoft, teams.cloud.microsoft and outlook.cloud.microsoft. Its published policy restricts this namespace to Microsoft-managed services and excludes customer-hosted workloads. Public entry points and application shells were reviewed.

Potential value

  • A stable service family could make application destinations easier for users and IT teams to recognise.
  • Published namespace restrictions can support network-policy decisions alongside identity, tenant and application controls.

What to measure Endpoint-policy maintenance, service-access incidents and user recognition of approved application destinations.

09 / Komatsu · .komatsu

Connect equipment ownership with service.

Customer
Komatsu .komatsu
  • mykomatsu.komatsu Customer, fleet and parts services
  • usedequipment.komatsu Used-equipment marketplace
  • kuec-auction.komatsu Dealer auction application

Customers, equipment and dealers meet around the ownership lifecycle.

  • Customer portals
  • Dealer networks
  • Connected ecosystems

Public storefront and service terms reviewed

What is deployed

MyKomatsu presents a parts storefront and customer sign-in. Its official terms describe fleet management, machine data, manuals, training and parts orders from authorised dealers in the United States and Canada. Related .komatsu destinations support used equipment and dealer auctions.

Potential value

  • A branded service entrance could connect equipment ownership, maintenance and dealer support through a recognisable journey.
  • Related aftermarket destinations could help extend the customer relationship across the machine’s working life.

What to measure Portal adoption, parts-order completion, support resolution and use of documented fleet services.

10 / Amazon Sidewalk · .amazon

A brand consistent destination structure for developers.

Service
Amazon Sidewalk .amazon
  • sidewalk.amazon Developer programme
  • docs.sidewalk.amazon Technical and manufacturing documentation
  • 360.sidewalk.amazon Device-maker onboarding portal

One programme hierarchy, from introduction to documented operational workflows.

  • Service naming
  • Connected ecosystems

Official workflow documentation and portal shell

What is deployed

Amazon Sidewalk uses sidewalk.amazon, docs.sidewalk.amazon and 360.sidewalk.amazon for its developer programme, technical documentation and onboarding portal. Official manufacturing instructions direct security-profile allowlisting and device-provisioning support requests through Sidewalk 360.

Potential value

  • A coherent programme, documentation and portal hierarchy could make the developer journey easier to navigate.
  • Stable destinations could support consistent onboarding and governance as new device makers join an ecosystem.

What to measure Onboarding completion, documentation-to-portal journeys, support volume and time to qualify a device integration.

FROM CONCEPT TO PUBLIC EVIDENCE

How public examples relate to the seven use cases.

The examples illustrate the marketing, customer, channel and service categories. Some directly match the stated use cases; others demonstrate only selected elements. They are provided for inspiration.

1. Campaigns people trust and remember

Examples in the research

Google programmes; BNP Paribas cinema and tennis; E.Leclerc price proposition; Apple Wallet; DVAG coaching

Strength of connection

Direct naming examples
Memorable programmes, sponsorship communities and campaign destinations are visible. Better recall or conversion remains a hypothesis unless measured.

2. NXDOMAIN: opportunities in data insights

Examples in the research

No named-brand deployment verified

Strength of connection

Evidence gap
Brands utilizing the NXD capability cannot be verified by public records.

3. Recognizable customer portals

Examples in the research

Microsoft 365; MyKomatsu; Sharp COCORO MEMBERS; BNP Paribas retail banking; DVAG customer portal; MyDHL+

Strength of connection

Direct public entrances; workflows documented
Public entry points and official service descriptions were reviewed. Sign-in, purchases, account functions and machine telemetry were not exercised.

4. Dealer networks under brand control

Examples in the research

Audi dealer hostnames; SEAT dealer locator/pages; Komatsu used-equipment services

Strength of connection

Direct dealer hosts plus shared-platform examples
Audi supplies the clearest dealer-name hostname pattern. SEAT and Komatsu also show dealer services within shared destinations; that is a different deployment model.

5. Authorized agent and adviser networks

Examples in the research

DVAG and Allfinanz adviser aliases; MMA town-based agent aliases; Bradesco correspondent hub

Strength of connection

Direct adviser and agent address examples
The reviewed DVAG/Allfinanz aliases redirect to current profiles on other domains. MMA town addresses worked from HTTP; HTTPS origins were not verified. Do not imply universal deployment across a network.

6. Consistent service naming and governed infrastructure

Examples in the research

AWS regional/global APIs; SAP tenant and identity patterns; Microsoft cloud.microsoft; BNP Paribas nested business/API names

Strength of connection

Strong official infrastructure evidence
AWS and SAP documentation establish actual service patterns. Namespace policy, credential handling and operational controls must be evaluated separately.

7. Trusted connections across networks

Examples in the research

Amazon Sidewalk developer onboarding; Sharp connected appliances; MyKomatsu machine/dealer ecosystem; Microsoft governed SaaS namespace

Strength of connection

Partial connection; architecture not established
These show connected services, shared identities or governed application destinations. The sources do not establish that a brand TLD by itself provides a trust mesh, authenticates devices or routes their traffic.

PUT YOUR BRAND TLD TO WORK

Which business objective should your namespace serve?

Start with the customer experience, commercial opportunity or operating challenge you want to improve. Authentic Web’s Brand Registry Introduction Path connects that choice to a strategic plan, execution plan and go-to-market programme.

This is a broad public-web investigation, not a complete enumeration of all brand TLD zones. Private applications, unindexed services, internal DNS, device traffic and NXDOMAIN analytics cannot be exhaustively discovered through public search. Read-only public content was reviewed; authenticated workflows and transactions were not tested.