Is bawsaq.net 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.

bawsaq.net is a single-page website titled "BAWSAQ Stock Exchange | AirDrop". It dresses itself in stock-exchange branding and pairs that with an airdrop (free token distribution) promotion. Its apparent purpose is to draw visitors into an exchange-styled crypto-asset offer. The page loads normally and carries a substantial block of text, but nothing independently links it to a recognised exchange or operator.

Scam/Impersonation Risk

The domain carries confirmed hostile reputation. Several independent threat-intelligence engines currently classify it as malicious, including three major endpoint-security vendors, and it is blacklisted by an external reputation source. This is the decisive finding and it dominates the assessment. The pairing of a "stock exchange" brand with an "AirDrop" call to action is a recognised lure pattern for token-claim and wallet-linking schemes. This report does not claim the page's mechanics were observed to be malicious. Automated interaction on the homepage showed no wallet-connection prompts, no clipboard manipulation, no hidden forms, no credential posts to third-party hosts, and no cloaking. That absence reduces the evidence of active on-page exploitation, but it does not offset the independent malicious classifications. Content can also be swapped quickly on a young or re-registered domain. The domain's history compounds the concern. It had archived activity in its early years, then a long dormant period, and then reappeared recently under a new registration with an undetermined change in purpose. That pattern is typical of aged domains acquired to inherit residual credibility. No conflicting legal entities were identified, so the issue is hostile reputation rather than an identity contradiction. Evidence:

• Homepage: titled as a stock exchange with an airdrop offer, a combination commonly used to lure visitors into token-claim flows.
• Threat reputation: 10 engines report the domain as malicious and 2 as suspicious, with an external blacklist hit; the Google Safe Browsing feed returned no match.
• Domain provenance: registered 2026-06-18 (~0.36 years old), yet 72 archive snapshots span 2013–2025 (13 years tracked), with no captures between 2016 and 2024. That points to a lapsed domain re-registered and repurposed.
• Homepage behaviour: three sandbox runs completed successfully with no wallet-drainer, clipboard-hijack or external password-form activity detected.

Regulatory Verification Notes

The site gives no verifiable legal entity, licence, or registration that would support its use of exchange branding. The operator's real-world identity could not be independently connected to any known brand or person. Registration details are also incomplete and the owner is obscured, which amounts to ownership opacity. Presenting as a "stock exchange" implies regulated market activity, and nothing in the evidence supports that implication. No third-party broker or regulatory database lists the site, so there is no external regulatory context to soften the picture. The technical hygiene is basic and does not indicate legitimacy. The site uses a domain-validated certificate from a recognised public issuer, which shows only that the connection is encrypted, not that the operator is who it claims to be. Evidence:

• Legal and identity content: no corporate registrant, regulator or licence reference was available to support the exchange claim.
• Registration: the domain is held through the registrar Global Domain Group LLC and expires 2027-06-18.
• Transport security: TLS certificate issued by WE1 (DV), valid to 2027-01-13.
• Hosting: served from AS13335 (Cloudflare, Inc., US).

What to Verify Next

Any prospective interaction should first be tested against independent sources rather than the site's own claims. If the site asserts exchange or securities-trading activity, that status should be checked directly in the relevant national financial-regulator registry. Any airdrop, token or brand it claims to represent should be confirmed through that project's or brand's official channels, reached by an independent route and never through links on this site. The domain's threat listings should be re-checked later to see whether the detections persist or are withdrawn. Official support or contact channels should be confirmed outside the site itself. Evidence:

• Homepage: the exchange and airdrop claims are made without any linked, verifiable registry entry.
• Reputation: the current malicious and suspicious classifications are the baseline against which any later re-check should be compared.
• Domain history: the recent re-registration after a long archival gap makes any inherited reputation unreliable as a trust anchor.

Summary Verdict

The overall posture is high risk. The convergence of confirmed hostile reputation, a re-registered domain with an unexplained change of purpose, and an unverifiable exchange identity outweighs the site's technically clean behaviour in testing. Legitimacy cannot be assumed on any point, and the site belongs in a clearly cautionary category.

Infrastructure Integrity

The site sits behind Cloudflare's CDN and WAF, and every observed address is an edge node, so the origin server is not visible and cannot be independently attributed. This is a mitigating factor only. It shows the site is competently fronted and encrypted, but it says nothing about who operates it. Edge-only visibility also makes rapid content changes harder to detect. Protective infrastructure therefore cannot offset the reputational findings.

Closing Assessment

At most, the site should be viewed read-only from an isolated environment. Credentials, wallet connections, token approvals, personal data and payments should not be submitted to it. If the site is encountered through a message, advertisement or social post, the referring item should be treated as suspicious and reported. Organisations should consider blocking the domain at the network or email-filter level.