On 2026-10-09, aylift.shop was checked by VirusTotal and found to have zero detections among 92 scanners. The same day, the domain was also listed in the PhishDestroy internal catalogue.
Recorded Evidence
VirusTotal reported 0 detections out of 92 scanners for aylift.shop on 2026-10-09. OTX recorded four pulses referencing the domain on that date. The domain was included in the PhishDestroy internal listing as of 2026-10-09. A PageSpeed performance score of 85 was measured, and the SSL certificate was scanned on 2026-10-09.
Interpretation
These records show that aylift.shop was referenced by multiple security and performance monitoring sources on 2026-10-09. VirusTotal's results indicate no detections by its participating scanners, while OTX and PhishDestroy both noted the domain in their respective catalogues. The PageSpeed score provides additional context about the site's technical performance at the time.
Recommended Actions
For any future assessments of aylift.shop, compare the VirusTotal, OTX, and PhishDestroy records to identify changes or new observations. Retain the PageSpeed and SSL scan results for reference when reviewing technical updates or shifts in monitoring status.
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:01:02 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:01:02 UTClast content: 2026-10-11 10:01:02 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 aylift.shop· checked Oct 9, 2026
85
Needs Work
Performance
FCP
2.89s
First Contentful Paint
LCP
3.15s
Largest Contentful Paint
CLS
0.051
Cumulative Layout Shift
TBT
152ms
Total Blocking Time
SI
3.84s
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-09 00:31:30 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.252.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
9 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.
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
2026年10月9日
Brand Impersonation
Impersonation of Fakeshop
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
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)
