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

Security Alert

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

This website is a web application served from a subdomain of a shared static-hosting platform, with an application path under the name "gonkadev". When analysed, the page presented to automated visitors was a security interstitial headed "Suspected Phishing", not a branded product page. Its apparent purpose could not be established from on-page content. The deployment pattern is that of a free, disposable project subdomain, not an independently branded business domain.

Scam/Impersonation Risk

Contradictory signals are present, and the posture is cautionary. Multiple independent threat-intelligence engines currently flag the site as malicious, including two tier-one security vendors, and the site is blacklisted by external reputation sources. The application path returned an access-denied response behind a bot-challenge page whose title labels the destination as suspected phishing. This is a platform-level warning that corroborates the external detections. It is not proof of a specific phishing kit. No brand impersonation or conflicting legal identities were observed, and the reputational evidence is the decisive factor. The site's hostname also closely resembles the generic hosting-platform domain it sits under. That gives it a borrowed appearance of platform legitimacy, which attackers commonly exploit. Behavioural testing showed no wallet-connection prompts, clipboard tampering, hidden forms, or credential posts to external hosts. This is a mitigating observation, but it does not offset the reputation findings. The same testing showed that nearly all traffic went to external origins, with dozens of external background requests and several external POST submissions. Over a thousand page mutations followed interaction, and repeated script errors occurred. That profile is consistent with a heavily scripted, externally dependent front end whose data destinations cannot be vouched for. Evidence:

• Application path (/app): the page returned an access-denied response behind a bot-challenge interstitial titled "Suspected Phishing".
• External reputation: 11 engines rated the site malicious and 3 suspicious, and the aggregate crossed the threshold for a hard reputation cap.
• Behavioural sandbox: 54 external background requests and 5 external POSTs, with up to 96.9% of activity going to external origins.
• Behavioural sandbox: 16 console errors and 1,503 DOM mutations after interaction, with no wallet-drainer, clipboard-hijack or external password-form activity detected.

Regulatory Verification Notes

The real-world operator could not be connected to any identifiable person or company, and no licensing, registration or legal-entity information could be assessed. The captured page was a security interstitial, so no terms, privacy or about pages were available to evaluate. This is a limit on the review, not a finding about what the operator discloses. No third-party broker or regulator-style record matched this site, so no outside signal supports any regulated status. Given the reputation findings above, any legitimacy claim made by the site cannot be taken at face value. Evidence:

• Site capture: the only content observed was a roughly 380-character interstitial, so no legal or identity pages were reviewable.
• Hosting: served from AS13335 (Cloudflare, Inc., US).
• Transport encryption: TLS certificate issued by YE2 (domain-validated only), valid to 2026-12-14. This confirms an encrypted connection but says nothing about who operates the site.
• Broker intelligence: no match, so no third-party reputational context exists in either direction.

What to Verify Next

Before any interaction, the intended destination should be confirmed through a channel independent of this address. If the site is claimed to belong to a company or project, its official domain should be obtained directly from that organisation's known website or documented support route. The operator's licensing or registration status should then be checked in the relevant public registry, if the activity is regulated. Anyone who already visited the site and entered credentials or approved wallet or app permissions should treat them as exposed, rotate the credentials, and revoke the permissions. The hosting platform's abuse process is the right route for reporting or clarifying the suspected-phishing label. The site should be re-assessed only after the hosting platform or the operator confirms that the flag has been cleared. Evidence:

• Application path (/app): the interstitial warning is the platform's own signal and is the first item to resolve.
• External reputation: the current malicious detections must clear across the engines before any re-assessment is meaningful.
• Identity: no verifiable operator identity exists, so ownership must be established offline.

Summary Verdict

The overall posture is high-risk. Strong, converging external threat detections and a platform-level phishing warning outweigh the technically valid encryption and the behavioural absence of drainer-style tactics. The site's identity is unverified, and the evidence provides no basis for treating it as a legitimate, trustworthy destination.

Infrastructure Integrity

The site sits behind Cloudflare's CDN and WAF, and all observed addresses are edge nodes of that network. The origin server was not observable, so the real hosting location cannot be independently established. The edge network is reputable and its address space is clean. This is a mitigating factor only. It shows that the content is delivered through a well-run network and says nothing about the content itself, and it cannot offset the reputation findings. The valid but domain-validated certificate adds encryption without any vetting of the operator.

Closing Assessment

The site should not be used for login, credential entry, wallet connection or any financial interaction. Any visit should be limited to passive viewing, ideally from an isolated browser or environment. Access should be reconsidered only after the hosting platform and the external threat-intelligence sources clear the warnings.