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; 16 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.
The domain akasoexclusive.shop returned HTTP status 301 on 2026-10-01, indicating a recorded redirect response. The domain was first observed on 2026-09-25, marking its earliest appearance in the evidence set.
Recorded Evidence
On 2026-10-01, the HTTP check recorded status 301 for akasoexclusive.shop. VirusTotal, checked on 2026-09-29, reported 8 detections out of 91 scanners. OTX, checked on 2026-09-27, listed 4 pulses for the domain. The PhishDestroy internal listing flagged the domain as true on the same date as the blocklist check.
Interpretation
The HTTP 301 response documents a redirect recorded on 2026-10-01 without describing the destination or content. VirusTotal detections and OTX pulses represent separate dated observations that should be reviewed independently rather than combined. The PhishDestroy internal listing adds a publisher-maintained catalogue entry distinct from scanner outputs.
Recommended Actions
Retain the akasoexclusive.shop HTTP record and PhishDestroy internal listing as preserved source entries for future comparison. Compare the VirusTotal and OTX observations separately, as each was collected on its own schedule. Re-check akasoexclusive.shop against these named sources and retain each result with its collection date.
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 observationRedirectingHTTP redirect observed80%2026-10-11 10:12:04 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:12:04 UTClast content: 2026-10-11 01:45:42 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.
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.
VirusTotal Detections Update2026-09-25 05:51:09 UTC
VirusTotal scanner detections updated from 4 to 5. Added scanner alerts: SOCRadar.
Threat First Observed2026-09-25 02:44:40 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 162.222.90.248.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
13 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.
