Sansan uses HubSpot for marketing email and SendGrid for transactional/notifications. They rank #58,215 in the Tranco list of most-popular domains. We've also observed sends via Amazon SES. Email goes out from 2 different subdomains. Their email authentication setup is good (score 73/100). Missing: DMARC enforcement.
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.
SPF / DKIM / DMARC above reflect the last 2 emails we've observed. DMARC policy is read live from DNS.
DMARC reports sent to PowerDMARC. Policy
p=none is monitor-only — receivers won't act on spoofing yet.
SPF alignment: 15% of observed emails use an aligned return-path (mail.sansan.com); the rest use third-party paths (bf53x.hubspotemail.net, amazonses.com) where DMARC has to rely on DKIM alignment.
DKIM alignment: all 13 observed emails sign with a domain aligned with sansan.com (jp.sansan.com, sansan.com). DKIM authenticates the visible From — supports DMARC directly.
TLS: 33% TLS 1.3, 67% TLS 1.2 (across 6 sends).
Brands often use multiple ESPs (e.g. one for marketing, another for transactional/notifications).
Amazon SES 1ESPs 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.
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.
Probed: sansan.com, mail.sansan.com, bf53x.hubspotemail.net, amazonses.com, jp.sansan.com
Folder distribution across all emails from this brand observed in Gmail inboxes. High inbox % = good deliverability; spam appearances are the headline signal.
| Folder | Count | Share |
|---|---|---|
| inbox | 3 | 50.0% |
| promotions | 3 | 50.0% |
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 % |
|---|---|---|---|---|---|
| HubSpot | 3 | 0.0% | 100.0% | 0.0% | |
| Amazon SES | 1 | 100.0% | 0.0% | 0.0% | |
| SendGrid | 2 | 100.0% | 0.0% | 0.0% |
Daily observations per ESP. Brands often run multiple ESPs concurrently — marketing on one, transactional on another — so this chart shows usage rather than switches.
IP addresses sansan.com has been observed sending from, and where their mail landed in Gmail.
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
jp.sansan.com | HubSpot 10 | |
sansan.com | SendGrid 2 Amazon SES 1 |
