Skip to security report
2-allocations-flarenetwork.pages.dev favicon
Domain security and threat intelligence

2-allocations-flarenetwork.pages.dev

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

This 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”

More about the sources
Recorded security signals

Listed by external blocklists: MetaMask, SEAL. Use caution — do not enter credentials or personal information.

Stored blocklist matches: 2
Registrar
United StatesCloudflare
Resolved IP
Canada172.66.47.152Cloudflare, Inc. · CDN
First seen by PhishDestroy
2026-11-22
Page captures
open gallery
2026-11-22 CDN

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

Analysis

Domain summary

PhishDestroy first recorded 2-allocations-flarenetwork.pages.dev on 2026-11-22. Listed by external blocklists: MetaMask, SEAL. Risk: high (evidence score 66/100). Registrar: Cloudflare. Status: Last known active. Hosting: Cloudflare, Inc. Do not enter credentials or connect a wallet.

High
Status
Last known active
Blocklist matches
2 external + PhishDestroy list
Hosting
Canada172.66.47.152Cloudflare, Inc. · CDN
Registrar
United StatesCloudflare
Page captures
4

URLScan capture · 2026-11-22 05:27 UTC · SHA-256 4ba1ff20…684e373

PhishDestroy analysis, reviewed version

Flare rewards allocation proposal page layout and design

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.

Wallet connection risks and security telemetry

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.

Infrastructure and network observations

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.

Source evidence 4 sources

PhishDestroy DOM

10 / 100 · heuristic score · 3 brand references · 0 classifications

Content heuristic only; not the final score

Open report
Page code check by a separate monitor · 10 / 100 · 2026-11-22 07:20 UTC

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

Heuristic score
10
Analyzed at
2026-11-22T07:20:11Z
Source timestamp
2026-11-22 08:20:11
Technical metadata

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

AI title
2-allocations-flarenetwork.pages.dev — Flare rewards voting
AI description
2-allocations-flarenetwork.pages.dev presents a Flare rewards allocation proposal page asking visitors to connect wallets, flagged by urlscan.
AI summary
Flare rewards allocation proposal page layout and design 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. Wallet connection risks and security telemetry 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. Infrastructure and network observations 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.
AI generated by
threat-v10-gemini
AI generated at
2026-11-22T06:28:36Z
Revision
f3ed0444ef484cbdb9145d989d7ae67f82953ac43108b7b58522463ec6bb2298
Mode
reviewed
Interpretation
Selected public package; text generation time is separate from source observation dates.

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
VirusTotalOriginal source recordObserved: 12 fields
Open complete records
Website checksOriginal source recordRetrieved: 24 fields

Mail configuration

SPF lookups
0

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Page title and metadata

Page title
Flare: The blockchain for data
Open Graph type
website
Indexing directives
index, follow
Open Graph image
https://flare.network/en/static/Flare-logo.png
Open Graph title
Flare: The blockchain for data
Open Graph site name
Flare
Theme color
#ffffff
Description
Flare is a full-stack layer 1 solution designed for data intensive use cases.
Twitter card
summary_large_image
Twitter account
@FlareNetworks
Canonical URL
https://flare.network
Open Graph description
Flare is a full-stack layer 1 solution designed for data intensive use cases.
Twitter Creator
@FlareNetworks

Trackers

Requests
1

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
0
Waiting
276
Download
734
Response time, ms
1099

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443
  • 8080

Carbon estimate

Bytes
6458205
CO₂, grams
0.2362
Cleaner than, %
1

DNS servers

Nameservers
  • IP address
    173.245.59.85
    Host
    chris.ns.cloudflare.com
  • IP address
    108.162.194.215
    Host
    alexa.ns.cloudflare.com
DNS zone
2-allocations-flarenetwork.pages.dev

Page quality

