3 ms·

I asked them (Posteo) about this 2 weeks ago and below is the response I received. I'm not an expert in this area, but the response sounded reasonable to me: >

I asked them (Posteo) about this 2 weeks ago and below is the response I received. I'm not an expert in this area, but the response sounded reasonable to me: > We do not offer domain services because we do not save any personal data for any of our services. This is not possible with domains. > Domains must be registered to a person’s name and address. As a provider, we would be required to store inventory data for all customers that use their own domains with us. As a result, we would have to provide this information to government agencies when requested. > Additionally, security reasons also play a role in this decision. With customer domains, the owner of the domain is responsible for setting up security features like DNSSEC (and as a result also DANE). Even things such as SPF and other protocols for delivery would lie in the customer’s hand and could not be guaranteed by us. > Because of these reasons we have decided not to offer domain services and instead to remain consistent with our focus on data economy.

Tomte 8y ago
I got the same mail two years ago, I think (haven't kept it, but the "reasoning" sounds familiar). See, that's just half-truths that amount to lies. They claim they need to store personal information about you when you're using your personal domain. That's untrue. Only if you registered the domain with them they would need to know about you. It's also untrue, because unlike .de, many other TLDs don't require full names and addresses in WHOIS, or there are "privacy shield" services like the one nearlyfreespeech.net is operating. Security reasons. Also untrue (although it's a reasonable business decision that they don't want to handle customers calling their support with the customer's own domain set up problems). I continue to claim that there is exactly one reason they are refusing: A customer with a *@posteo.de address will pretty much never leave. I wouldn't mind very much if they admitted that, it's certainly a geeky niche to serve, but this security-and-privacy bullshit really makes me mad. Do you want to trust your privacy with a company that's lying, even if you wanted to argue that it's a white lie?

Tomte 8y ago

I got the same mail two years ago, I think (haven't kept it, but the "reasoning" sounds familiar). See, that's just half-truths that amount to lies. They claim they need to store personal information about you when you're using your personal domain. That's untrue. Only if you registered the domain with them they would need to know about you. It's also untrue, because unlike .de, many other TLDs don't require full names and addresses in WHOIS, or there are "privacy shield" services like the one nearlyfreespeech.net is operating. Security reasons. Also untrue (although it's a reasonable business decision that they don't want to handle customers calling their support with the customer's own domain set up problems). I continue to claim that there is exactly one reason they are refusing: A customer with a *@posteo.de address will pretty much never leave. I wouldn't mind very much if they admitted that, it's certainly a geeky niche to serve, but this security-and-privacy bullshit really makes me mad. Do you want to trust your privacy with a company that's lying, even if you wanted to argue that it's a white lie?