This page contains an overview of all standardized Resolver records. The reference is divided into sections, grouping records by their namespaces and use-cases:

• ​Crypto payments​

• ​Browser resolution​

  • ​DWeb records​

  • ​DNS records​

Developers may also set custom records for the domains. Domain records are stored as a key-value dictionary by Resolvers and are not validated on the smart-contract level. For more details, read Architecture Overview and Managing Domain Records.

Cryptocurrency payments

For information about crypto payments, see Managing Domain Records - Cryptocurrency Payment Records.

crypto.ETH.address

Ethereum Address to receive cryptocurrency payments.

crypto.BTC.address

Bitcoin Address to receive cryptocurrency payments.

crypto.<TICKER>.address

Cryptocurrency address of the ticker.

Multi-chain currencies

Some currencies exist on multiple chains.

crypto.<TICKER>.version.<VERSION>.address

Cryptocurrency address of ticker version

Browser resolution

Browser resolution is described in the Browser Resolution Algorithm page.

browser.preferred_protocols

Protocols that browser should prioritize to display content for.

browser.redirect_url

A fallback URL, to which a user will be redirected if no other resolution method is supported.

DWeb records

For more details, read Browser Resolution Algorithm - DWeb Records.

dweb.ipfs.hash

IPFS network content hash.

dweb.bzz.hash

Swarm network content hash.

DNS records

For more details, see Browser Resolution Algorithm - DNS Records.

dns.ttl

Default TTL setting for all DNS records.

dns.A

DNS A record IP addresses.

dns.A.ttl

TTL setting for all A records.

dns.CNAME

DNS CNAME record IP addresses.

dns.CNAME.ttl

TTL setting for all CNAME records.

dns.<RECORD>

Specified DNS record values.

dns.<RECORD>.ttl

TTL setting for corresponding type of records.

Deprecated records

ipfs.html.value

Deprecated: use dweb.ipfs.hash instead.

ipfs.redirect_domain.value

Deprecated: use browser.redirect_url instead.