Changing domain name registrar from Turbify to Namecheap

According to https://getreadyletsgrow.com/turbify-url-changes/, "On June 10, 2022, Verizon's Small Business Essentials (formerly Yahoo Small Business) was acquired by Infinite Computer Solutions. It is being rebranded as Turbify." I decided to change domain name registrar from Turbify to Namecheap.

I am sharing below my DNS Records configured from the Turbify interface.

Turbify A and CNAME Records:

Turbify A and CNAME Records

Turbify TXT Records:

Turbify TXT Records

Turbify MX Records:

Turbify MX Records

Turbify Name Servers:

Turbify NS Records

How to get the authorization code to transfer a domain away from Turbify is explained at https://help.turbify.com/s/article/how-do-i-transfer-my-domain-to-a-new-registrar. By clicking the "View" link, I could see the Authorization Code:

Get Turbify domain transfer Authorization Code

A pop-up window appeared with the "Follow these steps" link:

Turbify Follow These Steps Authorization Code link

Finally, I received could obtain the Authorization Code to transfer my domain away from Turbify.

Authorization Code to transfer domain away from Turbify

From https://www.namecheap.com/ I verified that my domain jaimemontoya.com was eligible for transfer. Then I provided the Authorization Code that I obtained from Turbify:

Authorization Code to transfer domain away from Turbify

I completed my domain transfer order from Namecheap:

Authorization Code to transfer domain away from Turbify

I received my Namecheap order confirmation and purchase summary:

Namecheap order confirmation and purchase summary

In my Namecheap Dashboard, I found jaimemontoya.com with an alert and the following status: "Awaiting email confirmation.".

Namecheap order confirmation and purchase summary

I received an email from Turbify to notify me about the transfer away request for jaimemontoya.com:

Transfer away request from Turbify for jaimemontoya.com

I clicked the "website" link from the email above, and it contained the following:

Turbify domain transfer confirmation

I clicked the "ACCEPT TRANSFER" button. I was expecting to get some success confirmation message, but I did not. When I tried reloading https://approve.domainadmin.com/transfer/?away=1&domain=jaimemontoya.com&id=mN6uYHbaS4, I received this message:

No active transfer request found / AAT

From the Namecheap Dashboard, the status message changed from "Awaiting email confirmation" to "Awaiting release from previous registrar":

No active transfer request found / AAT

According to https://www.namecheap.com/support/knowledgebase/article.aspx/270/83/what-does-awaiting-release-from-previous-registrar-transfer-status-mean/, that status means that "there are no issues at this time, the transfer is being processed normally."

I received a Domain Transfer Complete confirmation email from Namecheap:

Namecheap Domain Transfer Complete email

This is the body of the Domain Transfer Complete confirmation email that I received from Namecheap:

Namecheap Domain Transfer Complete email

The domain jaimemontoya.com appeared in the Namecheap Dashboard with the "ACTIVE" status:

jaimemontoya.com successfully transferred in the Namecheap Dashboard

From my Namecheap Dashboard Domain configuration, I found that the NAMESERVERS were pointing to ns1.turbify.com and ns2.turbify.com:

NAMESERVERS still pointing to Turbify

I changed the NAMESERVERS to these values: ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com:

NAMESERVERS changed to DigitalOcean

I already had the DNS Records configured for jaimemontoya.com in the DigitalOcean domains interface:

DigitalOcean domains DNS Records

I was missing MX Records. I added them by clicking the "Add Gmail MX Records" button.:

Add Gmail MX Records

Five MX Records were added after clicking the "Add Gmail XM Records" button:

MX Records added successfully

The steps I followed to setup DKIM records were:

  1. Login to my Google Workspace Admin Console from https://admin.google.com/:
    Google Workspace Admin Console

  2. Go to Apps > Google Workspace > Gmail:
    Google Workspace Admin Console

  3. Click on 'Authenticate email':
    Google Workspace Admin Console

  4. Click on 'Generate New Record'. I did not need to follow this step because I had already done it in the past. I saw the status as "Not authenticating email":
    DKIM authentication status: Not authenticating email

  5. Click on the 'Generate'. No need to follow this step because I had already done it in the past.
  6. Login to my domain host control panel using credentials. For me, it means logging in to my DigitalOcean account.
  7. Locate the page to setup TXT record. That means navigating to the DNS Records section from my DigitalOcean account.
  8. Create a TXT record with the following details:
    Type: TXT
    Host: google._domainkey
    Value: (Paste the generated value Eg: v=DKIM1; k=rsa;...)
    TTL: 1 hour / Default value
    Creating TXT Record for DKIM

  9. Save changes. NB: The field names might be different for your provider. DNS TXT record field names can vary slightly from provider to provider.
    TXT Record for DKIM

After adding the DKIM in the domain control panel, please go back to admin console where we generated the DKIM record value and please click on 'Start Authentication':

DKIM start authentication

The new status is "Authenticating email with DKIM":

DKIM start authentication

When you add the DKIM record at your domain, it can take up to 48 hours for DKIM authentication to start working.

The steps I followed to setup SPF Records were:

  1. Login to your domain host provider. In my case, logging in to my DigitalOcean account.
  2. Locate the page to setup TXT record. In my case, navigating to the DNS Records section from my DigitalOcean account.
  3. Create a TXT Record with the following details:
    Type: TXT
    Host: @
    Value: v=spf1 include:_spf.google.com ~all
    TTL: 1 hour (or 3600 seconds)
    Create TXT Record for SPF

  4. Save changes. NB: The field names might be different for your provider. DNS TXT record field names can vary slightly from provider to provider.
    SPF Record created as TXT Record
Published: 2:48 AM GMT · Nov 29, 2023