ankershop.shop appears in the PhishDestroy internal listing as of 2026-10-02, and VirusTotal recorded 6 detections across 91 scanners on the same date. The domain also returned a PageSpeed performance score of 66 when measured on 2026-10-02.
Recorded Evidence
The PhishDestroy internal listing for ankershop.shop was recorded on 2026-10-02. VirusTotal reported 6 detections out of 91 scanners on 2026-10-02. OTX recorded 2 pulses on 2026-10-02. The SSL certificate was issued by Let's Encrypt / YE1, scanned on 2026-10-02. PageSpeed recorded a performance score of 66 on 2026-10-02.
Interpretation
The PhishDestroy listing and VirusTotal detections are separate source observations that each describe the domain from a different collection method. OTX pulses represent another record, while the PageSpeed score reflects a performance measurement rather than a security judgment. Because all recorded dates fall on the same calendar day, the evidence does not show a sequence of events or a trend over time.
Recommended Actions
Review the PhishDestroy listing and VirusTotal record for ankershop.shop to determine whether further investigation is warranted. Preserve the OTX pulse record and the PageSpeed measurement for comparison with future observations. Compare the PhishDestroy catalogue entry against the VirusTotal scanner results in separate evaluations rather than merging them into a single conclusion.
DOM Analysisanalyzed 2026年10月9日score 83/1003 brand signals
Submitted URLhttp://ankershop.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.
Latest HTTP observation未知Probe Inconclusive20%2026-10-11 10:08:39 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 01:41:47 UTClast content: 2026-10-11 01:41:47 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 ankershop.shop· checked Oct 2, 2026
66
Needs Work
Performance
FCP
2.86s
First Contentful Paint
LCP
9.3s
Largest Contentful Paint
CLS
0.004
Cumulative Layout Shift
TBT
242ms
Total Blocking Time
SI
2.86s
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-02 15:11:49 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.240.
威胁响应 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.
(US)
