Red Flags

Pause when identity or terms are unclear, someone pressures you to share secrets, or a contact asks for an unexpected payment to release funds. Verify the claim through primary records and preserve evidence without publishing private data.

Potential warning signs include a mismatch between the domain and claimed operator, terms that conflict across pages, or a demand for passwords, one-time codes, seed phrases, or private keys. A red flag guides the next check; it does not establish who is responsible or whether a violation occurred.

Verify the operator and any license through the named official register. Compare the exact legal entity, product, and territory rather than relying on brand logos, screenshots, or search snippets. Save dated copies of the relevant terms and note any uncertainty.

If a payment or recovery request feels coercive, stop and contact the relevant provider through a route you locate independently. For a public review, distinguish your direct observation from a user's allegation, cite verifiable records, and avoid exposing personal or account information.

Pause and verify

• Check domain and operator identity
• Compare the relevant current terms
• Verify licensing claims with the named authority
• Reject requests for passwords or wallet secrets
• Record evidence and label uncertainty precisely

Avoid unsupported accusations

• One complaint does not establish a general pattern
• A missing search result is not proof of misconduct
• Do not publish private messages or identifying data without a need

Describe the observable issue, link it to a primary source where possible, and keep unverified reports clearly attributed.