DMARC Aggregate Sender Change Review

    1

    Compare two batches of DMARC aggregate XML locally and review observed sender and alignment changes.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    DMARC Aggregate Sender Change Review

    Example session with this skill installed

    Using the included synthetic before and after RFC 9990 XML reports for example.com, run the local DMARC sender-change review. Show the observed source and alignment changes and the manual checks I should do next. Do not query DNS or change mail policy.

    • Read your context and instructions
    • Compiled the dmarc aggregate sender

    Synthetic DMARC sender-change review

    Scope: one supplied before report and one supplied after report for example.com.

    Status: REVIEW. This example uses invented IP addresses and contains no customer data.

    Source IPBefore reportAfter reportFinding
    192.0.2.10100 messages; DKIM/SPF reported pass; disposition pass80 messages; DKIM/SPF reported fail; disposition quarantineRESULT_SET_CHANGED
    198.51.100.3Not observed5 messages; DKIM/SPF reported fail; disposition quarantineNEW_SOURCE and NEW_SOURCE_WITH_BOTH_ALIGNMENT_FAILURES

    Review queue: confirm that the report time windows and receivers are comparable; inspect 192.0.2.10 for the changed reported result; identify 198.51.100.3 before treating it as an authorized or unauthorized sender. Compare live DNS, mail logs and sender configuration separately before any policy change.

    Limits: message-volume differences alone are not a health verdict. Absence from these reports does not prove a sender stopped. The local packet does not verify report authenticity, live DNS, actual message delivery, or sender legitimacy. Its receipt verifies packet bytes, not the truth of the input reports. No mailbox, DNS or policy change was performed.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Compare user-supplied before and after RFC 9990 DMARC aggregate XML without connecting to a mailbox or DNS. The included Python CLI and optional local stdio MCP tool produce a deterministic source-IP change table, human-review checklist, and hash-bound receipt. The companion SKILL.md guides an assistant through the review. The ZIP includes readable source, invented runnable examples, and a sample packet. Requires Python 3.11–3.14 and uncompressed RFC 9990 XML; optional MCP mode installs the pinned official SDK. Findings describe only the supplied reports. They do not certify sender legitimacy, live DNS policy, report coverage, message delivery, or compliance, and the tool makes no automatic changes.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Security.

    Uncompressed RFC 9990 XML only; no legacy no-namespace or gzip/ZIP input. Supplied report windows and receiver coverage may differ. Findings do not prove sender legitimacy, live DNS state, message delivery or DMARC compliance.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Software
    Dmarc Sender Change MCPPython

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    File Scopes

    **/*

    Reads only the user-selected local XML files and writes a new user-selected local result folder. The broad file glob reflects user-selectable paths, not background access. No mailbox, DNS, network or credentials are needed; the IETF URL in the README is documentation only.

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    This skill provides a local tool to compare two sets of DMARC aggregate XML reports, generating a change table and human-review checklist to identify new or missing sender IPs and alignment shifts. It solves the manual burden of parsing complex XML when verifying email infrastructure migrations or vendor changes.

    No, this tool operates entirely locally on your machine and does not require access to your mailbox or live DNS records. You simply provide the uncompressed RFC 9990 XML files for the tool to analyze.

    The package includes the Python CLI source code, a local MCP tool for AI assistants, a guide (SKILL.md), and sample data for testing. It is compatible with any AI agent that supports the Model Context Protocol (MCP) or can execute local Python scripts.

    This skill requires Python 3.11–3.14; if you use the optional MCP mode, the tool will automatically install the necessary official SDK. The tool works with standard uncompressed DMARC XML reports as defined by RFC 9990.

    The tool generates a deterministic report of observed changes between two data points, but it does not certify if a sender is legitimate or guarantee DMARC compliance. It is designed to assist human review, not to automate security decisions or live policy changes.

    New in Security