On 2026-10-01, alvjewels.shop returned an HTTP 301 response according to the recorded HTTP check. The same evidence set includes a page title observed as "On Trend Jewelry | ALV Jewels" and a PhishDestroy internal listing.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 301, and the page title observed that day was "On Trend Jewelry | ALV Jewels". A PhishDestroy internal listing was recorded, and the target brand field was recorded as fakeshop. VirusTotal, checked on 2026-09-29, reported 8 detections across 91 scanners. OTX was checked on 2026-10-01 and showed 2 pulses. The URLScan check on 2026-10-01 found a report available, and PageSpeed on 2026-10-01 recorded a performance score of 71.
Interpretation
These records describe separate observations made by different sources, each with its own scope and measurement method. The VirusTotal detections, OTX pulses, URLScan report availability, PageSpeed score, and PhishDestroy listing each capture a different kind of signal, so they should be read individually rather than merged into a single conclusion. The dates show that the VirusTotal check occurred two days before the other checks, which is a chronological detail worth noting when comparing the records.
Recommended Actions
Preserve the PhishDestroy listing, the VirusTotal detection record, and the OTX pulse record for alvjewels.shop so they can be compared later. Separately retain the URLScan report and the PageSpeed result, since they document different aspects of the domain. Compare these saved records against future observations of alvjewels.shop rather than relying on any single source.
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:29:49 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 10:29:49 UTClast content: 2026-10-11 10:29:49 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.
Google PageSpeed Insights — mobile performance audit of alvjewels.shop· checked Oct 1, 2026
71
Needs Work
Performance
FCP
2.99s
First Contentful Paint
LCP
5.69s
Largest Contentful Paint
CLS
0.004
Cumulative Layout Shift
TBT
115ms
Total Blocking Time
SI
4.19s
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-01 02:36:26 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.217.
威胁响应 Pipeline
发现
Analysis
Monitoring
11 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.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
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.
