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

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

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

Sensitive Interaction Risk Governance Risk

Assessed 2026-10-26 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 engines12 flagged itVirusTotalRisk
Google Safe BrowsingNot listedGoogleClear
Abuse reports on the host0% confidenceAbuseIPDB, 0 reports; shared hosting inflates reportsClear
Domain ageNot availableNo registration record was returnedNoted
CertificateEncrypted connectionIssued by YE1Noted
Hosted byCLOUDFLARENETServer in USNoted

The page as captured

https://protocolresync.pages.dev/app
Screenshot of the protocolresync.pages.dev homepage captured during the TrustSniffer assessment
What protocolresync.pages.dev served when TrustSniffer captured it on 2026-10-26. 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, Sophos flagged this site in external intelligence checks, indicating elevated compromise/scam exposure that requires immediate caution.

This website is a subdomain on a shared static-hosting platform, reached at an application path. The only content it presented to the analysis was a security interstitial titled "Suspected Phishing", served in place of any storefront, product or company page. The page carries almost no text of its own, and the analysis recovered no brand, product or business model. The path name suggests a web application front end, but its purpose cannot be established from what was captured.

Scam/Impersonation Risk

Contradictory signals are present. Several independent security engines currently flag the domain as malicious, including two tier-one security vendors, and the aggregate detection level confirms a blacklist listing. The hosting platform's own interstitial separately labels the destination as suspected phishing. The behavioural flags reviewed did not show wallet-drainer activity, clipboard manipulation, hidden forms or credential posts to outside parties. Those clean results do not offset a confirmed blacklist and a phishing warning issued by the platform. No conflicting legal entities were observed, and no brand impersonation was established, because no brand content was retrievable. The risk therefore rests on reputation and platform-level warnings rather than on identity inconsistency. Runtime behaviour was also unusual for a page with so little text. Nearly all outbound activity went to external destinations, with dozens of background requests and four external submissions. The page structure shifted heavily after interaction, and the browser console logged repeated errors, which suggests a script-driven application shell rather than static content. Evidence:

  • Homepage/app path: the captured page was titled "Suspected Phishing", returned a forbidden status and was gated by a bot challenge.
  • Reputation checks: 12 malicious and 2 suspicious engine verdicts, with a tier-one vendor flag, triggered the automatic hard cap on the score.
  • Behavioural sandbox: 51 external background requests and 4 external POSTs, with a peak external-traffic share of 96.2%.
  • Behavioural sandbox: 1,508 DOM mutations after interaction and 13 console errors across 3 successful runs, with no wallet-connect, clipboard or hidden-form activity.

Regulatory Verification Notes

The retrieved content consisted only of the warning interstitial. No terms, privacy, about or legal pages were evaluated, so licensing status and operator disclosures cannot be assessed. The absence of regulatory information here is a verification gap, not evidence of wrongdoing in itself. The weight of the assessment comes from the security listings, not from disclosure gaps. No third-party broker or regulator record was matched to this domain. The site's transport encryption is valid but is only domain-validated, so it confirms control of the hostname and says nothing about the identity or legitimacy of the operator. Evidence:

  • Transport encryption: the certificate is DV-level, issued by YE1 and valid to 2027-01-14.
  • Hosting: served from AS13335 (Cloudflare, Inc., US).
  • Application path: only a 381-character interstitial was retrieved, with no legal or corporate identity text.
  • Broker/regulatory datasets: no matching record was found.

What to Verify Next

Before any interaction, the exact address should be compared against any official domain the claimed operator publishes through an independent channel. Anyone who reached this address through a link, message or advertisement should confirm with the supposed sender, through a separate route, that the link is genuine. Any claimed operator should be asked for a licence or registration number and checked against the relevant public registry. The official support or contact channels should also be confirmed. Where an operator is claimed, the owner of the domain should be allowed to demonstrate control of it, and any listing status should be re-checked after the owner reports a clean-up. Evidence:

  • Application path: the platform interstitial gives no operator, company or licensing information to check.
  • Reputation status: the blacklist listing and the platform phishing warning are current and should be re-checked before any reassessment.
  • Hosting: the address sits on a shared platform subdomain, which any account holder on that platform can create, so the address alone does not identify who operates it.

Summary Verdict

The overall posture is high risk. Confirmed reputation listings and a platform-issued phishing warning determine the outcome, and neither the technical hygiene signals nor the absence of overtly malicious behaviour in the sandbox mitigates them. Operator identity is unconfirmed, and no evidence supports treating the site as legitimate.

Infrastructure Integrity

The site sits behind Cloudflare's CDN and WAF, and all observed addresses are edge servers within the same network. The origin server was not observable. The protective layer and bot challenge are mitigating technical factors only. They do not indicate legitimacy and cannot offset the external threat listings.

Closing Assessment

Account logins, credential entry, wallet connections and any payment or financial interaction should be avoided. At most, passive viewing from an isolated, non-sensitive environment is acceptable. Anyone who already entered credentials or approved transactions here should change passwords and review account and wallet activity immediately.

Written analysis generated 2026-10-26 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 structure of the page changed sharply while it was loading.Behaviour in a sandbox rule:BEHAV_DOM_DENSITY_SPIKE
  • 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 protocolresync.pages.dev.

  • The request stayed on protocolresync.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:2c5f
Name serversNot available
CDN / edge networkDetected (cloudflare)
Resolved IP addresses4
Edge IP addresses4
Likely origin IP addresses0
SSL issuerYE1
SSL expiry2027-01-14
Domain ageNot available (no registration date was returned)
Domain expiryNot available
Archive first seenNot available
Archive snapshotsNot counted (archive lookup incomplete)
ReputationVirusTotal: 12 flagged | AbuseIPDB: 0% confidence, 0 reports | Google Safe Browsing: 0 matches

About this assessment

A trust score summarises the evidence TrustSniffer could collect about protocolresync.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 protocolresync.pages.dev

Is protocolresync.pages.dev a scam?

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

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

protocolresync.pages.dev scored 0 out of 100 on 2026-10-26, 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-26 · how we assess · report a mistake