Privacy
Email content is processed in-memory only — we never persist your email body. Headers, URLs, and sender IPs are queried against public threat-intel sources; body text is not sent to upstream APIs. There are no submission permalinks; every analysis is one-shot.
ReferenceWhat does a phishing analyzer do?
It parses the email's headers (SPF, DKIM, DMARC, Received chain), extracts every URL and attachment, scores them against 8 threat-intel sources, and surfaces the deceptive patterns attackers use — look-alike domains, encoded display names, mismatched Reply-To, base64-encoded URLs in the body. The output is a verdict you can hand a Tier-1 analyst, not raw header dumps.
API
Want this in your SOAR or SIEM?
SARA Open ships an OpenAI-compatible API. Call POST /api/v1/phishing-analyze — SPF/DKIM/DMARC parsing, URL enrichment, and attachment risk scoring on any email or .eml.
curl -X POST https://sara-open.sirp.io/api/v1/phishing-analyze \
-H "Authorization: Bearer $SARA_API_KEY" \
-H "Content-Type: application/json" \
-d '{"raw_text": "Received: from …"}'
Read the API reference →