atkhq.shop was observed in a VirusTotal scan on 2026-09-11, which reported detections from multiple scanners. The domain also appeared in a publisher-owned PhishDestroy internal listing, indicating it has been catalogued for further review.
Recorded Evidence
VirusTotal checked atkhq.shop on 2026-09-11 and reported 8 detections out of 92 total scanners. OTX included atkhq.shop in 3 pulses as of 2026-10-07. The domain was first observed on 2026-10-07 and had a PageSpeed performance score of 78 on the same date. PhishDestroy internally listed the domain for monitoring.
Interpretation
The VirusTotal and OTX records provide evidence that atkhq.shop has been flagged for review by multiple independent sources. The presence of the domain in the PhishDestroy internal listing and its inclusion in OTX pulses suggest it has drawn attention from threat intelligence platforms. The PageSpeed score is a technical metric and does not indicate content or security status.
Recommended Actions
Further review of atkhq.shop should consider the VirusTotal scan results and OTX pulse activity as key reference points. Preserve the VirusTotal and OTX records for ongoing comparison with future observations. The PhishDestroy internal listing should also be retained to track any changes in the domain’s status over time.
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.
Stored cloaking flag
Not yet scanned
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-07 02:00:26 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-07 02:00:26 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.
Google PageSpeed Insights — mobile performance audit of atkhq.shop· checked Oct 7, 2026
78
Needs Work
Performance
FCP
2.71s
First Contentful Paint
LCP
3.16s
Largest Contentful Paint
CLS
0.042
Cumulative Layout Shift
TBT
446ms
Total Blocking Time
SI
2.71s
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-07 02:00:26 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 62.106.90.114.
Threat Response Pipeline
Discovery
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.
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 · atkhq.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.
