Skip to content
LookupOwl

Email spoofing check

Find out whether someone could send mail that looks like it came from your domain, using only the public records it already has.

We never send a fake email. We read your DNS records.

Results for ebay.com

Checked live lookup421 ms

JSONCheck again

Can someone send mail as you?

No: receivers are told to refuse it.

We never send a fake email. We read your DNS records.

DNS only: SPF, DMARC, MX

Why

  1. No
  2. Partly
  3. Yes

No. Scale: No, receivers refuse fakes. Partly, fakes go to spam. Yes, fakes are likely delivered.

  • Passp=reject: fake mail pretending to be @ebay.com is told to be refused.
  • Passpct=100: the policy applies to all mail.
  • PassSPF ~all: fine with an enforcing DMARC.

Subdomains: Subdomains follow the main policy (p=reject), so fake mail from one is refused.

  • Check the whole mail setupSPF, DKIM, DMARC, BIMI, MTA-STS, TLS-RPT and blocklists, with the fixes to make first.
    Email health check
Structured result (JSON) · 2.3 KB
{
  "domain": "ebay.com",
  "scope": "spoofing",
  "scannedAt": "2026-11-16T19:50:25.974Z",
  "state": "ok",
  "level": "good-with-fixes",
  "counts": {
    "pass": 2,
    "info": 0,
    "warn": 1,
    "fail": 0,
    "skipped": 0,
    "unknown": 0,
    "total": 3
  },
  "categories": [
    {
      "id": "mx",
      "status": "pass",
      "headline": "2 mail servers",
      "sub": "2 hosts",
      "tool": "dns-lookup"
    },
    {
      "id": "spf",
      "status": "warn",
      "headline": "Valid, but no lookups to spare (At least 10 of 10 lookups)",
      "sub": "At least 10 of 10 lookups",
      "tool": "spf-checker"
    },
    {
      "id": "dmarc",
      "status": "pass",
      "headline": "Reject for the domain",
      "sub": "p=reject",
      "tool": "dmarc-checker"
    }
  ],
  "unfinished": [],
  "notChecked": [],
  "mailServers": [
    "mx1.hc2186-24.iphmx.com",
    "mx2.hc2186-24.iphmx.com"
  ],
  "topFixes": [
    {
      "id": "spf-no-spare",
      "category": "spf",
      "severity": "warn",
      "message": "Free up SPF lookups",
      "why": "At least 10 of 10: one more include breaks the record.",
      "fix": {
        "tool": "spf-optimize",
        "text": "Remove includes you no longer use, or move a sender to its own subdomain."
      }
    }
  ],
  "findings": [
    {
      "severity": "warn",
      "category": "spf",
      "message": "At least 10 of 10 lookups (a lower bound: some includes check each sender live). One more include from a provider could break the record.",
      "fix": "Move marketing senders to a subdomain, or use the SPF optimizer",
      "record": null
    }
  ],
  "provider": null,
  "policyDomain": null,
  "spoofability": {
    "verdict": "protected",
    "reasons": [
      {
        "status": "pass",
        "text": "p=reject: fake mail pretending to be @ebay.com is told to be refused."
      },
      {
        "status": "pass",
        "text": "pct=100: the policy applies to all mail."
      },
      {
        "status": "pass",
        "text": "SPF ~all: fine with an enforcing DMARC."
      }
    ],
    "parked": false,
    "mailboxProvider": false,
    "subdomains": "Subdomains follow the main policy (p=reject), so fake mail from one is refused.",
    "hardening": []
  },
  "changesSinceLastScan": null,
  "permalink": "/email-spoofing-check?domain=ebay.com"
}

Next step

How spoofing works

Anyone can type your domain into the From line of a message, and the mail system does not stop them. What decides whether receivers believe it is your SPF record, your DKIM keys and above all your DMARC policy, which tells receivers what to do with mail that fails those checks.

This check reads only DNS, so it takes a few seconds and costs nothing. It does not send a fake message, and it does not need your permission to look, because everything it reads is public.

Reading the answer

The answer is one of three words, with the reasons listed under it.

  • No: DMARC is set to reject at full strength, and subdomains follow the same rule. Receivers are told to refuse fakes.
  • Partly: DMARC is set to quarantine, applies to only some mail, or leaves subdomains weaker. Fakes mostly go to spam but some may land in the inbox.
  • Yes: there is no DMARC record, or it is p=none, which only reports. Fakes will probably be delivered.

The reasons are the part to act on. Each is a short sentence such as "sp=reject: fake mail from a subdomain is refused", with an icon and a word, so you can see which setting led to the answer.

Domains that send no mail

A parked domain, or a brand name you own but never use for mail, is an attractive thing to fake because nobody is watching it. The safe setup is three records: a null MX so it says it receives nothing, an SPF record that allows no sender, and a DMARC policy of reject. When the domain is open, the page gives you those records ready to copy.

Free mail domains are different

Domains such as gmail.com and outlook.com publish a weak policy on purpose. Their users send through many other services, and a strict policy would block that real mail. For these the page says "Yes, and that is on purpose" and explains the reasoning, instead of treating it as an oversight.

For the full picture of a domain you run, the email health check adds DKIM, blocklists and the optional records.

Questions people ask

Does a p=none DMARC policy protect me?

No. It asks receivers to send you reports about failures but not to block anything, so it gives you visibility and no protection. It is the right place to start and the wrong place to stay.

What if my domain sends no email?

Publish a null MX, an SPF record of v=spf1 -all and a DMARC policy of reject. Together they say the domain neither sends nor receives mail, and receivers are told to refuse anything that claims otherwise.

Does SPF alone stop spoofing?

No. SPF checks the hidden envelope address, not the From line people see. DMARC ties the visible From domain to a passing SPF or DKIM result, and that is what makes a fake fail.

Do you send a fake email to find out?

No. We never send anything. The verdict comes from reading your records and applying what receivers do with them.

Why does it say "partly" for a quarantine policy?

Quarantine tells receivers to treat a failing message with suspicion, usually by putting it in spam. That helps, but some receivers still deliver it, so it is not the same as refusing it.

What about subdomains?

A DMARC record applies to subdomains too unless it has an sp tag that says otherwise. A strong policy on the main domain with a weak one on subdomains still leaves a way in, and the page points that out.

Use it from AI, the API or the command line

Every LookupOwl tool is also a free API and an MCP tool, with no key and no account. This one is email_health. Please be kind to the rate limits.

curl
curl "https://lookupowl.com/api/v1/tools/email-health?q=github.com"
MCP
claude mcp add --transport http lookupowl https://lookupowl.com/mcp