Layout shift (CLS)
0.379
SEO score
83
Speed Index, s
23.11
First Contentful Paint (FCP), s
23.11
Largest Contentful Paint (LCP), s
23.16
Total Blocking Time (TBT), ms
370
Performance score
28
Accessibility score
86
Best practices score
73

Location

IP address
2606:4700:310c::ac42:2c68
ASN
13335
Organization
Cloudflare, Inc.
City
Montreal
Country
CA

TLS certificate

Subject alternative names
  • *.2-allocations-flarenetwork.pages.dev
  • 2-allocations-flarenetwork.pages.dev
Key size, bits
256
Certificate chain
  • 2-allocations-flarenetwork.pages.dev
  • YE2
  • Root YE
  • ISRG Root X2
  • ISRG Root X1
Issuer
Let's Encrypt / YE2
Serial
061EA8B1682563A998D0DAA444AFE3156C9A
SHA-256
b0dc556014c65d500893ee421c27e84505e2f553002d303974971e0d64129f41
Subject
2-allocations-flarenetwork.pages.dev
Valid until
Valid from

DNS records

A
  • 172.66.47.152
  • 172.66.44.104
NS
  • chris.ns.cloudflare.com
  • alexa.ns.cloudflare.com
SOA
Primary nameserver
alexa.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2420777081
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
AAAA
  • 2606:4700:310c::ac42:2f98
  • 2606:4700:310c::ac42:2c68

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2606:4700:310c::ac42:2c68
IP version
6

Redirects

Redirect chain
  • https://2-allocations-flarenetwork.pages.dev

Technology 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 link addresses
  • 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 link addresses
  • https://2-allocations-flarenetwork.pages.dev/
External links
57
Internal links
1

HTTP headers

Response headers
Server
cloudflare
Content-Type
text/html;charset=utf-8
Original source fields · JSON
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

Questions about 2-allocations-flarenetwork.pages.dev

Is 2-allocations-flarenetwork.pages.dev legit?

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.

What happens if I connected my wallet?

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.

Where is the real Flare rewards information published?

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.

Explore

Blocklist matches2 external + PhishDestroy list · MetaMask · PhishDestroy · SEAL 2
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Page captures (4)

All capture links and hashes (4)

Domain details

Domain
IP Context Canada172.66.47.152 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider Cloudflare US(US)
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First Detected2026-11-22
DOM Analysisanalyzed 2026-11-22score 10/1003 brand signals
Submitted URLhttp://2-allocations-flarenetwork.pages.dev/
Favicon Hash
Observed page title
Flare: The blockchain for data
Automated brand references
Across Ethereum Google
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 89 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Canada172.66.47.152
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
CanadaToronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • adi.ns.cloudflare.com
  • karl.ns.cloudflare.com

SOA

  • nsname: alexa.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2420777081
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 1800

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-11-21 19:04:11
Valid until
2027-02-19 19:04:10
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintb0dc556014c65d500893ee421c27e84505e2f553002d303974971e0d64129f41
Certificate names · 2 SANs
  • *.2-allocations-flarenetwork.pages.dev
  • 2-allocations-flarenetwork.pages.dev

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Technologies · 3 identified
Open complete records
PageSpeed (mobile): 44

Google PageSpeed Insights — mobile performance audit of 2-allocations-flarenetwork.pages.dev ·

44
Poor
Performance
FCP
22.14 s
First Contentful Paint
LCP
22.19 s
Largest Contentful Paint
CLS
0.08
Cumulative Layout Shift
TBT
397 ms
Total Blocking Time
SI
22.14 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details1

Availability observations

Last reachable observation

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

All stored data93
Open complete records

Captured network requests

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 ↗

Stored observation history1

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Domain monitor · First collection record

    Reachable

