Domain does not have a domain transfer lock set
- Severity
- Low
- Service
- Route 53
- Check ID
- DOMAIN_HAS_NO_TRANSFER_LOCK
What this check finds
A domain transfer lock mitigates the possibility of someone else taking ownership of your domain. Not all TLD's support this. For example, the .io domain does not support this.
Passing looks like: Domain transfer lock enabled.
How to fix it
Enable the transfer lock on the domain if your TLD supports it.
AWS console
Route53 → Registered domains → select domain → Transfer lock → Enable. Note that .io and some other TLDs do not support this feature.
Compliance controls it is evidence for
A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works
| Framework | Controls |
|---|---|
| NIST SP 800-53 Rev5 (Moderate) |
|
| NIST Cybersecurity Framework 2.0 |
|
| ISO/IEC 27001:2022 Annex A |
|
Checked on every scan
KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs