setting-up-sending-domain

Verify Mailtrap sending domains and troubleshoot DNS record propagation.

7|1|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/mailtrap/mailtrap-skills --skill setting-up-sending-domain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setting-up-sending-domain
Source: https://github.com/mailtrap/mailtrap-skills/tree/main/skills/setting-up-sending-domain
Command: npx skills add https://github.com/mailtrap/mailtrap-skills --skill setting-up-sending-domain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides users through adding and verifying a Mailtrap sending domain, resolving DNS propagation and proxying issues, and completing any post-verification compliance so that the domain can be used for live email delivery.

Core Features & Use Cases

  • Exact-domain verification: Add the precise subdomain or root domain you will use in the From address and verify it before sending.
  • DNS record management: Copy and publish all Mailtrap-provided DNS records (SPF, DKIM, tracking CNAMEs) exactly as shown, or automate via the Sending Domains API and DNS provider APIs.
  • Troubleshooting: Diagnose propagation and proxied DNS issues with dig/nslookup and ensure DNS-only records when required.
  • Use Case: Provision a notifications.mycompany.com sending domain, create the exact records at Cloudflare or Route 53, wait for dns_records verification, and finish the compliance flow to start production sends.

Quick Start

Add the sending domain in Mailtrap, publish every DNS record shown in the UI or returned by the Sending Domains API at your DNS host, wait for dns_records to report verified, and complete the compliance step if prompted.

Frequently Asked Questions about setting-up-sending-domain

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

FAQPage Schema
How do I verify a sending domain for live email delivery?

To verify a sending domain, add the exact subdomain or root domain in Mailtrap, publish all provided SPF, DKIM, and tracking DNS records at your host, and poll the dns_records status until verified.

Why is my DKIM or SPF record not verifying after adding it to DNS?

DNS propagation delays or proxied DNS records often prevent verification. Use dig or nslookup to confirm records are published correctly and set to DNS-only mode to resolve proxying issues.

Does Mailtrap domain verification work with Cloudflare or Route 53?

Yes, Mailtrap domain verification works with Cloudflare, Route 53, Google Cloud DNS, GoDaddy, Namecheap, and DigitalOcean by publishing the exact SPF, DKIM, and tracking records provided by the API or UI.

What DNS records do I need to publish to enable a Mailtrap sending domain?

You must publish all Mailtrap-provided SPF, DKIM, and tracking CNAME records exactly as returned by the Sending Domains API or UI to successfully verify and enable your sending domain.

Do I need to complete compliance steps after DNS verification for my sending domain?

Yes, after your dns_records report a verified status, you must complete the compliance step if prompted before you can start production email sends through the verified sending domain.

Can I automate sending domain DNS record creation across multiple DNS providers?

Yes, you can automate DNS record publishing by using the Sending Domains API to fetch records and provisioning them automatically via your DNS provider's API for exact-domain verification.