Service Status Submit a Request go back to rebel.com

How to Manage Email Forwarding for a .NAME Domain (firstname.lastname.name)

Articles in this section

See more
Avatar
Israel
Updated
Follow
If you registered a personal .NAME domain during its original release (such as john.smith.name), your registration included a unique, registry-level email forwarding feature built directly into the domain itself (e.g., john@smith.name).
 
Because this forwarding mechanism runs on the central registry's infrastructure (Verisign) rather than a standard web hosting server, it operates differently from traditional email packages.
 

Key Information About Legacy .NAME Email Forwarding

  • No Web Hosting Required: Your .NAME email forwarder is bundled directly with your domain registration. It does not require a paid email or web hosting package to function.
  • No Account Dashboard Toggles: Because the forwarding mapping is stored on the central domain registry's master ledger, there are no controls to edit or update this destination address inside your standard account portal.
  • Direct Mail Routing: Emails sent to your firstname@lastname.name address are automatically relayed by the central registry to your designated personal inbox (such as a Gmail, Yahoo, or private email account).

How to Update Your Forwarding Address

If you need to change the destination inbox where your .NAME emails are delivered, our Support Team must manually update the master registry settings on your behalf.
 
To request an update, please contact Rebel Support or submit a ticket with the following details:
  1. Your .NAME Domain Name: (e.g., john.smith.name)
  2. Your .NAME Email Address: (e.g., john@smith.name)
  3. The New Destination Email Address: (The personal inbox where you want your incoming emails delivered).
Once received, an administrator will process the update directly with the registry operator. Updates typically take effect across global mail networks within a few hours.
 

Important Note on Modern Email Delivery (SPF & DMARC)

Because registry-level email forwarding was designed in the early 2000s, it relays incoming messages without modern email signing protocols (such as SRS). Today, some external mail providers (like Gmail, Outlook, or Yahoo) strictly enforce SPF and DMARC security checks, which may occasionally cause forwarded emails to be filtered into spam or rejected by the receiving server.
 
If you require guaranteed email deliverability, custom outbound sending (SMTP), or full mailbox management for your domain, please reach out to our support team to explore setting up a dedicated email hosting package.

Comments

0 comments

Please sign in to leave a comment.