Enterprise DNA

Instead of DMARC.global

Stop renting DMARC.global. Own your email authentication desk.

We build your version around the domains you manage, bring your available report history across and run the review work for you. Your sender decisions and investigation history stay in a database you own.

DMARC.global lists its 1,000-domain MSP plan at US$14,990 billed yearly, or US$1,499 billed monthly. Smaller portfolios have lower-priced plans.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the subscription covers

Domain capacity, report analysis and managed services

The large-portfolio plan combines a review workspace with hosted services. Separate the evidence and decisions you can own from the collection and hosting your business still needs.

paid

A recurring portfolio bill

The published 1,000-domain tier costs US$14,990 with annual billing. This comparison is for that larger portfolio, not the free single-domain plan.

domain

Capacity priced by domain count

The MSP choices cover 50, 250 or 1,000 domains. Your review history is still the record of the domains you manage.

analytics

Report interpretation

Aggregate reports describe sending sources, authentication outcomes and receiver handling. Your own version keeps that evidence alongside the work it creates.

dns

Hosted authentication records

Paid plans include hosted SPF and DMARC management. Agree the hosting and collection arrangements as part of your custom build.

group

A workspace for engineers

Team access and organisation controls sit around the portfolio. Enterprise DNA defines the access your own installation needs.

support_agent

An ongoing service relationship

Support and managed features are part of the package. Your own version needs someone responsible for its operation too.

The desk you own

Connect reported failures to decisions and follow-up work

Evidence

Keep the report and its meaning together

Read the original evidence whenever a summary raises a question.

  • check Retain the original receiver report with its reporting interval
  • check Keep source addresses and reported handling beside message counts
  • check Separate aligned authentication results from raw signature results
  • check Reject duplicate or overlapping evidence before it inflates totals

Senders

Know who has reviewed each source

An unfamiliar source becomes a review task, not an automatic accusation.

  • check Record a service name, reviewer and supporting evidence
  • check Keep sender approval separate from authentication success
  • check Find approved services that have gone quiet
  • check Connect failed checks to the recorded sender decision

Follow-up

Give each investigation an owner

Move from a failure count to a named piece of work.

  • check Record a case, evidence, due date and responsible person
  • check See overdue cases across the portfolio
  • check Require an outcome before closing an investigation
  • check Draft a weekly review from coverage, unknown sources and overdue work

Review

Prepare decisions from your own history

Bring the domain, its sources and unfinished work into one review.

  • check Show missing collection purposes and overdue retention reviews
  • check Keep policy observations separate from proposed changes
  • check Save a policy-review draft with its evidence snapshot
  • check Produce branded domain reviews and investigation records

Make it yours

Design your own DMARC.global replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from DMARC.global. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your DMARC.global replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your DMARC.global data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Email Authentication for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Email Authentication for Claude Code

Connected to your own database

Which unfamiliar sources are failing our email checks?

harbour.example

Ip
198.51.100.20
Service
Unidentified
Decision
unknown
Messages_30d
12
Failures_30d
12

Ask it anything

Ten questions your own records answer

Each question is answered by the working demo. Change the review rules and reports to fit your business.

chat_bubble Which domains have received no reports or only old reports?
chat_bubble Which unknown sources account for authentication failures?
chat_bubble Which approved sending sources still fail both aligned checks?
chat_bubble Which approved services have been quiet for over a month?
chat_bubble Which investigations are overdue and who owns them?
chat_bubble Which domains lack a recorded collection purpose?
chat_bubble Which domain retention reviews are due?
chat_bubble Which sender reviews have expired?
chat_bubble Which domains combine failed messages, unreviewed sources and open cases?
chat_bubble What did a receiver actually report before we opened a case?

Switching

How to switch from DMARC.global

