Sender reputation intelligence. In one place.
Feedback loops, blacklist monitoring and reputation signals combined into one actionable view. Know who is complaining, where reputation is changing, why it matters — and what to do next.
Today — scattered
6 providers, 6 formats, no correlation
- GmailCSV
- YahooARF
- MicrosoftSNDS
- Validity UFLLoop
- Signal SpamMailbox
- ApplePDF
- 1. Collectevery provider feed, one inbox
- 2. Normalize6 formats → one schema
- 3. Attributeto your IP, domain, campaign
- 4. Score & alertonly when it matters
With Floopr
One alert you can act on
0.42%
+240% vs 7-day baseline
- Domain
- news.acme.io
- IP
- 185.12.44.9
- Campaign
- aug-newsletter
- Providers
- 4 agree
Illustrative demo data
Floopr Reputation Score
3 pts / 7 days
Normalized from your complaint feed and blacklist monitoring.
Floopr's own normalized score. It is not a Gmail, Yahoo or Microsoft score and no provider endorses or publishes it.
Contributing signals
Complaint health
24h rate across all monitored identities
0.11%
weight 30%
Blacklist status
185.24.10.4 on a public DNSBL
1 listed
weight 25%
Yahoo / AOL complaint trend
vs. the account's own 7-day baseline
+38%
weight 15%
Microsoft status
JMRP volume flat, SNDS colour green
Stable
weight 10%
Domain reputation
news.acme.io — no negative movement
Good
weight 10%
IP reputation
185.24.10.4 — complaints then listing
Degrading
weight 10%
Complaint rate
0.11%
-0.03
FBL events (24h)
2,530
+184
Identities
18
+2
Complaint trend — 12 weeks
per 10k sendsProvider signals
Recent FBL events
mx1.eu-west
185.24.10.4 · Yahoo
news.acme.io
185.24.10.9 · Validity
tx.acme.io
185.24.11.2 · Microsoft
news.acme.io
185.24.10.4 · Yahoo
mail.acme.io
185.24.11.7 · Signal Spam
Affected domains & IPs
news.acme.io
185.24.10.4
mail.acme.io
185.24.11.7
tx.acme.io
185.24.11.2
Attribution — what is behind the change
Sending IP
185.24.10.4
Customer / account
acct_4821 · Northbound
Campaign / source
aug-newsletter
Mailbox provider
Yahoo / AOL
Illustrative sample data — every number, domain and IP above is fictional.
Why Floopr
Know who is complaining, where reputation is changing, why it matters.
Floopr turns complaint feedback and blacklist monitoring into one structured reputation signal layer for the teams responsible for deliverability — correlated and normalized, not a pile of raw reports.
Combine complaints and blacklists
Feedback loop complaints and blacklist monitoring land in the same place, on the same assets, on the same timeline — instead of two tools that never talk to each other.
Normalize every source
Providers report differently and blocklists report differently again. Floopr maps everything into one consistent model of identity, provider, category and timestamp.
One reputation score
A normalized Floopr Reputation Score summarises complaint health, blacklist status and provider trends, with the contributing signals always visible behind it.
Know what to do next
Attribution resolves a reputation change to an IP, a customer, a campaign and a provider, so the next action is obvious instead of theoretical.
The intelligence chain
From a single complaint to the action that protects your sending
Floopr's value is correlation and normalization, not raw report display. Feedback loops and blacklist monitoring are placed on one timeline so the sequence is visible — Floopr shows what happened in which order, and does not claim one event caused the next unless that is proven.
- 01Live
Complaint signal
A recipient marks a message as spam. The provider's feedback loop returns a per-complaint report tied to your sending identity.
- 02Live
Reputation deterioration
Complaint volume for that IP, domain or source moves above its own baseline. Floopr tracks the drift rather than a single event.
- 03Live
Blacklist event
Blacklist monitoring shows a listing on the same asset. Floopr places it on the same timeline as the complaint movement.
- 04Observed
Deliverability impact
Provider-side behaviour changes — throttling, foldering, rejections. Floopr shows the signals it can observe and labels the rest as unverified.
- 05Action
Recommended action
Pause a stream, isolate a customer, review a campaign, request delisting. One prioritised next step instead of five open tabs.
Correlation, stated carefully: a complaint spike that precedes a listing on the same IP is shown as a sequence with timings, not as a causal claim. You get the evidence and the ordering; the conclusion stays yours.
Attribution
Not “73 complaints” — which IP, which customer, which campaign
A complaint count tells you something is wrong. Attribution tells you where to act. Every normalized event carries the sending IP, the customer or account behind it, the campaign or source reference and the mailbox provider — so a reputation change resolves to an owner in minutes.
Reputation change on 185.24.10.4 — attributed
Illustrative demo data.
An operational layer for ESP abuse teams
- Isolate the sending customer creating reputation risk before it reaches your shared pools.
- Hand your abuse desk evidence per account: complaint counts, timings, providers and listings on one record.
- Feed suppression and throttling decisions from the same normalized event your dashboard shows.
- Keep per-customer history so an account's pattern is visible, not just today's incident.
FBL Coverage
Exactly who your complaints come from — and who gives nothing back
Only providers that actually run a documented feedback loop produce per-complaint events. Aggregate providers publish rates only, some operators report by agreement, and several large mailboxes offer nothing at all. Every group is labelled so nothing looks like coverage it is not.
Did you know…
Gmail, Microsoft and Yahoo together handle the majority of the world's consumer email. Depending on geography and audience, they typically represent 60–80% of consumer inboxes — so coverage of those three decides most of what you can actually see.
Yahoo / AOL
Documented FBLPublic self-service programme (CFL), enrolled per DKIM signing domain.
Microsoft
Documented FBLPublic programme. JMRP returns complaint copies per IP; SNDS adds reputation and volume data.
French ecosystem
Documented FBLOrange, SFR and La Poste run no standalone self-service loop. Signal Spam membership is the single route to French consumer complaint data.
Aggregators
Documented FBLOne commercial enrolment is now the route to several mailbox groups that closed their own loops — Comcast, La Poste, Libero / Virgilio and Seznam among them.
Any ARF loop (RFC 5965)
Documented FBLPoint an existing loop at your Floopr address and it is parsed like a native source.
Aggregate-only providers
Aggregate onlyDaily complaint rates per domain. No per-message copies exist, so no recipient-level action is possible here.
No FBL offered
No public feedThese providers return nothing directly to senders — only an abuse desk you can complain to, which is the mailbox owner's channel, not a sender feed. Floopr names the blind spot instead of implying coverage.
Coverage map by market
Gmail + Microsoft + Yahoo share · local mailboxes · what Floopr can see
The big three dominate globally, but the local remainder is where your blind spots live. The bar shows roughly how much of each market Floopr can observe today.
Apple iCloud, regional ISPs
Apple iCloud returns nothing to senders
BT/Sky (Yahoo-hosted), Apple
Apple and some ISP brands unmeasured
GMX + Web.de (United Internet) ~30–40%
United Internet runs no feedback loop at all
Orange, SFR, Free, La Poste
French ISPs report only via Signal Spam / Validity
Telenor, Telia, Get (no FBL)
Telco mailboxes have abuse desks, no loops
Libero, Virgilio, PEC mailboxes
Libero/Virgilio only through Validity UFL
Terra, UOL, Locaweb
Telefónica and Brazilian ISPs publish nothing
Seznam (email.cz) ~30%+
Seznam complaints arrive only via Validity
Yahoo! Japan, Naver, Daum
Korean mailboxes are whitelist-only, no feed
Share figures are public industry estimates of consumer mailbox mix and vary by audience, age group and B2B/B2C split. Treat them as planning guidance, not measurement.
Provider support and access requirements differ. Some feedback loops require domain or IP verification, some are limited to certain sender types, and not every mailbox provider offers complaint data at all. Source counts are indicative of programs Floopr can ingest, not a guarantee of enrolment for every sender.
Data layer
Complaint and reputation signals — deliberately not everything
Floopr's territory is complaint and sender reputation intelligence. The data layer is built to expand into adjacent reputation sources, but it is not becoming a generic all-in-one deliverability toolbox. Everything below is labelled by what exists today and what is planned or possible.
Feedback loops (FBL)
Per-complaint ARF reports from documented provider programmes, normalized into one event model.
Blacklist monitoring
Listing status for your monitored IPs and domains, correlated with complaint movement on the same asset.
Google Postmaster Tools
Aggregate Gmail spam rates, authentication pass rates and delivery-error breakdown as an early-warning trend.
Microsoft SNDS / JMRP
Per-IP complaint copies plus Microsoft's own volume and reputation colouring.
DMARC aggregate reports
Authentication alignment and unauthorised-use signals for the same sending identities.
SMTP / bounce telemetry
Rejection and deferral patterns from your own MTA, aligned to complaint and listing events.
DNS / SPF / DKIM / DMARC health
Configuration drift on monitored domains that can quietly degrade reputation.
Additional reputation feeds
Further provider and third-party reputation sources as they become available to senders.
How it works
Three steps from raw reports to usable intelligence
Connect sender identities
Submit the domains, IP ranges and sending sources you are responsible for. Floopr keeps them organised per brand, platform or customer.
Ingest FBL complaint signals
Complaint reports from enrolled provider programs are received, parsed and normalized into one consistent event model.
Investigate and act
Filter by provider, identity or time window, see where complaints concentrate, and hand a clear picture to whoever owns the sending stream.
Sender intelligence
Slice complaint data the way your sending is actually structured
Every FBL event is stored with the context you need to trace it back to a stream, a customer or a campaign.
Available filters & fields
Complaint rate by sending domain
Illustrative demo data.
Case story
A transactional sender at 100,000 emails a day
Illustrative scenario. “Northbound Pay”, a fictional European payments platform, sends receipts, password resets and account alerts from a small set of dedicated IPs. When those messages stop reaching the inbox, support tickets follow within hours.
Daily volume
100,000
transactional emails
Peak complaint rate
0.41%
vs. 0.04% baseline
Time to root cause
28 min
from first alert
Recovery
6 days
to baseline reputation
Day 0 · 09:12
Complaint rate crosses threshold
Floopr flags 0.41% complaints on 185.24.x.18 — a single IP carrying the password-reset and receipt streams. Yahoo's loop and Validity's (carrying Comcast) account for 78% of the reports.
Day 0 · 09:40
Root cause isolated
Normalized events group by List-Id: one re-engagement campaign was accidentally routed through the transactional pool, mixing marketing volume into a trusted IP.
Day 0 · 11:05
Traffic re-segmented
The campaign is moved back to the marketing pool and complainers are suppressed automatically through the Floopr webhook into the sending platform.
Day 6
Reputation recovered
Complaint rate back to 0.04%. Inbox placement on the transactional pool returns to pre-incident levels before any provider-side throttling took hold.
Architecture
Dashboard + API + Webhooks
Floopr is built to be consumed, not just looked at. The same intelligence that renders in the portal is designed to flow into suppression systems, abuse workflows, MTA dashboards and the customer-facing dashboards ESPs and platforms already run.
Dashboard
The Floopr portal: reputation score, contributing signals, correlation timeline, attribution and event logs for the assets you monitor.
API
Read normalized complaint events, rollups and monitored-asset data programmatically with scoped keys, so your MTA dashboard, suppression system or warehouse can consume Floopr intelligence directly.
Webhooks
HMAC-signed push events the moment a complaint lands, with delivery logs, replay and automatic retries, so abuse workflows and customer dashboards react in near real time.
The API and webhooks are live: create a scoped key in the dashboard and call /api/public/v1/events. Anything not yet built is still labelled planned wherever it appears.
Data out
FBL data only works when it reaches your sending system
Complaints are operational, not reporting. Floopr is built to hand every normalized event back to the platform that actually sends — so suppression, unsubscribes and reputation logic run inside your own stack, automatically.
REST API
Pull normalized complaint events by sender identity, provider, date range or campaign reference. Cursor-based paging for backfills, incremental polling for daily jobs.
Webhooks
Push each normalized FBL event to your endpoint as it lands, signed so your system can verify origin, with retries and replay for missed deliveries.
Scheduled exports
Recurring CSV or JSON drops to object storage or SFTP for warehouses, BI tooling and compliance archives, using the same schema as the API.
MCP endpoint
Expose your complaint data to AI assistants and internal agents over MCP, so investigations can be asked in plain language against scoped, read-only access.
One event schema, every channel
Provider formats differ wildly — ARF reports, portal exports, aggregate feeds. Floopr normalizes them into a single event shape, so you integrate once instead of per provider.
Illustrative field set. Recipient data is minimised — Floopr never asks you to send mail through it, and never returns more identifying data than an investigation needs.
Who it's for
Built for the people who own sending reputation
ESPs
Monitor complaint signals across many sending customers and isolate the accounts creating reputation risk.
SaaS platforms
Keep product notifications and shared sending domains healthy as your user base grows.
Transactional senders
Detect when receipts, alerts or lifecycle mail start attracting complaints on specific providers.
Deliverability teams
Get one evidence-backed view to work from during investigations and provider conversations.
Pricing
Start free. Pay by how much you send from, not by feature drip.
Every plan is metered on monitored assets — the IPs and domains you mail from. Free Test covers 4 IPs or domains for 30 days, no card needed, cancel any time. Billing in EUR, handled securely by Stripe.
Free Test
Free for 30 days. 4 IPs or domains — see your own complaint stream before you spend anything.
no card required
4 monitored IPs or domains
Create free accountUpgrade whenever you outgrow it
Signal
For single brands and small senders who want alerts that actually arrive.
billed yearly · excl. VAT
15 monitored IPs or domains
Start 30-day trialNo card charged for 30 days
Scanner
For platforms that need the data inside their own systems.
billed yearly · excl. VAT
75 monitored IPs or domains
Start 30-day trialNo card charged for 30 days
Watch Tower
For high-volume senders tracking reputation per customer and per stream.
billed yearly · excl. VAT
300 monitored IPs or domains
Start 30-day trialNo card charged for 30 days
Need more capacity?
Add an extra 50 monitored assets to any paid plan for €15 / month. Stack as many packs as you need — no forced jump to the next tier.
Platform — from €399 / month
1,000+ assets, sub-accounts, SLA. For esps and multi-tenant platforms that resell deliverability and need complaint data per end customer.
Talk to us| What's included | Free Test | Signal | Scanner | Watch Tower |
|---|---|---|---|---|
| Monitored IPs & domains | 4 | 15 | 75 | 300 |
| Normalized FBL event ingestion | ||||
| Provider programs connected | All supported | All supported | All supported | All supported |
| History retention | 1 month | 6 months | 12 months | 36 months |
| Alerts | Email spike alert | Cadence + chat | Cadence + chat | Cadence + chat |
| Per-provider alert targeting | ||||
| Blacklist / RBL monitoring | ||||
| CSV & scheduled exports | ||||
| REST API & outbound webhooks | ||||
| MCP endpoint for agents | ||||
| Team seats | 1 | 3 | 10 | 10 |
| Support | Community + email | Email support | Priority email support | Dedicated support channel |
Prices are indicative for early access and may change before general availability.
See your complaint signals in one place.
Floopr is opening early access to senders and deliverability teams who want a clearer view of feedback loop data.
No sending, no spam — Floopr is monitoring only.