Is tor-bgc.pages.dev safe? TrustSniffer's moderate-trust assessment: 50/100

Overview

This website is a single-page site published on a free subdomain of a shared developer hosting platform. It presents itself under the title "THORChain", a name associated with crypto-asset infrastructure. Its apparent purpose is to present a crypto-related service, but the captured homepage does not evidence any specific products, rates or claims, and it names no operator.

Scam/Impersonation Risk

Contradictory signals are present and are the decisive factor in this assessment. Multiple independent threat-intelligence engines currently classify the site as malicious, and further engines rate it suspicious. The domain is therefore treated as blacklisted by external reputation sources, and that listing outweighs the site's otherwise orderly technical hygiene. A browser-level safe-browsing list does not currently flag it, and no phishing, legal-identity conflict or confirmed impersonation was established. However, the page trades under a recognisable protocol name while living on a generic, freely registrable hosted subdomain rather than a dedicated domain. That is a pattern commonly seen with brand-mimicking pages, although it is not proof of impersonation here. In sandbox testing, the homepage generated an unusually heavy volume of third-party traffic. Over 200 background requests and 35 outbound data submissions went to external destinations, with about 99 percent of observed activity external. A subset of these went to destinations outside the recognised-service allow-list, including several submissions to unrecognised endpoints. The page also rewrote thousands of DOM elements after interaction and logged repeated script errors. No wallet-connection prompts, wallet-drainer behaviour, clipboard tampering, hidden forms or credential posts to outside parties were observed. The absence of these behaviours is mitigating, but it does not offset the reputation listings. Outbound data flows of this scale on a thin page are consistent with a template that relays visitor data or dynamically loads third-party code. Evidence:

• Homepage: the title carries the protocol name, while the address is a generic hosted subdomain on a shared platform.
• Homepage sandbox runs (3 of 3 successful): 212 external XHR requests (20 to non-allow-listed destinations), 35 external POSTs (6 non-allow-listed), 16 console errors, and a peak DOM change of 2,725 mutations after interaction.
• External reputation: 2 engines report malicious and 2 report suspicious; no safe-browsing flag; the hosting provider's abuse record is clean (0 reports).
• Provenance: ~2.1 years of registration continuity, with 11 archive snapshots spanning September 2024 to March 2025 (2 years tracked) and no content repurposing detected.

Regulatory Verification Notes

The captured homepage identifies no legal entity, jurisdiction, licence or registration number, and no dedicated legal, terms or about pages were evidenced. Ownership is opaque, which is an administrative limitation of the registration record and not an identity contradiction. No regulatory or broker-database match was found, so no third-party reputational signal on licensing exists either way. Real-world operator identity remains unestablished, and the available evidence cannot be read as confirming a legitimate operator. Any crypto-asset activity associated with the site would be expected to sit with a clearly identified, accountable entity, and none is shown. Evidence:

• Served from AS13335 (Cloudflare, Inc., US), registry ARIN.
• TLS certificate issued by WE1 (DV, domain validation only), valid to 2027-01-15. This confirms encrypted transport, not organisational identity.
• Homepage: no corporate name, registration number or regulator reference. The site is also not recognised in the DeFiLlama protocol directory, so no TVL figure is available.

What to Verify Next

The first step is to establish through the protocol's own official channels, reached independently of this site, whether this address is an authorised property. If it is not, it should be treated as unaffiliated. Current reputation results should be re-checked from at least two independent threat-intelligence sources, since a listing on a shared hosting platform may change as takedowns or clean-ups occur. Any claimed operator should be identified through an official registry or the protocol's published documentation, not through anything stated on the page. Official contact and support channels should likewise be confirmed through an offline or independent route. Evidence:

• Homepage: returned HTTP 200 and was stable across all 3 sandbox runs, so the page reviewed is reproducible.
• Homepage: no wallet-connection prompt was triggered during testing, so any such prompt appearing later would indicate a change in the page's behaviour.

Summary Verdict

Technical hygiene and a continuous, if short, history hold this site at a moderate classification. External threat listings are the decisive factor, and they place the site at an elevated risk posture. The real-world operator is unestablished, so the site cannot be treated as a credible representative of the brand it uses.

Infrastructure Integrity

The site is fronted by Cloudflare, a mainstream CDN and WAF. All four observed addresses, IPv4 and IPv6, are edge nodes, and the origin server was not observable. Bot-protection challenges were detected, and this accounts for the absence of cloaking in testing. This posture is a mitigating factor only. It does not verify the hosting origin, and it can obscure rapid content changes behind the edge. It cannot offset the reputation risk.

Closing Assessment

Use should be limited to passive, read-only viewing. No credentials should be entered, no wallet should be connected, and no funds should be committed through this address. Any genuine interaction with the protocol should start from its officially published channels.