Is clawnchtoken.com a scam? TrustSniffer's high-risk assessment: 5/100

Security Alert

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

The website at clawnchtoken.com is a very young, single-page property titled "clawnch - token infrastructure for agents". It presents a short block of promotional text positioning itself as token-related infrastructure for automated agents. Its apparent purpose is to promote or support a crypto-token project. The captured content is too thin to establish a concrete product, a business model or a responsible operator.

Scam/Impersonation Risk

This site shows hard contradictory signals. It is currently blacklisted by external reputation sources. Several independent security engines flag it as malicious, and a recognised tier-one security vendor is among them. A further group of engines rates it suspicious. This is the decisive finding. It points to an elevated likelihood that the domain is being used for abusive purposes, and the protections noted elsewhere in this report do not offset it. The site's brand wording pairs a token name with "infrastructure for agents". That is exactly the kind of framing used to attract crypto-asset users, which raises the stakes for any wallet, credential or payment interaction. No brand impersonation, conflicting legal identities or phishing-page indicators were identified, and no published contact address was observed. The risk therefore rests on external threat detections and the domain's extreme youth, not on a proven impersonation. Automated browsing of the homepage showed benign behaviour. It made no external data transfers, no wallet-connection prompts, no clipboard manipulation, no hidden forms and no cloaking. That is a mitigating observation about the page as captured and does not reduce the weight of the external detections. Page content can be swapped quickly on a domain of this age. Evidence:

• Domain registered 2026-09-12 (~0.11 years old, roughly five weeks before analysis), so the domain has no meaningful operating track record.
• Web archive shows only 2 snapshots, from 2026-09-20 to 2026-09-22 (1 year tracked), so there is no history to corroborate a legitimate project.
• Homepage: 3 engines flag the domain as malicious and 3 as suspicious, with at least one tier-one vendor among them.
• Homepage behaviour across 3 successful runs: zero external requests, zero wallet-connect attempts and no cloaking.

Regulatory Verification Notes

The captured homepage discloses no legal entity, licence, registration number or governance information. The captured content is also too thin to show any terms or policy pages. Ownership is not transparently attributable to a named operator, and the registration record is incomplete. This is an ownership-opacity concern, not an identity contradiction. A missing licence or registration is a verification gap, not proof of wrongdoing. Here it compounds the external threat detections instead of standing alone. No third-party broker or regulatory profile matched this domain, and the domain is not recognised as a listed DeFi protocol. Any claim to be a legitimate token or agent-infrastructure venture therefore has no independent footing. Evidence:

• Registered through NICENIC INTERNATIONAL GROUP CO., LIMITED, with a one-year term running to 2027-09-12.
• Served from AS13335 (Cloudflare, Inc., US).
• TLS certificate issued by YE1 (DV, domain validation only), valid to 2026-12-11. Domain validation confirms control of the domain, not the identity of the operator.
• Homepage: no company name, licence or registry reference is disclosed.

What to Verify Next

Before any interaction, confirm independently whether a project called Clawnch exists and which organisation operates it. Use official channels reached by a route other than this website, such as a known project announcement, a reputable token or protocol directory, or an established company registry. Check whether the legal entity and any claimed regulatory authorisation can be found in the relevant public registry. Confirm any official support or contact channels offline as well. Re-check the domain against threat-intelligence sources over the coming weeks. A genuine false positive should clear, and a persistent or growing set of detections should be treated as confirmation. Evidence:

• Homepage: the stated purpose, token infrastructure for agents, names no team, contract or product that could be checked.
• The detections date from a domain only weeks old, so reassessment after remediation or delisting is meaningful.
• No broker or regulatory-profile match exists to anchor any independent verification.

Summary Verdict

The overall posture is high risk. The decisive factor is the convergence of confirmed external blacklisting with a domain only weeks old, which has a minimal archive record and no verifiable operator. The benign behaviour of the captured page and a working encrypted connection are the only offsetting observations. They show technical hygiene and do not establish legitimacy. Identity could not be independently connected to any real-world brand or person.

Infrastructure Integrity

The domain resolves entirely to Cloudflare edge addresses, including both IPv4 and IPv6 endpoints. No origin server could be observed, so the actual hosting location cannot be verified independently. Cloudflare's protection is a modest mitigating factor, because it reflects mainstream, reputable infrastructure. Anyone can use it, so it does not vouch for the site's operator. The same edge-only visibility can conceal rapid content changes behind a stable front end. A heuristic also notes a young domain with sparse subdomains. That is an unconfirmed pattern, consistent with a newly created site.

Closing Assessment

The site should be treated as unsafe for any sensitive interaction. Do not log in, enter credentials, connect a wallet, make a payment or buy or trade tokens through it. At most, limited read-only viewing is reasonable, and nothing should be downloaded from it. Any decision to engage should wait until the operator is independently identified and the external threat detections have been cleared.