Alaqsadirect.shop was observed in a VirusTotal scan on 2026-10-02 with 0 detections out of 92 scanners, indicating no threats were found at that time. The domain also appeared in the PhishDestroy internal listing, which is a publisher-owned catalogue.
Recorded Evidence
VirusTotal checked alaqsadirect.shop on 2026-10-02, recording 0 detections from 92 total scanners. OTX included the domain in 3 pulses as of 2026-10-06. The domain was observed in the PhishDestroy internal listing on 2026-10-06. A PageSpeed performance score of 81 was recorded on 2026-10-06.
Interpretation
The VirusTotal scan provides a snapshot of the domain’s status among multiple scanners, while OTX pulses indicate that the domain has been referenced in several security intelligence contexts. The PhishDestroy internal listing shows that the domain is tracked by the publisher’s own catalogue. The PageSpeed performance score offers a measure of the domain’s technical performance but does not indicate security or content.
Recommended Actions
Review the VirusTotal and OTX records for alaqsadirect.shop to understand the context of its security observations. Retain the PhishDestroy internal listing and PageSpeed performance score for future comparison with subsequent scans. Monitoring these sources can help track changes in how the domain is categorized or referenced over time.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='alaqsadirect.shop', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-11 10:07:53 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-09 01:48:46 UTClast content: 2026-10-08 22:00:17 UTCcurrent episode first observed: 2026-10-09 20:20:42 UTCobserved RIP window: 2026-10-09 01:48:46 UTC → 2026-10-09 20:20:42 UTC · 18.53hmidpoint estimate ≈ 2026-10-09 11:04:44 UTC · precision medium · basis bounded
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.
Last analyzed First positive detection Previous stored snapshot: 0 detections
alphaMountain.ai
BitDefender
CRDF
ESET
Forcepoint ThreatSeeker
G-Data
Gridinsoft
ネットクラフト
SOCRadar
サイトパフォーマンス分析
Google PageSpeed Insights — mobile performance audit of alaqsadirect.shop· checked Oct 6, 2026
81
Needs Work
Performance
FCP
2.86s
First Contentful Paint
LCP
4.05s
Largest Contentful Paint
CLS
0.004
Cumulative Layout Shift
TBT
67ms
Total Blocking Time
SI
3.57s
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 21:15:32 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.211.
脅威対応 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.
