Set up DNS automatically

MailBlastr can apply your domain's DNS records for you if your domain is managed by Cloudflare, GoDaddy, or Namecheap. The flow is: detect which provider the domain uses, then call the matching apply endpoint with your provider API credentials. MailBlastr upserts the SPF, DKIM, and DMARC records and immediately triggers a verification pass.

All three endpoints require a key with at least read access for detect, and full access for the apply endpoints.

Detect provider

Looks up the nameservers for the domain and identifies which DNS provider is in use. Returns the provider details and a methods array listing which one-click apply options are available for that provider.

import { MailBlastr } from 'mailblastr';

const mb = new MailBlastr('mb_xxxxxxxxx');

const { data, error } = await mb.domains.detectDns('d91a7c4e-1f2b-4a8c-9e3d-7b5f0a2c1d6e');
console.log({ data, error });

Response

{
  "provider": {
    "id": "cloudflare",
    "label": "Cloudflare",
    "domainConnect": false,
    "api": true
  },
  "nameservers": ["ns1.cloudflare.com", "ns2.cloudflare.com"],
  "methods": [
    {
      "type": "cloudflare",
      "label": "Connect Cloudflare",
      "needs": "api_token"
    },
    {
      "type": "open_panel",
      "label": "Open Cloudflare DNS settings",
      "url": "https://dash.cloudflare.com/?to=/:account/:zone/dns"
    }
  ]
}

The provider.id is one of cloudflare, godaddy, namecheap, ionos, google, route53, or other. Each object in methods describes one available path: cloudflare and godaddy entries include a needs field indicating the credential the apply endpoint requires; open_panel entries include a url deep-link to the provider's DNS settings page.

Errors: not_found if the domain does not exist or is not yours. See Errors.

Apply via Cloudflare

Upserts the domain's SPF, DKIM, and DMARC records directly into your Cloudflare zone using a scoped API token, then immediately triggers a verification pass and returns the resulting domain status. The token must have Zone → DNS → Edit permission on the domain's zone.

import { MailBlastr } from 'mailblastr';

const mb = new MailBlastr('mb_xxxxxxxxx');

const { data, error } = await mb.domains.applyCloudflareDns('d91a7c4e-1f2b-4a8c-9e3d-7b5f0a2c1d6e', { "token": "cf_token_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" });
console.log({ data, error });

Response

{
  "applied": 3,
  "updated": 0,
  "failed": [],
  "zoneId": "023e105f4ecef8ad9ca31a8372d0c353",
  "status": "verified"
}

applied is the count of records created, updated is the count of records overwritten (already existed with a different value), and failed is a list of any records that could not be written — each entry has host and error. status is the domain verification status after the immediate re-check (verified, pending, or failed).

Errors: not_found if the domain does not exist or is not yours, validation_error if the token is missing, rejected by Cloudflare (bad scope or wrong account), or the domain's zone is not found in this Cloudflare account. See Errors.

Apply via GoDaddy

Upserts the domain's SPF, DKIM, and DMARC records into GoDaddy via the GoDaddy Domains API, then immediately triggers a verification pass and returns the resulting domain status. Use a Production API key — OTE keys will not work against live domains.

import { MailBlastr } from 'mailblastr';

const mb = new MailBlastr('mb_xxxxxxxxx');

const { data, error } = await mb.domains.applyGoDaddyDns('d91a7c4e-1f2b-4a8c-9e3d-7b5f0a2c1d6e', { "key": "gd_key_xxxxxxxxxxxxxxxxxxxxxxxxxxxx", "secret": "gd_secret_xxxxxxxxxxxxxxxxxxxxxxxxxxxx" });
console.log({ data, error });

Response

{
  "applied": 3,
  "failed": [],
  "status": "verified"
}

applied is the count of records written and failed is a list of any records that could not be written — each entry has host and error. status is the domain verification status after the immediate re-check (verified, pending, or failed). Unlike the Cloudflare response, GoDaddy does not return an updated count because its API replaces records by type/name rather than patching individual record IDs.

Errors: not_found if the domain does not exist or is not yours, validation_error if key or secret is missing, rejected by GoDaddy (bad credentials or wrong environment), or the domain is not in this GoDaddy account. See Errors.

Apply via Namecheap

Applies the domain's SPF, DKIM, and DMARC records via the Namecheap API, then immediately triggers a verification pass. Namecheap's host API is a full replace, so MailBlastr first reads your existing host records and re-sends them unchanged alongside the new ones — your current DNS is preserved.

import { MailBlastr } from 'mailblastr';

const mb = new MailBlastr('mb_xxxxxxxxx');

const { data, error } = await mb.domains.applyNamecheapDns('d91a7c4e-1f2b-4a8c-9e3d-7b5f0a2c1d6e', { "apiUser": "your_namecheap_username", "apiKey": "nc_key_xxxxxxxxxxxxxxxxxxxxxxxxxxxx" });
console.log({ data, error });

Response

{
  "applied": 3,
  "preserved": 2,
  "failed": [],
  "status": "verified"
}

applied is the number of new records added, preserved is the number of your existing host records kept in place, and failed lists any that could not be written. status is the verification status after the immediate re-check.