Get Email DetectiveDetect any senderright in your inbox Gmail Outlook

Circle

circle.so
🏆Rank #18,970 🏷 SaaS 🇺🇸United States ✓ Inbox 99%

Circle uses HubSpot for marketing email and Mailgun for transactional/notifications. They rank #18,970 in the Tranco list of most-popular domains. We've also observed sends via Substack. Email goes out from 4 different subdomains. Their email authentication setup is good (score 73/100). Missing: DMARC enforcement.

Marketing ESPHubSpot
Transactional ESPMailgun
Total observations420
Active days50
Avg per active day8.4
Last activity📬 Active · yesterday
Cadencealmost daily
Interested in using HubSpot?
Learn about the pros and cons at .
Read the review →
Compare Circle 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 7/10

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

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 (bf54x.hubspotemail.net) — SPF passes there but doesn't align with circle.so, so DMARC has to rely on DKIM alignment.

DKIM alignment: 99% of observed emails sign with an aligned DKIM key (notification.circle.so, circle.so, email.circle.so); the rest sign with third-party keys (zendesk.com) where DMARC has to rely on SPF alignment.

Transport & deliverability

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

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

Gmail trust warnings observed
  • 🚩 Suspicious-images banner ("This message appears suspicious") — observed on 1 email (0% of tracked) · last seen Jun 5, 2026

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.

Other ESPs detected

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

Zendesk 3 Substack 2

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.

HubSpot ✓ confirmed Mailgun ✓ confirmed

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 SendGrid

Probed: circle.so, bf54x.hubspotemail.net, notification.circle.so, email.circle.so, auth.circle.so

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 261 99.2%
promotions 2 0.8%

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 %
Mailgun 218
100.0% 0.0% 0.0%
HubSpot 28
92.9% 7.1% 0.0%
Zendesk 3
100.0% 0.0% 0.0%
Substack 2
100.0% 0.0% 0.0%

ESP activity over time

May 1 – Jun 29, 2026 · 49 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.

41 0 Mailgun: 1 (2026-05-01)1Mailgun: 4 (2026-05-02)4Mailgun: 3 (2026-05-04)3Mailgun: 1 (2026-05-05)1Mailgun: 2 (2026-05-06)2Mailgun: 1 (2026-05-07)1Mailgun: 1 (2026-05-09)1Mailgun: 1 (2026-05-10)1Mailgun: 8 (2026-05-11)8Mailgun: 5 (2026-05-12)5Mailgun: 4 (2026-05-13)4Mailgun: 4 (2026-05-14)4Mailgun: 2 (2026-05-15)2Mailgun: 1 (2026-05-16)1Mailgun: 3 (2026-05-18)3Mailgun: 4 (2026-05-19)4Mailgun: 6 (2026-05-20)HubSpot: 1 (2026-05-20)7Mailgun: 7 (2026-05-21)HubSpot: 1 (2026-05-21)8Mailgun: 5 (2026-05-22)5Mailgun: 1 (2026-05-25)1Mailgun: 3 (2026-05-26)3Mailgun: 4 (2026-05-27)4Mailgun: 14 (2026-05-28)14Mailgun: 26 (2026-05-29)26Mailgun: 34 (2026-06-01)HubSpot: 2 (2026-06-01)Zendesk: 3 (2026-06-01)39Mailgun: 15 (2026-06-02)15Mailgun: 39 (2026-06-03)Substack: 2 (2026-06-03)41Mailgun: 15 (2026-06-04)HubSpot: 2 (2026-06-04)17Mailgun: 9 (2026-06-05)9Mailgun: 1 (2026-06-06)1Mailgun: 1 (2026-06-07)HubSpot: 1 (2026-06-07)2Mailgun: 12 (2026-06-08)12Mailgun: 12 (2026-06-09)HubSpot: 3 (2026-06-09)15Mailgun: 19 (2026-06-10)HubSpot: 3 (2026-06-10)22Mailgun: 18 (2026-06-11)HubSpot: 3 (2026-06-11)21Mailgun: 10 (2026-06-12)10Mailgun: 11 (2026-06-15)HubSpot: 1 (2026-06-15)12Mailgun: 12 (2026-06-16)HubSpot: 10 (2026-06-16)22Mailgun: 14 (2026-06-17)HubSpot: 1 (2026-06-17)15Mailgun: 9 (2026-06-18)9Mailgun: 4 (2026-06-19)HubSpot: 1 (2026-06-19)5Mailgun: 1 (2026-06-20)1Mailgun: 1 (2026-06-21)1Mailgun: 2 (2026-06-22)2Mailgun: 8 (2026-06-23)HubSpot: 3 (2026-06-23)11Mailgun: 4 (2026-06-24)4Mailgun: 14 (2026-06-25)14Mailgun: 2 (2026-06-26)HubSpot: 1 (2026-06-26)3Mailgun: 3 (2026-06-29)305/0105/0705/1305/1905/2505/3106/0606/1206/1806/2406/29
🐌
Mailgun HubSpot Zendesk Substack Gmail warning

Similar brands using HubSpot

Sending IPs

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

IPHostnameObsPlacementReputation
198.244.59.202 c202.c09224bb.usw1.send.mailgun.net 67 6 Check →
198.244.59.154 c154.c09224bb.usw1.send.mailgun.net 59 9 Check →
198.244.59.134 c134.c09224bb.usw1.send.mailgun.net 46 3 Check →
198.244.59.200 c200.c09224bb.usw1.send.mailgun.net 40 6 Check →
198.244.59.136 c136.c09224bb.usw1.send.mailgun.net 40 7 Check →
198.244.59.167 c167.c09224bb.usw1.send.mailgun.net 36 2 Check →
198.244.59.105 c105.c09224bb.usw1.send.mailgun.net 36 3 Check →
198.244.59.142 c142.c09224bb.usw1.send.mailgun.net 28 4 Check →
198.244.59.214 c214.c09224bb.usw1.send.mailgun.net 19 2 Check →
143.244.91.109 bd77gm3.bf54x.hubspotemail.net 13 Check →
143.244.91.39 bd77gk5.bf54x.hubspotemail.net 12 3 Check →
198.244.59.37 c37.c09224bb.usw1.send.mailgun.net 10 2 Check →
143.244.91.72 bd77gl2.bf54x.hubspotemail.net 4 1 Check →
192.161.149.33 mta-out3.pod23.use1.zdsys.com 3 Check →
108.179.150.131 4f2oz5.bf54x.hubspotemail.net 1 Check →
143.244.91.80 bd77gma.bf54x.hubspotemail.net 1 Check →
143.244.91.63 bd77glt.bf54x.hubspotemail.net 1 Check →
143.244.91.100 bd77gmu.bf54x.hubspotemail.net 1 1 Check →

Sending domains

DomainESPs detectedDelivery (7d)
notification.circle.soMailgun 348 Substack 2
circle.soHubSpot 33 Zendesk 3
email.circle.soMailgun 29
auth.circle.soMailgun 5