DMARQ

Guided setup

Mail health setup

Connect DMARC reports, add your first domain, check DNS posture, and prepare the next safe remediation steps for this instance.

Setup path

Start with one monitored domain, then expand from the domain list once reports and DNS checks are working.

Self-hosted
  1. 1 Connect Gmail or IMAP so DMARQ can discover aggregate reports.
  2. 2 Add or import domains, then verify ownership before DNS repair actions.
  3. 3 Review DMARC, SPF, DKIM, MTA-STS, and remediation readiness.

Domain and DNS

Add the first domain to monitor. DMARQ will show DNS health, report coverage, and human-approved repair steps.

Verification gate

Report ingestion path

Choose whether DMARQ should prepare a report mailbox connection now or start with DNS posture checks first.

DMARQ will create the domain checklist without storing mailbox credentials. A report source can be connected later from Mail Sources.

Current release

v1.165.0 · 814725111bd2

Version
1.165.0
Environment
demo
Build
814725111bd2
Image tag
8147251
Ref
v1.165.0
Built
2026-07-07T13:51:49Z
Image
ghcr.io/christianlouis/dmarq:8147251

Release endpoint: /api/v1/health/release

What's changed

Full changelog

Faster domain pages

Domain list and domain detail views use precomputed database aggregates so report-heavy installs load with less waiting.

Sender intelligence

Sending sources now include provider detection, network context, first/last seen activity, and optional reputation feed checks.

Self-hosted demo focus

The default demo and navigation emphasize the single-user, multiple-domain self-hosted story.

Cloudflare rights profiles

The Cloudflare connector exposes read-only, read-only plus Radar context, and full DNS repair profiles so operators can choose the least privilege needed for the next action.

Safer DNS repair workflow

DNS changes remain human-approved, with provider imports, ownership verification, repair previews, and audit-friendly settings separated from automatic write actions.

In-product release visibility

The current version, build image, git ref, build date, and recent operator-facing fixes are available from the small release label in the app shell.

CSP hardening progress

Inline handlers and style bindings continue moving out of templates toward external scripts and CSS so strict CSP can become the default.

Actionable remediation groundwork

Domain and report detail views include clearer next steps, DNS lint evidence, source intelligence, and safer repair context for DMARC operations.