Is bluwhale-169.pages.dev a scam? 5/100

bluwhale-169.pages.dev

Is it safe to use? An external threat listing named this site as malicious when the evidence was captured. Do not pay or share personal details with this site.

Download PDF Check another site How we score
Ask your AI about this report

Pick your AI assistant. It opens in a new tab with a question about this report already written, and you can ask it anything from there.

Only this public report is shared. Your AI app's own privacy terms apply, and its answers are its own: the report is TrustSniffer's assessment. Connect TrustSniffer to your AI to check sites from the chat.

Verdict

An external threat listing named this site as malicious when the evidence was captured. Do not pay or share personal details with this site.

5 OUT OF 100
Critical Risk

bluwhale-169.pages.dev shows critical-risk indicators.

Sensitive Interaction Risk Governance Risk
  • Sensitive Interaction Risk: This label is given when the overall risk is high. The captured page did not ask for a password, card number or other sensitive details; if it ever does, entering them here could be unsafe.
  • Governance Risk: The governance checks raised a concern: a threat-intelligence listing limits the score; as a site on pages.dev, this address has no registration record of its own (the platform's domain is registered, not the site). The findings below give the detail.

Evidence captured 2026-11-10, re-scored 2026-11-15 by automated analysis. Evidence confidence 70%.

How the site describes itselfBluwhale landing page promoting a BLUAI token rewards update, under which voters receive an early BLUAI allocation from the Treasury Pool Funds. Navigation lists products, nodes, whitelist, docs, whitepaper and blog. No legal, contact, or risk disclosures are visible in the captured text.

Evidence status and limitations

Evidence completeness: CompleteThis says whether every check on the site was recorded as finished. All of them were.

  • The evidence was captured on 2026-11-10 and re-scored on 2026-11-15. The certificate, the registration age and the page content describe the site as it was on 2026-11-10.
  • Two sources reported this site when the evidence was captured: a threat-intelligence listing from a feed TrustSniffer monitors (phishing, the site itself as the source, last seen 2026-10-25), and 1 VirusTotal engine that marked it as malicious. A single VirusTotal engine is below TrustSniffer's bar for a confirming source, so no second source confirms the listing. The alert is from the evidence captured on 2026-11-10; it was not re-queried for this version and is treated as unconfirmed. On its own the alert would limit the score to at most 49; the threat-listing ceiling holds it at 5, because the listing names the site itself as the source.
  • The real-world operator identity was not independently verified.

How to read these numbers

The trust score runs from 0 to 100, higher is safer. 5/100 rates the evidence found, not the probability that the site is a scam.

Evidence confidence (70%) measures how much of TrustSniffer's evidence set this site produced: the page reading, the browser sandbox, the web archive, the registration record and the reputation services. It falls when a check returns nothing, as listed above, and it does not change the score.

At a glance

The checks that decide most of this verdict.

What limits the scoreThreat-listing ceilingA threat-intelligence feed TrustSniffer monitors listed this site itself as the source of a threat when the evidence was captured (last seen 2026-10-25), and that listing caps the score. The unconfirmed alert ceiling (at most 49) also applies, but the score is below it.Risk
Malware engines1 marked it malicious, 2 suspiciousVirusTotal; a single engine, not a confirmed listingWatch
Google Safe BrowsingNot listedGoogleClear
Abuse reports on the CDN edge address0% confidenceAbuseIPDB, 0 reports; this is the record of the CDN edge address, not of the server behind it, which was not observedNoted
First seen5 months before captureWeb archive; a site on pages.dev has no registration of its ownRisk
Web archiveArchived since 20261 snapshot; the archive has almost no record of this site, which counted against itWatch
CertificateEncrypted connectionIssued by WE1Noted

The page as captured

https://bluwhale-169.pages.dev/
Screenshot of the bluwhale-169.pages.dev homepage captured during the TrustSniffer assessment
What bluwhale-169.pages.dev served when TrustSniffer captured it on 2026-11-10. The page may look different now.

Key findings

  • Automated classification: Sensitive Interaction Risk, Governance Risk.
  • First seen: less than 1 year before capture (web archive; a site on pages.dev has no registration of its own).
  • Public web-archive history exists since 2026.
  • At least one reputation service TrustSniffer consulted had flagged this domain when the evidence was captured.

Full analysis

Overview

Bluwhale presents a single-page landing site for a token project called BLUAI, hosted on a numbered subdomain of a free web-hosting platform. Its only visible message is a "BLUAI Rewards Update" announcing that voters "will receive an early allocation in BLUAI from the TPF (Treasury Pool Funds)", with a "Vote Now" call to action. The navigation lists products, nodes, a whitelist, docs, a whitepaper and a blog, plus regional tabs for Global, CIS and Turkey. The apparent purpose is to attract participation in a token-reward campaign. The page itself describes no deposits, fixed returns or fee model.

Scam/Impersonation Risk

TrustSniffer assesses this site as a critical risk. A threat-intelligence listing classes the site as the actor in a phishing operation, with the listing last seen on 25 October 2026. The listing is the only source that supports this classification, and the score is held down by the threat-listing ceiling. One security engine in a multi-engine scan also marked the address malicious and two marked it suspicious, but none of them is a top-tier vendor and Google Safe Browsing did not list it. Those engine results are treated as a single supporting source, not an independent confirmation. A comparison of related sites found two other addresses on the same hosting platform that were flagged, which fits the pattern of throwaway campaign pages on free hosting. No conflicting legal identities and no brand impersonation were observed. The "Vote Now" prompt promises a token allocation, and that is the kind of incentive phishing lures typically use. The page names no contract address, team or operator that could be checked against that promise. Sensitive actions tied to the reward campaign should be treated as unsafe.

Evidence
  • Threat-intelligence listing (phishing, site as actor), last seen 25 October 2026, observed at capture on 10 November 2026.
  • VirusTotal: 1 engine malicious and 2 suspicious. No top-tier vendor flagged the site, and Google Safe Browsing did not list it.
  • Homepage: the quoted reward claim and the "Vote Now" prompt are the only substantive content, in a text fragment of roughly 186 characters.
  • Domain history: first seen in the web archive on 2026-06-03, 160 days before capture, with a single archive snapshot (span 0 days). The address is a subdomain of a free hosting platform, so the site has no registration of its own.

Regulatory Verification Notes

On the single page read, the homepage, none of the disclosures expected from a token project were present: no contract address, no named team, and no terms or privacy page. The page also lists no legal entity and no contact channel, so the Bluwhale name it uses cannot be tied to any verified operator. No licence is claimed, and no third-party regulatory or broker record matched the site. The two page-level warnings recorded concern the unverifiable legal status and the unverifiable contact or address. Behaviour measurements show the page sent 108 requests to other hosts. None went to destinations TrustSniffer does not recognise, though this behaviour counts as a scored finding. The page showed no login, password or payment form.

Evidence
  • Homepage: contract address, team and terms/privacy disclosures were not found on the pages read.
  • Homepage: no company name, registration number, licence or contact channel was visible in the captured text.
  • Site transport: the TLS certificate was issued by WE1 (DV, domain validation only) and was valid to 2027-01-08 at capture. This validates the connection, not the operator.
  • Hosting: served from AS13335 (Cloudflare, Inc., US), with 0 abuse reports on the host address when checked.

What to Verify Next

Any independent confirmation of the BLUAI project has to come from outside this page. That means locating the token's contract address and team through an official channel established independently of this site. It also means confirming that the project's official domain is not this free-platform address. No claim of an early allocation should be treated as real until that confirmation exists. The "Vote Now" prompt should be checked only by looking at where it leads, without acting on it.

Evidence
  • Homepage: the early-allocation claim names the Treasury Pool Funds, with no amount, schedule or eligibility rule stated.
  • Homepage: the whitepaper and docs links are named in the navigation, but no content from them was available to check the claim against.
  • Hosting: the numbered subdomain on a free platform is a pattern shared by the two flagged sibling addresses.

Summary Verdict

The site is rated critical risk. The page carries almost no verifiable substance, and a phishing listing attaches to the address. Technical hygiene such as a valid certificate does not outweigh the listing or the absence of any verifiable operator.

Infrastructure Integrity

The site is served through Cloudflare's network, and all four observed addresses are edge addresses of that provider. Origin hosting could not be observed. This is a neutral technical fact, not a mitigating factor, and it says nothing about the operator's legitimacy or the safety of the content.

Closing Assessment

This address should not be used for anything beyond reading. Prospective participants should not follow the voting prompt, claim any token allocation, or send funds or tokens in connection with it. If the project matters to them, they should reach it only through an official source confirmed independently of this page.

Written analysis generated 2026-11-15 by the TrustSniffer Analysis Engine from the evidence in this report.

What the analysis found

8 findings contributed to this verdict, raised by governance, history in the web archive, page content, hosting and network, registration and ownership and behaviour in a sandbox.

01 Governance

  • A threat-intelligence feed TrustSniffer monitors listed this site itself as the source of a threat when the evidence was captured (last seen 2026-10-25), and that listing caps the score.Governance rule:gov_active_threat_listing

02 History in the web archive

  • The web archive has almost no record of this domain, which fits a site that is new.History in the web archive rule:ARCH_PEN_YOUNG_AND_SPARSE

03 Page content

  • The page has very little readable content.Page content rule:PAGE_CONTENT_THIN
  • The page runs on a free hosting-platform address instead of a domain of its own, a setup common to short-lived phishing and claim pages.Page content rule:PAGE_FREE_PLATFORM_ADDRESS
  • The page content shows at least one warning sign that deceptive sites commonly use.Page content rule:PAGE_RED_FLAGS_SOME

04 Hosting and network

  • The domain was registered, or a site on a hosting platform was first seen, three to six months before capture.Hosting and network rule:DNS_YOUNG_6M

05 Registration and ownership

  • As a site on pages.dev, this address has no registration record of its own (the platform's domain is registered, not the site).Registration and ownership rule:KF_WHOIS_INCOMPLETE

06 Behaviour in a sandbox

  • The page made many background requests to other domains while it was open.Behaviour in a sandbox rule:BEHAV_EXTERNAL_XHR_HEAVY

Identity verification

StatusUNVERIFIED

The operator behind the site could not be connected to a real-world brand or person. What the page shows, if anything, is listed below; none of it was independently checked.

  • org:Bluwhale
  • on_site_identity

What TrustSniffer observed

First-party facts recorded during the assessment of bluwhale-169.pages.dev.

  • The request stayed on bluwhale-169.pages.dev. It was not redirected to another domain. Clear
  • The earliest public archive of this site is from 2026-06-03. Watch
  • It is hosted on CLOUDFLARENET, a network registered in US. Noted

Code shared with other sites rated Critical

TrustSniffer found that this site serves the same distinctive code files as 21 other sites it has analysed. All 21 are rated Critical on their own evidence.

Shared code shows that these sites were built from the same toolkit. It does not by itself show who operates them.

Shared files (SHA-256)fpbundle.js 126a8b465ef8734b4d7a289781e0535cd283ccf24394e08c44f23ae300be3a5a (22 sites)
modals.js 6d0c2c8d032982e9a86a1bed14f709911058b6b693abb5d46335a0106c12c411 (22 sites)
bundle.js 969be4f64afdeaca0568779c3b0f7291bc9a7185cc983a5104fbd90e4f901039 (22 sites)
main.js ef6c818437d7e45baf8db39611a38ee242ada87a72694cbad2b17f8ba0564c29 (4 sites)
main.js 76bf37e542786be710a860b96491637721add382d483f954a1a47a3937ffb494 (3 sites)
styles.css 5170301acec4e30a994bdbb46e99ab410f0e3203e629b4ec775a2c05000a65c0
main.js a835bce751f034f8e6500642f4fa8469c97214e1f4375a7bb5b415c0447f20e6
main.js c52b6118f3b9965cc4ed552dc21b0882fd7eeb1f8bfd709a93e42f18fc633539

Two sites are linked only by two or more shared distinctive files or one shared identifier: an endpoint written into the page's code (a Cloudflare Worker or a Telegram bot), a wallet address shown on the page (checksum-validated), a contact or an analytics ID. Common libraries, platform files, images, well-known contracts, a brand's own accounts and anything also used by a site rated Moderate or High are excluded. Contact details (Telegram, WhatsApp, phone, email) are withheld. A shared file can be checked by its SHA-256 hash.

Domain intelligence

RegistrarNot available
HostingCLOUDFLARENET - Cloudflare, Inc.
Network registered inUS
Server IP2606:4700:310c::ac42:2f63 (a CDN edge address; the server behind it was not observed)
Name serversNot available
CDN / edge networkDetected (cloudflare)
Resolved IP addresses4
Edge IP addresses4
Likely origin IP addresses0
SSL issuerWE1
SSL expiry2027-01-08
First seen (web archive)160 days before capture; a site on pages.dev has no registration of its own
Domain expiryNot available
Archive first seen2026-06-03 (160 days before capture)
Archive snapshots1
ReputationVirusTotal: 1 malicious, 2 suspicious | AbuseIPDB (CDN edge address, not the host): 0% confidence, 0 reports | Google Safe Browsing: 0 matches

About this assessment

A trust score summarises the evidence TrustSniffer could collect about bluwhale-169.pages.dev at a point in time: domain registration and age, hosting and certificate, the content the site served, and third-party reputation feeds. A high score means the signals were consistent with a legitimately operated site; a low or critical score means several risk patterns were present. It is a starting point for your own judgement, not a guarantee and not a legal finding. There is no human rating and no user review in it. A site can change after it is assessed.

Already paid or signed in? Do this now

Act fast. The sooner your bank knows, the better the chance of stopping the payment.

  1. Call your bank or card company now. Use the number on the back of your card. Ask them to stop or reverse the payment.
  2. Paid with crypto? Contact the exchange or wallet app you sent it from today. Give them the address you paid.
  3. Signed in or shared a password? Change it now, on every site where you use it, and turn on two-step sign-in.
  4. Report it to the police. In the US you can also report at reportfraud.ftc.gov and ic3.gov. In other countries, use your national police or fraud reporting service.
  5. Keep the evidence. Save screenshots, receipts, emails and chat messages. Your bank and the police will ask for them.
  6. Ignore anyone who offers to get your money back for a fee. These "recovery" offers are often a second scam.

Looking for the real site? Type the company name into a search engine yourself, or use the web address printed on your card, bill or letter. Do not use links from messages or ads.

Common questions about bluwhale-169.pages.dev

Is bluwhale-169.pages.dev a scam?

TrustSniffer's assessment of bluwhale-169.pages.dev found strong scam indicators. It scored 5 out of 100 on 2026-11-15, which is the critical-risk band. The specific signals are listed in the evidence above.

Is bluwhale-169.pages.dev safe to use?

An external threat listing named this site as malicious when the evidence was captured. Do not pay or share personal details with this site.

What is the trust score of bluwhale-169.pages.dev?

bluwhale-169.pages.dev scored 5 out of 100 on 2026-11-15, which places it in the critical-risk band. The score is built from the domain's age and registration history, its hosting and certificate, the content of the site itself, and third-party reputation data. There is no human rating and no user review in it.

Download this report as PDF Free, no account needed. Create one to keep a history of the sites you check.
Questions about this report? Ask your AI

Pick your AI assistant. It opens in a new tab with a question about this report already written, and you can ask it anything from there.

Only this public report is shared. Your AI app's own privacy terms apply, and its answers are its own: the report is TrustSniffer's assessment. Connect TrustSniffer to your AI to check sites from the chat.

By AminRez, Founder & Lead Security Researcher, TrustSniffer
Produced by the TrustSniffer Analysis Engine · assessed 2026-11-15 · how we assess · report a mistake