Server route
Every hop (Received) with server, IP, delays and inconsistent times; for public IPs the reverse name and the network owner (RDAP).
The Phishing analysis module examines a suspicious message and reports only verifiable technical facts: what anyone can re-check by reading the file and querying DNS. No judgement on the tone of the text, no brand or reputation lists: an indicator is a fact, or it isn't there. Links are never opened.
Every hop (Received) with server, IP, delays and inconsistent times; for public IPs the reverse name and the network owner (RDAP).
The result recorded by the server that received the message, and a fresh evaluation per RFC 7208 with a trace of every step: include, redirect, the ten-lookup limit.
The body hash is verified offline; the signature, with the key published in the domain's DNS. For each signature: domain, selector, algorithm and result.
Alignment between the visible sender's domain and those authenticated by SPF and DKIM, and the policy published by the domain.
If a link's text shows an address and the link leads to another host, it is flagged. The comparison is on hosts, not path or parameters, and a subdomain of the same domain is consistent. Links to IP addresses, with @ and domains with non-ASCII characters are flagged too.
The whole tree, attached messages and winmail.dat included: double extensions, real type different from the declared one, executables, encrypted ZIP archives.
The rules downloaded from the configured endpoint are applied to the message and its attachments. If they can't be downloaded, the report says so: “could not look” is not “clean”.
All headers, the Authentication-Results outcomes and a report with every finding and its explanation.
.eml, .emlx, .msg) and choose whether to use network checks and YARA.