Is nearnear-bdb.pages.dev a scam? TrustSniffer's high-risk assessment: 0/100

Security Alert

Fortinet, Google, Sophos flagged this site in external intelligence checks, indicating elevated compromise/scam exposure that requires immediate caution.

This website is a project-style subdomain on a free, shared web-hosting platform. When analysed, its homepage did not present ordinary site content. The request was answered with a security interstitial titled as a suspected-phishing warning, and the only readable text was a short notice of that kind. No products, branding, operator name or business model could be established from the page. The apparent purpose therefore cannot be stated, and the available evidence points to a deceptive or credential-harvesting deployment rather than a legitimate service.

Scam/Impersonation Risk

Contradictory signals are present and are decisive. The site is blacklisted: a major browser-protection service flags it under its social-engineering category, which covers deceptive and credential-harvesting pages. A large group of independent security vendors also classify it as malicious, and a smaller number mark it as suspicious. Several of the most widely deployed commercial security vendors are among those detections, which places this well beyond an isolated false positive. The corroborating browser-protection match and the high volume of malicious verdicts independently trigger the strongest category of external-intelligence alert. A hosting-level challenge page, which carries its own phishing warning, also replaced the homepage. No conflicting legal-entity names were observed, and no specific brand impersonation was documented. The risk therefore rests on reputation and behavior rather than on a named lookalike target. The behavioral profile reinforces caution without adding independent proof of malice. The page is dominated by outbound traffic to third-party endpoints, rewrites its own DOM heavily after interaction, and logs repeated script errors. The sandbox did not observe wallet-connection prompts, clipboard tampering, hidden forms or credential posts to external hosts. Because the real page content was withheld, those clean behavioral checks carry limited weight against the external detections. Evidence:

• Homepage: the capture returned an access-denied challenge response (HTTP 403) whose page title identifies a suspected-phishing warning.
• External reputation: 11 security vendors rated the domain malicious and 1 suspicious. A browser-protection service listed it under the social-engineering threat type.
• Homepage behavior across 3 sandbox runs: 88 external XHR/fetch calls, 4 external POST requests, up to 96.9% of requests going to third-party hosts, 1,508 DOM mutations after interaction and 11 console errors.
• Homepage behavior: no wallet-connect, clipboard-write, hidden-form or external password-form activity was recorded.

Regulatory Verification Notes

The site presents no readable legal, terms, privacy or about content and discloses no licence, registration number or corporate entity. Because the only content captured was a security interstitial, this is not a disclosure failure by a documented operator. It does mean there is nothing on the page that could support a claim of regulatory standing. The site is not associated with any third-party regulated status and has no matching broker-reputation record. These are the only grounds for a regulatory assessment, and they do not ground any positive finding. A valid transport-encryption certificate is present. It is a basic domain-validated certificate, which proves only that the connection is encrypted and says nothing about who runs the site. Encryption is routinely obtained by phishing pages and does not offset the reputation findings. Evidence:

• Homepage and all captured pages: no legal-entity name, licence number, registry reference or contact details were visible in the captured content.
• Transport security: TLS certificate issued by WE1 (DV, domain validation only), valid to 2027-01-04.
• Hosting: served from AS13335 (Cloudflare, Inc., US) on the pages.dev shared-hosting domain.

What to Verify Next

Verification here concerns how the visitor reached the site and whether any legitimate service is behind it. It is not an assessment of whether the site is safe to use. The first step is to establish where the link came from. If it arrived by message, email, social post or advertisement, the sender's identity should be confirmed through a separate channel. Any organisation claimed to be behind the site should then be checked independently by finding its official website through a search engine or a regulator's registry. The pages.dev address should not be treated as that organisation's official presence. If the site promotes financial, investment or crypto-asset services, the claimed provider should be checked against the relevant national financial-regulator register. The official support or contact channels should be confirmed through an offline or independently sourced route. Evidence:

• Homepage: no operator, brand or product claim was readable that could be matched against an external registry.
• Domain structure: the address is a free project subdomain on a shared platform, so the domain name carries no organisational identity.
• Security-vendor listings: the detections apply to this specific subdomain, so any legitimate counterpart would be hosted elsewhere under a different address.

Summary Verdict

The overall posture is high-risk and cautionary. Widespread, converging external threat detections, including a browser-level deception warning, override every neutral or positive technical signal. The site should be treated as a probable phishing or social-engineering deployment. The evidence does not support any claim to legitimacy, and operator identity is entirely unestablished.

Infrastructure Integrity

The site sits behind Cloudflare's CDN and WAF, with bot-protection challenges active and all observed addresses belonging to edge servers. The origin server was not observable, so the underlying host cannot be independently verified. This setup is a mitigating factor only. Shared edge delivery, a recognised certificate issuer and an identified network owner describe the platform, not the operator. They cannot offset the external threat findings, and they also let page content be swapped without any visible change in the address.

Closing Assessment

The site should not be used for login, credential entry, payments or any financial interaction, and wallets should not be connected to it. Files and software offered by the site should not be downloaded or installed. If credentials or payment details were already entered, passwords should be changed immediately, the relevant financial institution notified, and the link reported to the platform or channel that distributed it.