Is .name a Good Domain for a Personal Website and Email?

.name is a sensible choice for a personal website or email identity when the complete domain clearly reads as a person's name. It was created for that purpose, is still classified by IANA as a restricted generic top-level domain, and remains subject to personal-name eligibility rules.

The extension is less familiar than .com, so it works best when clarity and long-term ownership matter more than instant recognition. A clean address such as alexrivera.name can hold a portfolio, biography, speaking page, contact details, and a custom mailbox. A forced or ambiguous combination can make the same extension feel awkward.

1) Start with the personal-name rule

.name is not simply a generic label for any project. IANA's current record classifies it as a restricted generic TLD, lists VeriSign Information Services as the sponsoring organization, and records its registration in the root on 17 August 2001.

The ICANN registration restrictions say a personal-name registration can correspond to:

• an individual's own personal name;
• a name by which that individual is commonly known;
• the personal name of a fictional character when the registrant has trademark or service-mark rights in it; or
• one of those names with permitted numeric characters added to distinguish it.

ICANN's current dispute-policy overview still identifies .name as the restricted TLD covered by the Eligibility Requirements Dispute Resolution Policy, or ERDRP. That means an available checkout result is not permission to ignore the eligibility terms.

This distinction changes the buying question. Do not ask only whether brightstudio.name is available. Ask whether the string is your personal name, a name by which you are commonly known, or another category allowed by the policy. If the intended label is purely a company, product, campaign, or keyword, use a more suitable namespace.

2) Judge the complete address

A TLD is only the final part of the identity. Read the label and extension together:

• alexrivera.name reads naturally as a personal identity;
• drleila.name may read clearly if that is how the person is commonly known and the use does not misstate credentials;
• rivera.name may fit a family-name identity, subject to the applicable registration terms;
• bestaccounting.name reads like a keyword phrase rather than a person;
• launchwidget.name reads like a product and needs a different extension.

The best candidates are short enough to type, unambiguous when spoken, and stable even when a job changes. Use the %%EDITORIAL_0%% page to check the extension context, but make the decision from the complete address.

Before buying, write the candidate in four places: a résumé header, an email signature, a conference slide, and a spoken introduction. If listeners are likely to type .name.com, forget the extension, or mishear the label, compare a .com, a country-code option, or another personal extension.

3) Match the domain to the site's job

For a personal site, .name can create a durable home that is independent of an employer or social platform. The domain can lead to:

• a biography and contact page;
• a portfolio or case-study archive;
• writing, research, talks, or media appearances;
• a résumé or curriculum vitae;
• a booking page;
• verified links to social profiles; and
• a private family page when access controls are configured separately.

That breadth is useful for an individual whose work spans several roles. The name can remain stable while the content changes.

The fit weakens when the site is expected to become a company with several owners, a product with its own identity, or a marketplace that may be sold independently. A personal domain can still point to the venture, but it should not be the only asset holding a brand that is no longer person-led.

Use a simple ownership test: if the person changed employers or closed the current business, would the address still make sense? If yes, .name may be a durable personal layer. If no, compare the business name across multiple endings.

4) Separate a mailbox from forwarding

Buying alexrivera.name does not create an inbox by itself. A normal custom address such as hello@alexrivera.name needs an email service. The owner verifies the domain and publishes the DNS records required by that provider.

For example, Google's current Workspace setup guide says incoming mail is directed using MX records. The guide requires the administrator to add Google's MX record in the domain settings and activate Gmail for the domain. Other mail hosts publish their own values and verification steps.

Email forwarding is different. A registrar may forward messages sent to an address on the domain into an existing mailbox, but forwarding alone may not provide a full hosted inbox, independent sending, storage, calendars, or the same administration controls. Check exactly what the provider includes.

The practical stack is:

1. domain registration;
2. DNS hosting;
3. a mailbox or forwarding service;
4. MX and verification records;
5. sender-authentication records required by the mail provider; and
6. renewal control for both the domain and mail subscription.

The earlier email guide covers the identity and mail-hosting distinction in more detail.

5) Recognize the older .name email product

.name has an unusual registry design. VeriSign's current registry-registrar agreement defines a registered name as a second-level email address, a registered third-level domain, or a registered second-level domain. It gives john@smith.name as an example of the registry-level second-level email product and separately refers to names such as john.smith.name.

That historical structure explains why older .name documentation may discuss third-level domains and SLD email forwarding. It does not mean every registrar currently offers every product described in the registry agreement.

The two current retail pages reviewed for this article, Porkbun and Namecheap, advertise ordinary second-level .name domain searches and prices. Neither page used for the price comparison promises the registry's distinct SLD email product in its standard offer. If a seller presents first@last.name as a separate registration, verify its transfer, renewal, DNS, forwarding, and cancellation rules before purchase.

