# Check the sender, links and origin of a suspected phish

> 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.

- Canonical: https://www.anchorterminal.com/niches/security-intelligence.message-origin-check/
- Markdown: https://www.anchorterminal.com/niches/security-intelligence.message-origin-check/index.md (~1,000 tokens)
- Slim: https://www.anchorterminal.com/niches/security-intelligence.message-origin-check/index.min.md (~230 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/security-intelligence.message-origin-check/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

One company's docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 1 | 5 | 9 | 8 | 2 |

## What counts as done

Each 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.

How agents ask for it: is this email a phish; where did this message come from; check the links in this email

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **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.

## Does the job, with a limit

It 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.

- **AbuseIPDB (AbuseIPDB LLC)**: Covers sender IPs passively, with country, ISP, usageType and isTor; links and attachment hashes need another source.
- **Censys (Censys, Inc.)**: Sender IPs get location, ASN and, on Core, a reputation label, passively. URLs and attachment hashes aren't looked up.
- **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.
- **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.
- **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.

- 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.
- not this job: SecurityTrails (SecurityTrails (Recorded Future)): No verdict for sender IPs, URLs or hashes; only WHOIS and DNS context.
- 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.

## What stops agents finishing

- URL submission makes the link public
- free tier gives country only, not the network or proxy flag

## Around it

Before: email.read-message, mailbox-access.read-message. After: email.reply, human-in-the-loop.review-output.

## Where this comes from

Weight 8 of 100 in Security intelligence: 2 of 41 accounts (MAILSPECTRA, PhishGuard); weight raised above the count because vendor pages name it

As 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.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
