Email Security Analysis of uber.com

Complete verification of uber.com's SPF, DKIM, DMARC, and MTA-STS records. Find out if this domain is protected against email spoofing.

Last updated: April 14, 2026

72B
This domain is protected against spoofing

SPF

Warning
v=spf1 include:uber.com._nspf.vali.email include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email include:mailgun.org ~all
Read the guide

DKIM

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

DMARC

Warning
v=DMARC1; p=quarantine; rua=mailto:dmarc_agg@vali.email
Read the guide

MX

OK
aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt4.aspmx.l.google.com, alt3.aspmx.l.google.com

MTA-STS

Missing

No record found

Read the guide

Recommendations

  1. 1Upgrade your DMARC policy from p=quarantine to p=reject for full blocking

    With p=quarantine, spoofed emails are sent to spam instead of being blocked outright. Some recipients still check spam folders, and sophisticated attacks can be flagged as legitimate by users. p=reject ensures fraudulent emails never reach any folder.

  2. 2Harden your SPF by replacing ~all with -all (hardfail)

    With ~all (softfail), unauthorized senders are flagged but emails are usually still delivered. Switching to -all (hardfail) explicitly tells receiving servers to reject emails from unauthorized sources, providing much stronger protection against spoofing.

  3. 3Add 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 uber.com, run a live analysis.

Analyze uber.com live

Guides to understand these results