DMARQ
Öffentliche Demo - read-only
Änderungen werden nicht gespeichert. Nutze eine eigene DMARQ-Installation, um echte Einstellungen zu ändern.

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.

Unsaved setup changes
Checking the current setup...

Start with your situation ·

Also relevant to me

Optional. Your first choice remains the primary goal that determines the next action.

Can you change DNS for this domain?
Does this domain intentionally send email?
Optional symptom details

Progress is saved after each answer.

DMARQ will use these preferences to prioritize your next step. You can change them later.

Preparing your next step...

Your next step

Done when:

After that

Why DMARQ chose this step

Known facts

Still unknown

DMARQ's interpretation

Blocked by

Current setup

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.
Other ways to bring in reports

Choose the path that matches where your DMARC reports arrive. You can add more than one source later.

Gmail API Use Google OAuth when the report mailbox is in Gmail. DMARQ asks for read access to the configured mailbox only. Configure Gmail Microsoft 365 Use Microsoft Graph with delegated access or a tightly scoped Entra application for a dedicated report mailbox. Configure Microsoft 365 Upload a report Best for a quick evaluation or a first explanation. Upload XML, ZIP, or GZIP report files without connecting a mailbox. Upload a report Webhook or Cloudflare Email Worker For automated forwarding from an existing mail route. This needs a reachable HTTPS DMARQ URL and a webhook secret. Open webhook guide

Current release

v1.195.8 · 45820c65f323

Version
1.195.8
Environment
demo
Build
45820c65f323
Image tag
45820c6
Ref
v1.195.8
Built
2026-08-01T12:12:44Z
Image
ghcr.io/christianlouis/dmarq:45820c6

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.