{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/security-intelligence.message-origin-check/",
    "json": "https://www.anchorterminal.com/niches/security-intelligence.message-origin-check/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/security-intelligence.message-origin-check/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/security-intelligence.message-origin-check/index.min.md"
  },
  "markdown": "One company's docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 1 | 5 | 9 | 8 | 2 |\n\n## What counts as done\n\nEach sender IP, URL and hash with a verdict, location and network, unknown kept distinct from clean, without submitting the URL for a public scan unless asked.\n\nHow agents ask for it: is this email a phish; where did this message come from; check the links in this email\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **VirusTotal (Google LLC)**: Looks up sender IPs (country, asn, as_owner, network), URLs via POST /urls/lookup, which discloses but doesn't submit, and attachment hashes, with 404 kept as unknown and dates on each report. Submission is a separate call VTAI says to make only on request.\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **AbuseIPDB (AbuseIPDB LLC)**: Covers sender IPs passively, with country, ISP, usageType and isTor; links and attachment hashes need another source.\n- **Censys (Censys, Inc.)**: Sender IPs get location, ASN and, on Core, a reputation label, passively. URLs and attachment hashes aren't looked up.\n- **GreyNoise (GreyNoise Intelligence, Inc.)**: Sender IPs get noise, RIOT and classification with 404 for unseen IPs, passively. URLs and hashes aren't covered, and mail servers mostly come back not found.\n- **Pulsedive (Pulsedive LLC)**: Sender IPs and URLs get risk, geo and linked threats, and analyze.php with probe=0 and submit=0 scans without storing a new indicator. Attachment hashes aren't covered.\n- **WhoisXML API (Whois API, Inc.)**: Sender IPs, URLs and hashes can all go to the threat API as iocs, and IP geolocation is a separate API, passively. What a miss returns and whether a verdict is given wasn't shown on the requests page.\n\n- not this job: IPinfo (IPinfo Inc.): Gives sender IPs country and ASN free, and city and is_vpn, is_proxy, is_tor on Plus, but no verdict, and URLs and hashes aren't covered.\n- not this job: SecurityTrails (SecurityTrails (Recorded Future)): No verdict for sender IPs, URLs or hashes; only WHOIS and DNS context.\n- not this job: Shodan (Shodan (no company name on its pages; shodan.io is registered to John Matherly)): Gives a sender IP's organisation, ASN, location and exposure but no verdict, and doesn't look up URLs or hashes.\n\n## What stops agents finishing\n\n- URL submission makes the link public\n- free tier gives country only, not the network or proxy flag\n\n## Around it\n\nBefore: email.read-message, mailbox-access.read-message. After: email.reply, human-in-the-loop.review-output.\n\n## Where this comes from\n\nWeight 8 of 100 in Security intelligence: 2 of 41 accounts (MAILSPECTRA, PhishGuard); weight raised above the count because vendor pages name it\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/security-intelligence.message-origin-check.json, or the MCP tool get_use_case with id security-intelligence.message-origin-check. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Check the sender, links and origin of a suspected phish",
        "url": ""
      }
    ],
    "description": "Check the sender, links and origin of a suspected phish: 1 companies fully do it, 5 with a limit, 9 carry the tag. Every listing in Security intelligence with the reason and a source.",
    "facts": null,
    "h1": "Check the sender, links and origin of a suspected phish",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/security-intelligence.message-origin-check/",
    "published": "",
    "section": "agents",
    "title": "Check the sender, links and origin of a suspected phish | Anchor…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/security-intelligence.message-origin-check/"
  },
  "tokens": {
    "markdown": 1000,
    "slim": 230
  },
  "version": 1
}