For most buyers, the simpler route is a standard domain such as firstlast.name plus an address such as hello@firstlast.name. It uses familiar DNS and email-hosting controls and avoids depending on a niche registry-level forwarding product.

6) Plan for recognition and typing

.name communicates personal ownership once the reader sees the full address. The weakness appears when the address is heard without context. .com is more likely to be assumed, and some people may treat “name” as an instruction rather than the literal extension.

Run a five-person test before committing:

1. say the address once without spelling it;
2. ask each person to write what they heard;
3. check whether they included .name correctly;
4. repeat the test with the proposed email address; and
5. compare the error rate with the best alternative.

Also inspect the label-extension boundary. Repeated words such as myname.name may be memorable or clumsy depending on the label. Consecutive sounds, hyphens, initials, and transliterated names need extra testing.

If a matching .com is unavailable, do not assume the .name version is automatically second-best. A concise exact personal name can be clearer than a long .com with filler words. Compare the complete candidates rather than ranking extensions alone.

7) Keep search claims modest

Google says its systems can return a page on a new generic top-level domain when it is the best result and that keywords in a TLD do not create an advantage or disadvantage. .name should therefore be chosen for identity and availability, not for an assumed ranking boost.

Search performance still depends on the site and its pages: useful content, clear titles, crawlable navigation, relevant links, performance, and the match between the page and the searcher's question. A portfolio with original project evidence has a stronger basis than a thin page relying on the word after the dot.

The extension can improve human interpretation. Seeing .name may tell a visitor that the site belongs to a person. That is a messaging effect, not a guaranteed ranking factor.

8) Compare current prices

Prices below were checked on 16 August 2026 for standard, non-premium .name registrations. They are snapshots, not permanent quotes.

Porkbun's current pricing lists $7.31 for .name registration, renewal, and transfer. The three-year scenario is $7.31 × 3 = $21.93 if the displayed standard price remains applicable to all three years.

Namecheap's current page lists $8.98 for one-year registration, $9.98 for renewal, $8.98 for transfer, and $26.94 for a displayed three-year registration. Its page also warns that a $0.20 ICANN fee may be added for affected transactions and that premium names, promotions, taxes, or checkout conditions can change the total.

Price is only one line of the decision. Check renewal, transfer support, privacy eligibility, DNS features, email service, account security, and the registrar's handling of .name restrictions.

9) Check availability and conflicts

An “available” result means the registrar can currently attempt to create that registration. It does not establish that the buyer satisfies .name eligibility or has rights to another person's name or mark.

Before checkout:

• confirm that the string matches your legal name, commonly known name, or another permitted category;
• search the web for the exact phrase and close variants;
• inspect trademark and professional-name conflicts relevant to the use;
• check the candidate in the registry's RDAP data if it is already registered;
• compare common misspellings and the matching .com or country-code name;
• save the registrar's live price and terms; and
• avoid implying affiliation with another person.

ICANN's ERDRP says the registrant represents that the registered name conforms to the eligibility requirements. A challenge can lead to cancellation or transfer. The registry does not pre-approve every personal-name claim, so checkout friction is not the same as policy compliance.

Use domain research to inspect a registered candidate, then compare available variations in Bulk Search.

10) Build for long-term ownership

A personal domain is valuable when it survives platform and career changes. Protect that continuity:

• register through an account controlled by the individual, not a former employer;
• use a recovery address that does not depend on the new domain;
• enable multi-factor authentication at the registrar and email provider;
• turn on renewal reminders and verify the payment method;
• export site content and maintain DNS records in a recoverable form;
• document the email migration process before changing providers; and
• keep the administrative contact current.

If the domain becomes the primary email identity, expiration has a larger impact than a broken website. Mail can stop, password resets may fail, and another service may still treat the old address as the account owner. Renew early and keep a separate recovery channel.

For a family or estate context, document who can manage the registration if the owner becomes unavailable. Registrar account access and legal succession are operational questions that the extension itself does not solve.

11) Apply the decision rule

Choose .name when all of these are true:

• the registration fits the personal-name eligibility rules;
• the full address reads cleanly as the person's identity;
• the site is expected to remain person-led;
• the audience can learn or reliably type the extension;
• a custom mailbox or forwarding setup has been priced separately; and
• the renewal and recovery plan is sustainable.

Choose another extension when the proposed label is primarily a company, product, keyword, or campaign; when the audience repeatedly assumes .com; or when the name-extension combination needs explanation every time it appears.

The strongest .name purchase is not the cleverest available string. It is a compliant personal identity that still reads correctly after the current role, platform, or project changes.