What '.NET Expired Domains' Are
'Expired' here means .net registrations that moved beyond the active period for the prior registrant and are going through post-expiration recovery steps on their way to release. The practical question for buyers is timing: availability changes across Auto-Renew Grace, Redemption Grace, and pending delete.
During the recovery stages, the domain may appear in different states in registry and registrar interfaces. Use live status signals during due diligence rather than relying on a single fixed date.
How the .net expiration lifecycle works
For .net, the post-expiry recovery sequence typically follows the gTLD pattern under ICANN policy:
- Auto-Renew Grace Period: up to 45 days after expiry. In this window, the registrar can attempt renewal or recovery steps depending on its workflow.
- Redemption Grace Period (RGP): 30 calendar days after the registrar deletes the domain registration. During RGP, DNS resolution is disabled and attempted transfers are prohibited. Restoration can be requested through the registrar workflow during the window.
- Pending delete: after RGP ends without restoration, the domain enters a final pending-delete stage. For many gTLDs, this stage is commonly around 5 calendar days.
- Release for general registration: after pending delete completes, the registry purges or releases the name back into the pool of available domains.
Registry and registrar workflows can affect how a specific name appears in interfaces. Due diligence should focus on live status signals.
Registration and transfer expectations for .net
Renewing, redeeming, and restoring
During the Auto-Renew Grace Period, a registrar can accept renewal requests through its workflow if the domain is still inside the allowed recovery window. During Redemption Grace, restoration actions require a restore request via the registrar workflow. In RGP, DNS resolution is disabled and attempted transfers are prohibited by policy.
Transfers and registrar workflows
Transfers depend on the current lifecycle state:
- If the domain is in Redemption Grace, attempted transfers can fail because the policy requires transfers to be prohibited in that state.
- After the domain is released and newly registered under a new term, normal gTLD transfer flows apply for the new registration.
Account workflow matters even after the domain is newly registered. ICANN's Transfer Policy requires registrars to impose a 60-day inter-registrar transfer lock following a Change of Registrant. If a purchase plan includes changing registrant details before a transfer, the lock can extend the time until the next move. Confirm the timeline with the target registrar.
What the table in Karma.Domains represents
The table lists current .net Expired Domains candidates and overlays research signals needed for due diligence.
Typical columns include:
- Source and provider fields such as price or re-registration timing when available.
- Karma Score, calculated from Wayback Machine evidence.
- Wayback age and language coverage.
- Link and backlink indicators from third-party metrics such as Majestic and Moz.
When the underlying source supports marketplace-style rows, the table can also include timing fields such as an end time, plus bid or price context. Those fields help map an intended action window to the likely lifecycle stage.
Due diligence checklist for .net expired names
- Identify lifecycle stage from live status signals. Auto-Renew Grace, Redemption Grace, and pending delete imply different recovery and transfer expectations.
- Plan around the timeline. Avoid last-minute actions when the name is close to the end of the recovery window.
- Review Wayback snapshots across years. Look for consistent topics and avoid redirect-only archives, spam-like pages, or abrupt topic shifts.
- Check referring pages and anchor context shown in Karma.Domains. Confirm that linking pages match the intended niche and that anchor patterns look natural.
- Screen for legal and trademark exposure using the domain string and likely brand variants for the target markets.
- Validate third-party link metrics with archive evidence. Karma Score and link metrics support triage, but the historical content should explain what a future rebuild can support.
- If a transfer is part of the plan, confirm registrar prerequisites. Authorization code or EPP requirements, domain unlock status, and any registrant-change locks can affect transfer timing.
How Karma.Domains helps
Karma.Domains consolidates due diligence signals for .net candidates so screening can be done faster:
- It provides an hourly view of .net candidates.
- It overlays Karma Score and Wayback-derived evidence to screen archive consistency.
- It adds third-party backlink indicators and supports faster review of referring pages and anchor context.
- It gives a single table format that coordinates lifecycle timing with research fields for safer registration decisions.
Bottom line
.NET Expired Domains move through an Auto-Renew Grace phase, then a Redemption Grace period, then a pending delete stage, and only after that becomes available for general registration. Use live status signals for timing, and use Wayback plus link context in Karma.Domains to reduce history-related risk before registration or purchase actions.
