On 2026-10-06, arqhq.shop was flagged by PhishDestroy for phishing risks, per internal listing records. Notably, the domain received a PageSpeed performance score, indicating a technical assessment was performed alongside security reviews.
Recorded Evidence
VirusTotal reported 1 detection out of 92 scanners for arqhq.shop on 2026-10-06. On the same date, OTX recorded 2 pulses for the domain. PhishDestroy included arqhq.shop in its internal listing as of 2026-10-06, and a PageSpeed performance score of 71 was also recorded.
Interpretation
These records from VirusTotal, OTX, and PhishDestroy provide a diverse view of arqhq.shop's presence in security and technical monitoring systems on 2026-10-06. The OTX and PhishDestroy entries reflect attention from both community and internal catalogues, while the PageSpeed score offers insight into the site's technical performance.
Recommended Actions
For arqhq.shop, retain the VirusTotal, OTX, and PhishDestroy source records for future comparison. Use the PageSpeed score as a technical baseline for subsequent assessments. Preserve the first observation date to track the domain's timeline across monitoring sources.
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:07:48 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:07:48 UTClast content: 2026-10-11 10:07:48 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.
Last analyzed Previous stored snapshot: 1 detection
alphaMountain.ai
Forcepoint ThreatSeeker
Gridinsoft
SOCRadar
サイトパフォーマンス分析
Google PageSpeed Insights — mobile performance audit of arqhq.shop· checked Oct 6, 2026
71
Needs Work
Performance
FCP
2.87s
First Contentful Paint
LCP
6.69s
Largest Contentful Paint
CLS
0.004
Cumulative Layout Shift
TBT
121ms
Total Blocking Time
SI
3.28s
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.
Domain Status Transition2026-10-09 01:47:48 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-10-06 22:00:26 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-10-06 19:36:07 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 162.222.90.251.
脅威対応 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)
