You can store the addresses of over 100 blockchains, a content hash of a decentralized website, profile information such as an avatar and Twitter handle, and more. ENS even allows you to create custom records that can be used by other applications.
A Primary ENS Name (previously Reverse Record) points your Ethereum address to an ENS name. This allows dApps to find and display your ENS name when you connect to them with your Ethereum account. You can only have one primary name per address.
Sending money to an ENS name will resolve to the eth address record, and is not dependent on having a primary name set. However, your primary name must match your Ethereum address record.
To set or change your primary name, visit the settings page in the ENS app.
ENS profiles are a collection of pre-defined records, which are used by other dApps. When connected to the ENS app and viewing a name you own, you will see an Edit Profile button on the Profile tab. Here you can update the specific records used for profiles.
The Owner is the ultimate owner of the name. For .eth names the Owner (formerly Registrant) of a name can change the Manager and transfer ownership. Not all names will have an owner. If you have PARENT_CANNOT_CONTROL burned as a subname, you will be considered the owner as the parent cannot take over your name.
The Manager (formerly Controller) of a name can change the resolver and add/edit records. Some dApps (eg: Fleek, OpenSea) set themselves as Manager so they can update records on your behalf. If your .eth name is wrapped, you will not have a Manager as these ownerships are now combined under just a single owner.
A Resolver is a smart contract that holds records. By default, names are set to the Public Resolver, which is developed and maintained by the ENS team and has all the standard ENS record types. This is recommended for most users, but you can use custom contracts if you'd like.
If you are using an older version of the resolver, you can upgrade it from within the ENS app in the More tab.
Permissions allow the owner of a parent name to remove their access to certain features on subnames. For example, by default only the parent name owner can transfer ownership of a subname. With permissions, the parent name owner can remove their ability to do so, allowing trustless subnames. Before burning any permissions, the name must first burn the ability to unwrap and the wrapper expiry must not be expired.