zapmail-domain-setup-public

Automates domain purchase on Dynadot and inbox provisioning on Zapmail for cold email infrastructure.

678|243|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/growthenginenowoslawski/coldoutboundskills --skill zapmail-domain-setup-public
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zapmail-domain-setup-public
Source: https://github.com/growthenginenowoslawski/coldoutboundskills/tree/main/skills/zapmail-domain-setup-public
Command: npx skills add https://github.com/growthenginenowoslawski/coldoutboundskills --skill zapmail-domain-setup-public

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python-dotenv.

What problem does it solve?

Setting up cold email sending infrastructure requires manually buying domains, configuring nameservers, provisioning inboxes, and exporting them to a sending platform — a slow, error-prone process involving two separate APIs and hours of DNS and provisioning waits.

Core Features & Use Cases

  • Domain Generation & Availability Checking: Generates short brand-based domain candidates across tiered prefix/suffix patterns and batch-checks availability and pricing via the Dynadot search API.
  • End-to-End Provisioning Workflow: Purchases domains on Dynadot, switches nameservers to Zapmail DNS, connects domains, creates mailboxes, and exports ACTIVE inboxes to platforms like Smartlead, Instantly, or Lemlist.
  • Timing & Rate-Limit Guidance: Encodes real-world constraints such as 15-20 minute DNS propagation, 4-6 hour inbox provisioning, batch size limits, and known API gotchas like the Dynadot comma-encoding bug.
  • Use Case: A growth team needs 30 sending domains with 2 inboxes each for a new client. The skill walks through generating candidates, buying them, and having export-ready inboxes within a day.

Quick Start

Set up 20 cold email domains for the brand 'acme' on Dynadot and Zapmail, then export the provisioned inboxes to Smartlead.

Frequently Asked Questions about zapmail-domain-setup-public

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up cold email domains with Dynadot and Zapmail?

Generate short brand-based domain candidates, check availability via the Dynadot search API, register them, switch nameservers to Zapmail's DNS, connect the domains, create mailboxes, and export ACTIVE inboxes to your sending platform after 4-6 hours of provisioning.

How long does Zapmail inbox provisioning take?

Zapmail returns 200 immediately after mailbox creation, but inboxes stay in 'In Progress' status for 4-6 hours. Do not export until mailboxes show ACTIVE status, since exporting in-progress inboxes fails silently.

What TLDs should I use for cold email domains?

Use .com as the primary choice for best inbox trust, with .co as a secondary option. Avoid .info, .xyz, .click, .top, .buzz, and .loan because recipients pattern-match these TLDs as spammy, hurting deliverability.

Why does the Dynadot batch nameserver request fail?

Python's urllib.parse.urlencode encodes commas as %2C, which breaks Dynadot's batch set_ns requests that expect comma-separated domain lists. Fix it by passing safe=',' to urlencode so commas remain unencoded.

Which email sending platforms does Zapmail export support?

Zapmail exports to Smartlead, Instantly, ReachInbox, Reply.io, Quickmail, Emelia, Lemlist, Snov, EmailBison, and several others. Your platform account must be linked first via the Zapmail dashboard or the third-party accounts API endpoint.

Why did my Zapmail batch mailbox creation return a 400 error?

If any single mailbox in a batch already exists, the entire batch request fails with a 400 error. Handle this by retrying the failed domains one at a time to isolate the conflicting mailbox.