I’ve recently been working on de-Googling and part of that has been setting up an email with my custom domain. This mostly works great, but one issue I’ve noticed is email validation on some websites detect this email address as invalid. For instance, if I have the domain [name].rocks with the email [name]@[name].rocks (with [name] being a placeholder for my name) my email cannot be used to register with the Ventra app (for getting mobile train tickets) I believe because any site that has an extension with more than four characters is detected as invalid.

I understand this is a validation issue on the end of the app dev / website, but I was wondering if people had suggestions for workarounds when they encounter this? Setting up other custom emails with forwarding? Thanks!

  • @Spotlight7573@lemmy.world
    link
    fedilink
    English
    31 month ago

    Sadly I’ve run into the same type of problem with a newer TLD as well. My solution was to get a domain in the older TLD space (e.g. .com, .net, .org). I doubt this will be the last site you run into that doesn’t support a newer TLD and the low likelihood that you’re going to be able to convince someone to fix the issue at every one of those outdated sites means that you’ll eventually need a backup domain for something.