Skip to content

creatop-gtm/apollo-operator / .claude/skills/sending-infrastructure

sending-infrastructure

Verified

Build the sending stack from zero before you send: dedicated domains separate from your primary, mailboxes, SPF/DKIM/DMARC/MX, redirect, and warmup. Includes the volume math (mailboxes and domains per daily send target). Use for first-time setup or when scaling adds mailboxes.

FileKindSize
SKILL.mdskill md11.3 KB
references/dns-records.mdmarkdown4.6 KB

references/dns-records.md

View on GitHub
# DNS records for a sending domain

The depth behind Step 3 of `sending-infrastructure`. Every dedicated sending domain needs these records set at its DNS host (the registrar, or wherever the domain's nameservers point). Get all of SPF, DKIM, and DMARC passing before the first cold send. This is the difference between the inbox and the spam folder, and no amount of good copy makes up for getting it wrong.

If you bought provisioned domains and mailboxes, the provider usually sets these for you: your job is then to *verify* them (see the checklist at the bottom), not to author them.

## The four records

### MX (mail exchange)
Routes inbound mail (replies, and the warmup pool's messages) to your mailbox provider. Without a correct MX record, replies to your cold emails go nowhere, and you will not even know people answered. Your mailbox provider gives you the exact MX host and priority to set. This is table stakes: no MX, no two-way email.

### SPF (Sender Policy Framework)
A TXT record listing which servers are allowed to send email as this domain. When a receiver gets your email, it checks the sending server against this list. If the server is not authorized, the mail looks forged.

- One SPF record per domain, and only one. Multiple SPF records is itself a failure.
- It must `include:` the sending service you actually use (your mailbox provider or sending platform gives you the exact include).
- End it with `~all` (softfail) or `-all` (hardfail). Do not use `+all`, which authorizes the whole internet to send as you.

### DKIM (DomainKeys Identified Mail)
A cryptographic signature. Your provider publishes a public key as a DNS record; it signs every outbound message with the matching private key. Receivers verify the signature, which proves the mail genuinely came from your domain and was not altered in transit.

- The provider gives you the exact record (a TXT or CNAME at a selector host like `selector._domainkey.getbrand.com`). Paste it exactly. A single wrong character breaks the signature.
- Verify it is live and passing after you set it, propagation can take a few hours.

### DMARC (Domain-based Message Authentication)
A TXT record at `_dmarc.getbrand.com` that tells receivers what to do with mail claiming to be from your domain that fails SPF or DKIM, and where to send reports. This is where domain reputation is actually built.

- Start with a monitoring policy: `v=DMARC1; p=none; rua=mailto:you@brand.com`. `p=none` means "do not block anything yet, just report," so you can watch for problems without hurting delivery.
- Once SPF and DKIM are clean and you have watched the reports, you can tighten to `p=quarantine` and later `p=reject`. Never start at `reject`, one misconfiguration and all your mail disappears.
- A missing DMARC record increasingly gets mail sent straight to spam by major receivers. It is no longer optional.

## The redirect (not DNS, but part of setup)

Point the sending domain itself (a 301 redirect at the web/hosting layer) to the main website, so a prospect who types or clicks `getbrand.com` lands on the real brand. A sending domain that resolves to nothing looks abandoned and hurts trust. This is a redirect rule at your host or a redirect service, separate from the DNS records above.

## Verification checklist (before any cold send)

For every sending domain, confirm:

- [ ] MX record present and pointing at the mailbox provider.
- [ ] Exactly one SPF record, includes the real sending service, ends in `~all` or `-all`.
- [ ] DKIM record live at the provider's selector, signature passing.
- [ ] DMARC record at `_dmarc.<domain>`, at least `p=none` with a reporting address.
- [ ] Domain 301-redirects to the main website.
- [ ] For Apollo-provisioned domains, `apollo_domain_purchase_index` shows SPF, DKIM, and DMARC passing in its diagnostics.

Free public tools (MXToolbox and similar) will check SPF, DKIM, DMARC, and MX for any domain from the outside. Use one to confirm each record is live and passing before you trust it. Do not rely on "I set the record" as proof, confirm it resolves.

## Common failures

- **Two SPF records.** Only one is allowed; a second one makes SPF fail entirely. Merge includes into a single record.
- **DKIM pasted with a line break or a missing character.** The signature silently fails. Copy it exactly, verify externally.
- **Jumping straight to `p=reject` on DMARC.** One SPF or DKIM gap and every message vanishes. Start at `p=none`, tighten later.
- **Forgetting MX** because outbound seems to work. Outbound sends, but every reply is lost, which quietly kills the whole point of the campaign.
- **No redirect**, so the sending domain resolves to an error page. It reads as fake and costs you trust and clicks.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall