skills.rest
chunkydotdev
chunkydotdevCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

domain-authentication

Configure SPF, DKIM, and DMARC records for sending domains.

2|Updated Mar 30, 2026
Search Tags:#email deliverability#spf#dkim#dmarc#dns records#email authentication#bulk sender compliance
One-click install
npx skills add https://github.com/chunkydotdev/email-skills --skill domain-authentication
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: domain-authentication
Source: https://github.com/chunkydotdev/email-skills/tree/main/skills/setup/domain-authentication
Command: npx skills add https://github.com/chunkydotdev/email-skills --skill domain-authentication

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Missing or misconfigured email authentication protocols (SPF, DKIM, DMARC) cause emails to be rejected, land in spam folders, fail compliance with Google/Yahoo/Microsoft bulk sender rules, and leave domains vulnerable to spoofing attacks. This Skill provides end-to-end guidance to implement, verify, and troubleshoot email authentication for any sending domain.

Core Features & Use Cases

  • Full authentication stack configuration: Step-by-step instructions for setting up SPF, DKIM, and DMARC records for new sending domains, including DNS record formatting and alignment requirements.
  • Troubleshooting and debugging: Guidance for resolving common authentication failures such as SPF DNS lookup limit overages, DKIM key rotation issues, and SaaS tool envelope-from misconfigurations that break DMARC alignment.
  • Compliance and security: Includes bulk sender requirement checklists, non-sending domain lockdown steps to prevent spoofing, and optional advanced protocol guidance for MTA-STS and BIMI.
  • Use Case: A marketing team sending 12,000 monthly promotional emails can use this Skill to configure DMARC policy progression, fix SPF record lookup limits, and meet Google's bulk sender requirements to avoid junk folder placement and improve engagement rates.

Quick Start

Use the domain-authentication skill to configure SPF, DKIM, and DMARC records for your sending domain and verify all authentication checks pass for test emails.

Frequently Asked Questions about domain-authentication

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

FAQPage Schema
How do I set up SPF, DKIM, and DMARC records for a new sending domain?▼

To set up SPF, DKIM, and DMARC for a new sending domain, you need to publish specific DNS records that authorize your email servers and third-party tools to send mail, then verify alignment to ensure inbox delivery and prevent spoofing.

Why are my emails going to spam despite having SPF and DKIM configured?▼

Emails may land in spam due to DMARC alignment failures, where the envelope-from address mismatches the header-from, or because of SPF DNS lookup limit overages and missing bulk sender compliance records required by Google and Yahoo.

Do I need DMARC for Google and Yahoo bulk sender compliance?▼

Yes, DMARC is required for Google, Yahoo, and Microsoft bulk sender compliance, alongside valid SPF and DKIM records, to prevent emails from being rejected or directed to recipients' junk folders.

What is the best way to prevent domain spoofing for parked or non-sending domains?▼

The best way to prevent spoofing on parked or non-sending domains is to implement a strict DMARC policy with p=reject and lock down DNS records to proactively block unauthorized email sending attempts.

How do I fix SPF DNS lookup limit overages when using multiple SaaS email tools?▼

To fix SPF DNS lookup limit overages, you must flatten your SPF record by replacing nested include mechanisms with direct IP addresses or use specialized SPF flattening services to stay under the 10 DNS lookup limit.

When should I progress my DMARC policy from monitoring to enforcement?▼

You should progress your DMARC policy from p=none to p=quarantine and eventually p=reject only after analyzing aggregate reports to confirm that all legitimate sending sources are properly authenticated and aligned.

Related Skills

Explore More Marketing & Sales Skills→
flavien-iaflavien-ia
34

_dns-brevo

Configure custom email domains via Brevo and Cloudflare REST APIs.

Community
Intermediate
Sir-chawakornSir-chawakorn
9

send-transactional-email

Configure SPF, DKIM, and DMARC alignment for transactional email delivery.

Community
Advanced
aaron-he-zhuaaron-he-zhu
2.5k

deliverability-qa

Scores email deliverability pre-flight via DNS, DMARC-RUA, and seed-list checks.

Community
Advanced
autosendhqautosendhq
16

monitoring

Monitor email deliverability and diagnose inbox placement issues across domains and IPs.

Official
Advanced