Cloudflare Radar
Scan report
Open reportThis pages.dev subdomain presents a Flare rewards allocation proposal page that prompts visitors to connect a crypto wallet to vote. If you connected your wallet, disconnect it immediately and check for unauthorized token approvals.
Page title: “Flare: The blockchain for data”
Listed by external blocklists: MetaMask, SEAL. Use caution — do not enter credentials or personal information.
Risk score, higher = worse · How this score works
Pick what happened and tick the steps as you go. The ticks are kept only in this browser.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
URLScan capture · 2026-11-22 05:27 UTC · SHA-256 4ba1ff20…684e373
PhishDestroy analysis, reviewed version
The page on 2-allocations-flarenetwork.pages.dev mimics the Flare brand, displaying a top banner with the text "Earn yield, lend and stake" alongside a button marked "Launch XRPFi". The main section features the headline "$FLR Rewards Allocation Proposal" and the subtitle "Vote on how $FLR rewards will be distributed in the upcoming rewards distribution event." A prominent red button in the center invites users to "Vote Now". Below this section, partner logos including Elliptic, LayerZero, Hypernative, Ankr, Arkham, and HexTrust are displayed above a footer reading "BUILDING WITH THE BEST". The primary interaction point requires visitors to connect a crypto wallet via Reown components.
By prompting visitors to click "Vote Now" and connect their crypto wallets using external connection libraries like fonts.reown.com, the page sets up an environment to request token approvals or signature permissions. Because urlscan classified the page as malicious, and MetaMask and SEAL block it, the address is recognized as a malicious deployment rather than an authentic project portal. Visitors who connect their wallets risk granting malicious contracts access to drain funds or transfer tokens from their accounts.
The domain is hosted on the pages.dev platform and it was still reachable on 22 Nov 2026 at 06:25 UTC. While brand-themed subdomains on public hosting providers can appear convincing, they often lack official affiliation with the organizations they reference. Always verify token distributions and governance proposals through official channels before interacting with unfamiliar web apps.
Scan report
Open reportPage capture
SHA-256 83d501df…7fde1ae
Separate stored monitor snapshot; does not replace the primary report record or establish current availability.
10 / 100 · heuristic score · 3 brand references · 0 classifications
Content heuristic only; not the final score
Open reportThis dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.
Narrative generation metadata
Open reportThe narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Stored page, network and scanner observations, grouped by source and observation time.
| Mail configuration | Spf lookups: 0 |
|---|---|
| Protective DNS results | Resolvers: 12; Blocked count: 0 |
| Page title and metadata | Title: Flare: The blockchain for data; Ogtype: website; Robots: index, follow; Ogimage: https://flare.network/en/static/Flare-logo.png; Ogtitle: Flare: The blockchain for data; Ogsitename: Flare; Themecolor: #ffffff; Description: Flare is a full-stack layer 1 solution designed for data intensive use cases.; Twittercard: Summary large image; Twittersite: @FlareNetworks; Canonicalurl: https://flare.network; Ogdescription: Flare is a full-stack layer 1 solution designed for data intensive use cases.; Twittercreator: @FlareNetworks |
| Trackers | Requests: 1 |
| Forms and mixed content | Third party scripts: 0 |
| Status | Up: ✓; Code: 200; Timings: DNS: 0; Wait: 276; Download: 734; Response ms: 1099 |
| TLS connection | Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓ |
| Ports | Open: 80, 443, 8080 |
| Carbon | Bytes: 6458205; Co2 grams: 0.2362; Cleaner than: 1 |
| DNS server | NS: (IP: 173.245.59.85; Host: chris.ns.cloudflare.com), (IP: 108.162.194.215; Host: alexa.ns.cloudflare.com); Zone: 2-allocations-flarenetwork.pages.dev |
| Quality | Cls: 0.379; Seo: 83; Si s: 23.11; Fcp s: 23.11; Lcp s: 23.16; Tbt ms: 370; Performance: 28; Accessibility: 86; Best practices: 73 |
| Location | IP: 2606:4700:310c::ac42:2c68; ASN: 13335; Org: Cloudflare, Inc.; City: Montreal; Country: CA |
| SSL | San: *.2-allocations-flarenetwork.pages.dev, 2-allocations-flarenetwork.pages.dev; Bits: 256; Chain: 2-allocations-flarenetwork.pages.dev, YE2, Root YE, ISRG Root X2, ISRG Root X1; Issuer: Let's Encrypt / YE2; Serial: 061EA8B1682563A998D0DAA444AFE3156C9A; SHA256: b0dc556014c65d500893ee421c27e84505e2f553002d303974971e0d64129f41; Subject: 2-allocations-flarenetwork.pages.dev; Valid to: 2027-02-19T19:04:10Z; Valid from: 2026-11-21T19:04:11Z |
| DNS records | A: 172.66.47.152, 172.66.44.104; NS: chris.ns.cloudflare.com, alexa.ns.cloudflare.com; Soa: Nsname: alexa.ns.cloudflare.com; Hostmaster: dns.cloudflare.com; Serial: 2420777081; Refresh: 10000; Retry: 2400; Expire: 604800; Minttl: 1800; Aaaa: 2606:4700:310c::ac42:2f98, 2606:4700:310c::ac42:2c68 |
| Dnssec | Ds: ✗; Rrsig: ✗; Dnskey: ✗ |
| Hsts | Message: Site does not serve any HSTS headers. |
| HTTP security policies | Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: ✗; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗ |
| Firewall | Waf: Cloudflare; Has waf: ✓ |
| Get IP | IP: 2606:4700:310c::ac42:2c68; Family: 6 |
| Redirects | Chain: https://2-allocations-flarenetwork.pages.dev |
| Tech stack | Technologies: HSTS, lit-html 3.3.3, lit-element 4.2.2, Cloudflare, Open Graph, HTTP/3 |
| Social profiles | Profiles: https://x.com/FlareNetworks, https://github.com/flare-foundation |
| Page links | External: https://flare.network/resources/developer-hub, https://flare.network/events, https://flare.network/sign-up, https://twitter.com/FlareNetworks, https://t.me/FlareNetwork, https://flare.network/, https://flare.network/delegate-and-stake, https://flare.network/vote, https://portal.flare.network/, https://flare.network/whitepapers, https://flare.network/community, https://flare.network/careers, https://merch.flare.network/, https://flare.network/products/fassets, https://flare.network/products/flare-data-connector, https://flare.network/products/flare-time-series-oracle, https://flare.network/resources/technical-support, https://flarescan.com/, https://flare-systems-explorer.flare.network/, https://www.cookieyes.com/product/cookie-consent/, https://flare.network/wallets, https://flare.network/onofframps, https://flare.network/products/flare-smart-accounts, https://flare.network/resources/grants, https://dev.flare.network/network/getting-started; Internal: https://2-allocations-flarenetwork.pages.dev/; External count: 57; Internal count: 1 |
| HTTP headers | Headers: Server: cloudflare; Content type: text/html;charset=utf-8 |
It uses a look-alike subdomain on pages.dev to host a fake rewards allocation proposal, and urlscan classified the page as malicious, and MetaMask and SEAL block it.
Connecting your wallet to 2-allocations-flarenetwork.pages.dev may have allowed the site to request malicious token approvals or signature permissions. You should immediately disconnect your wallet and revoke any unfamiliar allowances using an explorer tool like Revoke.cash.
Authentic announcements and governance proposals regarding Flare are published through official channels and verified domain names associated with the project, rather than third-party subdomains like 2-allocations-flarenetwork.pages.dev.
Last checked
Edge-IP reputation is not attributed to this domain.
adi.ns.cloudflare.comkarl.ns.cloudflare.comnsname: alexa.ns.cloudflare.comhostmaster: dns.cloudflare.comserial: 2420777081refresh: 10000retry: 2400expire: 604800minttl: 1800Location describes the IP network.
b0dc556014c65d500893ee421c27e84505e2f553002d303974971e0d64129f41*.2-allocations-flarenetwork.pages.dev2-allocations-flarenetwork.pages.devSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of 2-allocations-flarenetwork.pages.dev ·
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Network requests: 82 SHA-256 hashes: 51 URLScan scan:
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-22 05:26 UTC.
Open this scan on URLScan 01a201b6-2d95-71e5-84f1-929163014515 ↗
Loads saved data; the suspicious site is not opened.
| # | Network request | HTTP method · status | Type | Uncompressed size | Response body SHA-256 |
|---|
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Reachable
Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.
Recorded events: 8. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Lifecycle
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.
Download all records as JSON| ID | Stored data |
|---|
52 stored lookalike domains
Names that imitate the brand, found by dnstwist. A similar name alone does not prove the same owner.
A similar name alone does not prove fraud. Send the list to services that check each address themselves. Report a domain as phishing only if you saw a fake page on it.
Where to send it:
Nothing matches. Clear the search or choose another filter.
Showing 12 of 52
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
2-allocations-flarenetwork.pages.dev Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
The draft stays only with you.
First secure your money: call your bank or revoke wallet approvals. Immediate steps →
Emergency help from security researchers when a crypto wallet is being drained right now.
Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.
Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.
Forward scam emails and text messages to the National Cyber Security Centre, which takes down the malicious sites it finds.
Emailreport@phishing.gov.uk Text messages7726Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.
Forward phishing emails to the Anti-Phishing Working Group.
Emailreportphishing@apwg.orgNational Cyber Crime Reporting Portal. For financial fraud, also call the 1930 helpline straight away.
Helpline1930Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
2-allocations-flarenetwork.pages.dev)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.