> ## Content Index
> Fetch the complete content index at: https://iris-on-bookrest.info/llms.txt
> Use this file to discover other available public pages before exploring further.

# Migrating My Domain to Cloudflare
- URL: https://iris-on-bookrest.info/en/blog-domain-transfer-en/
- Published: 2026-08-19T10:49:04.000Z
- Updated: 2026-08-19T10:58:08.000Z
- Description: I've migrated my blog's domain to Cloudflare. Reasons include centralized DNS settings, an annual operational cost reduction of approximately 800 JPY, and long-term trust in the service. I'll also explain the specific migration steps, providing useful information for efficient domain management a...
- Author: やまぐろ
- Tags: ブログ運用, ノウハウ, Cloudflare, en

Hello everyone, I'm a professional engineer.  
It wasn't long ago that [this blog celebrated its 5th anniversary](https://iris-on-bookrest.info/blog-5th-anniversary/), and I mentioned that domain migration seemed bothersome, so I decided against it. But surprisingly, I've already migrated it to Cloudflare! This post will tell you all about it.

## Why I Chose Cloudflare

### Service Consolidation

Since I frequently open the Cloudflare dashboard anyway, I figured why not migrate everything here! That was the first point. Not having to jump between different platforms when tweaking DNS settings is a subtle yet significant benefit.

### Lower Operational Costs with Cloudflare

Cost was another factor. Cloudflare only charges the wholesale cost to the domain registrar plus the ICANN public fee (approximately $0.18-$0.20), without adding any profit margin. This policy means that domestic "service maintenance adjustment fees" that typically occur in Japan are avoided. Based on my estimates, this should result in cost savings of around 800 JPY per year.

### Trust Built Over Years of Use

I've been using Cloudflare for over a decade, so I have a significant amount of trust in them. In the past, I recall their CDN occasionally going down and causing errors, but that's rarely the case nowadays. Plus, as a service designed to mitigate security risks, it provides an additional layer of peace of mind.

## Rough Migration Steps

While you can easily find this information by searching online or asking AI, I'll outline it here just in case.

- ① Disable "WHOIS Privacy Protection" on the original domain provider and note down the AuthCode (authorization code).
- ② Initiate the transfer request with the new domain provider, using the AuthCode you just noted.
- ③ Approve the transfer request (via email) from the original domain provider.
- ④ Wait!

That's roughly it. The actual process took less than an hour! Most of that time was probably spent waiting!

## Conclusion

I've been tinkering with my infrastructure a lot over the past month, but it seems things will finally settle down now.

---

*This article was translated from the [original Japanese version](https://iris-on-bookrest.info/blog-domain-transfer/) (ドメインをCloudflareに移管してみた) using Gemini API.*