Basics
My domain registration is about to expire
What 13x checks
This is rule basics.domain-expiry in the public registry: Domain registration is not about to lapse. It runs on every audit, against the pages we actually fetched, and its result is derived from the response rather than estimated.
- Surface
- Basics
- Score weight
- 8 of the readiness score
- Scope
- Runs on every audited page
- Applies
- Only where the market or the page shape makes it relevant
Registry version 2026-07-30. Every rule is published, and the audit is deterministic — the same page produces the same finding every time.
The fix
The same text the audit hands you when this check fails on your own site.
The registration expires on ( days).
Do three things now:
1. Turn on auto-renew at your registrar. 2. Check the card on file has not expired. This is the actual failure mode — auto-renew is on, the card is dead, and the renewal notice goes to an address on the domain that is about to stop working. 3. Set the registrar contact to an address on a different domain, for the same reason.
When a domain lapses, everything goes at once: the site, the email, and any account whose password reset depends on that inbox. Recovery inside the redemption period costs a premium; after it, the name goes to auction.
Renewing for several years at once is cheap insurance.
Does your site have this problem?
13x checks this and 112 others against your live URL in about 30 seconds. No account, and every finding comes with the fix for your framework.
No signup. Results in 30 seconds.
More basics checks
- My site is not served over HTTPSServed over HTTPS with a valid certificate
- My TLS certificate is expiringCertificate is not about to expire
- How to redirect HTTP to HTTPSHTTP redirects to HTTPS
- My 404 page returns a 200 statusMissing pages return a real 404
- My certificate does not cover wwwCertificate covers apex and www
- Should I use www or non-wwwOne canonical host (www or non-www)