More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Email DNS Auth Check

    1

    Adding Google Workspace often leaves a second v=spf1 record next to the old one, and receivers then return permerror, so SPF fails for every message.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Email DNS Auth Check

    Email DNS Auth Check

    Example session with this skill installed

    Check this project with email-dns-auth-check.

    • Read your context and instructions
    • Compiled the email dns auth
    • Generated the data export

    $ python3 scripts/check_email_dns.py examples/risky
    BLOCK dns/cloudflare/example.net.txt:27 E06 SPF_OVER_10_LOOKUPS
    11 DNS lookups counted in these files (limit 10): example.net. TXT "v=spf1 a mx include:_spf.google.com include:spf.protection.outlook.com include:sendgrid.net ...
    Why: The include, a, mx, ptr and exists terms and the redirect modifier that can be seen (in this record and in included records found in the scanned files) already need more than 10 DNS lookups. RFC 7208 (section 4.6.4) allows 10; above that receivers return permerror and SPF fails for every message. Lookups inside includes not in these files come on top.
    Safer: Remove services you no longer use, replace a and mx with ip4/ip6 ranges, and move occasional senders to a subdomain with its own SPF record.

    BLOCK dns/zones/db.example.com:4 E04 NO_DMARC_RECORD
    BLOCK dns/zones/db.example.com:23 E02 SPF_ALLOWS_ANY_SENDER
    BLOCK dns/zones/db.example.com:24 E03 MULTIPLE_SPF_RECORDS
    BLOCK dns/zones/db.example.com:24 E05 SPF_RECORD_INVALID
    BLOCK dns/zones/db.example.com:27 E07 DKIM_KEY_UNDER_1024_BITS
    BLOCK dns/zones/shop.example.zone:4 E04 NO_DMARC_RECORD
    BLOCK dns/zones/shop.example.zone:8 E01 NO_SPF_FOR_MAIL_DOMAIN
    REVIEW dns/cloudflare/example.net.txt:22 E21 NO_SPF_ON_MAIL_SUBDOMAIN
    REVIEW dns/cloudflare/example.net.txt:26 E11 DMARC_NOT_ENFORCED
    REVIEW dns/cloudflare/example.net.txt:26 E12 DMARC_NO_REPORTS
    REVIEW dns/cloudflare/example.net.txt:28 E16 DKIM_KEY_SHORT
    REVIEW dns/cloudflare/example.net.txt:29 E17 DKIM_RECORD_PROBLEM
    REVIEW dns/exports/brand.example.csv:2 E20 NO_MAIL_DOMAIN_NOT_LOCKED
    REVIEW dns/route53/example.org.json:42 E13 SPF_LOOKUPS_NEAR_LIMIT
    REVIEW dns/route53/example.org.json:52 E11 DMARC_NOT_ENFORCED
    REVIEW dns/route53/example.org.json:52 E12 DMARC_NO_REPORTS
    REVIEW dns/zones/db.example.com:4 E15 NO_DKIM_KEY
    REVIEW dns/zones/db.example.com:18 E18 MX_TARGET_IP_OR_CNAME
    REVIEW dns/zones/db.example.com:19 E18 MX_TARGET_IP_OR_CNAME
    REVIEW dns/zones/db.example.com:23 E14 SPF_PTR_MECHANISM
    REVIEW dns/zones/db.example.com:27 E19 NAME_MISSING_TRAILING_DOT
    REVIEW dns/zones/shop.example.zone:12 E19 NAME_MISSING_TRAILING_DOT

    (Each finding also has Why and Safer lines, as in the first one.)
    Verdict: BLOCK. Checked 5 files, 5 with DNS zone content.
    This is a static check of file text. NOT FLAGGED is not a guarantee.

    example.csv

    CSV · data export

    Generated

    Example file from a real run - the skill writes it into your workspace.

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

    About this skill

    Adding Google Workspace often leaves a second v=spf1 record next to the old one, and receivers then return permerror, so SPF fails for every message. A DKIM record written in a BIND file as google._domainkey.example.com without the trailing dot ends up at google._domainkey.example.com.example.com, and a DMARC record with p=none and rua=dmarc@example.com (no mailto:) gives you neither protection nor reports. Gmail and Yahoo (since February 2024) and Outlook.com (since May 2025) send bulk mail without SPF, DKIM and DMARC to spam or reject it. This skill finds these mistakes in your zone files before you publish them, and tells you how to fix each one.

    Your agent runs a scanner on your DNS files: BIND zone files (db.example.com, example.com.zone), Cloudflare's BIND export, Route 53 JSON (list-resource-record-sets output, its ResourceRecordSets array, and change batches) and CSV exports with type, name and content columns. It reads them the way DNS servers and receivers do: $ORIGIN, $TTL, @ and relative names (also when the zone name comes from named.conf), records split over lines with parentheses, and TXT values split into several quoted strings, which are joined with no space. It decodes each DKIM key to measure its real size, counts SPF lookups and follows includes whose records are in the scanned files, and knows that subdomain zones inherit DMARC, that a null MX means no mail, that hosted DMARC and DKIM services delegated by CNAME or NS count as present, and that records meant to be included may end without all. It makes no DNS lookups. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Long keys and tokens are shortened in the report.

    What it checks

    BLOCK

    • E01: a domain (zone apex) with MX records but no SPF TXT record (an SPF-type record does not count)
    • E02: SPF ending in +all, all or ?all, or with no all and no redirect (neutral, like ?all)
    • E03: more than one v=spf1 record at the same name (permerror)
    • E04: a mail domain with no usable DMARC record at _dmarc: missing or at the wrong name, more than one, v=DMARC1 not first, or an invalid p= without rua
    • E05: SPF syntax errors: typos, include: with a space, an IP in include: or a:, bad ip4/ip6 ranges, strings joined to v=spf1 without a space, terms after all
    • E06: more than 10 SPF DNS lookups counted in the files (RFC 7208)
    • E07: a DKIM RSA key under 1024 bits, which verifiers must reject (RFC 8301)

    REVIEW

    • E11: DMARC p=none or no p=, pct below 100, t=y, sp=none or np=none
    • E12: DMARC without rua, or rua without mailto:
    • E13: 6 to 10 counted SPF lookups plus includes that are not in the files
    • E14: SPF ptr
    • E15: a mail domain with no working DKIM key under _domainkey (any selector; CNAME, NS and DNAME delegation count as present)
    • E16: a DKIM RSA key of 1024 to 2047 bits
    • E17: DKIM records without p=, with a cut-off or damaged key, v= not first, an unknown k=, t=y testing mode or sha1 only
    • E18: MX pointing to an IP address or to a CNAME
    • E19: mail record names or MX/CNAME targets in BIND files written as full names without the trailing dot
    • E20: domains that send no mail but lack v=spf1 -all or DMARC (reverse and subdomain zones are skipped)
    • E21: subdomains with MX but no SPF, often receive-only (publish v=spf1 -all there)

    What's included

    • The scanner (Python 3.9+, standard library only)
    • A rules guide with the reason and safer approach for each rule
    • A risky and a safe example DNS folder (two BIND zones, a Cloudflare export, a Route 53 listing and a CSV export for reserved example domains), and the real report the scanner produces on the risky one

    Limits It reads the records written in the files. Includes, CNAME targets, delegated DMARC and DKIM hosts and keys outside the scanned files are not looked up, and the lookup count covers only what it can see. Missing records are reported only for whole zones (an SOA record or a CSV export); snippets, change batches and single pages of a Route 53 listing are checked record by record. Terraform and other provider configs are not read, and DMARC alignment and live delivery are not checked. NOT FLAGGED is not a guarantee.

    Static check of DNS zone file text (BIND, Cloudflare export, Route 53 JSON, CSV). The live DNS, records outside the scanned files, DMARC alignment and delivery are not checked; Terraform is not read. NOT FLAGGED is not a guarantee.

    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 any payment.

    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 5 days ago

    Permissions

    Terminal / Shell
    Read Files

    Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example zone files are inert samples for reserved example domains, and their DKIM keys are made-up test values. The scanner reads files only: it makes no DNS lookups and never changes DNS records.

    Listed5 days ago

    What's inside

    Frequently Asked Questions

    No. The script reads local files only and makes no network calls.

    No. It only reports. Your agent changes files only if you ask it to.

    Any agent that supports SKILL.md skills and can run a terminal command, such as Claude Code. It needs Python 3.9 or newer and nothing else.

    No. It reads zone files and DNS exports you give it. It never makes a DNS query or calls any service.

    BLOCK: fix it before you ship. REVIEW: check it before release. NOT FLAGGED: no rule matched. It is a static check, so NOT FLAGGED is not a guarantee.

    The scanner, a rules guide with the reason and safer approach for every rule, a risky and a safe example set of zone files, and the real report the scanner prints on the risky example.

    New in DevOps & Cloud