Is api-versesync-web.pages.dev a scam? TrustSniffer's high-risk assessment: 0/100

Security Alert

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

This website is a bare-bones web property hosted on a free developer-platform subdomain. Its captured homepage is an empty document with no visible text, navigation, forms, branding or page metadata. A visitor sees nothing, so no product, service or business model can be observed. The hostname's wording suggests an API or web-synchronisation service, but that is not evidence of any real function.

Scam/Impersonation Risk

Contradictory signals are present and decisive. Multiple major security vendors currently flag the site as malicious, including several tier-one engines. The site is therefore blacklisted on the strength of independent external detections. The detections do not say what the site does, so its precise role (malware, phishing or abuse staging) remains unspecified. The hostname also closely resembles the generic hosting-platform domain it sits under, which a brand-similarity check treated as a likely lookalike pattern. No conflicting legal entities were found, and no phishing form, credential harvester or wallet-draining behaviour was observed in the sandbox runs. The empty page is nonetheless a concern. A placeholder that exposes no content is the shape of a staging or cloaking asset, because content can be swapped in later without any change to the address. Sandbox runs recorded no cloaking, but they saw only a blank page, so they cannot clear the site. Taken together, the confirmed external listings override the absence of visible malicious content. Evidence:

• Homepage: the captured document is blank, with no title, description, forms or links. The site gives no basis for assessing intent.
• Reputation: independent security vendors currently flag the domain as malicious, which triggered the highest-severity external-listing safeguard.
• Sandbox behaviour: three successful runs recorded about a dozen external background requests and several external POST submissions, all to allow-listed destinations. They also recorded nine console errors and no login, hidden-form or wallet interactions.
• Domain provenance: the domain was first observed in December 2024 (~1.7 years old). Only 9 archive snapshots exist, spanning 2024–2026 (3 years tracked), and these show no content changes.

Regulatory Verification Notes

The site has no legal, terms, privacy, about or contact pages, and it names no operator, company, address or licence. Because there is no content to disclose anything, the real-world operator cannot be linked to the site, and legitimacy cannot be inferred. This is a transparency gap and is not by itself evidence of wrongdoing. No third-party broker or regulator listing matched the site. The site makes no regulated-activity claims, so there is nothing to validate beyond the absence of identity. Evidence:

• Homepage: no company name, registration number, licence reference or jurisdiction appears anywhere on the captured page.
• Regulator and broker data: no third-party broker or regulatory profile was matched to the domain.
• Transport security: the site presents a Domain Validated TLS certificate issued by WE1, valid to 2026-12-18. This confirms encryption only and says nothing about who operates the site.

What to Verify Next

Because the site has been flagged by independent security vendors, the priority is to establish why it was shared and whether it is expected. Anyone who received the address in a message, advertisement or token-approval prompt should treat the source as suspect. The operator's identity should be established through the organisation the site purports to represent, using contact details obtained independently and not from the site. If the site is believed to be the organisation's own asset, its owner should check for compromise and review recent deployments to the hosting project. Only a fresh independent assessment showing a clean reputation and real, attributable content would change this posture. Evidence:

• Homepage: the page offers no contact route, so any outreach must go through independently sourced channels.
• External listings: the current vendor detections should be re-checked after any clean-up, because the status can change.
• Domain history: the domain is under two years old, with a thin archive record and no earlier content to compare against.

Summary Verdict

The overall posture is clearly cautionary. Independent security detections outweigh every neutral or positive technical signal, and the lack of any visible, attributable content leaves nothing to counterbalance them. The site is treated as an elevated-risk asset of unverified identity, and its apparent legitimacy is unsupported by evidence.

Infrastructure Integrity

The site sits behind Cloudflare's CDN and WAF, and all four observed addresses are edge servers in Cloudflare's network (AS13335, US). The origin server was not observable, so the real hosting location cannot be independently checked. The valid certificate and mainstream edge network are mitigating factors only. They are commonly used by legitimate and malicious sites alike and do not offset the external threat detections. Evidence:

• Hosting infrastructure: served from AS13335 (Cloudflare, Inc., US), with 4 edge addresses observed and no origin candidates.
• Network reputation: the edge network itself carries no abuse reports, which reflects shared infrastructure and says nothing about this site.

Closing Assessment

The site should not be visited for account login, credential entry, wallet connection, payments or file downloads. Any interaction should be limited to passive inspection in an isolated environment. Links to it received through messages or advertisements should be reported to the security team or the platform's abuse channel.