Connect Name.com

Step-by-step guide to connect your Name.com account to Domain Pilot

This guide walks you through connecting your Name.com account to Domain Pilot so you can manage all your Name.com domains from a single dashboard.

Before You Begin

  • A Name.com account with at least one domain
  • Access to your Name.com account settings

Step 1: Access API Token Settings

  1. Log in to your Name.com account
  2. Click on your profile icon in the top right
  3. Select Settings
Click on your profile and select Settings
  1. Under Security, click API Tokens
Click API Tokens under Security

Step 2: Generate an API Token

  1. Enter a Token Nickname (e.g., "Domain Pilot")
  2. Click Generate new token
Enter a nickname and click Generate new token
  1. Your token will appear under the Production section
  2. Copy your Username and Token
Important: Save both values securely — you'll need them to connect in Domain Pilot. Copy your Username and Token from the Production section

Step 3: Whitelist Domain Pilot's IP Address

Name.com requires you to whitelist IP addresses that will access their API.

  1. On the same API Token settings page, scroll down to Add new allowed IP address
  2. Enter the following IP address: 3.77.180.226
  3. Click Allow IP Address
Whitelist Domain Pilot's IP address

Step 4: Connect in Domain Pilot

  1. Log in to Domain Pilot
  2. Go to SettingsRegistrars
  3. Click Add Registrar and select Name.com
  4. Enter your Username and API Token
  5. Click Connect

Verifying the Connection

Once connected, Domain Pilot will automatically sync your domains. This usually takes a few seconds. You should see all your Name.com domains appear in the Domains section.

Troubleshooting

"Invalid Credentials" Error

  • Ensure you're using the correct username and API token
  • Check that the token has not been revoked or regenerated
  • Try generating a new API token if the issue persists

"Forbidden" or Connection Error

  • Verify that you have whitelisted Domain Pilot's IP address (3.77.180.226) on the API Token settings page
  • Ensure you are using the Production token, not the Development/Test token

Domains Not Appearing

  • Allow a few minutes for the initial sync to complete
  • Verify your API token has the correct permissions