Get Email DetectiveDetect any senderright in your inbox Gmail Outlook

Beefree

beefree.io
🏆Rank #82,662 🏷 SaaS 🇺🇸United States 📥 Inbox 68%

Beefree uses Customer.io for marketing email and Amazon SES for transactional/notifications. They rank #82,662 in the Tranco list of most-popular domains. Email goes out from 3 different subdomains. Their email authentication setup is solid (score 90/100). We've recorded 2 ESP changes since first observing this brand.

Marketing ESPCustomer.io
Transactional ESPAmazon SES
Total observations38
Active days13
Avg per active day2.9
Last activity📬 Active · 8 days ago
Cadence~weekly

Other technologies

Non-ESP tools detected in this brand's emails. Independent of who sends — a brand can use any combination.

HTML builder RGE Studio
Compare Beefree with another brand:

Email setup 90/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.

Strong email setup
Authentication is in good shape — SPF, DKIM, and DMARC enforcement all configured.
90/100
SPF
pass
DKIM
pass
DMARC
pass (quarantine)
BIMI
pass
Unsubscribe
one-click
SPF lookups 8/10

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

Authentication

DMARC reports sent to URIports. Policy p=quarantine means receivers actively block or quarantine spoofed mail.

SPF alignment: 87% of observed emails use an aligned return-path (cioeu110647.createdwith.beefree.io, cioeu110647.uptodate.beefree.io); the rest use third-party paths (eu-west-1.amazonses.com) where DMARC has to rely on DKIM alignment.

DKIM alignment: all 23 observed emails sign with a domain aligned with beefree.io (cioeu110647.createdwith.beefree.io, cioeu110647.uptodate.beefree.io). DKIM authenticates the visible From — supports DMARC directly.

Transport & deliverability

TLS: 0% TLS 1.3, 100% TLS 1.2 (across 18 sends).

Engagement

Dynamic content: NiftyImages — real-time/personalised email content layered on top of the ESP.

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.

Amazon SES ✓ confirmed Customer.io ✓ via Mailgun

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.

ActiveCampaign Brevo Google Workspace Mailgun

Probed: beefree.io, cioeu110647.createdwith.beefree.io, cioeu110647.uptodate.beefree.io, eu-west-1.amazonses.com, createdwith.beefree.io, uptodate.beefree.io

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 25 67.6%
promotions 12 32.4%

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 %
Amazon SES 5
100.0% 0.0% 0.0%
Customer.io 32
62.5% 37.5% 0.0%

ESP activity over time

Apr 30 – Jun 22, 2026 · 13 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.

13 0 Customer.io: 2 (2026-04-30)2Customer.io: 1 (2026-05-03)1Customer.io: 1 (2026-05-10)1Customer.io: 3 (2026-05-14)3Customer.io: 2 (2026-05-15)Amazon SES: 1 (2026-05-15)3Amazon SES: 4 (2026-05-16)4Customer.io: 1 (2026-05-19)1Customer.io: 1 (2026-05-29)1Customer.io: 6 (2026-06-04)6Customer.io: 1 (2026-06-10)1Customer.io: 13 (2026-06-16)13Customer.io: 1 (2026-06-17)1Customer.io: 1 (2026-06-22)104/3005/0605/1205/1805/2405/3006/0506/1106/1706/22
Customer.io Amazon SES

Similar brands using Customer.io

Sending IPs

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

IPHostnameObsPlacementReputation
161.38.205.176 v5176.v5b52dc11.euw1.send.eu.mailgun.net 15 Check →
161.38.205.175 v5175.v5b52dc11.euw1.send.eu.mailgun.net 12 1 Check →
198.244.60.95 a95.a5d06dfa.euw1.send.eu.mailgun.net 3 Check →
204.220.162.15 c15.c8d50bb3.euw1.send.eu.mailgun.net 3 Check →
54.240.7.49 a7-49.smtp-out.eu-west-1.amazonses.com 1 Check →
54.240.7.51 a7-51.smtp-out.eu-west-1.amazonses.com 1 Check →
54.240.7.30 a7-30.smtp-out.eu-west-1.amazonses.com 1 Check →
54.240.7.39 a7-39.smtp-out.eu-west-1.amazonses.com 1 Check →
54.240.7.28 a7-28.smtp-out.eu-west-1.amazonses.com 1 Check →

Sending domains

DomainESPs detectedDelivery (7d)
createdwith.beefree.ioCustomer.io 27
uptodate.beefree.ioCustomer.io 6
beefree.ioAmazon SES 5