Security engines reporting a detection: 12. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
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.
Registration (base domain)flnance.network · Created Feb 21, 2026 (233d)
Elapsed Since First Report54 days
What we count
Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Last known active.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedFeb 26, 2026
DOM Analysisanalyzed Mar 24, 2026score 63/1001 brand signal
ICANN OVERSIGHTRegistration: flnance.network
Accreditation and RAA context
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.
Accountability draft
Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
104.21.17.87
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
Nameservers 1
ns2.verification-hold.suspended-domain.com
Location describes the IP network.
TLS certificate
Issuer
WE1
Hostname coverage
Hostname coverage not recorded
Collection source
PhishDestroy collector
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Attributionactor class: Hostingmechanism: Placeholder Pagesource: Current Http Probe
Evidence layersAvailability: Non Threat ContentContent: Replaced Or ParkedDNS: ResolvedRegistration: Unknown
Latest HTTP observationInactiveHosting Placeholderactor class: HostingPlaceholder Page45%2026-10-11 01:28:52 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-17 01:49:50 UTCcurrent episode first observed: 2026-10-01 01:52:20 UTCobserved RIP window: 2026-09-17 01:49:50 UTC → 2026-10-01 01:52:20 UTC · 336.04hmidpoint estimate ≈ 2026-09-24 01:51:05 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.
Last analyzed Previous stored snapshot: 12 detections
ADMINUSLabs
alphaMountain.ai
BitDefender
Chong Lua Dao
CyRadar
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Sophos
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
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.
Domain Status Transition2026-09-17 10:17:10 UTC
Domain state transitioned from alive to dead.
Domain Status Transition2026-09-13 22:18:04 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-09-13 10:21:23 UTC
Domain state transitioned from alive to dead.
Domain Status Transition2026-09-11 22:17:44 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-09-10 22:23:59 UTC
Domain state transitioned from alive to dead.
Threat Response Pipeline
Discovery
Analysis
Monitoring
14 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
falcon.flnance.network detected and queued for full analysis
The domain remains reachable or access-restricted; future checks may update this observation.
How we investigate & report
Public scans, evidence and abuse channels
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.
4 evidence signal groups linked0 reports recordedLast known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · falcon.flnance.network
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches4
Same favicon hash or the same page title as this host.
(IN)
