Sign inCreate free account

DOMAIN EXTENSION GUIDE

.did Domain Names

Pre-launch application

.did is a proposed identity-themed top-level domain that suggests decentralised identity, credentials and trust-led digital services. Publicly announced information identifies Starlight Registry (Namecheap) as the applicant associated with.did, while the string remains in pre-launch status rather than an active root-zone delegation. (rapidwombat.com)

.did registrations are not available yet. Search related extensions or get a launch alert.

Get launch alerts

Application and status facts

Verified status information is kept separate from illustrative naming ideas.

Extension
.did
Current status
Pre-launch applicationRoot Zone Management - IANA
Root-zone delegation status
No root-zone delegation confirmed in recorded public sources.Root Zone Database - IANA
Number of publicly announced claims
1
Contested
No
Application round/programme
ICANN application programme information recorded.Root Zone Management - IANA
Registry operator
Not verified
Registration availability
Public registration is not confirmed by this guide.Root Zone Database - IANA
Last fact checked
2026-08-25

A public application, applicant identity, approval, registry operation, root-zone delegation and live registration availability are separate facts.

Illustrative uses

What could a .did domain be used for?

If delegated,.did would suit identity-centric projects that want a clear signal of authentication, verification and digital trust.

Digital identity profilesCould be used for identity hubs that present verified credentials, logins and personal or organisational identity signals.
Decentralised identity toolsSuitable for services built around self-sovereign identity, wallet-based identity and portable credentials.
Authentication servicesCould support products focused on sign-in, access control, identity checks and verification flows.
Developer identity projectsA natural fit for platforms building identity APIs, authentication infrastructure or identity orchestration.
Credential walletsCould be used by applications that manage attestations, badges, certificates and proofs.
Identity standards communitiesUseful for groups discussing standards, interoperability and privacy-preserving identity design.
Trust and verification servicesWell suited to tools that help confirm people, organisations, devices or data sources.
Web3 identity brandsCould suit blockchain-adjacent identity products that want a short, thematic namespace.

Domain name ideas

Example names only. Illustrative examples only. Availability has not been checked.

alice.didverify.didvault.didlogin.didtrust.didapi.did

Possible audiences

Who is .did for?

  • Identity startups
  • Authentication vendors
  • Decentralised web builders
  • Developers and platform teams
  • Standards and protocol communities
  • Security and compliance teams

Benefits and considerations

Benefits

  • Strong thematic fit
  • Short and memorable
  • Flexible for multiple identity models

Considerations

  • Not yet delegated
  • Potential similarity review risk
  • Meaning may be interpreted in different ways

Related domain extensions

.authAuthentication-oriented naming concept.View extension

Relevant DomainUI marketplace listings

No closely matched public DomainUI marketplace listings are available for this guide right now.

Browse domains for sale

Frequently asked questions

Is.did live and available to register?

No public root-zone delegation is shown in the IANA Root Zone Database, so.did should be treated as pre-launch rather than live.

What does.did suggest?

It most naturally suggests decentralised identity, digital identity or verification-related services.

Who is associated with.did?

Publicly announced information identifies Starlight Registry (Namecheap) as the applicant associated with.did.

Would.did suit a consumer product?

Yes, especially if the product focuses on identity profiles, sign-in, credentials or verification.

Could.did work for developer tools?

Yes. The name is well suited to APIs, SDKs and infrastructure for authentication or identity management.

What should be checked before using a proposed TLD brand?

It is sensible to confirm delegation status, evaluation outcomes and any later registry policies before planning launch materials.

Sources and review information