ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@rashost.com.
The latest stored availability evidence still shows the domain reachable; 8 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
arktisworld.shop is recorded in the PhishDestroy internal listing as of 2026-10-03, the same date as its first observation and blocklist check. A PageSpeed performance score of 76 was also recorded for the domain on 2026-10-03, giving a separate performance measurement alongside the listing record.
Recorded Evidence
The PhishDestroy internal listing for arktisworld.shop was recorded as true on 2026-10-03. VirusTotal recorded 11 detections across 91 scanners for arktisworld.shop on 2026-09-20, with the observation time known. The domain resolved to IP address 23.252.79.138 on 2026-10-03. PageSpeed recorded a performance score of 76 for arktisworld.shop on 2026-10-03.
Interpretation
The PhishDestroy listing and the VirusTotal detection count are separate source records, and neither should be read as a combined verdict on the domain. The VirusTotal observation predates the PhishDestroy listing, first observation and PageSpeed check, so the dates show a sequence rather than a measured change. The PageSpeed score describes a performance measurement only and does not speak to the listing or detection records.
Recommended Actions
Preserve the PhishDestroy listing record, the VirusTotal detection record and the PageSpeed performance record for arktisworld.shop as separate source documents. Compare the PhishDestroy listing against the VirusTotal detection record when reviewing arktisworld.shop, keeping each source's own measurement scope in view. Treat the PageSpeed performance score as a distinct metric from the listing and detection records when assessing arktisworld.shop.
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:38:19 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:38:19 UTClast content: 2026-10-11 10:38:19 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 arktisworld.shop· checked Oct 3, 2026
76
Needs Work
Performance
FCP
2.89s
First Contentful Paint
LCP
4.81s
Largest Contentful Paint
CLS
0.017
Cumulative Layout Shift
TBT
101ms
Total Blocking Time
SI
3.5s
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-03 03:42:12 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 23.252.79.138.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
12 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.
PDF notice generated Notice text archived (650 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
