Make uses Customer.io for marketing email and Amazon SES for transactional/notifications. They rank #5,787 in the Tranco list of most-popular domains. Their email authentication setup is solid (score 85/100).
Amazon SESNon-ESP tools detected in this brand's emails. Independent of who sends — a brand can use any combination.
| HTML builder |
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.
SPF / DKIM / DMARC above reflect the last 6 emails we've observed. DMARC policy is read live from DNS.
DMARC reports sent to make.com!15m. Policy
p=reject means receivers actively block or quarantine spoofed mail.
SPF alignment: 89% of observed emails use an aligned return-path (cio51825.make.com, bounce.make.com); the rest use third-party paths (themathergroupllc.com) where DMARC has to rely on DKIM alignment.
DKIM alignment: all 24 observed emails sign with a domain aligned with make.com (cio51825.make.com, make.com). DKIM authenticates the visible From — supports DMARC directly.
TLS: 0% TLS 1.3, 100% TLS 1.2 (across 11 sends).
Delivery (last 7 days): 25% under 10 seconds, 75% over 1 minute (across 4 sends).
Gmail's own filter showed these warnings to real subscribers in their inbox — independent of SPF/DKIM/DMARC pass/fail status. A consistent pattern often signals reputation issues or brand-impersonation concerns.
Brands often use multiple ESPs (e.g. one for marketing, another for transactional/notifications).
None — only the primary ESP(s) shown aboveESPs 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.
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.
Probed: make.com, cio51825.make.com, bounce.make.com, themathergroupllc.com
Folder distribution across all emails from this brand observed in Gmail inboxes. High inbox % = good deliverability; spam appearances are the headline signal.
| Folder | Count | Share |
|---|---|---|
| inbox | 27 | 93.1% |
| promotions | 2 | 6.9% |
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 % |
|---|---|---|---|---|---|
| Amazon SES | 1 | 100.0% | 0.0% | 0.0% | |
| Customer.io | 27 | 92.6% | 7.4% | 0.0% |
Daily observations per ESP. Brands often run multiple ESPs concurrently — marketing on one, transactional on another — so this chart shows usage rather than switches.
IP addresses make.com has been observed sending from, and where their mail landed in Gmail.
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
make.com | Customer.io 28 Amazon SES 1 |