A clone-site risk finding should rest on reproducible similarity plus conflicting identity or provenance signals. Visual resemblance alone is insufficient; the deliverable compares domain, certificate or transport context, policy text, support route, content, and verified canonical references.
What remains visible
Clone-site risk belongs to the website and identity layer. ERC20 and TRC20 explorer visibility remains a separate transaction-layer question, so the page should not mix identity checks with transfer-outcome claims.
What it does not prove
A visual match does not prove identity, and a familiar name does not prove safety, legitimacy, or current control. The surrounding signals need to be checked together.
Evaluation checklist
- Compare brand, domain, and update-history signals.
- Look for copied policy wording and repeated trust badges.
- Check whether support channels align with the visible domain.
- Review external mentions for repetition, dates, and criteria.
Clone-site provenance matrix
Inspect independent identity surfaces and preserve false-positive explanations such as shared templates or authorized mirrors.
Capture both surfaces
Record exact domains, timestamps, page titles, policy and support URLs, and representative content.
Compare provenance
Check RDAP events, canonical references, published official links, certificate context, and contact identity.
Classify cautiously
Use match, conflict, unavailable, or authorized relation; do not accuse from design similarity alone.
Filled evidence record
Clone-site provenance matrix snapshot: 2026-08-05. The worked record for clone mixer site labels every synthetic or non-attributed specimen directly in the table.
| Evidence item | Worked record | Interpretation boundary |
|---|---|---|
| Domain and age | Different registration events or registrar context can establish separate domain histories. | Age or privacy redaction alone does not prove cloning. |
| Content and identity | Copied wording plus changed support or policy identity is stronger than a shared layout. | Templates and licensed content can create benign similarity. |
| Canonical reference | An official source can identify an authorized domain or mirror. | Absence of a public list leaves authorization unresolved. |
Pass or hold criteria
For clone mixer site, a missing decisive input remains unknown and blocks the affected conclusion; the clone-site provenance matrix never converts it to a silent pass or zero.
| Dimension | Pass condition | Hold or fail condition |
|---|---|---|
| Reproducibility | Domains, captures, and compared elements recorded | Looks similar |
| Provenance | Multiple independent identity conflicts | One cosmetic match |
| Verdict | Risk classification with alternatives | Definitive fraud allegation without authority |
Next evidence layer
Mixer Domain Age And Identity Signals
Mixer Domain Age And Identity Signals adds risk guide context to clone mixer site. Review domain history in context. An older domain does not prove safe behavior, and a newer domain does not prove abuse. Domain age is context, not a verdict.
Fake Mixer Review Red Flags
Fake Mixer Review Red Flags adds review framework context to clone mixer site. Look for published criteria. A negative red-flag list does not prove every listed service is unsafe. It identifies content-quality patterns that reduce trust.
Mixer Support Channel Risk Signals
Mixer Support Channel Risk Signals adds risk guide context to clone mixer site. Check channel-domain consistency. Responsive support does not prove privacy, custody safety, or legitimate identity. It only shows one interaction surface that should match the rest of the site.
Mixer Letter Of Guarantee Claims
Mixer Letter Of Guarantee Claims adds trust review context to clone mixer site. Identify the exact claim made by the document. A document claim does not prove custody safety, legal compliance, transaction outcome, private logging practices, or the absence of clone-site risk.
Source notes
The sources below clarify clone mixer site terminology and the evidence limits described above. They do not verify private service operations or guarantee an outcome.
Related questions
What if both sites use the same analytics or CDN?
Treat shared infrastructure as one weak relationship signal; it can result from common vendors and does not prove common control.
What if the original site lists a mirror?
Record the dated first-party authorization and keep scope limited to the exact domain listed.