The domain app-rhea.network has been identified as a generic phishing site. There is no evidence it impersonated a specific brand or deployed a drainer kit. The site is currently offline. Users searching for information about whether app-rhea.network is safe or a scam should be aware that it has been associated with phishing activity and is not considered safe.
Technical analysis shows that app-rhea.network was registered through OwnRegistrar, Inc. on July 31, 2025, and resolves to the IP address 188.114.97.3, located in the US under AS13335 (Cloudflare, Inc.). The domain has been detected by 1 of 95 security vendors on VirusTotal, specifically Gridinsoft, and appears on one security blocklist (PhishDestroy). The SSL certificate is not present, and the page title observed was 'Nur einen Moment…'. The current HTTP status is 429, and the domain has only one nameserver configured. The Gridinsoft trust score is 0/100.
Anyone who interacted with app-rhea.network should remain vigilant for potential phishing impacts. It is recommended to change any passwords entered on the site, enable two-factor authentication where possible, and monitor accounts for suspicious activity. If you suspect you have been targeted by this phishing domain, report the incident to relevant security teams or authorities for further investigation.
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.
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:11:52 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-06-16 16:28:38 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-16 16:28:38 UTC → 2026-09-30 16:14:55 UTC · 2,543.77hmidpoint estimate ≈ 2026-08-08 16:21:46 UTC · precision very 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.
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='app-rhea.network', port=80): Max retries exceeded with url: / (Caused by NewConnectionErro
app-rhea.network
保存済みの結果
到達不能
Stored observation history11
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.
(US)
