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

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

- Full: https://www.anchorterminal.com/niches/security-intelligence.message-origin-check/index.md (~1,000 tokens) · this version ~230 tokens · JSON https://www.anchorterminal.com/niches/security-intelligence.message-origin-check/index.json · canonical https://www.anchorterminal.com/niches/security-intelligence.message-origin-check/
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-15
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

One company's docs show a full fit. Full fit: 1 companies, with a limit: 5, tagged: 9. Weight 8, 2 accounts.

Done when: 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.
yes: virustotal (Google LLC)
caveat: abuseipdb (AbuseIPDB LLC)
caveat: censys (Censys, Inc.)
caveat: greynoise (GreyNoise Intelligence, Inc.)
caveat: pulsedive (Pulsedive LLC)
caveat: whoisxml-api (Whois API, Inc.)

Data: https://www.anchorterminal.com/api/v1/use-cases/security-intelligence.message-origin-check.json
