sendrules
Home
Product
  • Overview
    How sendrules fits between your app and every provider.
  • SMTP Proxy
    One endpoint. Every provider you already trust.
  • Grid & Rules
    Six routing strategies. Coverage warnings. Failover.
  • Quality Gate
    Verify recipients before the send, not after the bounce.
  • ISP Routing
    Route by the recipient's live MX record — not domain strings.
  • Ramp-up
    Auto-advancing cap with bounce/complaint safety gates.
  • Limits & Queue
    Four-tier caps. Queue, don't drop. Midnight-UTC release.
  • Webhooks
    Signed and verifiable. Retried on schedule. Replayable.
  • Activity
    Seven filtered inboxes. Sparklines. Share links.
  • Inbound
    Receive + classify replies, bounces, and OOOs.
  • Autoresponder Parser
    Harvest contacts from OOO replies into lists — webhook or CSV.
  • REST API
    Every UI action has an endpoint. Scoped, rotatable keys.
  • Teams and roles
    Fine-grained RBAC across 30 resource types + audit trail.
Deliverability
  • Overview
    The suite most vendors sell separately.
  • DMARC Monitoring
    DMARC aggregate reports ingested with per-source breakdowns.
  • Auth Check
    SPF / DKIM / DMARC, graded A through F.
  • Postmaster Tools
    Google Postmaster data in per-domain views.
  • Blocklists
    Continuous blocklist + seed-list inbox placement.
  • Free Tools
    Email validation, spam check, DMARC generator — free on every plan.
How it Works
Industries
  • All industries
    Every segment sendrules fits — and why.
  • B2B SaaS
    Transactional at scale. Failover across ESPs.
  • E-commerce & Retail
    One rule per ISP — Gmail buyers routed differently to Yahoo.
  • Marketing Agencies
    Per-client rules on your clients' own provider accounts.
  • Sales Development
    Verify every address. Parse every autoresponder for referrals.
  • Recruitment & Staffing
    OOO replies are full of decision-maker names — capture them.
  • Real Estate & Lead Gen
    Inquiry email hygiene + reply-source enrichment.
  • Financial Services
    DMARC compliance, audit log, signed webhooks.
  • Healthcare & Life Sciences
    Reliable patient comms with a full audit trail.
  • EdTech & Education
    Enrollment-week bursts absorbed by queue-don't-drop.
  • Nonprofit & Fundraising
    Donor-appeal deliverability without a deliverability team.
  • Publishers & Media
    Newsletter deliverability + list hygiene at every send.
  • Government & Public Sector
    IP allow-list at AUTH, DMARC-first, tenant isolation.
PricingProduct Demo
Sign inStart free
DMARC

DMARC monitoring, not just DMARC ingestion.

Publish one CNAME, and we take over the hosted reporting address, the report parsing, and the story the reports actually tell — the compliance percentage, the known and unknown sources, and the forwarders that would otherwise look like a threat.

Start freeSee the pricing
Sound familiar?

The reports arrive as XML you never open.

You send more than 5,000 messages a day to Gmail. Since Google and Yahoo’s February 2024 bulk-sender rules, that means you need DMARC — or your consumer mail starts landing in the promotions tab, then the spam folder, then nowhere. Your aggregate DMARC reports arrive as XML at an address you’ve never checked, from reporters you can’t identify. Nobody on the team can honestly say what percentage of your mail is aligned this week.

How sendrules fixes it

The reports become a picture, not a mailbox.

sendrules gives you a hosted reporting address you publish once. We ingest the reports, decode them, join them to the domains and lanes the routing layer already knows about, and surface the story: what your compliance percentage is today, which sources are sending under your domain, which of those are you, and which of the failures are forwarders you can safely ignore.

Why now

5,000 a day to Gmail is the line.

Google and Yahoo’s February 2024 bulk-sender rules made DMARC a requirement for anyone sending more than 5,000 messages a day to their consumer users. Fall below the bar and your mail starts landing in the promotions tab, then the spam folder, then nowhere at all — with no notification, no bounce, and no dashboard row telling you why open rates halved. The threshold is per-provider and cumulative, and it does not reset week to week.

Compliance

The compliance percentage that matters.

What it is
The share of your mail volume — as the ISPs saw it — that aligned on both SPF and DKIM under your published DMARC policy. Not the share of reports; the share of the messages behind them. This is the number the mailbox providers use to grade you.
Why weekly
Aggregate reports land on a rolling window from each reporter. A daily reading swings on which reporter reported when; a weekly reading is what actually predicts placement next week. sendrules surfaces both, with the weekly view as the default.
What good looks like
Above 99 percent aligned across the previous seven days on your production sending domains, with no unknown source above the noise floor. Below that, the workspace flags the specific source that’s dragging the number down and links to the route logs from the same lane.
Sources

Known, unknown, and forwarded.

Known
A source you have authorised — an ESP you attached, your own outbound infrastructure, a transactional provider on a rule. sendrules matches the report against the providers you have connected and marks them as expected, so a big number here is reassurance rather than an alarm.
Unknown
A source sending under your domain that we can’t match to anything you have authorised. This is the alerting bucket — a marketing agency spun up a new ESP without telling anyone, a legacy application is still sending from a server you thought was retired, or someone is spoofing you. Every unknown source is surfaced with its volume and its alignment so you can act on it before the ISPs do.
Forwarded
A message that left you clean and picked up a forwarder on the way to the recipient — a personal .forward, a mailing-list rewriter, a corporate mail gateway. The alignment fails through no fault of your setup. sendrules recognises the fingerprint and separates these out so the compliance number reflects your real posture, not the forwarding habits of your recipients.
Hosted reporting

One CNAME to publish. We take the reports from there.

The workspace generates the hosted reporting address for each of your domains. You publish one CNAME record — the reporters see a valid address, we receive the reports on your behalf, and the dashboard fills in as the first ones land (usually within twenty-four hours). No mailbox to provision, no XML parser to maintain, no separate vendor bill. If you already publish a reporting address elsewhere, you can add ours alongside it — DMARC allows more than one recipient.

Ready to see who’s sending under your domain — and how much of it is aligned?

Start freeSee the pricing
sendrules

One SMTP endpoint across 15 providers. Verify recipients before the send, route by real MX, and monitor DMARC in the same product.

Sign inStart free

Product

  • SMTP Proxy
  • Grid & Rules
  • Quality Gate
  • ISP Routing
  • Ramp-up
  • Limits & Queue
  • Webhooks
  • Activity
  • Inbound
  • Autoresponder Parser
  • REST API
  • Teams and roles
  • Integrations

Deliverability

  • DMARC Monitoring
  • Auth Check
  • Postmaster Tools
  • Blocklists
  • Free Tools
  • Providers

Solutions

  • How it Works
  • Industries
  • Customers
  • Pricing
  • Contact

Company

  • About
  • Security
  • Terms
  • Privacy
  • DPA
  • Acceptable Use

© 2026 sendrules.com