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; 1 month 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.
On 2026-10-01, aerotwist.shop returned an HTTP status code of 200 according to a recorded check. A separate observation on 2026-09-09 placed the domain's first recorded appearance in this evidence set.
Recorded Evidence
The PhishDestroy internal listing for aerotwist.shop was recorded as true. VirusTotal recorded 7 detections across 89 scanners on 2026-09-18. OTX showed 4 pulses on 2026-09-10, and the SSL certificate scanned on 2026-09-10 was issued by Let's Encrypt / YE1. A PageSpeed check on 2026-09-09 produced a performance score of 77, while the HTTP check on 2026-10-01 returned status 200 from IP 146.19.203.205 in GE.
Interpretation
The PhishDestroy listing and the VirusTotal count were captured on different dates, so they describe separate snapshots rather than one simultaneous state. OTX pulses and the SSL scan share the 2026-09-10 date, which allows closer comparison between those two sources than with the 2026-09-18 VirusTotal result. Because the HTTP check on 2026-10-01 is later than the first observation on 2026-09-09, the two dates bracket a period during which the recorded signals were collected.
Recommended Actions
Anyone reviewing aerotwist.shop should retain the dated records from PhishDestroy, VirusTotal, OTX and the HTTP check so later observations can be compared against them. Subsequent checks of aerotwist.shop should be logged with their own dates and source names rather than merged with the existing entries. During review, avoid submitting credentials, payment details or other sensitive information to aerotwist.shop until the recorded signals have been independently verified.
DOM Analysisanalyzed 2026年9月10日score 88/1001 brand signal
Submitted URLhttp://aerotwist.shop/
Favicon Hash
ケース ID
ICANN OVERSIGHT
認定と RAA の背景
Registrar accreditation and DNS abuse obligations
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.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observationコンテンツ公開中Ordinary HTTP content served90%2026-10-11 10:07:30 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:07:30 UTClast content: 2026-10-11 10:07:30 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 aerotwist.shop· checked Sep 9, 2026
77
Needs Work
Performance
FCP
2.86s
First Contentful Paint
LCP
4.51s
Largest Contentful Paint
CLS
0.016
Cumulative Layout Shift
TBT
152ms
Total Blocking Time
SI
2.86s
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.
Domain Status Transition2026-10-09 01:45:11 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-09-24 22:07:42 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-09-10 15:13:54 UTC
VirusTotal scanner detections updated from 5 to 6. Added scanner alerts: Gridinsoft.
VirusTotal Detections Update2026-09-10 10:01:29 UTC
VirusTotal scanner detections updated from 4 to 5. Added scanner alerts: alphaMountain.ai.
VirusTotal Detections Update2026-09-10 04:50:21 UTC
VirusTotal scanner detections updated from 3 to 4. Added scanner alerts: SOCRadar.
VirusTotal Detections Update2026-09-09 23:04:33 UTC
VirusTotal scanner detections updated from 2 to 3. Added scanner alerts: LevelBlue.
Threat First Observed2026-09-09 20:28:55 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 146.19.203.205.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
17 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.