All retained availability observations2

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.

  1. Current state backfill
    Observation source
    Current state backfill
    Cause
    Probe inconclusive
    Availability state
    unreachable
    DNS state
    stale
    Monitor confidence
    20
    Provider action verified
    ✗
    Registrar mechanism verified
    ✗
    Linked to a report
    ✗
    Original source timestamp
    2026-11-22 06:25:11.000000
    Evidence SHA-256
    eb1d4bc44c18a2028a71976a8b1647a9595e494c437a4c1abe7dd6bc6795fc8d
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-22 06:25:11
  2. Http observation
    Observation source
    Http observation
    Cause
    Probe inconclusive
    Availability state
    unreachable
    Monitor confidence
    20
    Provider action verified
    ✗
    Registrar mechanism verified
    ✗
    Linked to a report
    ✗
    Original source timestamp
    2026-11-22 06:25:11.000000
    Evidence SHA-256
    eb1d4bc44c18a2028a71976a8b1647a9595e494c437a4c1abe7dd6bc6795fc8d
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-22 06:25:11

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · in progress

Recorded events: 8. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested recorded
  • Threat Ingested
    2-allocations-flarenetwork.pages.dev detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Blocklist Detection · Forensic Evidence Collected · Technical Analysis Recorded recorded
Publication & AvailabilityDestroyList Published · Monitoring Continues ongoing
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.
    ongoing

Recorded activity

2 entries

Lifecycle

  1. Domain registered
  2. Added to PhishDestroy+2272 d 2 h
  1. Added to PhishDestroy

    2-allocations-flarenetwork.pages.dev

    same minute
  2. URLScan

    Page captured

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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

All stored records by source

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

Lookalike domains

52 stored lookalike domains

Names that imitate the brand, found by dnstwist. A similar name alone does not prove the same owner.

ethercum.org Lookalike letters Variant of ethereum.org Internal report A 188.114.96.3NS bart.ns.cloudflare.com etheruem.org Swapped characters Variant of ethereum.org Internal report A 212.99.218.66NS ns-1511.awsdns-60.org athereum.org Bit flip Variant of ethereum.org A 199.188.200.6MX mail.athereum.orgNS dns1.namecheaphosting.com dethereum.org Inserted character Variant of ethereum.org A 216.198.79.1NS liv.ns.cloudflare.com e.thereum.org Split into subdomain Variant of ethereum.org A 103.224.212.210MX park-mx.above.comNS ns15.abovedomains.com efhereum.org Replaced character Variant of ethereum.org A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com ehereum.org Missing character Variant of ethereum.org A 15.197.225.128NS ns65.domaincontrol.com etereum.org Missing character Variant of ethereum.org A !ServFailNS !ServFail eth3reum.org Replaced character Variant of ethereum.org A 15.197.142.173NS ns31.domaincontrol.com ether.eum.org Split into subdomain Variant of ethereum.org A 13.248.169.48NS ns1.afternic.com etheream.org Vowel swap Variant of ethereum.org A 162.255.119.154MX eforward1.registrar-servers.comNS dns1.registrar-servers.com ethereim.org Replaced character Variant of ethereum.org A 15.197.142.173NS ns33.domaincontrol.com

Showing 12 of 52

