What Exactly Is an ENS Active Name?
An ENS active name is an Ethereum Name Service (ENS) domain that is currently registered and owned by an address on the Ethereum blockchain, with its record set (usually a resolver and a target address) in a state that enables resolution. The name is not expired, not in a grace or auction state, and has a valid registration that has not been reclaimed by the registry. Active names are the functional backbone of ENS: they serve as human-readable aliases for cryptocurrency addresses, content hashes, and metadata.
To remain active, a name must be periodically renewed. ENS operates on a yearly rental model, not a permanent purchase. When you register, you pay for a fixed duration, after which the name enters a grace period (typically 90 days). If not renewed, the name becomes available for anyone to register. Once the registration expires and the grace period passes, the name is deactivated and the previous owner loses control. An active name is therefore one that is within its paid period or grace period, but crucially, still owned by the registrant — the owner's control is defined by the ENS registry contract. For precise record management, one must align the resolver and the public key (or other records).
How Do Registration and Renewal Impact Active Status?
Two key events determine whether an ENS name remains active: initial registration and subsequent renewals. The initial registration locks the name for a minimum of one year (though longer periods are common). The ENS protocol enforces that each registration is associated with a registration date and an expiration date. The active status is derived from the expiration date: if the current block timestamp is less than the expiration timestamp, the name is active; if not, it enters the grace period and eventually becomes inactive.
Renewals extend the expiration timestamp. This can be done at any time before or during the grace period. Many users set up automated renewal via smart contracts or services to avoid accidental deactivation. The cost of renewal is paid in ETH, proportional to the length of the extension (currently approximately $5 per year for a .eth name, but subject to gas and market fluctuations). Active status is binary — the name either resolves or it does not — but the user experience depends on what records you attach. For example, if you point your ENS name to an outdated address, resolution will still work, but the data may be stale. Keeping an ENS name active requires not just financial maintenance but also careful record management, known as ens recovery methods for cases where private keys are lost or the ownership address changes.
What Are the Most Common Questions about Subdomains and Active Status?
1. Do Subdomains Have an Independent Active Status?
Yes and no. ENS subdomains (e.g., subdomain.eth) are separate NFTs in the ENS registry. Their active status is determined by the subdomain's own registration — not the parent domain's. However, in practice, the parent domain controls the resolver and the owner of the subdomain's registration. If the parent domain expires, the subdomain's registration remains valid until its own expiration date (assuming it was registered independently). The subdomain's record set (address, text records, content hash) continues to resolve as long as the resolver is set and the subdomain's registration has not expired. Once the subdomain's registration expires, it becomes inactive regardless of the parent's status.
2. Can a Subdomain Be Active While the Parent Domain Is Inactive?
Technically, yes — because the ENS registry treats each subdomain as an independent entity with its own owner and expiration. However, the parent domain (the .eth name) is required for the subdomain to be resolvable in the ENS resolution process. If the parent domain is inactive (expired or reclaimed), the resolver for the subdomain may not be reachable through the standard ENS resolution path. In practice, most resolvers and dApps will fail to resolve a subdomain if its parent is inactive, because the resolution requires the parent name's controller to update the subdomain's record. This is a nuance: active subdomains under an inactive parent are effectively orphaned. They exist on-chain but are not resolvable via typical ENS libraries. To restore functionality, one must either renew the parent or re-register the subdomain under a new parent (which requires the parent's owner to re-assign it).
3. How Do I Check the Active Status of a Subdomain?
Use the ENS manager app (ens.domains) or an etherscan-based tool that queries the ENS registry contract. Input the subdomain (e.g., subdomain.eth) and check the registration record — the 'expiry' field tells you if it is active. Additionally, check the parent domain's registrar to see if it is still valid. If either is expired, the subdomain may be inactive. For bulk checks, use ENS subgraph queries. The active status can change at any time due to renewals or expiration, so real-time verification is recommended.
How Do Resolution and Records Affect Active Name Functionality?
An active ENS name is only useful if it resolves to the correct records. The ENS resolution process involves:
- Resolver contract: Maps the name to a resolver address. The resolver implements the ENS resolver interface.
- Records: Stored in the resolver — typically an address (for ETH or other cryptos), content hash (for IPFS/Arweave), or text records (e.g., email, URL).
- Name hash: A cryptographic hash of the name (e.g., keccak256 of "vitalik.eth") used to index records.
Even if the name is active (registration is valid), resolution can fail if the resolver is incorrectly set or points to a resolver that does not support the requested record type. For example, a common issue: a user registers an ENS name (so it is active), sets their ETH address, but then changes wallets and does not update the resolver — the name still resolves to the old address. Active status does not guarantee correct resolution; it only guarantees that the name is controlled by the owner. Therefore, when verifying an ENS name, check both the registration expiration and the resolver records.
When dealing with enterprise or multi-signature setups, the process of updating resolvers and records is often formalized as part of a larger on-chain governance. This is where Crypto Domain Requirement Gathering becomes critical — defining which addresses, text fields, and content hashes must be stored before deploying the resolver and setting records. Without proper requirements, an active name may resolve to stale or incorrect data, undermining trust.
What Happens When an ENS Name Expires — Can It Be Reactivated?
When an ENS name expires, it goes through a strict lifecycle:
- Grace period (90 days): The name is still active — the owner can renew at any time. Resolution continues to work.
- Reclaim period (28 days): After grace, anyone can start a "reclaim" process by paying a fee. The previous owner loses control but still has a 28-day window to reclaim by paying double the registration fee.
- Deactivation: After reclaim, the name is freed and anyone can register it as a new name. The previous owner has no rights.
Active status is lost after the grace period. Reactivation is only possible by re-registering the name as a new registration — there is no "restore" function. During the grace period, the owner can simply renew and the name stays active. After grace, the previous owner must outbid other registrants in a auction-style reclaim or wait for the name to become free and register it fresh (which may require a high gas fee and competition). The ENS smart contract does not store historical ownership data for recovery; once expired, the name is reset. This is why it is vital to set up renewal reminders (often via ENS dApps or third-party services) and understand ens recovery methods before the name enters the grace period. Note that ENS names with high-value addresses or subdomains require proactive management — automatic renewal via a smart contract or a multi-sig wallet is recommended for enterprises.
Security Considerations for Active ENS Names
Active ENS names are subject to several security risks that can render them unusable or hijacked:
- Private key loss: The owner address controls the name. If the private key is lost, the name cannot be renewed or updated. The only recovery path is through social recovery (if set via a contract wallet) or a multi-sig arrangement. Without these, the name expires naturally.
- Resolver hijacking: A malicious resolver can redirect the name to a different address. This is prevented by using a trusted resolver (e.g., the public ENS resolver) and verifying the resolver address on-chain. Never use a resolver from an untrusted source.
- Renewal frontrunning: In rare cases, an attacker might frontrun a renewal transaction to pay a smaller fee or replace the resolver. Use a contract that checks the current owner before renewing.
- Subdomain takeover: If a subdomain owner loses their private key, the parent domain owner can reclaim the subdomain by setting a new owner — but only if the subdomain's registration has not been extended. The parent domain owner also controls the resolver for subdomains.
To maintain active status securely, consider using a hardware wallet for the owner address, setting up automatic renewals via a smart contract (e.g., using the ENS Renewer), and regularly verifying that the resolver is correct by querying the ENS registry. For high-value names, a multi-sig wallet with time-locks can prevent single-point-of-failure. Finally, always keep the registration fee funded — even a short gap can lead to expiration and loss of the name.
Conclusion
ENS active names are straightforward in concept — a registered, non-expired name — but their management involves nuanced interactions between registration, renewal, subdomains, resolvers, and security. The key takeaway: an active name is not enough; the resolver and records must also be correctly configured. For developers and power users, understanding the underlying registry contract and resolution flow is essential for reliability. Keep your names funded, set up renewal automation, and always verify resolver records. With proper planning, ENS names remain active and functional for years, providing a reliable alias for your digital identity.