Wellsfargo uses Salesforce MC as their primary email service provider. They rank #3,015 in the Tranco list of most-popular domains. Their email authentication setup is solid (score 100/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.
SPF / DKIM / DMARC above reflect the last 2 emails we've observed. DMARC policy is read live from DNS.
DMARC reports sent to proofpoint.com. Policy
p=reject means receivers actively block or quarantine spoofed mail.
SPF alignment: all 16 observed emails use a return-path aligned with wellsfargo.com (bounce.mail1.wellsfargo.com). SPF authenticates the visible From — supports DMARC directly.
DKIM alignment: all 16 observed emails sign with a domain aligned with wellsfargo.com (mail1.wellsfargo.com). DKIM authenticates the visible From — supports DMARC directly.
VMC issued by: digicert.
TLS: modern — 100% TLS 1.3 (across 6 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: wellsfargo.com, bounce.mail1.wellsfargo.com, mail1.wellsfargo.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 | 15 | 100.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 % |
|---|---|---|---|---|---|
| Salesforce MC | 15 | 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 wellsfargo.com has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Placement | Reputation |
|---|---|---|---|---|
| 13.111.189.191 | mta7.mail1.wf.com |
6 | 1 | Check → |
| 136.147.185.171 | mta.mail1.wf.com |
3 | — | Check → |
| 13.111.189.192 | mta8.mail1.wf.com |
2 | 1 | Check → |
| 13.111.189.69 | mta4.mail1.wf.com |
2 | — | Check → |
| 13.111.189.189 | mta5.mail1.wf.com |
1 | — | Check → |
| 13.111.189.68 | mta3.mail1.wf.com |
1 | — | Check → |
| 13.111.189.30 | mta2.mail1.wf.com |
1 | — | Check → |
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
mail1.wellsfargo.com | Salesforce MC 16 |