Is revs-eralabs.pages.dev safe? TrustSniffer's low-trust assessment: 26/100

Overview

This is a project website published on a free, shared static-hosting subdomain. It is registered under a platform-level hostname rather than an independent brand domain. When analysed, its homepage did not serve ordinary content. It served a hosting-platform interstitial titled as a suspected-phishing warning, with only a small amount of page text. The site's products, operator and business purpose therefore cannot be established from first-party content. Its name suggests a lab or project property, but that is an inference from the hostname alone.

Scam/Impersonation Risk: Active contradictions are present. Multiple independent security engines currently flag the site as malicious or suspicious, and it is blacklisted by external reputation sources. This is the decisive factor in the assessment. The homepage was intercepted by a challenge page carrying a suspected-phishing label rather than a normal storefront or application. This is consistent with the external reputation findings and shows that the platform itself has treated the property as questionable. No conflicting legal entities were observed, so this is not an identity-contradiction case. The risk comes from the reputation and phishing-warning signals. Behavioural testing found no wallet-drainer activity, clipboard manipulation, hidden forms, credential posts to external hosts or device fingerprinting. Even so, the homepage generated a very heavy volume of third-party requests, about 119 external background calls, and four external POST submissions. Request destinations were mostly third-party, and the page rebuilt itself extensively after interaction, with large-scale page mutations and recurring script errors. That pattern fits a dynamic, script-driven front end that could be repurposed quickly, so the benign behavioural results do not offset the blacklist status. The domain is also young and has almost no archive history, so there is no track record to counterbalance the warnings. Evidence:

Regulatory Verification Notes: No regulatory registration, licence or corporate identity could be established from the site evidence, and the on-page disclosure position remains unclear. The deterministic assessment could not tie the site to any real-world brand or person. No third-party broker or regulatory-database match exists for it. This is an absence of corroboration, not a regulatory finding, and it adds no negative verdict of its own. Any claim of authorisation, custody or financial-service status that the site might make should be treated as unsupported until independently confirmed. The site's valid transport encryption proves only that the connection is encrypted. It does not show who operates the site or that the operator is legitimate. Evidence:

What to Verify Next: Because the site carries confirmed adverse reputation findings, verification should happen before any interaction rather than alongside it. The first step is to establish through an independent channel, such as the official website or social profile of the project the site claims to represent, whether this hostname is an authorised property of that project. Any link to it should be traced back to its originating source. A link received through a message, advertisement or social post should be treated as unconfirmed. If the site claims a regulated activity, the stated entity and licence should be checked against the relevant regulator's public register, not against details on the site. The status of the hosting-platform warning and the reputation listings should be re-checked later, because a rating produced by a compromise or a one-off misconfiguration can change. Evidence:

Summary Verdict: The site is assessed as low-trust and carries an elevated risk posture. Confirmed adverse reputation findings and a platform-level phishing warning outweigh its technically clean behaviour and valid encryption. Its legitimacy and operator identity are unverified, and the available evidence does not support treating it as a trustworthy counterparty.

Infrastructure Integrity: The site is delivered through Cloudflare's CDN/WAF, and all four observed IP addresses are edge nodes. The origin server was not visible, so hosting cannot be independently verified. The WAF's bot-protection layer was active and appears to account for the challenge page seen at capture. The shared-hosting subdomain model, short-lived DNS records and edge-only visibility make rapid content changes easy to conceal. The protective infrastructure is a mitigating factor only. It lowers some technical exposure but cannot offset the reputation findings.

Closing Assessment: The site should be avoided for any login, credential entry, wallet connection or payment. At most, it should be viewed read-only from an isolated environment, and nothing should be downloaded from it. Engagement should wait until the warnings are cleared and the operator is independently confirmed.

• Homepage: served a platform interstitial titled as a suspected-phishing warning, with a 403 response and only 381 characters of text.
• Reputation checks: two engines rated the site malicious and one suspicious, and an external blacklist listing is confirmed.
• Homepage behaviour: 119 external background requests, four external POSTs (none to non-whitelisted hosts), 1,508 page mutations after interaction and 5 console errors across 3 test runs.
• Provenance: domain about 1.6 years old (583 days), with only 2 archive snapshots, both in 2025, covering 1 year tracked.
• Hosting: served from AS13335 (Cloudflare, Inc., US), registry ARIN.
• Transport encryption: TLS certificate issued by WE1, domain-validated (DV) only, valid to 2026-12-03.
• Identity: no operator, legal entity or licence reference could be tied to the site, and no broker-database match was found.
• The homepage's platform warning and the external listings are the gating items to clear before any further engagement.
• No verifiable operator identity is available on the site, so any link to a known brand must be confirmed from the brand's own channels.
• Official support and contact channels should be taken from an independent source rather than from this site.