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

Security Alert

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

The website is a project published on a free, shared subdomain of a major edge-hosting platform's static-site service. In testing, the only content a visitor received was a short interstitial page titled as a suspected-phishing warning, with a few hundred characters of text and no visible product, brand or storefront. Its apparent purpose therefore cannot be determined from what it presents, and it has no standalone brand identity beyond a generic, solution-sounding project name.

Scam/Impersonation Risk

Contradictory signals are present and severe. The site is blacklisted: major browser safe-browsing protection flags it for social engineering, and a substantial cluster of security engines independently rate it malicious. Three leading security vendors are among them, and an additional external blacklist confirms the listing. This convergence is decisive, and it triggered an automatic ceiling on the overall assessment. The interstitial the site served is itself a platform-level warning that the page is suspected phishing, and the web-archive record also associates the host with known phishing. No conflicting legal identities were found, and no specific brand impersonation was established. The risk therefore rests on the confirmed external detections, not on a named impersonation target. Browser-behaviour testing reduces the likelihood of the most aggressive attack mechanics: no wallet-connection prompts, no clipboard manipulation, no hidden or externally posted credential forms, and no fingerprinting were observed. However, the pages generated an unusually high share of third-party network traffic and a large number of console errors. That pattern is consistent with a fragile or hastily assembled deployment, and it does not contradict the external verdict. Evidence:

• Homepage: served a platform-issued suspected-phishing interstitial with minimal text instead of business content.
• Safe-browsing and multi-engine reputation checks: social-engineering classification plus malicious ratings from a large group of engines, including three tier-one security vendors.
• Browser-behaviour testing of the homepage: no wallet, clipboard, hidden-form or password-exfiltration activity; heavy external request ratio and elevated console errors.
• Web-archive record: 11 snapshots spanning 2024–2026 (3 years tracked), first capture September 2024, domain registration continuity of about 2.1 years, with phishing association noted.

Regulatory Verification Notes

No legal, terms, privacy or about pages were available for assessment, because the visitor-facing content was the warning interstitial. No licensing, registration or regulator affiliation is evidenced, and no operator identity can be independently connected to the site. The site is a subdomain on a shared hosting platform and has no independently registered brand domain that could anchor an identity claim. No third-party broker or regulatory-database entry matched, so there is no reputational context in either direction beyond the security detections described above. Technical hygiene is intact but carries no weight against the threat listings. Transport encryption is valid, and the certificate is domain-validated only, which proves control of the hostname and nothing about the operator. Evidence:

• Homepage: no company name, registration number, licence or regulator reference could be observed.
• Hosting platform: the site resides on a shared platform subdomain, so no standalone registrant identity applies. Served from AS13335 (Cloudflare, US).
• Transport encryption: TLS certificate issued by WE1 (DV), valid to 2027-01-16.
• Third-party broker dataset: no matching entity.

What to Verify Next

Because the listings are current, the practical step is to treat the site as untrusted until the listing authorities and the platform host clear it. Anyone who received this address through a message, advertisement or social-media post should trace the original source and confirm through an independent, offline route (a known phone number, an official corporate site reached by typing the address manually) that the sender actually operates it. Any official support or contact channel should likewise be confirmed independently, not through details on this site. If the site is claimed to represent an existing organisation, that organisation should be asked directly whether it owns this deployment. The hosting platform's abuse process is the appropriate route for reporting the content and for requesting review. Evidence:

• Safe-browsing and multi-engine reputation checks: listing is current, so any clearance must come from the listing authorities.
• Homepage: no identifiable operator, so independent confirmation must come from outside the site.
• Hosting platform interstitial: confirms the platform itself has already flagged the content.

Summary Verdict

The site presents an elevated, clearly adverse risk posture. Current security detections from multiple independent sources outweigh the weak positive signals of valid encryption, continuous but short archive history and benign automated-browser behaviour. Its operator and purpose remain unestablished, and nothing on the site offsets the confirmed threat listings.

Infrastructure Integrity

The site is delivered through a major CDN and web application firewall, and all observed addresses are edge nodes, so the true origin server was not exposed. The provider is reputable and the DNS posture appears orderly, with mainstream registry and routing attribution. That reflects well on the platform but is only a mitigating factor. Free, shared edge hosting can be used by anyone, and protective infrastructure cannot offset the reputation risk from the external detections.

Closing Assessment

Interaction should be limited to passive observation, if any, and the site should not be used for login, credential entry, payments or any financial or personal-data submission. Links to it should not be followed or forwarded, and any message that directed a recipient here should be reported to the hosting platform and treated as potentially malicious.