Get Email DetectiveDetect any senderright in your inbox Gmail Outlook

Lovable

lovable.dev
🏆Rank #5,379 🏷 SaaS 🇺🇸United States ✓ Inbox 89%

Lovable uses Customer.io for marketing email and Amazon SES for transactional/notifications. They rank #5,379 in the Tranco list of most-popular domains. Their email authentication setup is good (score 80/100).

Marketing ESPCustomer.io
Transactional ESPAmazon SES
Total observations76
Active days36
Avg per active day2.1
Last activity📬 Active · today
Cadence~every 2 days
Compare Lovable with another brand:

Email setup 80/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.
80/100
SPF
pass
DKIM
pass
DMARC
pass (quarantine)
BIMI
none
Unsubscribe
one-click
SPF lookups 6/10

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

Authentication

DMARC enforced with p=quarantine — receivers actively reject or quarantine spoofed mail. No aggregate reporting destination configured.

SPF alignment: all 67 observed emails use a return-path aligned with lovable.dev (cioeu109333.lovable.dev, bounce.lovable.dev). SPF authenticates the visible From — supports DMARC directly.

DKIM alignment: all 56 observed emails sign with a domain aligned with lovable.dev (cioeu109333.lovable.dev, lovable.dev). DKIM authenticates the visible From — supports DMARC directly.

Transport & deliverability

TLS: 16% TLS 1.3, 84% TLS 1.2 (across 25 sends).

Delivery (last 7 days): 78% under 10 seconds, 22% over 1 minute (across 9 sends).

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.

Google Workspace HubSpot Mailgun SendGrid

Probed: lovable.dev, cioeu109333.lovable.dev, bounce.lovable.dev

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 63 88.7%
promotions 8 11.3%

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 4
100.0% 0.0% 0.0%
Customer.io 62
88.7% 11.3% 0.0%

ESP activity over time

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

7 0 Customer.io: 2 (2026-04-28)2Customer.io: 2 (2026-04-29)2Customer.io: 2 (2026-04-30)2Customer.io: 1 (2026-05-01)1Customer.io: 2 (2026-05-02)2Customer.io: 7 (2026-05-13)7Customer.io: 3 (2026-05-15)3Amazon SES: 1 (2026-05-18)1Customer.io: 1 (2026-05-19)1Customer.io: 1 (2026-05-20)1Customer.io: 4 (2026-05-22)4Customer.io: 1 (2026-05-23)1Customer.io: 6 (2026-05-25)6Customer.io: 1 (2026-05-27)1Customer.io: 2 (2026-05-28)2Customer.io: 1 (2026-05-29)1Customer.io: 1 (2026-06-01)1Customer.io: 2 (2026-06-02)2Customer.io: 2 (2026-06-03)2Customer.io: 1 (2026-06-04)1Customer.io: 5 (2026-06-05)5Customer.io: 1 (2026-06-06)1Customer.io: 1 (2026-06-07)1Customer.io: 2 (2026-06-10)2Customer.io: 7 (2026-06-12)7Customer.io: 2 (2026-06-15)2Amazon SES: 1 (2026-06-16)1Customer.io: 2 (2026-06-17)Amazon SES: 1 (2026-06-17)3Customer.io: 1 (2026-06-19)Amazon SES: 1 (2026-06-19)2Customer.io: 2 (2026-06-20)2Customer.io: 1 (2026-06-25)1Customer.io: 1 (2026-06-26)1Customer.io: 1 (2026-06-27)1Customer.io: 1 (2026-06-28)1Customer.io: 2 (2026-06-29)2Customer.io: 1 (2026-06-30)104/2805/0505/1205/1905/2606/0206/0906/1606/2306/30
🐢
Customer.io Amazon SES

Similar brands using Customer.io

Sending IPs

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

IPHostnameObsPlacementReputation
204.220.162.184 c184.c8d50bb3.euw1.send.eu.mailgun.net 35 7 Check →
198.244.60.135 a135.a5d06dfa.euw1.send.eu.mailgun.net 33 5 Check →
54.240.42.184 a42-184.smtp-out.amazonses.com 2 1 Check →
54.240.61.167 a61-167.smtp-out.us-west-2.amazonses.com 1 Check →
54.240.42.185 a42-185.smtp-out.amazonses.com 1 Check →

Sending domains

DomainESPs detectedDelivery (7d)
lovable.devCustomer.io 72 Amazon SES 4