Is Pages a scam? TrustSniffer's high-risk assessment of nearar.pages.dev: 0/100

nearar.pages.dev
Download PDF Check another site How we score

Verdict

This assessment found strong scam indicators. Do not pay, sign in, or share personal details with this site.

0 OUT OF 100
Critical Risk

nearar.pages.dev shows high-risk / scam indicators.

Sensitive Interaction Risk Governance Risk

Assessed 2026-10-29 by automated analysis. Classification confidence 55%.

Evidence status and limitations

Evidence completeness: Not recorded

  • The real-world operator identity was not independently verified.
  • Module-level completeness metadata is unavailable for this legacy report.

At a glance

The checks that decide most of this verdict.

Malware engines10 flagged itVirusTotalRisk
Google Safe BrowsingListed as unsafeGoogleRisk
Abuse reports on the host0% confidenceAbuseIPDB, 0 reports; shared hosting inflates reportsClear
Domain ageNot availableNo registration record was returnedNoted
Web archiveNever archivedNo public history of this siteWatch
CertificateEncrypted connectionIssued by WE1Noted

The page as captured

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

Key findings

  • Automated classification: Sensitive Interaction Risk.
  • At least one reputation service TrustSniffer consulted had flagged this domain at assessment time.

Full analysis

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 hosted on a free Cloudflare Pages subdomain. When visited, it served a platform-level "Suspected Phishing" warning interstitial instead of its own content. The visitor therefore sees only a short block notice, not a product, service or business. Its apparent purpose cannot be determined from the content, and the warning itself suggests it was set up to deceive visitors.

Scam/Impersonation Risk

The assessment is clearly cautionary. A leading browser-safety service flags the domain for social engineering, and several major security vendors independently classify it as malicious. Multiple confirmed blacklist sources agree, so this is a confirmed blacklisting, not a soft reputational signal. The hosting platform's own phishing interstitial, returned with an access-denied response, corroborates the external listings. Two independent signal families therefore converge on a deceptive-site classification. No conflicting legal identities and no specific brand impersonation were identified, because the site exposed no brand or identity content to compare. Behavioural testing did not detect wallet-connection prompts, wallet-drainer activity, clipboard manipulation, hidden forms or credential posts to external hosts. The protective block and the absence of observable content limit how much of the site's behaviour could be tested. These benign sandbox results cannot offset the external threat detections. The page also made heavy use of third-party network requests and produced a high volume of script errors, which is consistent with an unstable or hastily assembled deployment. Evidence:

  • Homepage: the only content served was a Cloudflare interstitial titled "Suspected Phishing", returned with a 403 response and about 380 characters of text.
  • Reputation: the browser-safety service flagged the domain for social engineering, and multiple security vendors, including several top-tier ones, flagged it as malicious.
  • Behavioural sandbox: three successful runs recorded no wallet-connect, drainer, clipboard-hijack or hidden-form activity, but did record 18 console errors and a majority of requests going to external hosts.

Regulatory Verification Notes

The only page reachable was the platform's warning notice, so no legal, terms, about or contact page could be assessed. No company name, licence, registration number or regulator claim was observed, and nothing can be inferred from that. The site could not be connected to any real-world operator, and no third-party broker or regulatory record matched the domain. This is context only, not a licensing verdict. The technical profile is ordinary. Transport encryption is valid, and the certificate is a domain-validated one from a known issuer. A domain-validated certificate only proves control of the domain, so it says nothing about the operator's identity or intent. Evidence:

  • Homepage: no operator, entity or licensing disclosure was present in the interstitial content.
  • Transport encryption: TLS certificate issued by WE1 (domain-validated), valid to 2026-12-18.
  • Hosting: served from AS13335 (Cloudflare, Inc., US), a shared platform subdomain, not a standalone registered domain.

What to Verify Next

Any prospective interaction should begin with the external listings, not with the site's own claims. Anyone who received this address by message, advertisement or social media should treat the source of that link as suspect and confirm the sender's identity through an independent channel. If the link claims to represent a known brand or service, the brand's official domain should be reached by typing it directly or through a trusted bookmark, and this address should be disregarded. Any repeat assessment should only take place after the listings have been formally cleared and the site serves substantive content with identifiable operator and legal pages. If the site is the user's own, a clean-up and review request with the listing providers is the proper route. Evidence:

  • Homepage: the platform warning replaced all site content, so no official contact or support channels could be confirmed from the site.
  • Reputation: both the browser-safety listing and the multi-vendor malicious detections are current and would need to be formally cleared.
  • Hosting: the address is a shared platform subdomain, so the site has no independent branded domain to check against an official registry.

