Is whitelist-mojoplanet.pages.dev safe? TrustSniffer's moderate-trust assessment: 61/100

Overview

Planet Mojo is a single-host website served from a Cloudflare Pages subdomain rather than a standalone registered domain. Its homepage is titled "Planet Mojo" and carries a moderate amount of text content, and it appears to be a content-oriented site. The visible material does not establish a clear commercial offering, so its business model and purpose remain undetermined.

Scam/Impersonation Risk

No contradictory signals were observed. There were no phishing indications, no brand impersonation, no conflicting legal identities, and no confirmed listing on any threat-intelligence or safe-browsing source. One reputation engine returned a single "suspicious" flag. No other source corroborated it, and the same reputation check recorded zero malicious detections. This is therefore a soft third-party reputation note, not a confirmed listing. It is shown here and given limited weight for that reason. Runtime behaviour was also free of the usual abuse mechanics: no wallet-connection prompts, clipboard manipulation, hidden forms, credential forms posting to outside parties, or content cloaking. The behavioural profile is not entirely quiet, though. The homepage generates a heavy volume of calls to third-party endpoints, including a considerable number of outbound POST requests, and the browser console logged a very high number of script errors. These observations come from the sandbox sessions on the homepage. They are discounted because most destinations are recognised and only a small handful fall outside the known set. The pattern is consistent with a busy, loosely engineered front end with substantial third-party integrations. It is not evidence of malicious intent, but it does widen the data-sharing surface. Evidence:

• Homepage runtime: three sandbox runs completed, with no cloaking, no wallet-drainer behaviour, no clipboard writes and no hidden forms.
• Homepage network activity: 78 external XHR/fetch calls and 12 external POSTs, of which only 3 external destinations were outside the recognised set.
• Homepage script health: 231 console errors recorded during sessions.
• Reputation: 0 malicious detections and 1 unconfirmed suspicious flag from a single engine; no safe-browsing hit and no abuse reports against the hosting address.

Regulatory Verification Notes

The evidence does not tie the site to a named company, a licensed entity or a regulated activity. No third-party broker or regulatory record matched it. The site is not presented as a financial or regulated service in the material reviewed, so the absence of licensing information is a verification gap rather than an adverse finding. Because the site sits on a shared platform subdomain, the hostname alone does not distinguish the operator from any other tenant of that platform. The page was captured, but AI page analysis was unavailable, so the site's identity has not been independently verified and the real-world operator is not established. Identity confidence is low. On the technical side, a valid transport-encryption certificate from a recognised issuer protects the site. This is consistent with basic technical upkeep, but it does not show who operates the site. Evidence:

• Hosting: served from AS13335 (Cloudflare, Inc., US).
• Transport encryption: TLS certificate issued by WE1 (DV), valid to 2026-12-09, 37 days remaining at the time of analysis.
• Homepage: no legal entity name, licence reference or registration number was identified in the captured content.
• Broker/regulatory datasets: no matching record.

What to Verify Next

Before any exchange of personal data, payments or credentials, the operator should be identified through an independent route, such as a named business registry search or a direct enquiry to an official channel. If the site is said to represent a known brand, that brand's own official website should confirm the link to this address. The third-party endpoints the homepage contacts should be reviewed if sensitive data is to be entered, since the site shares information with several external services. The certificate's renewal should also be rechecked after its expiry date, to confirm the site is maintained. Evidence:

• Homepage: shows no stated operator identity to cross-check against a registry.
• Homepage network activity: external POST traffic to third-party endpoints is present.
• Transport encryption: the certificate expires within about five weeks of the analysis.

Summary Verdict

The evidence is consistent with a moderate-trust property whose operator is unverified. Basic technical hygiene appears sound, and no contradictory or fraud-indicative signals were observed. The one soft third-party reputation note is uncorroborated and carries limited weight. The site's standing is held back by the lack of a connected real-world identity, an unclear purpose, and a noisy, third-party-heavy front end. Classification confidence is also modest. The overall position is cautiously neutral, neither endorsing nor condemning the site.

Infrastructure Integrity

The site is delivered through Cloudflare's CDN and WAF, and every observed address is a shared edge node. The origin server is not exposed, which reduces direct attack exposure. It also means the true hosting location cannot be independently confirmed. This is a mitigating factor only. It does not establish the operator's legitimacy or the stability of the content behind it.

Closing Assessment

Browsing the site for information is reasonable. Before submitting credentials, personal data or payments, the operator's identity and purpose should be confirmed independently. Where possible, sensitive interactions should use payment methods that offer buyer protection.