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; 10 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 amihaven.shop returned an HTTP 301 status on 2026-10-02, confirming a redirect response was recorded by that check. A PageSpeed performance score of 70 was also documented for the domain on 2026-10-01.
Recorded Evidence
On 2026-10-02, amihaven.shop appeared in the PhishDestroy internal listing with a recorded target brand of 'fakeshop.' VirusTotal recorded 10 detections out of 91 scanners on 2026-10-01. OTX referenced amihaven.shop in 2 pulses as of 2026-10-02.
Interpretation
These source records provide a dated technical and security context for amihaven.shop, including HTTP response, performance, and multiple third-party security observations. The combination of PhishDestroy listing, VirusTotal detections, and OTX pulses offers a range of perspectives on the domain's recent activity.
Recommended Actions
Further review of amihaven.shop should reference the HTTP status, PhishDestroy listing, VirusTotal detections, and OTX pulses for comparison with future findings. Retaining the PageSpeed score will also help track any changes in the domain's performance.
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:36:25 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 10:36:25 UTClast content: 2026-10-11 10:36:25 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 amihaven.shop· checked Oct 1, 2026
70
Needs Work
Performance
FCP
2.97s
First Contentful Paint
LCP
4.99s
Largest Contentful Paint
CLS
0.013
Cumulative Layout Shift
TBT
265ms
Total Blocking Time
SI
3.73s
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-01 03:05:58 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 23.252.79.202.
威胁响应 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.