Summary Verdict

The posture is high risk. Confirmed blacklisting by independent security sources, together with the hosting platform's own phishing warning, outweighs the technically valid but generic security setup. The operator's identity and purpose could not be established, and nothing observed supports treating the site as legitimate.

Infrastructure Integrity

The site sits entirely behind a major content-delivery and web-application-firewall provider. All four observed addresses are edge servers, and the origin server could not be observed, so the real hosting location cannot be independently checked. The provider's protections and its recognised network standing are mitigating factors only. They do not offset the reputational findings, and they make it easier to swap content quickly without an outside observer noticing.

Closing Assessment

The site should not be used for login, credential entry, wallet connection or any payment. Contact with it should be limited to read-only inspection in an isolated environment, if at all. Anyone who has already entered credentials or authorised a wallet should change the affected passwords and revoke wallet permissions immediately, and report the link to the hosting platform's abuse channel.

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

What the analysis found

3 findings contributed to this verdict, raised by external reputation, behaviour in a sandbox, registration and ownership.

01 External reputation

  • An external threat feed lists this domain: either Google Safe Browsing marked it malicious, or a significant number of malware engines flagged it.External reputation rule:EXT_BLACKLIST_CRITICAL

02 Behaviour in a sandbox

  • Most of what the page loaded came from other domains rather than from this one.Behaviour in a sandbox rule:BEHAV_EXTERNAL_RATIO_HIGH
  • The page produced an unusually high number of errors while it ran.Behaviour in a sandbox rule:BEHAV_CONSOLE_ERRORS_HIGH
  • The page made many background requests to other domains while it was open.Behaviour in a sandbox rule:BEHAV_EXTERNAL_XHR_HEAVY

03 Registration and ownership

  • The public registration record for this domain is incomplete.Registration and ownership rule:KF_WHOIS_INCOMPLETE

Identity verification

StatusUNKNOWN
Identity score50/100
Identity verification confidence30%
  • AI page analysis unavailable (page captured; identity not AI-verified)

Identity verification measures whether the site can be independently connected to a real-world brand or person. It is separate from the classification confidence.

What TrustSniffer observed

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

  • The request stayed on nearar.pages.dev. It was not redirected to another domain. Clear
  • It is hosted on CLOUDFLARENET, from a server in US. Noted

Domain intelligence

RegistrarNot available
HostingCLOUDFLARENET - Cloudflare, Inc., US
CountryUS
Server IP2606:4700:310c::ac42:2cf2
Name serversNot available
CDN / edge networkDetected (cloudflare)
Resolved IP addresses4
Edge IP addresses4
Likely origin IP addresses0
SSL issuerWE1
SSL expiry2026-12-18
Domain ageNot available (no registration date was returned)
Domain expiryNot available
Archive first seenNot available
Archive snapshots0
ReputationVirusTotal: 10 flagged | AbuseIPDB: 0% confidence, 0 reports | Google Safe Browsing: 1 match

About this assessment

A trust score summarises the evidence TrustSniffer could collect about nearar.pages.dev at assessment time. It is a starting point for your own judgement, not a guarantee: a high score means the signals were consistent with a legitimately operated site, a low or critical score means several risk patterns were present.

TrustSniffer assesses a website from the evidence it can collect at a point in time: domain registration and age, hosting and certificate, the content the site served, and third-party reputation feeds. A score is a summary of that evidence, 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 nearar.pages.dev

Is nearar.pages.dev a scam?

TrustSniffer's assessment of nearar.pages.dev found strong scam indicators. It scored 0 out of 100 on 2026-10-29, which is the critical-risk band. The specific signals are listed in the evidence above.

Is nearar.pages.dev safe to use?

This assessment found strong scam indicators. Do not pay, sign in, or share personal details with this site.

What is the trust score of nearar.pages.dev?

nearar.pages.dev scored 0 out of 100 on 2026-10-29, 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.
By AminRez, Founder & Lead Security Researcher, TrustSniffer
Produced by the TrustSniffer Analysis Engine · assessed 2026-10-29 · how we assess · report a mistake