The domain app.migrationfuel.network is a generic phishing site designed to deceive users into disclosing sensitive information. It does not impersonate a specific brand or employ a known drainer kit. As of the latest verification, app.migrationfuel.network has been taken offline, though it previously posed an elevated risk of credential theft or other fraudulent activity.
Technical analysis shows that app.migrationfuel.network was flagged by 2 of 95 VirusTotal security vendors, including ChainPatrol and SOCRadar. The domain was registered through HOSTINGER operations, UAB, on February 21, 2026, and resolved to the IP address 46.202.197.252, hosted by AS47583 Hostinger International Limited. It appeared on three security blocklists: PhishDestroy, MetaMask, and SEAL. No SSL certificate was issued for the domain, and the observed page title was 'Default page'. Nameservers were ns1.dns-parking.com and ns2.dns-parking.com.
Users who may have interacted with app.migrationfuel.network should immediately change any passwords or credentials entered on the site. Enable two-factor authentication (2FA) on all accounts as an additional security measure. Monitor financial and online accounts for unauthorized activity. Report the phishing domain to relevant platforms, such as Google Safe Browsing, anti-phishing organizations, or the registrar (HOSTINGER operations, UAB) to aid in mitigation efforts.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='app.migrationfuel.network', port=80): Max retries exceeded with url: / (Caused by NewConne
For the registrable domain migrationfuel.network behind this subdomain, 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-13 01:00:28 UTC
RDAP registration未知
Observed timelinecurrent episode first observed: 2026-09-30 16:14:55 UTCfirst terminal observation: 2026-09-30 16:14:55 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.
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.
12 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)
