Jcrew uses Salesforce MC for marketing email and Amazon SES for transactional/notifications. They rank #15,924 in the Tranco list of most-popular domains. Email goes out from 2 different subdomains. Their email authentication setup is solid (score 85/100).
Amazon SESAuthentication 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 proofpoint.com. Policy
p=reject means receivers actively block or quarantine spoofed mail.
SPF alignment: all 11 observed emails use a return-path aligned with jcrew.com (bounce.mail.jcrew.com, mailfrom.orders.jcrew.com). SPF authenticates the visible From — supports DMARC directly.
DKIM alignment: all 11 observed emails sign with a domain aligned with jcrew.com (mail.jcrew.com, orders.jcrew.com). DKIM authenticates the visible From — supports DMARC directly.
TLS: modern — 100% TLS 1.3 (across 5 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: jcrew.com, bounce.mail.jcrew.com, mailfrom.orders.jcrew.com, mail.jcrew.com, mailfrom.dev.orders.jcrew.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 | 6 | 60.0% |
| promotions | 2 | 20.0% |
| spam | 2 | 20.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 | 8 | 50.0% | 25.0% | 25.0% | |
| Amazon SES | 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 jcrew.com has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Placement | Reputation |
|---|---|---|---|---|
| 13.110.210.248 | mta5.mail.jcrew.com |
4 | — | Check → |
| 54.240.9.30 | a9-30.smtp-out.amazonses.com |
1 | — | Check → |
| 54.240.9.36 | a9-36.smtp-out.amazonses.com |
1 | — | Check → |
| 13.110.210.246 | mta3.mail.jcrew.com |
1 | — | Check → |
| 13.110.210.200 | mta.mail.jcrew.com |
1 | — | Check → |
| 13.110.212.157 | mta8.mail.jcrew.com |
1 | — | Check → |
| 13.110.210.245 | mta2.mail.jcrew.com |
1 | — | Check → |
| 13.110.212.158 | mta9.mail.jcrew.com |
1 | 1 | Check → |
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
mail.jcrew.com | Salesforce MC 9 | |
mailfrom.dev.orders.jcrew.com | Amazon SES 2 |