Email Security

CommunityPopular

uphiago

email-security

DMARC/SPF/DKIM check, email spoofing, SMTP test, and security header analysis

Overview

Publisher	uphiago
Repository	`recon-skills`
Skill name	`email-security`
Stars	1.3K
Forks	213
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by uphiago on GitHub. Read the source before you install it.

Installation

Install the Email Security AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/uphiago/recon-skills.git /tmp/recon-skills
mkdir -p .claude/skills
cp -r /tmp/recon-skills/recon/email-security .claude/skills/email-security

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Email Security in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Email Security on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Email Security is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Email Security -- DMARC, SPF, DKIM

When to Use

During passive reconnaissance (Phase 1)
After initial DNS enumeration
DMARC p=none means the domain can be totally spoofed
Critical for identifying phishing/business email compromise risks

DMARC/SPF/DKIM Check Commands

bash
# SPF
dig +short TXT $target | grep "v=spf1"

# DMARC
dig +short TXT _dmarc.$target

# DKIM (common selector: google)
dig +short TXT google._domainkey.$target

# MX
dig +short MX $target

Interpreting Results

Config	Meaning	Risk
v=spf1 ~all (softfail)	SPF suggests blocking but doesnt enforce	Spoofed emails may pass
v=spf1 ?all (neutral)	SPF does nothing	Totally permissive
v=spf1 include:amazonses.com ~all	SES can send as domain	Any AWS SES account can spoof
v=DMARC1; p=none	DMARC disabled	Zero spoofing protection
v=DMARC1; p=quarantine	Failed emails go to spam	Partial protection
v=DMARC1; p=reject	Failed emails rejected	Full protection
DKIM missing	No cryptographic signature	Email can be forged

Email Spoofing via SMTP

bash
# Test SMTP relay
timeout 3 bash -c 'exec 3<>/dev/tcp/TARGET/25; head -1 <&3'

# Send spoofed email via open relay (swaks)
swaks --to victim@target.com --from admin@target.com   --server TARGET --body "Spoofed email"

Headers That Indicate Security Level

Header	Value	Meaning
Authentication-Results	spf=pass	SPF passed
Authentication-Results	spf=fail	SPF failed
Authentication-Results	dmarc=pass	DMARC passed
Authentication-Results	dmarc=fail	DMARC failed
Authentication-Results	dkim=pass	DKIM passed
Received-SPF	Pass	Sender authorized
Received-SPF	Softfail	Sender not fully authorized
Received-SPF	Fail	Sender not authorized
ARC-Authentication-Results		Authentication chain

AWS SES Spoofing (When SPF includes amazonses.com)

With v=spf1 include:amazonses.com ~all:

Create AWS account
Configure SES with your own domain (verified)
Send email with From: admin@target.com
SPF PASSES (because of include:amazonses.com)
DMARC p=none -- provider delivers normally

Real-World Cases

Real-world case (CRITICAL): Political party -- DMARC p=none on both domains (DOMAIN_PLACEHOLDER_A, DOMAIN_PLACEHOLDER_B). SPF with include:amazonses.com (any SES account can send as the domain). Total email spoofing.

Pitfalls

Issue	Solution
SPF lookup limit	DNS has 10 lookup limit for SPF includes
DKIM selector unknown	Try common selectors: google, selector1, selector2, 2022, 2023
DMARC reporting	rua=mailto: may leak authentication results to third party

Verification

bash
# Verify email spoofing is possible
# Send test email and check headers:
dig +short TXT _dmarc.target.com
# If p=none -> confirmed spoofable

Frequently asked questions

What does the Email Security AI skill do?

DMARC/SPF/DKIM check, email spoofing, SMTP test, and security header analysis

Why use Email Security on TypingMind?

Because you install it once and use it with any model. Email Security is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Email Security in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/uphiago/recon-skills/tree/main/recon/email-security. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Email Security?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Email Security?

As many as you like. As long as a model supports skills, you can use Email Security with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Email Security AI skill free?

Yes. It is published on GitHub by uphiago under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Ponytail Audit

DietrichGebert

CommunityPopular

Whole-repo audit for over-engineering. Like ponytail-review, but scans the entire codebase instead of a diff: a ranked list of what to delete, simplify, or replace with stdlib/native equivalents. Use…

Dependency Doctor

Checks requirements.txt, pyproject.toml, and package.json dependency manifests for surface-level direct-dependency footguns: standard-library shadowing pins, abandoned backports, unpinned…

Cso

Security audit: supported static findings; qualified profiles add reproduction and repair candidates. (gstack)

Cavecrew

When to delegate to `cavecrew-investigator` (locate code), `cavecrew-builder` (1-2 file edit) or `cavecrew-reviewer` (diff review) instead of working inline or using `Explore`. Their output is…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Email Security -- DMARC, SPF, DKIM

When to Use

DMARC/SPF/DKIM Check Commands

Interpreting Results

Email Spoofing via SMTP

Headers That Indicate Security Level

AWS SES Spoofing (When SPF includes amazonses.com)

Real-World Cases

Pitfalls

Verification

Frequently asked questions

Related AI Skills

Set up your own AI workspace now