Skip to content
Skillpedia
APIs & servers (backend)48k · #3521

mailtrap-setting-up-sending-domain

Helps your agent set up and verify email sending domains. It also helps troubleshoot DNS issues and set up important records to ensure your emails reach their destination.

What it does

Helps you set up a domain to send emails through Mailtrap. This involves adding the domain, verifying it's truly yours, and configuring the necessary information so emails arrive correctly.

When to use it

  • ✓When setting up a new domain for sending emails via Mailtrap.
  • ✓If your domain verification is not working.
  • ✓When you need help with DNS settings (SPF, DKIM, DMARC).

Example of what to ask your AI

“I want to set up my domain 'myemail.com' to send emails via Mailtrap, but verification is failing.”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/mailtrap-setting-up-sending-domain/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/mailtrap-setting-up-sending-domain/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

You need to add specific records (like SPF, DKIM, and DMARC) in your domain's DNS system. Mailtrap provides these exact records for you to copy and paste.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add sickn33/agentic-awesome-skills --skill mailtrap-setting-up-sending-domain

Or download just the file:

curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/mailtrap-setting-up-sending-domain/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

Setting up a Mailtrap sending domain

Overview

You must add and verify a domain you control before live sending. Mailtrap shows every DNS record required for that domain in the UI: add the complete set as given (do not cherry-pick). After DNS verifies, complete the compliance step if requested.

Subdomain vs root: add the exact hostname you will use in the From address. If you send from notifications.mycompany.com, add that subdomain as the sending domain—not only mycompany.com, unless you truly send from the root domain.

For step-by-step clicks at common hosts, open the matching guide on Sending domain setup (Cloudflare, Route 53, etc.) and follow it alongside the live UI values.

Related skills: mailtrap-sending-emails (after domain is ready).

When to use

  • New Sending Domains setup, stuck verification, or compliance questions
  • DNS at Cloudflare, AWS, Google, Namecheap, GoDaddy, DigitalOcean, etc.

When not to use

  • Sandbox-only testing without a custom domain (see mailtrap-testing-with-sandbox)

Authorization

The Sending Domains API calls below need Authorization: Bearer $MAILTRAP_API_TOKEN and an $MAILTRAP_ACCOUNT_ID in the path. Resolve $MAILTRAP_ACCOUNT_ID from GET https://mailtrap.io/api/accounts, and store tokens in environment variables or a secrets manager.

Automating setup (API and DNS providers)

Prefer this path when building scripts or AI-assisted automation:

  1. DNS records and status via API — Use the Sending Domains API:
  • GET https://mailtrap.io/api/accounts/$MAILTRAP_ACCOUNT_ID/sending_domains — lists domains
  • GET https://mailtrap.io/api/accounts/$MAILTRAP_ACCOUNT_ID/sending_domains/{sending_domain_id} — returns dns_records (each with type, name, value, and verification status) and dns_verified. Poll after you publish DNS.
  1. Create domain via API —
  • POST https://mailtrap.io/api/accounts/$MAILTRAP_ACCOUNT_ID/sending_domains with domain_name when your flow provisions domains programmatically.
  1. Publish DNS programmatically —
  • Create the returned records at your DNS host using their API (e.g., Cloudflare API, AWS Route 53, Google Cloud DNS) or IaC. Align record names and values exactly with the API response.

Human fallback: Sending Domains > Add domain > copy values into the registrar UI > Verify when API automation is not available.

Workflow (summary)

  1. Sending Domains > Add domain and enter the domain name.
  2. Obtain required records from the UI or Sending Domains API; create all listed records at your DNS host exactly as shown (names, types, values).
  3. Wait for DNS propagation. If verification stays pending, use dig, nslookup, or an online DNS lookup to confirm each record is visible publicly before clicking Verify again.
  4. Complete the compliance flow when prompted.

Product walkthrough: Sending domain setup.

DNS provider guides (documentation)

Mailtrap publishes click-path guides for common providers. Open the page that matches the user's DNS host and follow it together with the live UI records:

If the user's provider is not listed, the same rule applies: copy every record from Mailtrap into the DNS zone that serves the From domain.

Important DNS caveat (proxied DNS)

…

FAQ

What are DNS records like SPF, DKIM, and DMARC?

They are like 'authenticity stamps' for your emails. They help email servers confirm that emails sent from your domain are legitimate and not spam.

What does 'DNS propagation' mean?

It's the time it takes for new DNS settings to be updated across the internet. It can take anywhere from a few minutes to a few hours.

Can I use a subdomain like 'contact.mydomain.com'?

Yes, you can use a subdomain. Make sure to add the exact subdomain you will use for sending emails in Mailtrap.

Details

Original description by the author

Add or verify a Mailtrap sending domain, troubleshoot DNS propagation, publish SPF/DKIM/DMARC records, and complete compliance.

repo: sickn33/agentic-awesome-skills

Popularity

GitHub stars
48k
Ranking position
#3521
License
MIT
Updated
10/15/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills