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

Security Alert

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

This web property is served from a subdomain of a shared, free web-publishing platform. The hostname is an unbranded, random-looking string. When the site was visited, it returned a hosting-provider interstitial titled as a suspected-phishing warning instead of ordinary content. No products, services or business model could be observed, so the site's purpose cannot be established. Its profile matches a disposable hosted landing page that could be used to stage fraudulent or malicious activity.

Scam/Impersonation Risk

Contradictory signals are present, and they are serious. Several independent security engines currently flag the domain as malicious, including two top-tier vendors. This amounts to a confirmed blacklist presence. The page shown to the automated visitor was a platform warning that classes the site as suspected phishing. The hostname also sits directly under a shared hosting platform's domain, so it closely resembles that platform's namespace. Any reputation the platform has does not carry over to an individual tenant subdomain. Behavioural testing found a heavy pattern of outbound activity. Most of the page's network requests went to third-party endpoints, and several outbound data submissions occurred. The page also changed its structure sharply after interaction and produced repeated script errors. The tests found no wallet-connection prompts, clipboard tampering, hidden forms or credential posts to external hosts. That reduces the evidence for a specific drainer or credential-harvesting mechanism, but it does not offset the confirmed threat listings. No conflicting legal identities were found, because no legal identity is presented at all. Evidence:

• Homepage: the captured page was a hosting-provider interstitial titled as a suspected-phishing warning, with a blocked (403) response to the automated visitor.
• Reputation checks: two top-tier security vendors and several other engines flag the domain as malicious, and the domain also appears on an external blacklist.
• Behavioural sandbox, homepage: 81 external fetch/XHR calls and 5 external POSTs across 3 runs, 11 console errors, and a 1,508-node DOM mutation after interaction. No wallet-connect, clipboard-hijack or hidden-form behaviour was detected.
• Domain provenance: 13 archive snapshots from 2024 to 2026 (3 years tracked, first seen October 2024), so the domain is about 2 years old.

Regulatory Verification Notes

The evidence contains no licence, registration number, named legal entity or regulatory affiliation, and no third-party regulatory source confirms the site. Identity verification remains unresolved. No on-site disclosure can be assessed in a way that would support a legitimate operator. No broker-database record exists for the site, so there is no reputational context either way. This gap is a verification matter. The threat listings above, not the missing disclosures, are what drive the elevated risk assessment. The technical profile is typical of a generic hosted deployment. It gives no indication of a regulated or institutionally accountable operator. Evidence:

• Hosting: served from AS13335 (Cloudflare, Inc., US, ARIN registry).
• Transport encryption: TLS certificate issued by WE1 with domain-validation (DV) only, valid to 2026-12-10 (48 days remaining). DV confirms control of the domain, not the identity of the operator.
• Legal and policy pages: no terms, privacy, about or licensing content was available in the captured evidence.

What to Verify Next

Verification should start with the threat listings, because they are the decisive factor. Anyone assessing the site should check the current status of the malicious listings with the relevant security vendors. They should also check whether the hosting platform's abuse process has acted on the tenant. If the site is claimed to represent a brand or business, that entity should confirm through an independent, offline route that it operates this exact hostname. Official channels should be sourced from the entity's established website, not from this site. Any licence or registration claim should be checked directly with the relevant registry. Anyone who has already used the site should treat any submitted credentials as exposed. Evidence:

• Homepage: the platform's suspected-phishing interstitial indicates that an abuse classification already exists at the hosting layer.
• Reputation checks: the malicious detections come from multiple independent engines, so they can be re-checked with each vendor.
• Hostname: the random, unbranded name under a shared platform domain gives no indication of any real-world owner.

Summary Verdict

The available evidence places this site in an elevated-risk, clearly cautionary posture. Active third-party malicious detections and a platform-level phishing warning outweigh the neutral technical hygiene, and the operator's identity is not independently established. The site should be treated as a probable fraud or malware vector until the listings are cleared.

Infrastructure Integrity

The site is fronted by Cloudflare's CDN and WAF. All four observed addresses (two IPv4 and two IPv6) are edge servers, and the origin host was not observable. The platform's bot-challenge layer was active during testing. This protection is a mitigating factor only. It shows that the hosting is mainstream and says nothing about the legitimacy of the tenant content behind it. The edge-only view also prevents independent verification of where the content is actually served from.

Closing Assessment

The site should not be used for login, credential entry, payments or any financial interaction, and nothing should be downloaded from it. Any access should be limited to read-only inspection in an isolated environment, and avoiding the site entirely is the safer course. Any link to it that was received unsolicited should be reported to the sender's organisation and to the hosting provider's abuse channel.