On 2026-10-07, americancrew.shop returned an HTTP 301 status, which means a redirect response was recorded on that date. The domain also appeared in a publisher-owned PhishDestroy internal listing, providing another observation from the same day.
Recorded Evidence
VirusTotal reported 3 detections out of 92 scanners for americancrew.shop on 2026-10-07. OTX referenced the domain in 3 separate pulses as of that date. The observed page title was "Official Provider of Men's Grooming & Styling | Crew" on 2026-10-07. A URLScan report and a PageSpeed performance score of 80 were also recorded on the same date.
Interpretation
These records show that americancrew.shop was checked by multiple security and analysis platforms, each providing separate observations about its characteristics. The HTTP 301 response documents the type of server reply received, while VirusTotal and OTX offer additional perspectives based on their own scanning and pulse systems. The presence in the publisher-owned PhishDestroy catalogue and the availability of a URLScan report further expand the range of documented evidence for this domain.
Recommended Actions
For any review involving americancrew.shop, retain the HTTP status record, VirusTotal detection results, and OTX pulse references. Compare these with the PhishDestroy internal listing and the URLScan report to understand the domain’s recorded characteristics. Regularly update and cross-check these sources to monitor for any new or changed observations.
DOM Analysisanalyzed 2026年10月9日score 81/1001 brand signal
Submitted URLhttp://americancrew.shop/
Favicon Hash
ICANN OVERSIGHT
认证和 RAA 背景
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
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:39:29 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 10:39:29 UTClast content: 2026-10-11 10:39:29 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: 3 detections
Forcepoint ThreatSeeker
Gridinsoft
Netcraft
网站性能分析
Google PageSpeed Insights — mobile performance audit of americancrew.shop· checked Oct 7, 2026
80
Needs Work
Performance
FCP
2.89s
First Contentful Paint
LCP
3.75s
Largest Contentful Paint
CLS
0.031
Cumulative Layout Shift
TBT
186ms
Total Blocking Time
SI
3.88s
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-06 22:51:17 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.
(US)
