Domain status codes (EPP)
The status codes the registry publishes about the name. Most are routine; clientHold, redemptionPeriod and pendingDelete mean it is out of DNS or on its way out.
Registries attach status codes (EPP statuses) to every domain. Most are routine and describe protection or a normal stage of the life cycle: ok or active, clientTransferProhibited, clientDeleteProhibited, clientUpdateProhibited, their server… versions set by the registry, autoRenewPeriod, renewPeriod or addPeriod. They are not a problem.
The codes that take a site down:
clientHoldorserverHold: the name is removed from DNS. Registrars set it for an unpaid renewal, an unanswered contact verification or an abuse complaint.redemptionPeriodandpendingRestore: the registration has lapsed; it can still be restored, for a fee.pendingDelete: the name is days away from being released to anyone.NOT DELEGATED: the wording of the .ru, .рф and .su registry for a name that is out of DNS.
How SiteScan shows it
The codes come from RDAP or WHOIS. If any of the codes above is present, the row is red and lists only those; otherwise it is green and lists all published codes.
What to do
For a hold, contact the registrar at once: pay the renewal, confirm the contact e-mail or answer the complaint. For redemption, restore the name through the registrar before it reaches pendingDelete. Then check the registration expiry.
See this check on your own site
Run a free scan: the report shows this row for your domain along with the other checks of the site audit.
More in “Domain registration”
What SiteScan checks
TLS certificate
- TLS certificate expiry
- Outdated TLS versions (TLS 1.0/1.1)
- TLS certificate chain
- TLS certificate issuer
- Certificate signature algorithm
Domain registration
- Domain registration expiry
- Registered domain name
- Domain registrar
- Domain registration date
- Domain last updated date
- Domain status codes (EPP)
- Domain transfer lock
- Registrar abuse contact
- RDAP and WHOIS data source
Indexing
- robots.txt file
- CSS and JS blocked in robots.txt
- XML sitemap
- Sitemap index file
- Off-domain URLs in the sitemap
- Sitemap lastmod dates
- Broken URLs in the sitemap
- RSS and Atom feed
Addresses & redirects
Security headers
- HTTP security headers and grade
- Strict-Transport-Security (HSTS) header
- Content-Security-Policy (CSP) header
- X-Content-Type-Options: nosniff
- X-Frame-Options and clickjacking
- Referrer-Policy header
- Permissions-Policy header
- HSTS preload list
- CORS and cross-origin reads
- HTTP TRACE method
Delivery & reputation
- Cache-Control header for HTML
- ETag and Last-Modified revalidation
- HTTP/3 and QUIC support
- Server version disclosure in headers
- DNS blocklist (DNSBL) check
Internal links
Exposure
- Exposed sensitive files (.env, .git, backups)
- Directory listing enabled
- Public JavaScript source maps
- Exposed WordPress endpoints
Well-known files
- security.txt file
- llms.txt for AI assistants
- llms-full.txt file
- ads.txt authorized sellers file
- humans.txt file
- Well-known change-password URL
DNS & email
- MX records (mail servers)
- SPF record
- DMARC record and policy
- DNSSEC signing
- CAA record
- Nameserver redundancy
- IPv6 support (AAAA record)
- MTA-STS policy
- TLS-RPT reporting record
- BIMI record (brand logo in email)
- Wildcard DNS record
- Dangling CNAME and subdomain takeover
Privacy & consent
- Analytics and tracking scripts
- Cookie consent banner
- Privacy policy link
- Terms of service link
- Imprint (Impressum)
- Accessibility statement
Core Web Vitals
- Lighthouse performance score
- Largest Contentful Paint (LCP)
- Cumulative Layout Shift (CLS)
- Interaction to Next Paint (INP)
- CrUX field data vs lab data