AWS Security ChangesHomeSearch

AWS Route53 documentation change

Service: Route53 · 2025-09-28 · Documentation low

File: Route53/latest/DeveloperGuide/jp.md

Summary

Removed paragraph about .jp domain authorization code expiration and transfer lock procedures

Security assessment

This removes outdated domain management information but does not relate to security vulnerabilities or features.

Diff

diff --git a/Route53/latest/DeveloperGuide/jp.md b/Route53/latest/DeveloperGuide/jp.md
index 573da7e5a..a610d1d43 100644
--- a//Route53/latest/DeveloperGuide/jp.md
+++ b//Route53/latest/DeveloperGuide/jp.md
@@ -44,2 +43,0 @@ Yes.
-The .jp registry manages the authorization code with a time-to-live and it might become expired. You can refresh the auth code by removing the transfer lock (clientTransferProhibited) status from your domain if it is present. If the domain has no transfer lock, you can refresh the auth code by turning it on first, and then off.
-