Skip to main content
Protect your account and wallet by verifying RNS.ID channels and treating unexpected payment or signing requests as suspicious.

​
Verify the site

The public product uses the rns.id domain, and these docs use docs.rns.id. Check the complete hostname before signing in, uploading identity information, connecting a wallet, or paying. A logo, copied design, advertisement, or search result is not proof that a page is official. Use a saved bookmark or type the domain yourself. Be cautious with misspellings, extra words, unusual subdomains, URL shorteners, and links sent through direct messages.

​
Secrets RNS.ID will not request

Never share:
  • your account password;
  • an email verification or two-factor code;
  • an authenticator QR code;
  • a wallet seed or recovery phrase;
  • a wallet private key;
  • a wallet signature or signed-message payload; or
  • a full payment-card number through support chat or email.

​
Read wallet prompts

RNS.ID wallet sign-in and binding use an off-chain signature, while a Legal DID mint or burn and a crypto payment can be on-chain transactions with permanent effects. Wallet-prompt text can vary, so read the complete message rather than expecting a fixed field or phrase. A no-gas statement alone does not prove that a prompt is safe. Before approving, confirm that you started the action from rns.id and verify the displayed purpose and address. For an on-chain action, also verify the network, contract, token, amount, and permissions. Reject a prompt that does not match the action you started, and never send the resulting signature to another person.
RNS.ID will not ask you to transfer a Voyager Pass or Legal DID to a support representative for verification, and cannot use your recovery phrase to fix a wallet problem.

​
If you suspect phishing or compromise

  1. Stop interacting with the page or sender.
  2. Do not approve another prompt or payment.
  3. Save the URL, sender address, screenshots, timestamps, transaction hashes, and public wallet addresses.
  4. Reset the RNS.ID password from the official site if it may be exposed; a successful reset requires all currently signed-in browsers and devices to sign in again.
  5. Review connected accounts, wallets, 2FA, payment methods, and active sessions where available.
  6. Use the wallet provider’s official guidance if a wallet secret or approval may be compromised.
  7. Report the incident to RNS.ID Support.
On-chain transactions generally cannot be reversed by RNS.ID. Act quickly through the appropriate wallet, exchange, card provider, or law-enforcement channel when funds are at risk.

​
Report a phishing email to your email provider

Do not reply, open an attachment, or follow a link in a suspicious message. Before deleting it, preserve the sender’s complete email address, subject, date and time, suspicious links, and any screenshots needed for an RNS.ID report. Use the email service’s Report phishing, Report spam, or equivalent action. The label and location vary between Gmail, Outlook, Apple Mail, mobile apps, and other providers. After reporting the message, block the sender where that option is available and delete the email. If you already opened a link, submitted information, approved a wallet prompt, or sent a payment, follow the compromise steps above instead of treating the message as ordinary spam.

​
Report safely

Send the suspicious link or sender and a description of what was requested. Redact passwords, codes, card data, identity-document numbers, seed phrases, and private keys. Support needs evidence of the attempt, not the secret itself.