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

Overview

This website is a single-page web utility presented under the name CoinFactory. Its page title describes a "multi-send" tool for Solana and SPL tokens, meaning a service for distributing tokens to many wallet addresses in one operation. It is published on a free, shared-platform subdomain with a non-descriptive, randomly styled name rather than on a branded domain. Its apparent purpose is to give crypto users and token issuers a bulk-transfer and airdrop utility.

Scam/Impersonation Risk

No contradictions were observed. The evidence shows no phishing indication, no brand impersonation, no conflicting legal identities and no confirmed blacklisting. One reputation engine did flag the site as suspicious. No other engine corroborated this, and the major browser-safety service did not list the site. It is therefore best read as a weak, unconfirmed reputational signal rather than a finding. The behavioural profile is the main point of attention. During interaction testing the page generated a large volume of requests to third-party endpoints, most of them outside the set of commonly recognised services. Several of these were outbound data submissions, and the browser console logged repeated script errors. For a token-distribution tool this pattern is unusual and unexplained. It may reflect analytics, RPC or pricing endpoints, or loosely assembled front-end code, but the evidence does not say which. On the other side, the testing observed no wallet-connection prompts, no wallet-draining behaviour, no clipboard tampering, no hidden or externally posting credential forms and no content cloaking. The branding of a "factory" for token operations on an anonymous shared-hosting subdomain is an unverified on-page claim only. Evidence:

• Homepage: the title presents a Solana and SPL-token multi-send service under the CoinFactory name, and this on-site claim is not independently corroborated.
• Interaction testing of the homepage: 61 external XHR/fetch requests, of which 52 went to non-whitelisted destinations, plus 9 external POSTs (4 to non-whitelisted destinations) and 18 console errors.
• Interaction testing of the homepage: no wallet-connect, wallet-drainer, clipboard-write, hidden-form, external password-form or cloaking behaviour in 3 of 3 successful runs.
• Reputation checks: 0 malicious detections, 1 unconfirmed "suspicious" detection, and no safe-browsing listing.

Regulatory Verification Notes

The captured homepage content does not establish a legal entity, licence or registration for the operator, and the identity behind the CoinFactory name has not been independently verified. The available evidence is therefore consistent with a functioning web utility, not with a verified business. A tool that moves digital assets would ordinarily be expected to state who operates it and under what terms. Here the disclosure position remains unclear, and this is a transparency matter, not evidence of wrongdoing. No third-party broker or regulatory record is associated with the site, so there is no external signal to weigh either way. The transport layer is sound: the encrypted connection is valid and was issued by a recognised certificate authority, but it is domain-validated only, so it confirms control of the hostname and says nothing about the operator. Evidence:

• Homepage: no operator name, licence or registration reference could be established from the captured content, which was about 3,000 characters of text.
• Hosting: served from AS13335 (Cloudflare, Inc., US), and the domain resolves under a shared Pages-type subdomain, not a standalone registered domain.
• Transport encryption: TLS certificate issued by WE1, DV validation, valid to 2027-01-10 (about 80 days remaining at analysis).
• Identity assessment: the site could not be independently linked to a real-world brand or person.

What to Verify Next

The operator should be identified through an independent route, for example the official social, repository or documentation channels of the CoinFactory name, and not through links on the page itself. Any claim of affiliation with a known Solana project should be confirmed there. Before real value is committed, the tool should be tested with a negligible amount on a secondary wallet. Every wallet signature request should be inspected to confirm it performs only the expected transfers and requests no broad token-delegation or account-authority permissions. The third-party endpoints receiving data from the page should be reviewed in the browser's developer tools, to confirm that no wallet addresses or other sensitive inputs are sent to unrecognised services. The official support and contact channels should also be confirmed through a source independent of the page. Evidence:

• Homepage: the multi-send function implies batch transfers whose permissions can only be judged from the signing prompts it generates.
• Interaction testing: a sizeable share of outbound traffic and several outbound data submissions went to destinations outside the recognised-service set.
• Identity assessment: the operator link to a real-world brand or person remains unestablished.

Summary Verdict

The site holds a moderate trust posture. No contradictory or fraudulent indicators were found, and its technical foundations are sound. Against that, its operator identity is unestablished and its runtime behaviour is notably dependent on third-party services.

Infrastructure Integrity

The site sits behind Cloudflare's CDN and WAF, and every observed address is a Cloudflare edge address. The origin server was not observable, so the underlying host cannot be assessed independently. Edge-only visibility also makes it harder to detect rapid content changes behind the front end. The protection is a mitigating factor for availability and basic exposure. It does not demonstrate that the operator is legitimate.

Closing Assessment

Ordinary caution is appropriate. The site can be inspected freely. Any step involving a wallet connection, a transaction signature or the transfer of assets should wait until the operator is independently identified, and a first trial should use only a small, disposable balance.