Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Cold Email Domain Guardian

    1

    Protect sender reputation with email authentication, domain health, list hygiene, and compliant outreach controls.

    $9.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Cold Email Domain Guardian

    Cold Email Domain Guardian

    Example session with this skill installed

    Review this fictional outbound email setup using only the supplied facts. Primary domain: example.com. SPF record exists but its content is unknown; DKIM is enabled for one provider; DMARC is p=none with aggregate reports enabled. Complaints increased from 0.05% to 0.18% over two weeks; hard bounces are 3.2%. The team imports a new event list with unclear consent provenance next week. No DNS lookup, provider dashboard, or legal review has been performed. Give an evidence-based risk summary, immediate containment steps, verification checklist, and 30-day remediation plan. Explicitly avoid evasion or sending advice that bypasses provider enforcement.

    • Read your context and instructions
    • Compiled the cold email domain

    Domain health review

    Scope: Fictional facts only. No DNS records, mailbox-provider dashboards, headers, legal records, or live reputation data were inspected. Current provider requirements and applicable law must be checked before action.

    Risk summary

    High, immediate: The upcoming event list has unclear consent provenance. Pause import and sending until source, collection purpose, permissions, suppression status, and applicable outreach rules are verified. Do not use the list to test deliverability.

    High: Hard bounces at 3.2% indicate a list-quality problem if measured accurately and consistently. Stop sending to invalid addresses, review acquisition source and validation practices, and protect existing customer mail streams.

    High: Complaints rose from 0.05% to 0.18%. Confirm provider-specific complaint signals, denominators, campaign, and audience; pause or sharply constrain affected outreach while root cause is investigated.

    Medium / unknown: SPF content is unknown, DKIM is enabled for only one provider, and DMARC is p=none. This does not establish misconfiguration, but domain alignment and all authorized senders need verification.

    Immediate containment (today)

    1. Freeze the event-list import and related campaigns until provenance, permission, and suppression checks pass.
    2. Pause the campaign or segment associated with the complaint and bounce increase; do not route it through a different domain or provider to avoid enforcement.
    3. Preserve evidence: campaign IDs, timestamps, recipient source, bounce categories, complaint signals, and provider notices. Remove or suppress invalid and opted-out recipients under the approved process.
    4. Check that transactional and customer-support mail remain isolated from marketing operations and are not disrupted.
    5. Assign an owner in deliverability, security, and legal/compliance to coordinate review.

    Verification checklist

    AreaEvidence to gatherSafe check
    SPFFull DNS record, all legitimate senders, lookup count, recent changesCompare authorized sending sources; correct only through controlled DNS change review
    DKIMSelectors, signing coverage, alignment, key ownership/rotationSend controlled tests to owned mailboxes; inspect headers and alignment
    DMARCExact record, reporting destinations, alignment mode, legitimate sender inventoryReview aggregate reports and policy with email/security owners before enforcement changes
    List qualitySource, collection date, permission basis, address validation, suppression syncQuarantine unclear sources; honor opt-outs and complaints
    ReputationProvider dashboard, complaint/bounce definitions, campaign/time trendsConfirm provider-specific thresholds and any notices directly with the provider
    OperationsRate changes, segmentation, templates, links, identity, incident recordsIdentify the affected change without bypassing provider safeguards

    30-day remediation plan

    Days 1–3: Pause uncertain data and affected campaigns; validate complaint/bounce measurements; inventory authorized senders and DNS records; honor suppression events.

    Days 4–10: Correct confirmed authentication or alignment gaps through reviewed changes. Remove unauthorized senders. Document list provenance and approval requirements. Test only with owned mailboxes and provider-approved diagnostics.

    Days 11–20: Rebuild list acquisition controls, verify permission and suppression sync, segment by source and engagement where lawfully appropriate, and update relevant message expectations and opt-out paths.

    Days 21–30: Resume only after responsible owners approve a conservative, provider-compliant plan. Monitor complaint, bounce, unsubscribe, and delivery signals; define pause thresholds from current provider guidance. Run an incident exercise and keep audit evidence.

    Guardrails

    Do not rotate domains/IPs to escape poor reputation or enforcement; do not manufacture engagement or conceal sender identity; do not send to unclear-consent lists. Escalate suspected spoofing, compromise, or provider enforcement using the provider’s official incident process.

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

    About this skill

    Cold Email Domain Guardian

    Review and strengthen the infrastructure, identity, data quality, and operational controls behind legitimate B2B email outreach. Assess SPF, DKIM, DMARC, DNS, domain alignment, sending identity, provider health, bounce and complaint signals, suppression handling, list provenance, consent, monitoring, and incident response using evidence the user supplies or explicitly authorizes.

    Produce a domain and campaign risk review, evidence-backed diagnostics, prioritized remediation plan, authentication and monitoring checklist, incident playbook, and safe rollout plan. Protect the organization’s primary domain and customer communications by favoring wanted, relevant messages, accurate sender identity, verified lists, conservative operations, opt-outs, observability, and root-cause remediation.

    Never provide tactics for spam-filter evasion, disposable-domain cycling, IP rotation to bypass enforcement, artificial engagement, hidden or obfuscated text, CAPTCHA circumvention, purchased or scraped list abuse, impersonation, phishing, spoofing, opt-out avoidance, provider-limit evasion, or deceptive identity. Never invent DNS state, domain age, reputation, deliverability, consent, or provider enforcement. Verify current provider requirements and applicable law before making changes.

    Assessment depends on supplied or expressly authorized DNS, provider, campaign, and list evidence; snapshots may be incomplete or stale. It cannot guarantee inbox placement, sender reputation, or legal compliance. Provider thresholds and requirements vary and change. Do not alter DNS, send campaigns, upload recipient lists, or change suppression state based solely on this report. All changes require authorized owners, current documentation, and controlled validation.

    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 1 month ago

    Permissions

    Browser
    Network Access

    Browser/network access is limited to public DNS, official provider documentation, and other explicitly authorized business sources. Do not sign into mail or DNS accounts, transmit recipient lists, send email, change DNS, or access provider dashboards unless the user separately authorizes those actions and tools. Never bypass provider safeguards.

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    It focuses on authentication, wanted mail, list quality, suppression, and root-cause remediation. It does not provide evasion tactics or guarantee inbox placement.

    No. It provides reviews and plans. Any DNS, provider, suppression, or campaign changes require separately authorized tools, approvals, and change controls.

    No. Pause the import and any related sending until list source, permissions, suppression checks, and applicable requirements are verified by responsible owners.

    New in Security