Problems with the letter "ñ" when routing e-mails

Hello colleagues,
I am contacting the community, to know if you can help me with this problem.

I currently have a domain with “ñ”, ganareseñ, this has brought me a lot of problems with email, SEO, google … And now tired I have decided to route all emails to

I have seen the fantastic option of Cloudflare and I have used it in other domains, however, I think that because I have a domain with “ñ” it does not let me.

I am attaching a couple of screenshots, in case I can get some help.

Thank you very much!


I wanted to add to this thread, that although it does not recognize the records to activate the routing, it does not allow me to delete them either, because it tells me that I have to deactivate it, but it is not active.
Thanks a lot!

According to the documentation for the e-mail routing beta, domain names with international characters are not supported at this time

1 Like

Thank you for the information. I did not know that. Likewise, I would like to say that I run into the problem that I can’t remove the MX records that routing has created. I can’t disable it, I have to delete the site and recreate it from another account. I hope this helps. Thank you very much for the answer.

Does it let you unlock the domain without removing the DNS records? Once they’re unlocked you can then remove the DNS records yourself.

If both of these options here don’t work on domains with international characters, then that seems like a rather serious bug in Email Routing and likely needs to be escalated.

1 Like

Thanks, the problem is that I can neither activate nor delete. In the DNS record it appears as active, and in the email routing it appears disabled. I can neither modify the MX nor delete them.

I have deleted the domain, but in that account I recover the configuration when I create it again. That is why I have thought about registering it in another one.

Can you think of another solution?


Thanks, this issue was escalated to the team from another thread detailing the same.

Adding the domain to a different Cloudflare account would create the configuration from scratch which would work around this problem in the way you expected. It is not an ideal situation to be in, but would work.

Thank you, I saw that this is an unusual situation. Erisa, thanks for your help. You guys are great!

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.