The Docket · Information technology

Can AI detect phishing emails reliably?

Ruling current. Adjudicated 23 October 2026; next review by 21 January 2027. 4 of 4 panel models answered.

Not legal or professional advice. This page is informational, not legal, medical or financial advice, nor any other professional advice. It is not a substitute for advice from a qualified professional about your own situation.

On the Surface

AI substantially improves phishing detection but cannot do so reliably on its own, and should be treated as one layer in a defense-in-depth strategy rather than a definitive filter.

Agreed by all four

  • AI analyzes sender behavior, URL and domain patterns, linguistic cues, urgency and manipulation tactics, attachment behavior, and metadata to catch phishing attempts that traditional rule-based or signature-based systems miss.
  • Controlled studies report detection rates of 90
  • 99% in some datasets, but those figures may not reflect performance against changing, real-world attacks.
  • Sophisticated phishing, including spear-phishing, business email compromise, and zero-day campaigns, frequently evades AI filters because such emails closely mimic legitimate communication.
  • Compromised legitimate accounts are a specific weakness: a message sent from a real, authenticated account can appear trustworthy even when its content is malicious.
  • Adversarial techniques mean attackers actively craft emails to bypass AI models, and generative AI now allows attackers to produce grammatically flawless, highly personalized phishing content that defeats standard NLP detection.
  • AI systems require continuous retraining because phishing tactics evolve faster than static models can accommodate.
  • False positives (legitimate emails flagged as phishing) and false negatives (malicious emails passed as safe) both occur.
  • Best practice is to combine AI with email authentication (SPF, DKIM, DMARC), URL and attachment scanning, sandboxing, user awareness training, and multi-factor authentication; treat an AI "safe" verdict as a risk estimate, not proof that an email is safe.

By three

  • AI can detect behavioral anomalies by learning what normal communication looks like for a specific user or organization, flagging deviations such as an unusual wire-transfer request from an unexpected IP address.
  • Advanced AI can apply computer vision to recognize brand logo impersonation on fake login pages.

By two

  • Business email compromise, where no malicious link or attachment is present and the attack relies purely on text-based social engineering, is among the hardest categories for AI to flag.
  • Major providers such as Gmail and Outlook already deploy these techniques and block the majority of bulk, obvious phishing before messages reach users.

Raised by one

  • AI can analyze hundreds of hidden metadata points in email headers, including domain age, to spot spoofing attempts that surface-level content analysis would miss.
  • LLMs tested as phishing detectors have been observed to classify the same message inconsistently across runs, adding an additional layer of unreliability beyond simple accuracy figures.
Digging Deeper

WHAT WAS ASKED

Whether AI can reliably detect phishing emails. No reframe was required. The question is straightforward and the panel addressed it directly.

WHERE THE PANEL DISAGREED

One substantive disagreement runs through the panel, and it is about framing rather than fact.

One response leads with "yes, but with limitations" and describes enterprise-grade AI as stopping "the vast majority" of attacks. Another leads with "no" and defines reliability as near-100% accuracy. A third and fourth land in the same place as the second but use softer phrasing.

This is not a genuine factual split. All four agree on the underlying numbers, the mechanism, and the limitations. The disagreement is about what word to put at the front of the answer. The "yes" framing and the "no" framing are both internally consistent, they just define "reliable" differently. This does not change the substance.

One response adds a specific vulnerability the others underweight: compromised legitimate accounts. When a real vendor's email account is hijacked, the authentication signals AI reads are clean. The sender is known, the domain is valid, SPF and DKIM pass. AI reads the surface as safe. This is not a minor edge case. Business email compromise via compromised accounts is among the most financially damaging phishing vectors in practice. This point deserved more weight than most responses gave it.

No response seriously challenged the 98 - 99% accuracy figures cited for controlled environments. One noted that these figures may not reflect real-world conditions. That caveat is correct and consequential. Controlled dataset accuracy and production inbox accuracy are different measurements, and the gap between them matters most for sophisticated targeted attacks, exactly the attacks that cause the most damage.

HOW STRONG THE AGREEMENT IS

The agreement is strong on the core finding and weaker on two specific points.

What would overturn the core consensus: evidence that AI detection performs at near-100% accuracy in production environments against sophisticated, targeted attacks, not benchmark datasets. No such evidence exists. The consensus holds.

Whether the agreement is independent: partly. All four responses draw on the same publicly available research base. The 98 - 99% accuracy figure traces to a small set of academic papers testing specific datasets. That number has been widely reproduced across the AI security literature, but the panel is citing a shared pool of sources, not conducting independent triangulation. The figure should be treated as indicative, not definitive.

The strongest counter-argument the panel did not fully represent: AI phishing detection and AI phishing generation are now on the same development curve, and the generator has a structural advantage. A defender must catch every attack. An attacker only needs to find one variant the model was not trained to catch. The adversarial asymmetry is real, and it compounds over time as generative AI makes high-quality phishing cheaper to produce at scale. None of the four responses made this argument with enough force. It belongs in any complete assessment.

WHAT THIS MEANS

This question has one clear answer, it is not genuinely contested.

AI phishing detection is effective, not reliable. Those are different claims. Effective means it reduces the volume of successful phishing substantially. Reliable means it can be depended on as a primary control. It cannot. The gap is not a rounding error. It lives precisely in the category of attacks that cause the most damage: targeted business email compromise, hijacked legitimate accounts, and adversarially crafted content designed to pass AI filters.

The panel's near-uniform recommendation, layered defense combining AI, email authentication, sandboxing, and human awareness, is not a hedge. It is the correct architecture. AI is a high-volume filter, not a trust signal. An AI "safe" verdict tells you the email does not match known patterns. It says nothing about whether the email is actually safe.

BOTTOM LINE

AI detects phishing effectively. It does not detect it reliably.

The decisive factor: AI reads signals. Sophisticated attackers, and compromised legitimate accounts, produce clean signals. When signals are clean, AI passes the email. The failure mode is not random noise. It is concentrated in exactly the attacks humans are least equipped to catch themselves.

What would change this verdict: a production-validated detection rate above 99% sustained against targeted spear-phishing and BEC, not controlled dataset benchmarks. That evidence does not currently exist.

The directive: deploy AI email filtering as a high-volume pre-filter. Apply stricter human review to any email requesting financial action, credential input, or access changes, regardless of filter verdict. Treat authentication pass (SPF, DKIM, DMARC) as a necessary check, not a sufficient one. Train users specifically on compromised-account scenarios, where everything about the email looks legitimate.

AI makes phishing harder. It does not make skepticism optional.

Both blocks are SimulQ’s result exactly as a member receives it: four frontier models answered independently, and SimulQ’s protocol compared and ruled on their answers. Nothing above has been edited.

Sources the panel cited

  1. AI phishing detection: Techniques, tools, and limitations - Valimail, valimail.com. Checked 23 October 2026.
  2. Analysis and prevention of AI-based phishing email attacks, arxiv.org. Checked 23 October 2026.
  3. AI Will Increase the Quantity — and Quality — of Phishing Scams - Schneier on Security, schneier.com. Checked 23 October 2026.
  4. Evaluating Large Language Models’ Capability to Launch Fully Automated Spear Phishing Campaigns: Validated on Human Subjects, arxiv.org. Checked 23 October 2026.
  5. "AI-Generated Phishing Emails Almost Impossible to Detect, Report Finds" | Science of Security Virtual Organization, sos-vo.org. Checked 23 October 2026.

Re-adjudication

Every Docket question goes back to the panel at least every 90 days. If the ruling changes, the change is recorded here.

Your question

Ask your own question — 5 free credits.

Start free trial