Get Email DetectiveDetect any senderright in your inbox Gmail Outlook

Mailflow

mailflow.io
🌐Web popularity N/A 🏷 SaaS

Mailflow uses Postmark as their primary email service provider. Their email authentication setup is good (score 73/100). Missing: DMARC enforcement, one-click unsubscribe.

Transactional ESPPostmark
Total observations7
Active days4
Avg per active day1.8
Last activity📬 Active · 10 days ago
Cadence~weekly
Compare Mailflow with another brand:

Email setup 73/100

Authentication signals observed in this brand's emails. SPF, DKIM and DMARC are the standard sender-authentication stack — see the DMARC policy below for whether spoofing is actually blocked or just monitored. One-click unsubscribe meets Google & Yahoo's bulk-sender requirements.

Solid setup, room to improve
Most authentication signals are present. A couple of pieces would tighten things up.
73/100
SPF
pass
DKIM
pass
DMARC
pass (none)
BIMI
none
Unsubscribe
missing
SPF lookups 2/10

SPF / DKIM / DMARC above reflect the last 3 emails we've observed. DMARC policy is read live from DNS.

Authentication

DMARC reports sent to mailflow.io. Policy p=none is monitor-only — receivers won't act on spoofing yet.

SPF alignment: 43% of observed emails use an aligned return-path (pm-bounces.mailflow.io); the rest use third-party paths (themathergroupllc.com) where DMARC has to rely on DKIM alignment.

DKIM alignment: all 7 observed emails sign with a domain aligned with mailflow.io (mailflow.io). DKIM authenticates the visible From — supports DMARC directly.

Other ESPs detected

Brands often use multiple ESPs (e.g. one for marketing, another for transactional/notifications).

None — only the primary ESP(s) shown above

Confirmed senders

ESPs we've seen sending email for this brand. Green = confirmed by SPF, sender IP rDNS, or known infra pairing (label shows the source). Grey = observed but not yet confirmed by SPF or PTR.

Postmark ✓ via sending IP

Other SPF authorizations

ESPs this brand has authorized in their SPF record. We confirm them with a green ✓ only after seeing recurring use (3+ emails across 2+ days). Until then they stay here — either we haven't observed any email yet, or we've seen a handful but not enough to call them a regular sender for the brand.

Microsoft 365

Probed: mailflow.io, pm-bounces.mailflow.io, themathergroupllc.com

Where emails landed (Gmail)

Folder distribution across all emails from this brand observed in Gmail inboxes. High inbox % = good deliverability; spam appearances are the headline signal.

FolderCountShare
inbox 7 100.0%

Placement by ESP

Which ESP's emails are landing where. Sorted by spam % so problem senders surface first. Brands using one ESP for marketing and another for transactional often see very different placement profiles per ESP. Per-ESP folder data only started being captured recently — counts here may be smaller than the total above until backfill catches up.

ESP Emails Placement Inbox % Tabs % Spam %
Postmark 7
100.0% 0.0% 0.0%

ESP activity over time

May 27 – Jun 21, 2026 · 4 days with sends

Daily observations per ESP. Brands often run multiple ESPs concurrently — marketing on one, transactional on another — so this chart shows usage rather than switches.

3 0 Postmark: 2 (2026-05-27)2Postmark: 1 (2026-06-10)1Postmark: 1 (2026-06-20)1Postmark: 3 (2026-06-21)305/2705/3006/0206/0506/0806/1106/1406/1706/20
Postmark

Similar brands using Postmark

Sending IPs

IP addresses mailflow.io has been observed sending from, and where their mail landed in Gmail.

IPHostnameObsReputation
50.31.205.203 mta203-ab1.mtasv.net 2 Check →

Per-IP inbox / promotions / spam is being collected and will appear here as new emails are observed.

Sending domains

DomainESPs detectedDelivery (7d)
mailflow.ioPostmark 7