Show 40 more
ethereium.org Inserted character Variant of ethereum.org A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com etherem.org Missing character Variant of ethereum.org A 15.197.225.128NS ns39.domaincontrol.com etheremu.org Swapped characters Variant of ethereum.org A 13.248.169.48NS ns1.afternic.com ethereom.org Vowel swap Variant of ethereum.org A 192.0.78.24NS ns1.wordpress.com etheresum.org Inserted character Variant of ethereum.org A 104.21.87.66NS aron.ns.cloudflare.com ethereujm.org Inserted character Variant of ethereum.org A 104.21.46.240NS jerry.ns.cloudflare.com ethereum2.org Added character Variant of ethereum.org A 24.199.74.33NS ns3.namefi.io ethereum3.org Added character Variant of ethereum.org NS a.share-dns.com ethereum4.org Added character Variant of ethereum.org A 198.54.117.242NS failed-whois-verification.namecheap.com ethereumc.org Added character Variant of ethereum.org A 188.114.96.3NS camilo.ns.cloudflare.com ethereumd.org Added character Variant of ethereum.org A 188.114.96.3NS earl.ns.cloudflare.com ethereumorg.com Variant Variant of ethereum.org NS ns1.openprovider.nl ethereumr.org Added character Variant of ethereum.org A 188.114.96.3NS monroe.ns.cloudflare.com ethereums.org Added character Variant of ethereum.org A 15.197.148.33MX mailstore1.secureserver.netNS ns73.domaincontrol.com ethereumx.org Added character Variant of ethereum.org A 64.190.63.222MX localhostNS ns1.sedoparking.com ethereun.org Lookalike letters Variant of ethereum.org A 52.20.84.62NS ns1.squadhelp.com ethereunm.org Lookalike letters Variant of ethereum.org A 104.21.86.145NS koa.ns.cloudflare.com ethereurm.org Lookalike letters Variant of ethereum.org A 188.114.96.3NS rita.ns.cloudflare.com ethereurn.org Lookalike letters Variant of ethereum.org MX eforward1.registrar-servers.comNS dns1.registrar-servers.com ethereuym.org Inserted character Variant of ethereum.org A 104.21.22.142NS everton.ns.cloudflare.com ethereuzm.org Inserted character Variant of ethereum.org A 188.114.96.3NS dale.ns.cloudflare.com ethereyum.org Inserted character Variant of ethereum.org A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com etherium.org Vowel swap Variant of ethereum.org A 32.216.8.188NS ns1.no-ip.com etherrum.org Replaced character Variant of ethereum.org MX eforward1.registrar-servers.comNS dns1.registrar-servers.com etherteum.org Inserted character Variant of ethereum.org A 13.248.243.5NS ns41.domaincontrol.com etherum.org Missing character Variant of ethereum.org A 103.224.212.201MX park-mx.above.comNS ns1.abovedomains.com ethezeum.org Bit flip Variant of ethereum.org A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com ethireum.org Vowel swap Variant of ethereum.org A 192.64.119.29MX eforward1.registrar-servers.comNS dns1.registrar-servers.com ethnereum.org Inserted character Variant of ethereum.org A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com ethreum.org Missing character Variant of ethereum.org A 15.197.225.128NS ns65.domaincontrol.com ethureum.org Bit flip Variant of ethereum.org A 162.255.119.109MX eforward1.registrar-servers.comNS dns1.registrar-servers.com etihereum.org Lookalike letters Variant of ethereum.org A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com ithereum.org Vowel swap Variant of ethereum.org A 188.114.96.3NS celine.ns.cloudflare.com othereum.org Vowel swap Variant of ethereum.org NS ns-cloud-a1.googledomains.com rethereum.org Inserted character Variant of ethereum.org A 54.36.108.60MX eforward1.registrar-servers.comNS dns1.registrar-servers.com sethereum.org Inserted character Variant of ethereum.org A !ServFailNS !ServFail thereum.org Missing character Variant of ethereum.org A 103.224.212.210MX park-mx.above.comNS ns15.abovedomains.com uthereum.org Bit flip Variant of ethereum.org A 15.197.148.33NS ns15.domaincontrol.com zethereum.org Inserted character Variant of ethereum.org NS ns-1335.awsdns-38.org zthereum.org Replaced character Variant of ethereum.org NS ns-1294.awsdns-33.org

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

2-allocations-flarenetwork.pages.dev

Evidence & External Reports

Deep Analysis

Were You Affected by This Site?

You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.

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.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
  • Downloaded a file — do not open it and scan the device with security software
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
  • Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed

What information should I collect for my report?

FBI guidelines

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.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including 2-allocations-flarenetwork.pages.dev)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

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 →
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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/2-allocations-flarenetwork.pages.dev"
  title="PhishDestroy threat report for 2-allocations-flarenetwork.pages.dev"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>