Is play-sopho.pages.dev a scam? TrustSniffer's critical-risk assessment: 0/100

play-sopho.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.

0 OUT OF 100
Critical Risk

play-sopho.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: A registration check came back incomplete: as a site on pages.dev, this address has no registration record of its own (the platform's domain is registered, not the site). That is a gap in what could be looked up, not a sign that ownership is hidden, and it does not say who runs the site.

Assessed 2026-11-06 by automated analysis. Evidence confidence 75%.

How the site describes itselfThe page is a Cloudflare interstitial warning that the requested website has been reported for potential phishing. It shows a 'Suspected Phishing' notice, an explanation of phishing, a Ray ID, and the visitor's IP. It contains no forms, links, or service content from the target site, so the target's purpose and legitimacy are unverified.

Evidence status and limitations

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

  • The real-world operator identity was not independently verified.

How to read these numbers

A trust score of 0 means the risk evidence outweighed every trust signal by more than the 0 to 100 scale can show. It rates the evidence found, not the probability that the site is a scam.

Evidence confidence (75%) 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.

Malware engines11 marked it maliciousVirusTotalRisk
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 seen2.6 years before captureWeb archive; a site on pages.dev has no registration of its ownClear
Web archiveArchived since 202415 snapshotsClear
CertificateEncrypted connectionIssued by WE1Noted

The page as captured

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

Key findings

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

Full analysis

Security Alert

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

Overview

The website is a tenant subdomain on a free application-hosting platform. Its own content could not be captured. Automated visits instead returned a security-provider interstitial headed "Suspected Phishing", stating that the requested site has been reported for potential phishing. The captured page has no forms, navigation, product claims or commercial content, so the site's purpose and business model cannot be established. What can be established is that the site is currently flagged as a phishing risk by both its hosting-edge provider and independent security engines.

Scam/Impersonation Risk

Contradictory signals are present and are serious. The site is confirmed as blacklisted by independent threat-intelligence sources. A double-digit number of security engines classify it as malicious, including several tier-one vendors. Behavioral capture also recorded a suspicious final-destination mismatch and a phishing-warning browser flag. Page-level analysis found a strong typographic similarity to the name of the hosting platform's own domain. This is treated as an unconfirmed lookalike indicator, because the site is a tenant of that platform and no impersonation of a distinct brand was confirmed. Neither the sandbox nor the page content showed login forms, hidden forms, wallet-connection prompts, clipboard manipulation or cross-site password submission. Those absences describe only what could be observed behind the interstitial and do not offset the external detections. No conflicting legal identities were observed, since no legal or identity pages were reachable. The cautionary posture rests on reputation evidence, not on harvested content, and should be treated as decisive for any sensitive interaction. The site's low-effort tenant-subdomain naming pattern and the repeated external detections are consistent with a disposable phishing or lure page, but the page evidence does not prove that purpose.

Evidence
  • Homepage capture: a "Suspected Phishing" interstitial with no forms, links or service content, returned with a 403 status after a bot challenge.
  • Reputation checks: the site has external detections from multiple security engines, which triggered a hard score ceiling. No page-level fraud red flags were extracted, because the real content was never rendered.
  • Archive history: 15 snapshots spanning 2024–2026 (about 3 years tracked), with the domain registration continuity dated about 2.6 years back. Known-phishing status is recorded against the archive record.
  • Behavioral sandbox: three successful runs recorded heavy external request activity, many console errors and a very large DOM mutation after interaction, all on the interstitial page.A console error is a technical error message that the page's own code reported inside the browser while it ran. It describes how the page is built, and on its own it is not proof that the site is harmful.

Regulatory Verification Notes

No licensing authority, license number, registered company name or legal entity is presented anywhere in the observable material. The only page captured is a third-party security warning, and it carries no legal, terms or privacy content. The operator's real-world identity is therefore unverified, and the site shows no connection to a regulated financial or commercial entity. No broker-reputation match exists for this site. Because the operator sits behind a shared-platform subdomain with no disclosed ownership, governance and ownership are opaque. This is a significant gap in this context, given the confirmed external detections. The absence of a license is a verification gap in itself and does not prove wrongdoing. Here, though, it adds to the reputation evidence instead of standing alone.

Evidence
  • Homepage capture: contains no company name, registration number, license claim, terms of service or privacy policy.
  • Transport encryption: a domain-validated certificate issued by WE1, valid to 2027-01-22. This shows only that the connection is encrypted and does not establish operator identity.
  • Hosting: served from AS13335 (Cloudflare, Inc., US), a shared platform that hosts large numbers of unrelated tenants.

What to Verify Next

Verification should start by establishing whether the reported phishing classification still stands. The site's current behavior should be reviewed only in an isolated, non-credentialed environment, never from a work or personal account session. Any party who sent a link to this address should be asked, through an independent channel, what it was supposed to lead to. The claimed organisation's official domain should be confirmed from a source the sender did not supply. If the site claims to represent a financial or commercial service, its license should be checked directly in the relevant regulator's public register. Official support and contact channels should be taken from that register or the organisation's verified website, not from this page.

Evidence
  • Homepage capture: the interstitial itself recommends treating the site as a suspected credential-theft risk.
  • Reputation checks: the external detections are current and were assessed in this analysis.
  • Identity: no operator, brand or license claim is presented, so the sender is the only available lead to the intended organisation.

Summary Verdict

The overall posture is high-risk. The combination of confirmed external blacklisting, an active phishing warning and an unverifiable operator outweighs the neutral technical hygiene signals. The site should be classed as unsafe for login, credential entry or financial activity. Only passive, read-only observation is compatible with the evidence.

Infrastructure Integrity

The site is delivered through Cloudflare's CDN and WAF, and every observed address is a Cloudflare edge address. The origin server is not visible, so the underlying host cannot be independently attributed. Cloudflare is a reputable, widely used provider, and the sandbox found bot protection in place and no hosting anomalies. This is a mitigating factor only. The same edge-only visibility that protects legitimate sites also makes it harder to attribute the operator or to detect content being swapped, and infrastructure quality cannot offset the external reputation evidence.

Closing Assessment

Do not log in, submit credentials, connect wallets or make any payment through this site. Any message or advertisement that directed a user here should be treated as suspicious and reported to the platform it came from. Anyone who has already entered credentials should change them immediately and enable multi-factor authentication.

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

What the analysis found

6 findings contributed to this verdict, raised by external reputation, page content, and registration and ownership.

01 External reputation

  • A confirmed external listing marks this domain as malicious: at least five security engines including a leading vendor, ten engines, or Google Safe Browsing.External reputation rule:EXT_BLACKLIST_CRITICAL

02 Page content

  • The page shows few of the signs expected from a trustworthy operator.Page content rule:PAGE_TRUST_QUALITY_LOW
  • The review of the page content rated it moderate risk.Page content rule:PAGE_RISK_MED
  • The page runs on a free pages.dev address instead of a domain of its own, a setup common to short-lived phishing and claim pages.Page content rule:PAGE_BRAND_SUSPECTED
  • The browser raised a warning while loading the page.Page content rule:PAGE_BROWSER_FLAGS_SUSPICIOUS

03 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

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.

  • No contact detail, company registration number or linked social profile was extracted from the page for checking. Any operator the page names in its own words (see how the site describes itself, above) is not verified here.

What TrustSniffer observed

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

  • The request stayed on play-sopho.pages.dev. It was not redirected to another domain. Clear
  • The earliest public archive of this site is from 2024-03-22. Clear
  • It is hosted on CLOUDFLARENET, a network registered in US. Noted

Domain intelligence

RegistrarNot available
HostingCLOUDFLARENET - Cloudflare, Inc.
Network registered inUS
Server IP2606:4700:310c::ac42:2f5d (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-22
First seen (web archive)2.62 years before capture; a site on pages.dev has no registration of its own
Domain expiryNot available
Archive first seen2024-03-22 (2.6 years before capture)
Archive snapshots15
ReputationVirusTotal: 11 malicious | 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 play-sopho.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 play-sopho.pages.dev

Is play-sopho.pages.dev a scam?

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

Is play-sopho.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 play-sopho.pages.dev?

play-sopho.pages.dev scored 0 out of 100 on 2026-11-06, 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-06 · how we assess · report a mistake