How to Catch Domains with Hidden Expiry Dates

You found the perfect domain. It is taken, but it looks dormant. You run a WHOIS lookup expecting to see an expiry date so you can plan your move. Instead you get a wall of redaction. No expiry date. No registrant. Sometimes nothing but two nameservers and a status field.

Every guide you find says the same thing: just check the expiry date in WHOIS. What expiry date?

Here is the good news. The date was never the only signal. Registries can hide a date, but they cannot hide behavior. A dying domain behaves predictably long before any date matters, and those behaviors are always public. This post shows you exactly what to watch, why the old approach fails, and how to monitor a domain for expiration even when its record tells you nothing.

Why Domain Expiry Dates Disappear from Public Records

Most people assume a missing expiry date means privacy protection is on. That is only part of the story. There are three distinct reasons a domain expiry date can vanish from public view, and they require different responses.

Privacy Redaction: GDPR and Friends

Since the GDPR took effect in 2018, most gTLD registries redacted registrant contact data by default. RDAP, which became mandatory for gTLD registries in January 2025, standardized tiered redaction across the industry. The key point most guides miss: privacy redaction usually hides who owns the domain, but the expiry date typically remains visible for gTLDs under ICANN contract.

The real problem is not privacy law. It is registry policy.

Registry Policy: The TLDs That Simply Do Not Publish Dates

A growing list of ccTLD registries made a deliberate choice to withhold expiry dates from public WHOIS and RDAP. Their reasoning is anti-poaching. They know the expiry date is the number one signal that domain investors and drop catchers watch, so they removed it.

Here is the confirmed list as of 2026:

DENIC, SWITCH, and SIDN are the three most commonly cited examples, but .ai and .nz are increasingly relevant as both TLDs have grown in popularity among startups and investors.

The Thin Registry Problem: When the Date Lies

There is a third scenario that catches even experienced domainers off guard. The .com and .net registries run a thin model. The registry holds minimal data and the registrar holds the rest. When a domain expires, the registry automatically adds one year to the expiry date to keep DNS resolution active during the grace period. The registrar can still delete the domain within roughly 45 days.

The result: WHOIS can show an expiry date a full year in the future for a domain that is already expired and heading toward deletion. The date is visible, but it is wrong. Monitoring the date alone gives you false negatives and false positives in equal measure.

The fix is to read EPP status codes instead of dates. Codes like autoRenewPeriod, redemptionPeriod, and pendingDelete tell you the truth about where a domain sits in its lifecycle, regardless of what the date field says.

Rate Limiting and Captchas

Even where the data exists, port 43 WHOIS is heavily throttled. The .nz registry moved expiry data to a captcha-protected web lookup specifically to prevent automated monitoring. If you are trying to poll WHOIS programmatically, you will hit a wall regardless of what the record contains.

Why "Just Use a WHOIS Monitor" Fails

Every existing domain monitoring tool, from DNS Spy to SecurityBot to Uptime.com, works the same way. They query one field: the expiry date. When that field is absent, redacted, or wrong, they go blind.

That is technically correct. No tool can look up a date that does not exist. But that framing misses the point entirely. You do not need the date. You need to know when the domain is about to become available, and a domain approaching death behaves in ways that are impossible to hide.

The mindset shift is this: stop monitoring the record. Monitor the behavior.

A domain that is about to expire or drop shows detectable changes across five public signals, often weeks before any date would have told you anything.

The 5 Behavioral Signals That Reveal a Hidden Expiry

Signal 1: Nameserver Changes (The Loudest Signal)

When a domain expires, the registrar typically takes control of the nameservers and points them to a parking or expiry page. If a domain was running custom nameservers like ns1.hostgator.com and suddenly flips to ns1.expireddomains.net or Sedo or Dynadot parking nameservers, that is the single strongest signal that the domain has expired or is in the process of expiring.

Why this beats WHOIS: nameserver records are never redacted. They are part of the public DNS zone and they are required for the domain to resolve at all. No registry can hide them without breaking the internet. Owners also rarely update their own nameservers unless they are actively managing the domain, so a change here almost always means the registrar did it automatically after non-renewal.

Manual check: run dig NS domain.tld or use any DNS lookup tool. Compare the result to what the domain was using last week.

Signal 2: Website Content and HTTP Behavior

A live website that suddenly serves a parking page, a redirect to a registrar expiry notice, or a "this domain has expired" banner is telling you everything you need to know. Even more telling is the difference between a domain that returns connection refused (DNS removed entirely) and one that returns a 200 with parking content.

A domain that resolves to a parking page is a domain whose owner has stopped investing in it. That is a stronger expiry signal than any date field.

Manual check: visit the domain in a browser, or run curl -I domain.tld to see the HTTP status and any redirects.

Signal 3: DNS Record Decay (MX, TXT, SOA)

Email is usually the first casualty when a domain owner stops paying attention. MX records disappear. SPF and DKIM TXT records get dropped. The SOA serial number changes when the zone is updated by a new party.

The sequence matters. In a typical expiration cascade, MX records die first, then nameservers flip to parking, then the website serves a parking page, then the domain drops from the zone entirely. You can watch this cascade happen in real time, and each stage gives you a clearer picture of how close the domain is to release.

Manual check: dig MX domain.tld and dig TXT domain.tld. Compare against historical records using a tool like SecurityTrails or your own DNS history.

Signal 4: EPP Status Codes

Even in redacted RDAP responses, EPP status codes are almost always published. They are part of the registry's operational data, not the registrant's personal data, so GDPR and similar laws do not apply to them.

The code you want most is pendingDelete. It means the domain has finished the redemption period and will be released within approximately five days. This code is always public, even for TLDs that hide everything else.