A move like this involves collecting the records you can obtain, mapping them into the replacement, checking the results and confirming report collection before you end your subscription.

  1. 1

    Gather the records

    Ask DMARC.global what your account can export, usually CSV or Excel, and check with them if you need help. The replacement can import retained aggregate XML reports from an authorised mailbox or archive. A complete native DMARC.global history export has not been verified, so do not assume all historical reports are available.

  2. 2

    Load the available records

    Have the replacement import retained aggregate XML reports, and use a test run first to see what it will accept before committing the import. If you only have a CSV export, it needs its own tested mapping. Include the domains and records you want to bring across, and keep the original exports and reports available while you check the results.

  3. 3

    Review import findings

    Check what the import accepts or rejects before relying on the new records. Identical duplicate reports are harmless, but changed content with the same report identity and overlapping periods needs reconciliation. Only registered policy domains are accepted. Resolve mismatches and confirm the imported reports and domain records make sense against your source material.

  4. 4

    Run both side by side

    Keep DMARC.global running while you arrange replacement report collection and authentication hosting. The replacement does not collect reports automatically or publish DNS changes. For a short period, compare incoming report coverage, receiver observations and the records you use for reviews. Investigate gaps or differences before you rely on the replacement.

  5. 5

    Switch off DMARC.global

    End your DMARC.global subscription only after you have tested continuity, reconciled the records you intend to keep and confirmed the replacement collection and hosting arrangements. Keep any retained reports or exports you still need for your records. The replacement is an internal review workflow, not a like-for-like replacement for DMARC.global's hosted services.

construction

Where the real effort goes

The main work is usually mapping your own fields and review rules, then deciding how much history to bring. Retained aggregate XML can be imported; a CSV export needs a separately tested mapping, and complete DMARC.global history may not be available. When Enterprise DNA runs your version, it maps the available history and sets up the agreed fields and review rules.

Not ready for a call?

Get your DMARC.global switch plan by email

We will send you the step-by-step plan for moving your business off DMARC.global, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Build it yourself, have it customised, or have it run for you

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo, run npm install and npm run demo
  2. 2 Open it with Claude Code, Codex, OpenCode or Cursor and ask for the sender review
  3. 3 Register your domain and test a retained aggregate XML report before importing it
  4. 4 Arrange your reporting mailbox, database access and backups before switching
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your available DMARC.global history checked and mapped across
  • check Your sender fields, review dates, domain ownership and decision rules
  • check Report collection and hosting connections scoped for your business
  • check A web front end or a different stack where your team needs one
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed with access, backups and operating responsibilities arranged
  • check The weekly domain review and investigation follow-ups prepared
  • check Maintained as your domains and sending services change
  • check Run through Omni by Enterprise DNA beside the rest of your business
Book a 30-minute call

Questions

Instead of DMARC.global, answered

Can we stop paying DMARC.global as soon as the records move? expand_more

First confirm what it currently hosts or collects for you. Agree replacement report collection and authentication hosting, test continuity, and reconcile the records before ending a subscription. Enterprise DNA scopes those connections with your own version.

Can you bring across all our existing history? expand_more

The free version imports retained aggregate XML reports from an authorised mailbox or archive. We have not verified a native export of the complete DMARC.global history. We inspect the records you can obtain and agree the mapping before promising a migration.

Will this block unwanted mail or change our domain settings? expand_more

The free version records evidence and prepares review drafts. It does not publish domain changes or block messages. Your own managed version can include approved connections, with a separate decision before changing live email handling.

Does a passing check mean the message reached the inbox? expand_more

No. Authentication is one part of the receiving service's decision. Reports show what participating receivers observed. They do not prove inbox delivery, complete coverage or that a sending service has your permission.

What do we pay Enterprise DNA? expand_more

One setup fee to build your version and bring the agreed records across, then a retainer to run and improve it. Sam scopes the domains, hosting, access, review work and connections with you. The free version is also available to run yourself.

Bring your domain bill and one unresolved sender

In a 30-minute call, Sam will work through the records you have, the services you still need and what your own email authentication desk should do first.

Book a 30-minute call Get the free version

Email Authentication for Claude Code is free and open source, published by Enterprise DNA.

Done paying for DMARC.global?

Get your version built