anomwear.shop appears in the PhishDestroy internal listing, a publisher-owned catalogue, as recorded on 2026-10-03. The same evidence set records a VirusTotal result of 4 detections across 91 scanners, checked on 2026-09-11.
Recorded Evidence
Recorded evidence for anomwear.shop includes the PhishDestroy internal listing observed on 2026-10-03. VirusTotal recorded 4 detections out of 91 scanners on 2026-09-11. OTX recorded 1 pulse on 2026-10-03. The domain resolved to IP address 195.96.130.219, and the first observation date was 2026-10-03. PageSpeed recorded a performance score of 59 on 2026-10-03.
Interpretation
The PhishDestroy listing and the VirusTotal detection count are separate source records that describe different kinds of observation. The OTX pulse count reflects a single dated entry in that platform, while the PageSpeed score reflects a performance measurement taken on its own date. Because the VirusTotal check and the other records carry different dates, they should be compared as distinct snapshots rather than treated as one combined result.
Recommended Actions
For anomwear.shop, preserve the PhishDestroy listing record and the VirusTotal detection record as separate items for future comparison. Review the OTX pulse entry alongside those records to see whether the same domain continues to appear in each source. Compare the PageSpeed performance score against later measurements to track any change in that metric. Retain the first observation date and the IP address record as reference points when reviewing the domain's evidence history.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not yet scanned
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-03 01:34:01 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-03 01:34:01 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Google PageSpeed Insights — mobile performance audit of anomwear.shop· checked Oct 3, 2026
59
Needs Work
Performance
FCP
2.89s
First Contentful Paint
LCP
11.77s
Largest Contentful Paint
CLS
0.055
Cumulative Layout Shift
TBT
400ms
Total Blocking Time
SI
3.4s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Threat First Observed2026-10-03 01:34:01 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.219.
Threat Response Pipeline
Discovery
Analysis
Monitoring
8 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
anomwear.shop detected and queued for full analysis
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