Other codes to watch:

One caveat: some ccTLDs like .fr do not use the standard pendingDelete code. Check the lifecycle rules for your specific TLD.

Signal 5: Certificate Transparency Logs

Every TLS certificate issued for a domain is logged publicly in certificate transparency logs, searchable at crt.sh. A domain whose certificate lapses and is never renewed is a domain whose owner has stopped maintaining it. This signal is fully public, impossible to redact, and timestamped to the second.

If a domain had a certificate for years and suddenly stops renewing it, that is a strong signal the domain is abandoned, often months before any expiration event.

Manual check: search the domain at crt.sh and look at the issuance history.

How to Monitor a Domain When You Cannot See Its Expiry Date

The Manual Way (Free, Tedious)

You can check all five signals yourself with free tools. It takes about ten minutes per domain per week. Dig the nameservers, curl the website, check RDAP status codes, search crt.sh. This works fine for one or two domains. It collapses completely at ten.

The Automated Way: Behavioral Monitoring

This is where Domainyze comes in. Instead of polling a date field that may not exist, Domainyze watches the domain's actual state across all five behavioral signals simultaneously.

Here is what Domainyze tracks for every monitored domain:

• Nameserver changes, including flips to known parking or auction platforms
• DNS record changes across A, AAAA, MX, TXT, and SOA
• Website status and content changes, including parking page detection
• RDAP status code transitions, including the shift to pendingDelete
• Availability status flips, alerting you the moment a domain becomes registerable

The critical differentiator: Domainyze does not rely on registry-published expiry dates. It detects the behavioral cascade that precedes a drop. That means it works on .de, .ch, .nl, .ai, .nz, and any other TLD that hides or fudges its dates. It also works on .com and .net, where the date is visible but frequently wrong.

When a signal fires, you get an alert. You then have time to place a backorder or prepare to hand-register the domain the moment it drops.

Pairing Monitoring With a Backorder

Monitoring tells you when to act. A backorder executes the catch. The two are complementary, not competitive.

If you see nameservers flip to an auction platform like GoDaddy Auctions or NameJet, that is your signal to bid, not to wait for a drop. Many expired domains never reach public availability because the registrar auctions them during the redemption period. Behavioral monitoring catches this too, because auction platform nameservers are a distinct, recognizable pattern.

For domains that do reach the drop, services like DropCatch, SnapNames, and NameJet compete to register the domain the instant it is released. Your monitoring alert gives you the heads up to place your backorder before the drop happens, not after.

Registry Expiry vs. Registrar Expiry: Why Some Visible Dates Are Wrong

The .com and .net registries use a thin model. The registry database holds the domain, the nameservers, and the expiry date. The registrar holds everything else, including the registrant's actual renewal status.

When a .com domain reaches its expiry date, the registry automatically renews it for one year. This keeps the domain resolving while the registrar attempts to collect payment from the registrant. The registrar then has roughly 45 days to delete the domain if the registrant does not pay. During this window, WHOIS shows a date one year in the future, but the domain is functionally expired.

This is why the common advice to "just check the expiry date" is dangerous. The date can be a full year off in either direction. The rule is simple: trust status codes over dates, and trust behavior over both.

The Same Approach Protects Your Own Portfolio

Everything in this post applies in reverse. If you manage domains for clients or run a portfolio, behavioral monitoring catches renewal failures before they become losses. A missing MX record or a nameserver change on a domain you own is an early warning that a renewal did not process, even if the WHOIS date looks fine.

Domainyze monitors your own domains with the same behavioral signals, so you get alerted to problems that a date-based monitor would never catch.

Frequently Asked Questions

Why doesn't WHOIS show an expiration date for some domains?

Three reasons. First, privacy redaction under GDPR and similar laws hides registrant data, though this usually does not affect the expiry date itself. Second, some registries like DENIC (.de), SWITCH (.ch), and SIDN (.nl) deliberately withhold expiry dates to prevent domain poaching. Third, some registries like NZRS (.nz) moved expiry data behind captcha-protected web lookups to block automated monitoring.

Can I find the expiry date of a .de, .ai, or .nz domain?

Not through public WHOIS or RDAP. These registries do not publish expiry dates. Your options are to contact the registrar directly (if you know who it is), use historical WHOIS archives, or monitor the domain behaviorally for signs of expiration.

Does WHOIS privacy hide the expiry date?

Usually not for gTLDs. Privacy protection typically redacts the registrant's name, email, and address, but the expiry date remains visible because it is operational data, not personal data. The TLDs that hide expiry dates do so as a policy choice, not because of privacy law.

What is the difference between registry expiry and registrar expiry?

Registry expiry is the date in the registry's database. Registrar expiry is the date the registrar shows to the registrant. For .com and .net, these can diverge by up to 45 days because the registry auto-renews expired domains while the registrar decides whether to delete them. Always check EPP status codes to know the real state.

How do I know when a domain will drop if there is no date?

Watch for the behavioral cascade: MX records disappear, nameservers flip to parking, the website serves a parking page, and the EPP status shifts to pendingDelete. The pendingDelete code means the domain will drop within approximately five days. This code is public even for TLDs that hide all other data.

Is monitoring a competitor's domain expiration legal?

Yes. All the signals described in this post are public data. DNS records, HTTP responses, EPP status codes, and certificate transparency logs are openly accessible to anyone. You are not accessing private information.

Should I monitor, backorder, or both?

Both. Monitoring tells you when something is happening. A backorder executes the registration when the domain drops. If you only monitor, you might miss the narrow window to act. If you only backorder without monitoring, you are relying on luck. The combination gives you the best chance of catching the domain.