Ba uses Salesforce MC for marketing email and Amazon SES for transactional/notifications. They rank #37,224 in the Tranco list of most-popular domains. Email goes out from 2 different subdomains. Their email authentication setup is solid (score 85/100). We've recorded 2 ESP changes since first observing this brand.
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 vali.email. Policy
p=reject means receivers actively block or quarantine spoofed mail.
SPF alignment: all 27 observed emails use a return-path aligned with ba.com (bounce.crm.ba.com, fromses.ba.com). SPF authenticates the visible From — supports DMARC directly.
DKIM alignment: all 27 observed emails sign with a domain aligned with ba.com (crm.ba.com, ba.com). DKIM authenticates the visible From — supports DMARC directly.
TLS: modern — 86% TLS 1.3 (across 7 sends).
Delivery: fast — 100% of emails in the last 7 days arrive in under 10 seconds (across 2 sends).
Brands often use multiple ESPs (e.g. one for marketing, another for transactional/notifications).
None — only the primary ESP(s) shown aboveESPs 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: ba.com, bounce.crm.ba.com, fromses.ba.com, crm.ba.com, email.ba.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 | 13 | 56.5% |
| promotions | 10 | 43.5% |
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 % |
|---|---|---|---|---|---|
| Salesforce MC | 19 | 47.4% | 52.6% | 0.0% | |
| Amazon SES | 4 | 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 ba.com has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Placement | Reputation |
|---|---|---|---|---|
| 161.71.70.27 | mta8.crm.ba.com |
8 | — | Check → |
| 161.71.69.78 | mta.crm.ba.com |
5 | — | Check → |
| 54.240.91.68 | a91-68.smtp-out.eu-west-1.amazonses.com |
4 | — | Check → |
| 161.71.70.22 | mta3.crm.ba.com |
4 | 1 | Check → |
| 161.71.70.30 | mta11.crm.ba.com |
2 | 1 | Check → |
| 161.71.70.29 | mta10.crm.ba.com |
2 | — | Check → |
| 161.71.70.28 | mta9.crm.ba.com |
1 | — | Check → |
| 161.71.70.26 | mta7.crm.ba.com |
1 | — | Check → |
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
crm.ba.com | Salesforce MC 23 | |
email.ba.com | Amazon SES 4 |