DMARC monitoring
Hosted rua ingestion with per-source breakdown, forwarder detection, and alerts on new sources sending under your domain.
See DMARCDeliverability
The whole deliverability picture, in one workspace.
DMARC monitoring, auth check, Google Postmaster ingestion, blocklist watch, and seed-list placement testing — on the same data model as the routing that carries the send. One workspace, one answer.
Sound familiar?
Half a day, half your team, four different tools.
Root-causing a deliverability drop takes half a day and half your team. You check the ESP dashboard, then the Postmaster page you have to log into separately, then MXToolbox, then the seed-list tool your marketing agency runs once a month. Every tool sees a different slice; nobody sees the whole picture. By the time the story adds up, the drop has been running for two days and the exec review is tomorrow.
How sendrules fixes it
One data model. One dashboard. One story.
sendrules ingests DMARC aggregate reports, Google Postmaster telemetry, blocklist state, and seed-list placement into the same workspace as your route logs, and joins them on the domain and the lane. When the story is “Gmail placement dropped on Monday,” the DMARC alignment, the Postmaster reputation, the blocklist state, and the recipient-level bounce reasons are on the same screen at the same time.
What’s included
Five surfaces. One workspace. No add-on SKU.
Auth check
SPF, DKIM, and DMARC graded together — the same view an auditor or a large ISP would look at when accepting a message from you.
Grade a domainPostmaster ingestion
Google Postmaster Tools ingested into per-domain views so IP and domain reputation, spam rate, and authentication sit on your dashboard.
See PostmasterBlocklist watch
Live probe of the major blocklists — your sending IPs and domains checked on a schedule with an alert the moment a listing appears.
See blocklistsSeed-list placement
Inbox, promotions, or spam — measured across the mailbox providers that matter, on a schedule you set, joined to the campaign that produced the placement.
See placementWhich do I need?
Start with the question you actually have.
Are you a bulk sender?
If you send more than 5,000 messages a day to Gmail or Yahoo, you are subject to their bulk-sender rules. Start with DMARC monitoring and the auth check — those are the two surfaces the ISPs are grading you on.
Are your consumer messages landing?
If replies dropped, opens dropped, or a marketing campaign under-delivered against the same list as last week, add Postmaster ingestion and seed-list placement. The first tells you what Google sees; the second tells you which folder the message ended up in across the mailbox providers that matter.
Has your reputation dropped?
If a specific sending IP or domain took a hit, blocklist watch tells you whether a listing is the cause, Postmaster tells you whether the ISP’s reputation signal has moved, and the route log tells you which campaign the drop started on.
Are you being spoofed?
If someone else is sending under your domain, DMARC monitoring is the first surface — the aggregate reports show the source, the alignment, and the volume of unauthorised mail. Move from monitor to enforce when the picture is clean.
Unified data model
How they work together.
Every surface writes into the same workspace and keys off the same domain, the same sending mailbox, and the same lane classification the routing layer already uses. A Monday Gmail placement drop stops being “what happened?” and starts being “the auth check is green, the blocklist watch is clear, the Postmaster reputation moved from High to Medium at 09:00, and the campaign that started at 08:45 shows a spam-complaint rate above your usual baseline.” The story assembles itself.