The domain benmenwearfashion.shop was included in the PhishDestroy internal listing on 2026-10-13, documenting its presence for security review. Another notable fact is that VirusTotal recorded detections for this domain from multiple scanners, providing an external reference point.
Recorded Evidence
VirusTotal checked benmenwearfashion.shop on 2026-10-11, recording 6 detections out of 92 total scanners. OTX documented four pulses referencing this domain as of 2026-10-13. PhishDestroy internally listed the domain on 2026-10-13. A PageSpeed performance score of 65 was recorded on 2026-10-13, and the SSL certificate was issued by Let's Encrypt / YE1.
Interpretation
PhishDestroy provides a catalogue entry for benmenwearfashion.shop, serving as an internal record of its observation. VirusTotal contains a quantitative measurement of how many external scanners detected the domain, reflecting its evaluation by multiple security tools. OTX records pulses that represent community-driven intelligence, expanding the context of its security profile. These sources together offer a technical snapshot of the domain from several perspectives.
Recommended Actions
For benmenwearfashion.shop, retain the VirusTotal detection results and OTX pulse records for ongoing reference. Preserve the PhishDestroy internal listing as a catalogue entry for future comparison. Use these dated records to track any subsequent changes in the domain’s observed profile and inform future evidence reviews.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
저장된 은신 플래그
아직 스캔되지 않았습니다
TDS 지문 인식 실시간 확인
이 패널이 열려 있을 때 PhishDestroy 스캐너에서 실행되는 7개의 케이타로 지문과 크롤러 대 브라우저 비교 결과.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation알 수 없음Probe Inconclusive20%2026-10-13 06:09:19 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-13 06:09:19 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.
Last analyzed First positive detection Previous stored snapshot: 6 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Gridinsoft
LevelBlue
넷크래프트
사이트 성능 분석
Google PageSpeed Insights — mobile performance audit of benmenwearfashion.shop· checked Oct 13, 2026
65
Needs Work
Performance
FCP
2.88s
First Contentful Paint
LCP
13.08s
Largest Contentful Paint
CLS
0.02
Cumulative Layout Shift
TBT
211ms
Total Blocking Time
SI
3.89s
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-13 06:09:19 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 162.222.90.226.
위협 대응 Pipeline
발견
Analysis
Monitoring
8 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.
