trustyourinbox

Lock down your domain. See the impact before you enforce.

Identify your senders and preview how a stricter DMARC policy could affect legitimate email.

Free DNS check. No signup required.

Start monitoring to build an Enforcement Preview from incoming DMARC reports. Free monitoring for 1 domain. Compare plans.

See the live demo (opens in a new tab)
Illustrated Enforcement Preview for kanbello.xyz at Reject: Google Workspace passes alignment, Mailchimp needs review, and sources we can't name would prompt a reject request.
Illustrated example. Preview replays past reports; receivers decide how to handle mail.

DMARC enforcement, without the guesswork.

  1. Know who’s sending

    Identify the services using your domain and spot authentication issues.

  2. Preview the impact

    Test a stricter policy against 30 days of reports to see what could be affected.

  3. Fix issues. Enforce protection.

    Resolve authentication issues for legitimate senders, then move your policy to Reject.

Attackers don’t need your mail server. They can still impersonate your domain.

Forged email can come from outside your infrastructure, so your mail logs never see it. DMARC reports from participating receivers show sending sources and authentication results. That’s how you find who is using your domain.

kanbello.xyzPolicy Reject
Example receiver report
SourceSPFDKIMReported action
Google WorkspaceIdentified senderPassPassNone
203.0.113.7Not identifiedFailFailReject

Your DMARC briefing. Straight to your inbox.

Catch up on your domain’s email activity in about a minute, daily or weekly. No login needed.

What arrived while you slept
Parsed.Distilled.
trustyourinboxExample briefing: your email needs a look

One thing needs your attention

2,523Alignment failures
90%Alignment after exclusions
New sender on kanbello.xyzLooks like Mailchimp. Confirm it is yours.
Review in demo (opens in a new tab)
The 90% leaves out failures from unnamed sources that receivers reported quarantining or rejecting. Those messages still count among the 2,523 failures.Findings include a next step.

Turn DMARC reports into clear next steps.

Identify your senders, enforce your policy in one click, and get answers where you already work.

Product examples below. Try the live demo (opens in a new tab)

See your senders by name

We match sending IPs against 1,000+ network ranges we maintain to identify services like SendGrid. Name your own servers once, and recognize them across your reports.

See a sender identification example
Example sender identification
Source IPIdentified asMatched range
198.51.100.24SendGridIdentified senderMatched range: 198.51.100.0/24
192.0.2.61PostmarkIdentified senderMatched range: 192.0.2.0/24
203.0.113.140MailchimpIdentified senderMatched range: 203.0.113.0/24
198.51.100.9mail.kanbello.xyzNamed by youMatched range: 198.51.100.9/32

One-click DMARC enforcement

Move from Monitoring to Quarantine, then Reject, one click per step. We write each change to Cloudflare or AWS Route 53 after five minutes and email you a record. Cancel before it applies, or undo it afterward.

Example policy change
kanbello.xyz
_dmarc.kanbello.xyzv=DMARC1; p=reject; rua=mailto:reports@kanbello.xyz
Writing to Cloudflare in five minutesWe’ll email you a copy once the record is written.Cancel
  1. Reject chosen
  2. Five-minute delay
  3. Written to Cloudflare
  4. Record emailed

Forward the message. Find the cause.

Send a bounce or an email that landed in spam to your private diagnosis address. Delivery Diagnosis explains what went wrong in plain English, with one-click fixes for supported DNS issues.

Example diagnosis
Forwarded bounce550 5.7.26 This mail is unauthenticated
Cause

The message failed DMARC. Its headers show no aligned DKIM signature and a Postmark Return-Path that does not align with kanbello.xyz.

Bounce codeMessage headers
Configure aligned DKIM or a custom Return-Path in Postmark.Postmark setup

Your DMARC data. In your AI assistant.

Connect Claude, Cursor, or another MCP-compatible client to your workspace. Ask questions in plain English and get answers grounded in your actual DMARC reports.

ClaudeCursorAny MCP client
See an example conversation
Example conversation
Who sent as kanbello.xyz this week, and did anything fail?

Three identified senders, all passing. One source I can’t name failed both checks and receivers reported Reject.

Google WorkspacePass
SendGridPass
Microsoft 365Pass
203.0.113.7Fail
Is 203.0.113.7 one of ours?

Reports alone can’t confirm that. This source failed SPF and DKIM alignment, and receivers reported Reject.

Same reports, same numbers as the app

Don’t take our word for it. Check the record.

DMARCv=DMARC1; p=reject; rua=mailto:…Reject
MTA-STSv=STSv1; id=… · policy mode: enforceEnforce
BIMIv=BIMI1; l=https://trustyourinbox.com/bimi/trustyourinbox.svgPublished

Every price

Pricing
Free1 domain$0
Lite5 domains$9/mo
Pro25 domains$19/mo

Yearly: Lite $84, Pro $180. MSPs pay per domain.

All systems operational
Application6 of 6
Email pipeline4 of 4

Checked every 5 minutes. Nov 6, 17:20 UTC.

Shipped

Changelog
The dashboard for a sample workspace: four summary cards for open issues, protected domains, mail passing and mail turned away, above a Start here card.

A clearer app, rebuilt around what needs you

Monitor your domain. For free.

Set up in five minutes. Get daily or weekly digests and fix supported DNS issues in one click.

  1. Monitoring
  2. Quarantine
  3. Reject