DOMAIN COMMAND POSTMonitor. Manage. Discover. Protect.

Help Center / Connections & Providers

Create the credential, paste it, test it and control where it appears.

Practical setup for registrar, acquisition, WHOIS, WHM and cPanel connections after you sign in to the provider.

Applies toEditions and add-ons that include the selected providerTypical time10–25 minutes per providerGuide formatPrepare → Click → Verify → Recover

Before you start

  • Open Domain Command Post and the provider account in separate windows.
  • Use a provider account you are authorized to connect.
  • Create the least-privileged API credential that supports the checks you need.
  • Never paste provider passwords or API secrets into a support message.

Standard provider setup

Program path: System → Settings → Connections → choose provider

  1. Open Setup Directions

    Keep the directions visible while the provider page opens separately. If the provider changes its menu labels, look for API, Developer, Security, Integration or Reseller settings.

  2. Create the required value

    Generate the API key, token, reseller key or account identifier described for that provider. Restrict source IPs only if your public IP is stable and the provider requires it.

  3. Copy once and store safely

    Some providers show a secret only once. Copy it directly into the matching Domain Command Post field.

  4. Test before enabling

    Select Test Connection. Read the returned account identity or permission result. Do not enable discovery or live workflows after a failed test.

  5. Enable the provider

    Turn on only the workflows you intend to use, then save. Open the relevant page and confirm the provider appears.

Success looks like: the test is green, the expected account or capability is named, and the provider appears only in workflows it actually supports.

Registrar and acquisition connections

Provider familyWhat you usually needWhere the result appears
WHOIS.com / LogicBoxesReseller identifier, API key and allowed source IP when requiredRegistration lookup and supported registrar workflows
Porkbun, Dynadot, GoDaddy, Namecheap, Sav, HEXONETProvider API key/token and any required secret or usernameLookup, coverage and supported registrar actions
DropCatch, NameJet / SnapNamesSupported account handoff or coverage settingsAcquisition Center and Opportunity Finder comparisons

Provider APIs are not identical. A connection may support live checks, browser-assisted setup or manual handoff. The app should state which one is in use.

Connect WHM

Program path: Operations → Hosting → Connections → Add WHM

  1. In WHM, create an API token for the authorized account. Give it only the permissions required to list accounts and retrieve approved metadata.
  2. In Domain Command Post, enter a recognizable connection name, the WHM host, port, username and API token.
  3. Select Test Connection. Confirm the server identity and account count are reasonable.
  4. Save, then select Discover Accounts.
  5. Review primary, addon, parked and subdomains before choosing which records to import.

Connect an individual cPanel account

Program path: Operations → Hosting → Connections → Add cPanel

  1. Create an API token in cPanel under its security/API token area.
  2. Enter the cPanel hostname, port, username and token in Domain Command Post.
  3. Test the connection, then review discovered domain types and account usage.
  4. Import only approved records.

Disable versus delete credentials

  1. Disable: open Settings → Connections, turn off Enabled and save. The provider disappears from active checks, coverage warnings, research and ordinary controls, but its credential remains stored.
  2. Delete credentials: open the same connection → Security / Remove Credentials, confirm the provider name, then test that the connection is no longer usable. This is separate so an accidental disable does not erase setup.

If the test fails

MessageCheck
Unauthorized / 401 / 403Username, token, API permission, allowed IP and whether the credential was revoked.
Host not found / timeoutHostname, port, firewall, TLS and whether the service is reachable outside the app.
Connected but no resultsAccount scope, provider capability and whether the relevant workflow is enabled.
Provider should disappearDisable it, save, close and reopen the target workflow; do not delete credentials unless intended.

Still stuck?

Write down the edition, program version, the exact path you opened, the last successful step and the full visible error. Do not send product keys, passwords or provider secrets.

Contact support with those detailsBack to Help Center