Domain transfer lock
Whether the registrar transfer lock is set. With it on, nobody can move the domain to another registrar without unlocking it first.
The transfer lock is the clientTransferProhibited status (or serverTransferProhibited, set by the registry itself). While it is on, the registry refuses any request to move the domain to another registrar. To transfer the name you first have to unlock it in your registrar account and request the authorisation (EPP) code.
Why it matters. Domain hijacking usually goes through a transfer: someone gets into the registrar account or the owner's mailbox and moves the name to a registrar under their control. Getting it back takes weeks of disputes, while the site and e-mail are in someone else's hands. The lock adds a step that an attacker has to take visibly first.
How SiteScan checks it
The row appears only for registries that publish EPP status codes. DENIC (.de) and the .ru registry publish no lock state at all, and reading their silence as "unlocked" would be wrong, so for them there is no row. Green "On" means a transfer prohibition is set; amber "Off" means none is.
How to turn it on
In the registrar's control panel look for "Registrar lock", "Transfer lock" or "Domain lock" and enable it. Unlock only for a transfer you are doing yourself, and turn it back on afterwards. For high-value domains ask for a registry lock (the server… statuses). See also the registry status.
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