Start here
Before You Fix It: What This Check Means
Domain expiry is an operational single-point risk that can cause total service loss if missed. In plain terms, this tells you whether your domain could unexpectedly go offline if renewal is missed. Scavo extracts the domain from the scanned URL and queries RDAP endpoints for expiry events.
Why this matters in practice: operational drift here often causes hard-to-debug regressions across environments.
How to use this result: treat this as directional evidence, not final truth. Registry and DNS states can change outside release cycles and may propagate asynchronously. First, confirm the issue in live output: confirm authoritative registrar or DNS provider records directly Then ship one controlled change: Validate current expiry date directly in registrar dashboard. Finally, re-scan the same URL to confirm the result improves.
Background sources
TL;DR: Your domain expires soon — if it lapses, your site goes offline and someone else can buy your domain.
A lapsed domain takes your entire site offline instantly, and recovery can take days even after renewal due to DNS propagation. Worse, expired domains are actively targeted by squatters and spammers who register them within hours. Your search rankings, email delivery, and brand reputation all depend on keeping your domain active. Set auto-renewal and monitor expiry dates.
What Scavo checks (plain English)
Scavo extracts the domain from the scanned URL and queries RDAP endpoints for expiry events.
Exact logic:
Fail: domain already expired (days_until_expiry < 0).Fail: domain expires in 0–7 days.Warning: domain expires in 8–30 days.Pass: domain expires in 31–90 days (heads-up pass).Pass: domain expires in 91+ days.Warning: Scavo could not retrieve expiry data (unsupported TLD, rate limits, or registrar policy).
Scavo includes days_until_expiry, expiry_date, and domain in check details when available.
How Scavo scores this check
Scavo assigns one result state for this check on the tested page:
- Pass: baseline signals for this check were found.
- Warning: partial coverage or risk signals were found and should be reviewed.
- Fail: required signals were missing or risky behavior was confirmed.
- Info: Scavo could not gather enough reliable evidence on this run to score pass/fail confidently.
In your scan report, this appears under What failed / What needs attention / What is working for domain_expiry, followed by Recommended next steps and Technical evidence (for developers) when needed.
- Scan key:
domain_expiry - Category:
TECHNICAL
Why fixing this matters
Expired domains can take your entire site offline and can become a severe brand/security incident if ownership lapses.
This is a low-noise, high-impact operational signal: you usually act rarely, but delays are expensive.
Common reasons this check warns
- Domain really is close to expiry.
- Billing method failed for auto-renew.
- Registrar account contact/email is outdated.
- TLD/registrar RDAP data is limited or temporarily unavailable.
If you are not technical
- Ask whoever owns billing/registrar access to confirm renewal status today.
- If expiry is within 30 days, treat as priority and resolve immediately.
- Confirm auto-renew is enabled and payment method is valid.
- Re-run scan after renewal is confirmed.
Technical handoff message
Copy and share this with your developer.
Scavo flagged Domain expiry monitoring (domain_expiry). Please verify registrar expiry and renewal status for this domain, renew immediately if within 30 days, and confirm auto-renew + billing health. Share registrar proof and re-run the scan.If you are technical
- Validate current expiry date directly in registrar dashboard.
- Enable auto-renew and add backup payment method.
- Restrict registrar access with MFA and role-based controls.
- Add calendar reminders at 90/30/7 day windows.
- Keep emergency recovery contacts current.
How to verify
- Registrar UI shows updated expiry date and active renewal status.
- Domain remains in good standing (no pending delete/redemption status).
- Scavo details reflect safe
days_until_expiryon re-scan.
What this scan cannot confirm
- It does not cover every TLD in existence; unsupported RDAP mappings can return warning.
- It cannot verify your registrar account security settings automatically.
- It is not legal/ownership proof; registrar records remain source of truth.
Owner checklist
- [ ] Assign primary and backup owners for registrar account access.
- [ ] Enable MFA and registrar lock where supported.
- [ ] Verify auto-renew and payment method quarterly.
- [ ] Keep domain operations runbook with emergency contacts.
FAQ
Why would Scavo warn even if my domain is not near expiry?
Because data retrieval can fail for certain TLDs or RDAP responses. In that case, validate manually at the registrar.
Is RDAP the right source today?
Yes. RDAP is the modern standards-based replacement path for machine-readable registration data in many ecosystems.
Why does Scavo use day-based thresholds?
So teams can prioritize action before service risk becomes urgent (30 days) and critical (7 days).
If the check passes at 60 days, should we still renew now?
Usually yes if policy allows. The pass indicates current safety, not a recommendation to wait.
Sources
- RFC 9082: Registration Data Access Protocol (RDAP) Query Format
- IANA: RDAP DNS Bootstrap registry
- ICANN: Expired Registration Recovery Policy (ERRP)
Need help turning this into a registrar runbook your ops team can follow? Send support your current renewal workflow.
