Get Email DetectiveDetect any senderright in your inbox Gmail Outlook

Rebrandly

rebrandly.com
🏆Rank #28,842 🏷 Marketing & Agencies 🇺🇸United States ✓ Inbox 100%

Rebrandly uses Customer.io for marketing email and Amazon SES for transactional/notifications. They rank #28,842 in the Tranco list of most-popular domains. Their email authentication setup is solid (score 90/100). We've recorded 1 ESP change since first observing this brand.

Marketing ESPCustomer.io
Transactional ESPAmazon SES
Total observations58
Active days25
Avg per active day2.3
Last activity📬 Active · today
Cadence~every 2 days
Compare Rebrandly 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 7/10

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

Authentication

DMARC reports sent to dmarc-report.com. Policy p=quarantine means receivers actively block or quarantine spoofed mail.

SPF alignment: 98% of observed emails use an aligned return-path (cioeu141755.rebrandly.com, outbound.intercom.rebrandly.com, outbound-eu.intercom.rebrandly.com); the rest use third-party paths (amazonses.com) where DMARC has to rely on DKIM alignment.

DKIM alignment: all 39 observed emails sign with a domain aligned with rebrandly.com (cioeu141755.rebrandly.com, rebrandly.com). DKIM authenticates the visible From — supports DMARC directly.

Transport & deliverability

TLS: 7% TLS 1.3, 93% TLS 1.2 (across 14 sends).

Delivery: fast — 100% of emails in the last 7 days arrive in under 10 seconds (across 5 sends).

Other ESPs detected

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

Intercom 25

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 Intercom ✓ via SparkPost 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 Salesforce MC SparkPost

Probed: rebrandly.com, outbound.intercom.rebrandly.com, cioeu141755.rebrandly.com, outbound-eu.intercom.rebrandly.com, amazonses.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 57 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 %
Amazon SES 1
100.0% 0.0% 0.0%
Customer.io 31
100.0% 0.0% 0.0%
Intercom 20
100.0% 0.0% 0.0%

ESP activity over time

May 4 – Jun 30, 2026 · 27 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.

5 0 Intercom: 2 (2026-05-04)2Intercom: 2 (2026-05-05)2Intercom: 1 (2026-05-06)1Customer.io: 1 (2026-05-09)1Intercom: 1 (2026-05-11)1Customer.io: 1 (2026-05-12)Intercom: 2 (2026-05-12)3Customer.io: 1 (2026-05-13)Intercom: 3 (2026-05-13)4Intercom: 2 (2026-05-19)2Intercom: 1 (2026-05-20)1Customer.io: 1 (2026-05-21)Intercom: 2 (2026-05-21)3Customer.io: 2 (2026-05-26)Intercom: 1 (2026-05-26)3Customer.io: 4 (2026-05-28)4Customer.io: 1 (2026-05-30)1Customer.io: 3 (2026-06-01)3Customer.io: 1 (2026-06-02)1Customer.io: 2 (2026-06-03)2Intercom: 2 (2026-06-04)2Intercom: 2 (2026-06-05)2Customer.io: 4 (2026-06-09)Intercom: 1 (2026-06-09)5Customer.io: 2 (2026-06-10)2Customer.io: 1 (2026-06-11)Intercom: 1 (2026-06-11)2Customer.io: 2 (2026-06-15)2Customer.io: 2 (2026-06-16)Intercom: 1 (2026-06-16)3Intercom: 1 (2026-06-17)1Amazon SES: 1 (2026-06-24)1Customer.io: 1 (2026-06-29)1Customer.io: 3 (2026-06-30)305/0405/1005/1605/2205/2806/0306/0906/1506/2106/2706/30
Customer.io Intercom Amazon SES

Similar brands using Customer.io

Sending IPs

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

IPHostnameObsPlacementReputation
143.55.239.106 v5106.v5a39be5d.euw1.send.eu.mailgun.net 21 4 Check →
192.174.84.120 mta-174-84-120.intercom.com.sparkpostmail.com 12 Check →
192.174.84.119 mta-174-84-119.intercom.com.sparkpostmail.com 11 Check →
143.55.239.109 v5109.v5a39be5d.euw1.send.eu.mailgun.net 11 Check →
147.253.221.176 mta-221-176.sparkpostmail.com 2 Check →
54.240.40.225 a40-225.smtp-out.amazonses.com 1 1 Check →

Sending domains

DomainESPs detectedDelivery (7d)
rebrandly.comCustomer.io 32 Intercom 25 Amazon SES 1