[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A802EFE232TF4FVGYHAR97":3,"skill-same:01M7A802EFE232TF4FVGYHAR97":103},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":14,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M7A802EFE232TF4FVGYHAR97","implementing-dmarc-dkim-spf-email-security",null,"Configures SPF, DKIM, and DMARC DNS TXT records to authenticate outbound email, prevent domain spoofing, and enforce a rejection\u002Fquarantine policy on unauthenticated mail, including auditing a domain's current DNS state. Use when hardening a domain's email security posture or defending against phishing and spoofing attacks.","NeelakshSaxena\u002FVayu","NeelakshSaxena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87892838?v=4","01M7A3B9YFS6F6N9DD1787DT86","Neelaksh Saxena","01M7A3B9ZKBT09MNMPX2XN69BY",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-dmarc-dkim-spf-email-security\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-dmarc-dkim-spf-email-security\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: implementing-dmarc-dkim-spf-email-security\ndescription: Configures SPF, DKIM, and DMARC DNS TXT records to authenticate outbound email, prevent domain spoofing, and enforce a rejection\u002Fquarantine policy on unauthenticated mail, including auditing a domain's current DNS state. Use when hardening a domain's email security posture or defending against phishing and spoofing attacks.\ndomain: cybersecurity\nsubdomain: phishing-defense\ntags:\n- phishing\n- email-security\n- social-engineering\n- dmarc\n- awareness\n- dkim\n- spf\n- dns\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.AT-01\n- DE.CM-09\n- RS.CO-02\n- DE.AE-02\nmitre_attack:\n- T1566\n- T1598\n- T1534\n- T1036\n---\n# Implementing DMARC, DKIM, and SPF Email Security\n\n## Overview\nSPF, DKIM, and DMARC form the three pillars of email authentication. Together they prevent domain spoofing, validate message integrity, and define policies for handling unauthenticated mail. Proper implementation drastically reduces phishing attacks that impersonate your organization's domain.\n\n\n## When to Use\n\n- When deploying or configuring implementing dmarc dkim spf email security capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n- DNS management access for your domain\n- Access to email server\u002FMTA configuration (Postfix, Exchange, Google Workspace, Microsoft 365)\n- Basic understanding of DNS TXT records\n- Python 3.8+ for validation scripts\n\n## Key Concepts\n\n### SPF (Sender Policy Framework)\nPublishes a DNS TXT record listing authorized IP addresses and mail servers that can send email on behalf of your domain. Receiving servers check the envelope sender's IP against this list.\n\n### DKIM (DomainKeys Identified Mail)\nAdds a cryptographic signature to outgoing emails using a private key. The corresponding public key is published in DNS. Receivers verify the signature to ensure the message was not altered in transit.\n\n### DMARC (Domain-based Message Authentication, Reporting and Conformance)\nBuilds on SPF and DKIM by specifying a policy (none\u002Fquarantine\u002Freject) for messages that fail authentication, and provides a reporting mechanism to monitor spoofing attempts.\n\n## Workflow\n\n### Step 1: Audit Current State\n```bash\n# Check existing SPF record\ndig TXT example.com | grep spf\n\n# Check existing DKIM selector\ndig TXT selector1._domainkey.example.com\n\n# Check existing DMARC record\ndig TXT _dmarc.example.com\n```\n\n### Step 2: Implement SPF\n```\n# DNS TXT record for example.com\nv=spf1 ip4:203.0.113.0\u002F24 include:_spf.google.com include:spf.protection.outlook.com -all\n```\n\nKey SPF mechanisms:\n- `ip4:` \u002F `ip6:` - Authorize specific IP ranges\n- `include:` - Include another domain's SPF record\n- `a` - Authorize domain's A record IPs\n- `mx` - Authorize domain's MX record IPs\n- `-all` - Hard fail all others (recommended)\n- `~all` - Soft fail (monitoring phase)\n\n### Step 3: Implement DKIM\n```bash\n# Generate DKIM key pair (2048-bit RSA)\nopenssl genrsa -out dkim_private.pem 2048\nopenssl rsa -in dkim_private.pem -pubout -out dkim_public.pem\n\n# Format public key for DNS (remove headers, join lines)\ngrep -v \"PUBLIC KEY\" dkim_public.pem | tr -d '\\n'\n```\n\nDNS TXT record at `selector1._domainkey.example.com`:\n```\nv=DKIM1; k=rsa; p=MIIBIjANBgkqhki...\n```\n\n### Step 4: Implement DMARC\n```\n# DNS TXT record at _dmarc.example.com\n# Phase 1 (Monitor):\nv=DMARC1; p=none; rua=mailto:dmarc-aggregate@example.com; ruf=mailto:dmarc-forensic@example.com; pct=100\n\n# Phase 2 (Quarantine):\nv=DMARC1; p=quarantine; rua=mailto:dmarc-aggregate@example.com; pct=25\n\n# Phase 3 (Reject):\nv=DMARC1; p=reject; rua=mailto:dmarc-aggregate@example.com; pct=100\n```\n\n### Step 5: Monitor and Analyze DMARC Reports\nUse the `scripts\u002Fprocess.py` to parse DMARC aggregate XML reports and identify authentication failures, unauthorized senders, and spoofing attempts.\n\n## Tools & Resources\n- **MXToolbox**: https:\u002F\u002Fmxtoolbox.com\u002FSuperTool.aspx\n- **DMARC Analyzer (dmarcian)**: https:\u002F\u002Fdmarcian.com\u002F\n- **Google Postmaster Tools**: https:\u002F\u002Fpostmaster.google.com\u002F\n- **Valimail DMARC Monitor**: https:\u002F\u002Fwww.valimail.com\u002F\n- **DMARC Report Analyzer**: https:\u002F\u002Fdmarc.postmarkapp.com\u002F\n\n## Validation\n- SPF record passes validation at mxtoolbox.com\n- DKIM signature verified on test emails\n- DMARC record properly formatted and reporting enabled\n- Test emails pass all three checks in recipient's Authentication-Results header\n","# Implementing DMARC, DKIM, and SPF Email Security\n\n## Overview\nSPF, DKIM, and DMARC form the three pillars of email authentication. Together they prevent domain spoofing, validate message integrity, and define policies for handling unauthenticated mail. Proper implementation drastically reduces phishing attacks that impersonate your organization's domain.\n\n\n## When to Use\n\n- When deploying or configuring implementing dmarc dkim spf email security capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n- DNS management access for your domain\n- Access to email server\u002FMTA configuration (Postfix, Exchange, Google Workspace, Microsoft 365)\n- Basic understanding of DNS TXT records\n- Python 3.8+ for validation scripts\n\n## Key Concepts\n\n### SPF (Sender Policy Framework)\nPublishes a DNS TXT record listing authorized IP addresses and mail servers that can send email on behalf of your domain. Receiving servers check the envelope sender's IP against this list.\n\n### DKIM (DomainKeys Identified Mail)\nAdds a cryptographic signature to outgoing emails using a private key. The corresponding public key is published in DNS. Receivers verify the signature to ensure the message was not altered in transit.\n\n### DMARC (Domain-based Message Authentication, Reporting and Conformance)\nBuilds on SPF and DKIM by specifying a policy (none\u002Fquarantine\u002Freject) for messages that fail authentication, and provides a reporting mechanism to monitor spoofing attempts.\n\n## Workflow\n\n### Step 1: Audit Current State\n```bash\n# Check existing SPF record\ndig TXT example.com | grep spf\n\n# Check existing DKIM selector\ndig TXT selector1._domainkey.example.com\n\n# Check existing DMARC record\ndig TXT _dmarc.example.com\n```\n\n### Step 2: Implement SPF\n```\n# DNS TXT record for example.com\nv=spf1 ip4:203.0.113.0\u002F24 include:_spf.google.com include:spf.protection.outlook.com -all\n```\n\nKey SPF mechanisms:\n- `ip4:` \u002F `ip6:` - Authorize specific IP ranges\n- `include:` - Include another domain's SPF record\n- `a` - Authorize domain's A record IPs\n- `mx` - Authorize domain's MX record IPs\n- `-all` - Hard fail all others (recommended)\n- `~all` - Soft fail (monitoring phase)\n\n### Step 3: Implement DKIM\n```bash\n# Generate DKIM key pair (2048-bit RSA)\nopenssl genrsa -out dkim_private.pem 2048\nopenssl rsa -in dkim_private.pem -pubout -out dkim_public.pem\n\n# Format public key for DNS (remove headers, join lines)\ngrep -v \"PUBLIC KEY\" dkim_public.pem | tr -d '\\n'\n```\n\nDNS TXT record at `selector1._domainkey.example.com`:\n```\nv=DKIM1; k=rsa; p=MIIBIjANBgkqhki...\n```\n\n### Step 4: Implement DMARC\n```\n# DNS TXT record at _dmarc.example.com\n# Phase 1 (Monitor):\nv=DMARC1; p=none; rua=mailto:dmarc-aggregate@example.com; ruf=mailto:dmarc-forensic@example.com; pct=100\n\n# Phase 2 (Quarantine):\nv=DMARC1; p=quarantine; rua=mailto:dmarc-aggregate@example.com; pct=25\n\n# Phase 3 (Reject):\nv=DMARC1; p=reject; rua=mailto:dmarc-aggregate@example.com; pct=100\n```\n\n### Step 5: Monitor and Analyze DMARC Reports\nUse the `scripts\u002Fprocess.py` to parse DMARC aggregate XML reports and identify authentication failures, unauthorized senders, and spoofing attempts.\n\n## Tools & Resources\n- **MXToolbox**: https:\u002F\u002Fmxtoolbox.com\u002FSuperTool.aspx\n- **DMARC Analyzer (dmarcian)**: https:\u002F\u002Fdmarcian.com\u002F\n- **Google Postmaster Tools**: https:\u002F\u002Fpostmaster.google.com\u002F\n- **Valimail DMARC Monitor**: https:\u002F\u002Fwww.valimail.com\u002F\n- **DMARC Report Analyzer**: https:\u002F\u002Fdmarc.postmarkapp.com\u002F\n\n## Validation\n- SPF record passes validation at mxtoolbox.com\n- DKIM signature verified on test emails\n- DMARC record properly formatted and reporting enabled\n- Test emails pass all three checks in recipient's Authentication-Results header\n",{"name":5,"tags":25,"author":34,"domain":35,"license":15,"version":36,"nist_csf":37,"subdomain":42,"description":7,"mitre_attack":43},[26,27,28,29,30,31,32,33],"phishing","email-security","social-engineering","dmarc","awareness","dkim","spf","dns","mahipal","cybersecurity","1.0",[38,39,40,41],"PR.AT-01","DE.CM-09","RS.CO-02","DE.AE-02","phishing-defense",[44,45,46,47],"T1566","T1598","T1534","T1036","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Fimplementing-dmarc-dkim-spf-email-security","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena","Currently exploring the intersection of tech","2026-09-11 03:02:31",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add NeelakshSaxena\u002FVayu --skill implementing-dmarc-dkim-spf-email-security",{"tool":61,"command":62},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill implementing-dmarc-dkim-spf-email-security",{"tool":64,"command":65},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill implementing-dmarc-dkim-spf-email-security","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-dmarc-dkim-spf-email-security\u002FSKILL.md",true,[69,75,79,85,89,93,99],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"assets\u002Ftemplate.md","ASSET","资产文件",2595,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-dmarc-dkim-spf-email-security\u002Fassets\u002Ftemplate.md",{"path":76,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fapi-reference.md","REFERENCE","参考文档",1412,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-dmarc-dkim-spf-email-security\u002Freferences\u002Fapi-reference.md",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fstandards.md",2930,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-dmarc-dkim-spf-email-security\u002Freferences\u002Fstandards.md",{"path":90,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fworkflows.md",3205,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-dmarc-dkim-spf-email-security\u002Freferences\u002Fworkflows.md",{"path":94,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},"scripts\u002Fagent.py","SCRIPT","脚本",5572,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-dmarc-dkim-spf-email-security\u002Fscripts\u002Fagent.py",{"path":100,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":101,"sourceHtmlUrl":102},"scripts\u002Fprocess.py",20891,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-dmarc-dkim-spf-email-security\u002Fscripts\u002Fprocess.py",[104,111,118,125,132,139],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":20},"01M7ACCCVNCFKMA9X6D15X6G98","runpodctl","Runpod CLI for managing GPU\u002FCPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send\u002Freceive). Use for terminal\u002FCI\u002Fscripting, Hub browse\u002Fdeploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpodctl\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":20},"01M7ACC63SRHEA5KMCHSMZK2TC","runpod","Start here for any Runpod task — running GPU\u002FCPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":20},"01M7ACC0Q1C89N9BZBV91CTQTF","runpod-usage","How Runpod works and how to work it — pods vs serverless, GPU\u002FVRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv\u002Fapt). Use to answer \"how does X work\", \"which GPU\", \"how do I build a container\", or \"how do I stand up a workload on a pod\". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-usage\u002FSKILL.md",[],[],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":20},"01M7ACBRPE345GF5GM5B8P8RRC","runpod-templates","Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says \"run \u003CX> on a pod\" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-templates\u002FSKILL.md",[],[],{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":20},"01M7ACBJATHKVX1TWES2F44GY8","runpod-migrate","Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-migrate\u002FSKILL.md",[],[],{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":20},"01M7ACBC7GHVH6T9YEAPCG2AP8","runpod-mcp","Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU\u002FCPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-mcp\u002FSKILL.md",[],[]]