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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-11 10:08:38 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 10:08:38 UTClast content: 2026-10-11 10:08:38 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.
技术 · 1 identified
H
HTTP/3
Miscellaneous
HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
Last analyzed First positive detection Previous stored snapshot: 5 detections
CRDF
Forcepoint ThreatSeeker
Gridinsoft
LevelBlue
Netcraft
SOCRadar
网站性能分析
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.
威胁响应 Pipeline
发现
Analysis
Monitoring
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
