Analysis of www.fletch.finance indicates that the domain is currently active and has been associated with a generic phishing campaign. Network resolution shows the domain pointing to the IPv4 address 64.29.17.65. The hosting infrastructure behind this address has not been publicly attributed to a known autonomous system or country in the supplied data, limiting the ability to assess the broader threat landscape of the host. DNS queries return no identifiable nameserver records, marked as NS_NOT_FOUND, which is a common tactic to hinder forensic tracing and may indicate use of a fast‑flux or dynamically allocated DNS service.
The domain is listed on a single security blocklist and has been explicitly blocked by the PhishDestroy filtering service, confirming that at least one external mitigation platform has taken action against it. VirusTotal reports that the domain was examined by 91 scanning engines, none of which raised a detection at the time of scanning; however, the absence of vendor flags does not constitute evidence of safety, especially given the confirmed phishing classification. No SSL/TLS certificate details, HTTP response codes, page title, or brand targeting information are available, leaving the content and payload characteristics unverified.
Consequently, the primary observable indicators are the IP resolution, blocklist presence, and the PhishDestroy block. Defenders should continue to deny any network traffic to www.fletch.finance, add the domain and its IP address to local and perimeter deny lists, and monitor for any emergent activity such as new DNS records or additional blocklist listings. Ongoing vigilance is recommended, as the lack of further technical artefacts suggests the operators may be employing a minimalist infrastructure that can be rapidly redeployed or altered.
Extracted from stored page analysis
Observed indicators
1 wallet · 1 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
