Domain Expiry Dates Explained: What RDAP Shows vs What Your Registrar Shows
Expiry dates drive backorders, transfer timing, and panic renewals. Yet two dashboards in front of you show different days.
That mismatch is normal enough that it deserves its own guide. Registries, registrars, and resellers each surface time in slightly different timezones, with grace periods layered on top.
Here is how to read expiry on BenOpt, what RDAP actually stores, and when to trust your registrar email instead.
Quick answer
RDAP exposes an expiration event when the registry publishes one. Your registrar adds renewal workflow, auto-renew flags, and marketing reminders around that core date.
For planning drops or buys, use RDAP for registry truth and your registrar for what will be charged tomorrow.
The domain age calculator summarizes “expires in about N days” when RDAP returns a parseable expiry instant.
What the registry stores
Registry operators track the end of the paid registration period in their database. RDAP returns it as an event with an ISO timestamp, often in UTC.
BenOpt shows it in human-readable form inside RDAP lookup and feeds the age tool’s expiry line.
If expiry is missing, the registry may redact it or the object may be in a state where expiry is not published the way you expect.
What registrars add on top
Registrars sit between you and the registry. Their panel may show:
- auto-renew on or off
- reminders 30/15/7 days out
- additional fees if you renew after a displayed date
- transfer locks that affect whether you can move the name before expiry
None of that replaces the registry event. It interprets it for customers.
Grace, redemption, and pending delete (why dates feel slippery)
After the nominal expiry day, many gTLDs enter automated phases:
- Auto-renew grace (registrar dependent)
- Redemption where the prior owner can pay a premium to recover
- Pending delete before the name drops
During redemption, RDAP may still list the domain object with statuses you can read in what RDAP status codes mean.
The calendar date you saw last month might not mean “anyone can register it today.”
Timezones and off-by-one-day confusion
RDAP timestamps often render in UTC on BenOpt. Your registrar email might use local time. A name that “expires tomorrow” in Dublin can still be today in Los Angeles.
When negotiating transfers, cite the ISO timestamp from RDAP notes, not only the friendly sentence.
Using expiry during aftermarket deals
Sellers advertise “expires in 30 days” to create urgency. Verify:
- RDAP lookup expiry event
- Whether status URIs mention redemption or delete prohibited
- Whether DNS still serves mail you do not want to inherit
If expiry is within weeks, confirm transfer mechanics with both registrars before you pay a broker.
Pair expiry with age
Old names with far-future expiry are different from old names expiring tomorrow. Pull creation and expiration together in the domain age calculator.
For full diligence, use the aftermarket checklist.
Auto-renew: the hidden second calendar
Many founders enable auto-renew and forget. The registrar may charge before the RDAP expiry displays on a dashboard you never open.
Set reminders anyway. Card expirations still fail. Email filters still hide warnings.
If you track domains in a spreadsheet, store:
- RDAP expiry (registry)
- Registrar panel expiry (reseller view)
- Auto-renew on/off
- Last invoice date
Four columns prevent “I thought we renewed” surprises.
Drop catching and backorder services
Drop services watch registry deletion queues, not your registrar inbox. They care about the precise moment the object transitions to available.
If BenOpt expiry says 12 days out but your registrar grace says 35 days of recovery, the drop service and your renewal button are on different clocks. Read both documents before you pay for a backorder.
Transfer locks near expiry
Registrars often block outbound transfers close to expiry to reduce support chaos. If you plan to move a portfolio to a new reseller, start transfers weeks before RDAP expiry, not the night before.
Status URIs like clientTransferProhibited are your hint to read transfer policy pages.
Multi-year registration and prepaid bundles
Some founders prepay ten years to avoid thinking about expiry. RDAP may still show a rolling expiry event per period depending on registry reporting. Your registrar receipt is the proof of prepaid years, not a single RDAP screen.
FAQ
Which date wins in a dispute?
Registry data in RDAP is the authoritative registration period for policy. Billing dates follow registrar contracts.
Why does BenOpt say expired yesterday but I renewed?
Propagation and event updates can lag. Refresh RDAP after renewal completes.
Do all TLDs publish expiry in RDAP?
No. Unsupported or redacted TLDs require registry-specific portals.
Should founders sync RDAP expiry to Google Calendar?
Yes, if you operate production on the name. Add a reminder 45 and 15 days before the RDAP date, then confirm auto-renew in the registrar panel the same week.
What if expiry shows yesterday but the site still loads?
Grace periods exist. Read status URIs and registrar emails before you assume the name dropped.
Coordinating multi-domain portfolios
Agencies managing dozens of client domains should export RDAP expiry fields monthly. One missed expiry on a client redirect domain can break campaigns. BenOpt lookups are cheap enough to run as a portfolio hygiene ritual.
Pair that export with the domain age calculator when clients ask how long a redirect asset has existed. Age and expiry together tell a fuller story than either field alone.
What to do next
Look up your production domain in RDAP lookup. Compare the expiry card to your registrar panel. Set a calendar reminder using the earlier of the two if you are risk-averse.
BenOpt reads live RDAP events. Renewal execution stays in your registrar account.
Look up registry data
Paste a hostname and read registrar, status codes, and key dates in plain cards.
Open RDAP lookup