Michaelpage uses Salesforce MC for marketing email and Salesforce CRM for transactional/notifications. They rank #324,913 in the Tranco list of most-popular domains. Email goes out from 2 different subdomains. Their email authentication setup is solid (score 85/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 1 email we've observed. DMARC policy is read live from DNS.
DMARC reports sent to DMARC Analyzer (Mimecast). Policy
p=reject means receivers actively block or quarantine spoofed mail.
SPF alignment: observed emails use a third-party return-path (lstirwcru0rik86o.fchzi4un6t5l9epe.1e27bfs.1t-u30leaq.gbr72.bnc.salesforce.com, bounce.email.page.com, s1209rwke1hj7k11.o2bfws7zo2hgbt1g.bwkl.1t-u30leaq.gbr72.bnc.salesforce.com) — SPF passes there but doesn't align with michaelpage.co.jp, so DMARC has to rely on DKIM alignment.
DKIM alignment: all 4 observed emails sign with a domain aligned with michaelpage.co.jp (michaelpage.co.jp, mail.michaelpage.co.jp). DKIM authenticates the visible From — supports DMARC directly.
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: michaelpage.co.jp, lstirwcru0rik86o.fchzi4un6t5l9epe.1e27bfs.1t-u30leaq.gbr72.bnc.salesforce.com, bounce.email.page.com, s1209rwke1hj7k11.o2bfws7zo2hgbt1g.bwkl.1t-u30leaq.gbr72.bnc.salesforce.com, mail.michaelpage.co.jp
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 | 4 | 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 | 1 | 100.0% | 0.0% | 0.0% | |
| Salesforce CRM | 3 | 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 michaelpage.co.jp has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Reputation |
|---|---|---|---|
| 161.71.35.107 | mta.email.page.com |
1 | Check → |
Per-IP inbox / promotions / spam is being collected and will appear here as new emails are observed.
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
michaelpage.co.jp | Salesforce CRM 3 | |
mail.michaelpage.co.jp | Salesforce MC 1 |