Make official surfaces recognizable
A consistent name, wordmark, domain pattern, navigation structure, and security language help users identify the intended product. Consistency must survive compact headers, wallet prompts, email, support pages, and incident communication.
Do not rely on color alone. Phishing pages can copy a palette quickly, and users with color-vision differences need other cues.
- Canonical domain
- Product name and lockup
- Verified support route
- Security destination
- Transaction language
- Consistent warning patterns
Separate reassurance from evidence
Bad trust copy asks users to believe broad claims. Useful trust content names the custody model, permissions, recovery process, security contact, and actions the company will never request. Link to a stable security page rather than repeating shortened claims across interfaces.
Warnings should be specific at the moment of risk. A generic safety badge beside a wallet approval does not explain what is being authorized.
Test the identity under attack conditions
Review the product at small sizes, in copied screenshots, in dark mode, and beside a plausible lookalike. Ask unfamiliar users to locate the official domain, security information, and support route without coaching.
Maintain an asset package for incident response so support and communication teams do not recreate logos, colors, or domain references during an urgent event.
- Lookalike domain comparison
- Monochrome recognition
- Small-screen header
- Wallet-signing context
- Security-page discovery
- Support-route discovery
Referenced resources
- Novrinex security overview
A live example of a dedicated product-security destination.
- About Novrinex
The official product and company context used to verify identity claims.
Place the official product and a plausible lookalike side by side, then test whether new viewers can identify the canonical domain, security information, and support route without relying only on color.