Definition and scope
How to Verify an XRPL Account’s Domain addresses a distinct part of accounts and wallet controls. Connect an on-ledger account domain with a hosted xrp-ledger.toml identity file.
An XRPL account is a ledger object controlled by cryptographic authorization—not an app login. These topics explain how accounts begin, how transactions are ordered, and how master keys, regular keys, signer lists, and domain settings change operational control. Authorization changes should be rehearsed with independent recovery paths. No guide requires sharing a seed, family secret, or private key.
How it works
An account can publish a hex-encoded Domain in AccountRoot, while the named domain hosts an xrp-ledger.toml file that lists associated accounts, validators, and tokens. Matching both directions creates a checkable association.
- Domain: verify this field, object, or component against the cited protocol documentation.
- xrp-ledger.toml: verify this field, object, or component against the cited protocol documentation.
- ACCOUNTS: verify this field, object, or component against the cited protocol documentation.
- HTTPS: verify this field, object, or component against the cited protocol documentation.
Practical example and checks
Decode the on-ledger Domain, retrieve /.well-known/xrp-ledger.toml over HTTPS, and confirm that the relevant account appears in the expected section with consistent organizational information.
For production use, preserve the exact signed or queried data, record the network and validated ledger reference, and compare the result with the current primary documentation before changing off-ledger state.
Open the related live demo or evidence lab →Limits, risks, and common confusion
A matching domain proves control of two publication points at review time; it does not certify solvency, licensing, honesty, or continuing ownership. HTTPS and document freshness still matter.
Authorization changes should be rehearsed with independent recovery paths. No guide requires sharing a seed, family secret, or private key.
Current network status
Enabled on XRPL Mainnet. The underlying protocol capability is available on XRPL Mainnet. Individual services can still impose additional rules, limits, or trust assumptions.
Status reviewed 2026-08-23. Amendment-dependent behavior must be rechecked against the network's live feature state before operational use.