Skip to content
emailrules.today

Authentication history · 60 days observed

uber.com

Observed from 4 Aug 2026 to 3 Oct 2026. Nothing published in DNS has moved in that window.

Where it stands today

Live lookup, 3 Oct 2026. The same check /check/uber.com runs.

  • 3fine
  • 4context

  • Looks fine

    present, ending ~all

    Soft fail. Accepted everywhere, though -all is stronger once your sender list is complete.

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

    See what this looks like →

  • Looks fine

    present with p=quarantine

    A policy that actually instructs receivers, which is more than most senders publish.

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

    From DMARC p=none is monitoring, not enforcementSee what this looks like →

  • Looks fine

    keys published on 6 selectors

    A key existing is not the same as working. Read a real received header and check the d= value matches your before you call this done.

    mandrill._domainkey (Mandrill), google._domainkey (Google Workspace), k1._domainkey (Mailchimp), s1._domainkey (SendGrid), k2._domainkey (Mailchimp), s2._domainkey (SendGrid)

    From DKIM passing is not DKIM alignedSee what this looks like →

    Part platform, part you

    The key is your platform's to publish and it has. Whether it signs the domain in your is yours to confirm, and cannot show it — send one campaign to yourself and look for =pass header.d=uber.com in the Authentication-Results header.

  • Context

    Mailchimp signs your mail, and your cannot be read to confirm it

    2 of Mailchimp's selectors carry live keys on this domain, so Mailchimp is signing mail as you. Whether your authorises it is not answerable by reading . Your record uses SPF macros (Valimail), so the authorised senders are resolved per message from the connecting IP and are never published as a list. No checker can settle it from DNS, including this one — anyone who tells you this record does or does not list Mailchimp is guessing.

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

    From Gmail enforces authentication, PTR, TLS and a 0.30 percent spam rateSee what this looks like →

    Good to know — nothing to fix

    Send one real campaign through Mailchimp and read the Authentication-Results header on what arrives. That header is the only place this question gets answered, because it is the receiver evaluating the macro against the real .

  • Context

    SendGrid signs your mail, and your cannot be read to confirm it

    2 of SendGrid's selectors carry live keys on this domain, so SendGrid is signing mail as you. Whether your authorises it is not answerable by reading . Your record uses SPF macros (Valimail), so the authorised senders are resolved per message from the connecting IP and are never published as a list. No checker can settle it from DNS, including this one — anyone who tells you this record does or does not list SendGrid is guessing.

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

    From Gmail enforces authentication, PTR, TLS and a 0.30 percent spam rateSee what this looks like →

    Good to know — nothing to fix

    Send one real campaign through SendGrid and read the Authentication-Results header on what arrives. That header is the only place this question gets answered, because it is the receiver evaluating the macro against the real .

  • Context

    record published

    Your logo can appear in supporting clients, which needs at quarantine or reject.

    See what this looks like →

  • Context

    Receiving mail via Google Workspace

    Where you receive mail says nothing about where you send it. Marketing sends usually leave through a different platform entirely.

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

    See what this looks like →

What has moved

One entry per day a published record actually changed. Days we looked and found nothing different are counted, not listed.

  1. First observation — what was already published

    SPF published.

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

    DMARC published.

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

    DKIM keys on selectors we probe.

    google._domainkey (Google Workspace), k1._domainkey (Mailchimp), k2._domainkey (Mailchimp), mandrill._domainkey (Mandrill), s1._domainkey (SendGrid), s2._domainkey (SendGrid)

    BIMI published.

    v=BIMI1; l=https://amplify.valimail.com/bimi/uber/WSc5-ZpWcvs-uber_tinyps_v4.svg; a=

    MX records present.

    alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx.l.google.com
Where this comes from. Public DNS, and nothing else. We read the same TXT and MX records any mail server reads before accepting a message, on the days someone looked. There is no scan, no login, no mail, and no score here — only what was published and the date we saw it. Gaps are days we did not get a clean answer from a resolver, and we would rather leave those blank than guess at them.
Run the full checkSee which rules are yours