Analysis indicates that the domain falcon.flnance.network is actively hosting a crypto‑scam site. The site resolves to 104.21.17.87, a Cloudflare edge node (AS13335) located in the United States. Registration data shows the domain was created on 21 Feb 2026 through PDR Ltd. d/b/a PublicDomainRegistry.com, and it uses an SSL certificate identified as WE1. HTTP requests return status 200 and the page title is “Claims | Falcon Finance”, matching the listed scam type. The domain is listed on two security blocklists, currently blocked by PhishDestroy and ScamSniffer, and receives a Gridinsoft trust score of 0/100. VirusTotal scans report 7 of 93 vendors flagging the domain. Nameservers are set to ns1.verification‑hold.suspended‑domain.com and ns2.verification‑hold.suspended‑..., indicating a hold or suspension pattern often associated with malicious infrastructure. The evidence confirms a high‑risk, active crypto‑scam operation, but the exact payload or victim‑interaction flow has not been publicly disclosed. Defenders should block the domain at perimeter and DNS layers, monitor outbound traffic for connections to 104.21.17.87, and add indicators to threat‑intel feeds. Continuous re‑evaluation is advised in case the infrastructure changes or additional detection data becomes available.
DOM Analysisanalyzed 2026年3月24日score 63/1001 brand signal
ICANN OVERSIGHTRegistration: flnance.network
認定と RAA の背景
Registrar accreditation and DNS abuse obligations
For the registrable domain flnance.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.
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.
(US)
