On July 12, 2026, the domain latam-rocketbot.digital was identified as a high-risk generic phishing domain. The domain is registered through HOSTINGER operations, UAB, and was created on February 21, 2026. Analysis indicates that the domain has a Gridinsoft trust score of 0/100, which is the lowest possible score, reflecting a high level of suspicion. The domain resolves to the IP address 46.202.172.166, which is located in France and is associated with HOSTINGER FR. Despite the low trust score, only one out of 95 security vendors on VirusTotal flagged this domain, which may suggest limited or emerging visibility in the security community. The HTTP status code of 403 indicates that the server is refusing to respond to the request, possibly due to security measures or the domain being taken down. However, the domain is still reported as active and is blocked by PhishDestroy, a known security blocklist. Infrastructure analysis reveals that the domain is using nameservers ns1.dns-parking.com and ns2.dns-parking.com, which are commonly associated with temporary or parked domains, further raising concerns about its legitimacy. Given the high risk level and the active status of the domain, defenders should exercise extreme caution and consider blocking access to this domain to prevent potential phishing attacks. The exact content of the domain has not been fully analyzed, but the page title 'Clock error' suggests that the site may be displaying an error or may be intentionally misleading users. Defenders should monitor for any related malicious activity and ensure that users are aware of the risks associated with this domain.
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.
Certificate fingerprint679f640cb39c1c632ca0270828269b2cba217c04bf4552f8fbea083679fc5a3aCertificate names · 1 SANs
www.latam-rocketbot.digital
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-19 01:13:42 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-09-07 22:14:28 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-07 22:14:28 UTC → 2026-09-30 16:14:55 UTC · 546.01hmidpoint estimate ≈ 2026-09-19 07:14:41 UTC · precision low · basis bounded
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.
Recorded subdomains1
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.latam-rocketbot.digitalDomain record
The original observation time is not recorded for these hostnames.
Last analyzed Previous stored snapshot: 3 detections
alphaMountain.ai
Gridinsoft
SOCRadar
サイトパフォーマンス分析
Google PageSpeed Insights — mobile performance audit of latam-rocketbot.digital· checked Apr 29, 2026
100
Good
Performance
FCP
0.89s
First Contentful Paint
LCP
0.89s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.05s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Registration & observation details8
Availability observations
Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
546.01
Estimate basis
Bounded by observations
Estimate precision
Low
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='latam-rocketbot.digital', port=80): Max retries exceeded with url: / (Caused by NewConnect
latam-rocketbot.digital
Stored observation history12
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.
(LT)
