Get Email DetectiveDetect any senderright in your inbox Gmail Outlook

Livespace

livespace.io
🏆Rank #572,125 🏷 SaaS

Livespace uses Customer.io as their primary email service provider. They rank #572,125 in the Tranco list of most-popular domains. Their email authentication setup is good (score 73/100). Missing: DMARC enforcement.

Marketing ESPCustomer.io
Total observations4
Active days4
Avg per active day1.0
Last activity📬 Active · 2 weeks ago
Cadence~every 2 weeks

Other technologies

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

HTML builder Beefree SDK
Compare Livespace 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
one-click
SPF lookups 9/10
Authentication

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

SPF alignment: observed emails use a third-party return-path (messageflow.com) — SPF passes there but doesn't align with livespace.io, so DMARC has to rely on DKIM alignment.

DKIM alignment: all 2 observed emails sign with a domain aligned with livespace.io (cioeu102791.livespace.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.

Customer.io observed

"Observed" pills mean we detected emails from these ESPs, but they don't appear in any SPF record we probed. They may still be properly authorized — sending infrastructure can live on subdomains we haven't seen yet, or use IP-listing instead of include: directives.

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.

Amazon SES Google Workspace MailerLite Microsoft 365 SALESmanago

Probed: livespace.io, messageflow.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 4 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 %
Customer.io 2
100.0% 0.0% 0.0%

ESP activity over time

Jun 17 – Jun 17, 2026 · 1 day 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.

1 0 Customer.io: 1 (2026-06-17)106/17
Customer.io

Similar brands using Customer.io

Sending domains

DomainESPs detectedDelivery (7d)
livespace.ioCustomer.io 4