doordash.com email security: SPF, DKIM & DMARC

Is doordash.com spoofable? See doordash.com's SPF, DKIM, DMARC and MTA-STS records and find out if this domain is protected against email spoofing.

Last updated: June 3, 2026

90A

This domain is protected against spoofing

v=spf1 include:doordash.com._nspf.vali.email include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all

Selectors: google, k1, mandrill, s1, s2, zendesk1, zendesk2

v=DMARC1; p=reject; rua=mailto:dmarc_agg@vali.email

aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, aspmx3.googlemail.com, aspmx2.googlemail.com

Missing

No record found

1Add MTA-STS to enforce TLS encryption for incoming emails
Without MTA-STS, an attacker performing a man-in-the-middle attack can downgrade the connection between mail servers to plaintext, intercepting emails in transit. MTA-STS tells sending servers to only deliver via TLS with a valid certificate, preventing downgrade attacks.

Run a live analysis

The results above are updated daily. For an instant check of doordash.com, run a live analysis.

No. doordash.com is protected against email spoofing with a robust configuration. Email security score: 90/100 (grade A).

Yes, doordash.com publishes an SPF record (~all qualifier).

doordash.com publishes a DMARC record (_dmarc.doordash.com) with a p=reject policy.

Yes, DKIM signatures were detected for doordash.com.

Want to test another domain? Run a free email spoofing test.

Understand how SPF defines which servers are authorized to send emails for a domain.

Discover how DKIM cryptographically signs your emails to guarantee their authenticity.

Learn how DMARC orchestrates SPF and DKIM to protect your domain.

Learn how MTA-STS enforces TLS encryption to protect your emails in transit.

Compare the three protocols and understand how they work together.