authentication

Explains SPF, DKIM, DMARC, and BIMI configuration and their interrelationships.

16|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/autosendhq/email-skills --skill authentication-autosendhq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: authentication
Source: https://github.com/autosendhq/email-skills/tree/main/authentication
Command: npx skills add https://github.com/autosendhq/email-skills --skill authentication-autosendhq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep reference for email authentication: SPF, DKIM, DMARC, and BIMI. Always use this skill before advising on anything involving DNS records for email, even if the question seems simple: authentication failures are the most common hidden cause of deliverability problems. Use it when: setting up a new sending domain, debugging why emails go to spam, reviewing DNS records, diagnosing DMARC alignment issues, interpreting authentication headers, reading DMARC aggregate reports, or advising on key rotation. If someone asks "why is my email going to spam" and authentication hasn't been verified yet, load this skill first.

Core Features & Use Cases

The four layers, in order of implementation: SPF, DKIM, DMARC, BIMI. Use cases include:

  • Setting up a new sending domain with proper SPF/DKIM/DMARC
  • Diagnosing authentication failures and interpreting DMARC reports
  • Rotating DKIM keys and aligning domains for deliverability and brand indicators

Quick Start

Load this skill when configuring domain authentication and start with SPF, then DKIM, DMARC, and BIMI.

Frequently Asked Questions about authentication

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

FAQPage Schema
Why are my emails going to spam and how do I check SPF, DKIM, and DMARC records?

Email authentication failures are the most common hidden cause of deliverability problems. You need to verify SPF, DKIM, and DMARC DNS records for your sending domain to diagnose why emails go to spam.

How do I set up email authentication for a new sending domain?

Configure email authentication by implementing DNS records in a strict order: SPF, then DKIM, DMARC, and BIMI. This layered approach ensures proper domain alignment and successful deliverability validation.

What is DMARC alignment and how does it relate to SPF and DKIM?

DMARC alignment verifies that the domain in the From header matches the domains authenticated by SPF and DKIM. It builds on those protocols to enforce policy and generate aggregate reports for deliverability compliance.

How do I interpret DMARC aggregate reports to troubleshoot authentication failures?

DMARC aggregate reports reveal which messages passed or failed SPF and DKIM alignment checks. Reading these reports helps diagnose DMARC failures, identify unauthorized sending sources, and adjust DNS policies.

When should I rotate DKIM keys and how does BIMI fit into email security?

Rotate DKIM keys periodically by generating new DNS records to maintain security. BIMI is configured last after DMARC, displaying brand logos in inboxes to provide visual trust once email authentication is fully established.

Do I need to update email authentication records when transitioning to a new ESP?

Yes, transitioning to a new ESP requires updating SPF, DKIM, and DMARC DNS records to reflect new sending IPs and domains. Avoiding common pitfalls like misconfigured records prevents deliverability failures.