Metamail uses Salesforce MC as their primary email service provider. They're the #271,892 most-visited website overall, per Tranco (a web-popularity measure, not an email one). Email goes out from 4 different subdomains. 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 10 emails we've observed. DMARC policy is read live from DNS.
DMARC reports sent to facebookmail.com. Policy
p=reject means receivers actively block or quarantine spoofed mail.
SPF alignment: all 56 observed emails use a return-path aligned with metamail.com (bounce.global.metamail.com, bounce.messaging.metamail.com, bounce.digital.metamail.com). SPF authenticates the visible From — supports DMARC directly.
DKIM alignment: all 50 observed emails sign with a domain aligned with metamail.com (global.metamail.com, messaging.metamail.com, marketing.metamail.com). DKIM authenticates the visible From — supports DMARC directly.
TLS: modern — 100% TLS 1.3 (across 21 sends).
3 of 12 emails in the last 7 days were delayed beyond 5 minutes (25%) — delays stayed within 5–15 minutes. Slow sends averaged 14 min. Healthy senders deliver in under 30 seconds. Consistent delays usually mean greylisting, reputation-based throttling, or receiver-side filter scrutiny — worth investigating sender reputation and authentication setup.
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.
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.
No additional ESPs authorized in the brand's SPF beyond the confirmed senders above.
Probed: metamail.com, bounce.messaging.metamail.com, bounce.global.metamail.com, bounce.digital.metamail.com, bounce.marketing.metamail.com, global.metamail.com, messaging.metamail.com, digital.metamail.com, marketing.metamail.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 | 50 | 87.7% |
| promotions | 7 | 12.3% |
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 | 55 | 87.3% | 12.7% | 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 metamail.com has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Placement | Reputation |
|---|---|---|---|---|
| 13.111.200.58 | mta.dev.oculusvr.com |
20 | 2 | Check → |
| 128.245.2.188 | mta2.global.metamail.com |
7 | 4 | Check → |
| 13.111.124.26 | mta8.mc.facebookmail.com |
6 | 2 | Check → |
| 128.245.2.199 | mta4.global.metamail.com |
4 | 2 | Check → |
| 128.245.2.202 | mta7.global.metamail.com |
4 | 1 | Check → |
| 13.111.124.28 | mta10.mc.facebookmail.com |
3 | — | Check → |
| 128.245.2.189 | mta3.global.metamail.com |
3 | — | Check → |
| 13.111.97.64 | mta2.digital.metaquestmail.com |
3 | 3 | Check → |
| 13.111.97.63 | mta.digital.metaquestmail.com |
2 | 1 | Check → |
| 128.245.2.203 | mta8.global.metamail.com |
2 | 1 | Check → |
| 128.245.2.200 | mta5.global.metamail.com |
2 | 1 | Check → |
| 128.245.2.204 | mta9.global.metamail.com |
1 | — | Check → |
| 13.111.200.109 | mta.global.metamail.com |
1 | — | Check → |
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
global.metamail.com | Salesforce MC 33 | 🐢 3/9 slow (avg 14 min) |
messaging.metamail.com | Salesforce MC 15 | |
digital.metamail.com | Salesforce MC 5 | |
marketing.metamail.com | Salesforce MC 5 |