amizly.shop was observed on 2026-10-07 with a VirusTotal scan recording 0 detections out of 92 scanners. On this date, the domain was also listed in the internal PhishDestroy catalogue and had a PageSpeed performance score of 65.
Recorded Evidence
On 2026-10-07, VirusTotal recorded 0 detections out of 92 scanners for amizly.shop. OTX documented four pulses for the domain on the same date. The domain was included in the PhishDestroy internal listing and received a PageSpeed performance score of 65, all observed on 2026-10-07.
Interpretation
The evidence for amizly.shop consists of multiple dated observations, each offering a distinct perspective on the domain's technical and reputational status. VirusTotal's scan did not identify any detections, while OTX's four pulses indicate the domain attracted some community attention. The PageSpeed score and internal PhishDestroy listing provide additional context for evaluating site performance and monitoring.
Recommended Actions
To assess amizly.shop, consult the VirusTotal scan results and OTX pulse records for reference. Preserve the internal PhishDestroy listing and PageSpeed performance score for ongoing comparison. Use these records to inform any future reviews or monitoring of amizly.shop.
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.
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.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-07 02:25:12 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-07 02:25:12 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.
Technologies · 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: 0 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
G-Data
Gridinsoft
Webroot
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of amizly.shop· checked Oct 7, 2026
65
Needs Work
Performance
FCP
2.74s
First Contentful Paint
LCP
12.83s
Largest Contentful Paint
CLS
0.007
Cumulative Layout Shift
TBT
175ms
Total Blocking Time
SI
4.87s
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:12:15 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 188.244.119.46.
Threat Response Pipeline
Discovery
Analysis
Notifications
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.
The domain remains reachable or access-restricted; future checks may update this observation.
How we investigate & report
Public scans, evidence and abuse channels
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.
PDF notice generated Notice text archived (650 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
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 →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · amizly.shop
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
(US)
