Doordash uses Braze for marketing email and SendGrid for transactional/notifications. They rank #2,457 in the Tranco list of most-popular domains. We've also observed sends via SparkPost. Email goes out from 2 different subdomains. Their email authentication setup is solid (score 100/100). We've recorded 3 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 9 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 56 observed emails use a return-path aligned with doordash.com (notify.doordash.com, bounce.c.doordash.com). SPF authenticates the visible From — supports DMARC directly.
DKIM alignment: all 52 observed emails sign with a domain aligned with doordash.com (doordash.com, messages.doordash.com, c.doordash.com). DKIM authenticates the visible From — supports DMARC directly.
VMC issued by: valimail.
TLS: modern — 82% TLS 1.3 (across 17 sends).
Delivery: fast — 100% of emails in the last 7 days arrive in under 10 seconds (across 6 sends).
Brands often use multiple ESPs (e.g. one for marketing, another for transactional/notifications).
SparkPost 6ESPs 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: doordash.com, notify.doordash.com, bounce.c.doordash.com, messages.doordash.com, send.doordash.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 | 62 | 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 % |
|---|---|---|---|---|---|
| SendGrid | 48 | 100.0% | 0.0% | 0.0% | |
| Braze | 3 | 100.0% | 0.0% | 0.0% | |
| SparkPost | 6 | 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 doordash.com has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Placement | Reputation |
|---|---|---|---|---|
| 159.183.91.112 | o22.send.doordash.com |
8 | — | Check → |
| 159.183.91.59 | o23.send.doordash.com |
8 | 2 | Check → |
| 159.183.92.49 | o25.send.doordash.com |
7 | — | Check → |
| 159.183.84.83 | o21.send.doordash.com |
7 | 2 | Check → |
| 159.183.96.41 | o27.send.doordash.com |
7 | 2 | Check → |
| 159.183.75.162 | o10.send.doordash.com |
6 | — | Check → |
| 159.183.84.80 | o20.send.doordash.com |
5 | — | Check → |
| 50.31.52.210 | o1.send.doordash.com |
5 | — | Check → |
| 159.183.94.152 | o26.send.doordash.com |
3 | — | Check → |
| 137.22.227.120 | hygfnjn3.messages.doordash.com |
3 | — | Check → |
| 137.22.224.243 | zhmvugxz.messages.doordash.com |
3 | — | Check → |
| 159.183.92.249 | o24.send.doordash.com |
2 | — | Check → |
| 159.183.75.165 | o11.send.doordash.com |
2 | — | Check → |
| 223.165.122.116 | lfj2kfrd.messages.doordash.com |
1 | 1 | Check → |
| 137.22.225.107 | hxxueyz2.messages.doordash.com |
1 | 1 | Check → |
| 137.22.226.143 | qjn6urnd.messages.doordash.com |
1 | 1 | Check → |
| 159.183.83.42 | o17.send.doordash.com |
1 | 1 | Check → |