Is smart-mainnet.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.

This site is a project subdomain on a shared, free application-hosting platform. Its name suggests a blockchain "mainnet" product. When visited, it did not present a normal landing page. The hosting platform's own security interstitial intercepted the request and was titled as a suspected-phishing warning. Only a few hundred characters of text were readable, with no product description, company information, or visible service offering. The apparent purpose is therefore not established by the site itself, and the available evidence is consistent with a disposable front-end for a crypto-themed lure rather than an operating business.

Scam/Impersonation Risk

The site carries a confirmed adverse reputation. A large cluster of independent security engines classify it as malicious, with an additional engine flagging it as suspicious. Several of the most widely deployed enterprise security vendors are among the detecting engines. This is a confirmed blacklisting and the decisive factor in the assessment. The hosting platform's own challenge page labels the site a suspected phishing destination, which corroborates the third-party detections. No brand impersonation or conflicting legal identities were observed, because the site exposes no readable identity content to compare. The risk therefore rests on the blacklist and phishing indications, not on an identified imitation of a named brand. The "mainnet" naming pattern is a common lure for wallet-connection and token-claim schemes. No readable page content confirmed that scenario. Behavioral testing was reassuring on some points. It found no wallet-connection prompts, wallet-draining routines, clipboard manipulation, hidden forms, or credential forms posting to outside parties. Those observations show only that the captured page was inert. They do not offset the blacklist. A reasonable reading is that malicious functionality may sit behind the interstitial or be served selectively. The site made a heavy volume of outbound requests relative to its content and produced repeated script errors, which is consistent with an unstable or hastily assembled front end. Evidence:

• Homepage: access was intercepted by a security challenge page titled as suspected phishing, and the capture returned a blocked status.
• Reputation: a double-digit count of security engines flagged the domain as malicious, including three tier-one vendors.
• Domain provenance: about 2.2 years of tracked domain history, with only 7 archive snapshots spanning 2024–2025 (2 years tracked), which is thin continuity for a site claiming to be a network product.
• Sandbox: 3 of 3 runs completed with 21 outbound XHR/fetch requests and 18 console errors. No wallet, clipboard, or external credential-form behavior was observed.

Regulatory Verification Notes

The captured page exposes no legal, terms, privacy, or about content. It states no company name, registration number, licence, or regulator, so there is nothing on the site to assess for disclosure quality. The operator of a subdomain on a shared hosting platform cannot be identified from the address alone. This is ownership opacity and is not an identity contradiction. No third-party broker or regulatory-database match exists for the site, which is neutral and not a verdict. A site that offers no licence or entity information while carrying a confirmed adverse reputation gives a reader no basis for assuming any regulated status. Evidence:

• Homepage: no company name, licence, registration number, or jurisdiction was readable on the captured page.
• Hosting infrastructure: served from AS13335 (Cloudflare, Inc., US).
• Transport encryption: TLS certificate issued by WE1 at domain-validation (DV) level, valid to 2026-12-22 with 54 days remaining. This confirms encryption only and says nothing about operator identity or legitimacy.

What to Verify Next

Any contact with the site should be preceded by independent confirmation that the project it claims to represent actually exists and that this address belongs to it. That means checking the project's official channels (published through an established, independently confirmed route, not through links found on this site). Any claim of licensing or custody should be checked directly in the relevant regulator's public register. A separate check should confirm that the hosting provider has not suspended the project. If this address was reached through an unsolicited message, advertisement, or social post, the sender should be treated as suspect and the message reported. Evidence:

• Homepage: the only content returned was the hosting provider's suspected-phishing warning, so no project claims can be checked against the site.
• Threat reporting: the combination of broad engine detections and the platform-level warning supports reporting the address to the hosting provider and the user's security team.

Summary Verdict

The overall posture is clearly cautionary and the risk is elevated. Independent security detections and the platform's own phishing warning converge, and they outweigh the site's technically orderly encryption and stable hosting. Legitimacy is not supported, and the operator's real-world identity remains unestablished.

Infrastructure Integrity

The site is delivered through Cloudflare's CDN and web application firewall. All four observed addresses (IPv4 and IPv6) are Cloudflare edge servers, and no origin server was observable, so the real hosting location cannot be independently confirmed. Behavioral testing detected the bot-protection layer. This infrastructure is a mitigating factor only. It is shared by very large numbers of unrelated sites and cannot offset the reputation findings.

Closing Assessment

Do not enter credentials, connect a crypto wallet, approve any signing request, download files, or send funds through this site. If it was reached through an unsolicited link, the link should be reported and discarded.