Mail Shield

Email incident response · engine v4.2

Quarantine the incoming mail. Trace it to the origin.

Paste headers or raw MIME, upload the source artifact, and MailShield renders threat score, hop chain, and intent in seconds. Case #TR-90341 is active.

Last sync · 00:00:00 UTC

Intake · Raw email artifact

MIME · Headers · Signature verified

Queue 01 / 02
From: svc.billing@auth0-secure.ioSPF · failDKIM · failDMARC · fail
AUTHENTICATION DETAILS
From domainauth0-secure.io
SPF domain (envelope)not detected
SPF resultFAIL
SPF alignmentn/a (SPF failed)
DKIM signing domain (d=)not detected
DKIM resultFAIL
DKIM alignmentn/a (DKIM failed)
DMARC resultFAIL
invoice_9042_final.exe

Threat score

Rule-based header assessment

Critical
0/100Assessment Confidence: High
Spoof0.97
Payload0.92
Social0.85
Primary Threat TypeIdentity Spoofing & Domain Impersonation
Threat Context

Warning: High threat score reflects identity fraud and email spoofing risks caused by failed sender authentication. This indicates a high risk of social engineering or credential theft rather than direct system malware execution.

Origin trace · hop chain

Select a node to inspect the relay

3 relays · 79 ms RTT
GRID 51.5N · 0.12WNODE VIEW / THERMAL OVERLAYTHREATFEED · LIVE185.220.101.445.148.10.92203.0.113.7

Stage 01 · Origin

185.220.101.4 — hosting / reputation classification

No reverse DNS · anonymising exit rotation · first seen with spoofed auth0-secure.io envelope.

RISK 0.99

IP Forensics & Origin Location

Live geolocation via ip-api.com

Resolving…
Origin IP Address185.220.101.4
Country & City—
ISP / Organization—
Network Geolocation—

IP geolocation represents approximate network location and does not identify an attacker's physical location.

Trace AI · Narrative summary

Reasoning visible · cited evidence

Live

ObservedExtracted directly from the submitted headers

Sender Identity: auth0-secure.ioPayload: invoice_9042_final.exe

AI InferenceRule-based reasoning over the observed data

Message claiming to be from auth0-secure.io ("Wire transfer — Q3 audit reconciliation (URGENT)") fails authentication — SPF FAIL, DKIM FAIL, DMARC FAIL — so the sender identity cannot be verified. 1 link/payload artifact(s) detected and origin 185.220.101.4 is untrusted; recommend quarantine and edge block.

AI Insights · AI Inference

Identity Fraud Detected: The message was routed via an unverified relay, but failed domain alignment with auth0-secure.io. This indicates unauthorized domain spoofing designed for credential theft rather than direct system malware execution.

HeuristicDeterministic rule-engine verdicts

Threat CategoryIdentity Spoofing & Phishing Hazard
System Risk LevelLow (No malicious code execution)
User Risk LevelCritical (High probability of social engineering & password theft)

ObservedSignals read from the submitted headers

Domain & Sender VerificationFAIL (Unverified Sender)
File & Link Security ScanHIGH RISK (1 Links / Payloads Found)
Server Origin & ReputationSUSPICIOUS (185.220.101.4)

Forensic export

Header artifact · SHA-256 integrity verification

Evidence IDEV-CALCULATING…Case IDTR-90341SHA-256Calculating…File namephishing-sample.emlFile size466 BAcquisition timeThu, 19 Nov 2026 00:26:11 GMTAnalysis timeThu, 19 Nov 2026 00:26:11 GMTReport generation timePending
Tamper-Evident Evidence Record

Hashing helps verify file integrity but does not by itself establish complete legal chain of custody.