The domain www.rocketbotlatam.space was a phishing site engaged in brand impersonation targeting the company Across. It posed an elevated risk by mimicking legitimate Rocketbot RPA software pages to deceive users into disclosing credentials or sensitive information. No crypto drainer kit was associated with this campaign. The site is currently taken offline.
Technical indicators confirm www.rocketbotlatam.space was registered through HOSTINGER operations, UAB on July 23, 2025. It resolved to the IP address 44.194.186.33, hosted on Amazon.com, Inc. infrastructure in the US. Only 1 of 95 VirusTotal security vendors flagged the domain, and it appeared on a single security blocklist (PhishDestroy). The site lacked an SSL certificate, and its nameservers were ns1.dns-parking.com and ns2.dns-parking.com. The observed page title was 'Inicio - Rocketbot Software de RPA y automatización de procesos', reinforcing its impersonation of Rocketbot’s branding. Gridinsoft assigned a trust score of 0/100.
Users who interacted with www.rocketbotlatam.space should immediately change any credentials entered on the site, enable two-factor authentication, and monitor accounts for unauthorized activity. Report the domain to Google Safe Browsing, PhishTank, or local cybersecurity authorities. If financial or crypto-related data was exposed, contact the relevant institution for fraud protection measures.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-10822.invalid', port=80): Max retries exceeded with url: / (Caused by N
DOM Analysisanalyzed 2026年4月23日score 10/1009 brand signals
Submitted URLhttp://www.rocketbotlatam.space/
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.
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 01:11:57 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-06-09 22:22:32 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.
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.
(LT)
