DNS registrar Hexonet (DE) is closing down and is force-migrating all customers and domains to a different registrar called Moniker (US).

Unfortunately, they will disable DNSSEC and thus breaking (the security of) services that rely on DNSSEC being present #fail

@cstrotm Moniker.com have a very... questionable history.

https://www.domainarts.com/2014/10/07/my-moniker-account-was-breached-security-flaws-persist/

https://www.namepros.com/threads/moniker-is-done.834723/

A single incident may have been written off by some as potential user error, but with multiple unrelated users having been compromised with the only common factor being they used Moniker.com it certainly raises more concerning questions than answers.

As far as I know, they never publicly investigated what occurred.

My Moniker Account was Breached – Security Flaws Persist | DomainArts.com

DomainArts.com | Occasional Thoughts on the Science and Art of Domaining
@jtl thanks, this confirms my decision to not move to Moniker and migrate all domains to other registrars.

@cstrotm You're welcome!

Out of interest what registrar(s) did you move to and what TLDs are involved?

Alas I'm in Canada, and the local options have their own faults (usually involving naivety towards security issues), but there are some decent options if you meet a narrow criteria.

@jtl I moved to NetCup (netcup.de) — because I already have server hosting there, and to inwx.de — because I had domains there before and both support DNSSEC.

Compared to Hexonet, the DNS/DNSSEC management UI of both is less than optimal, and both are not really prepared to have customers moving DNSSEC secured domains to them (and have the domains secure during the move).

I had limited time for the move, as the shutdown of Hexonet approaches, there might be better options around.

@cstrotm Thanks for all that. Depending on how things go I may potentially move in a similar direction in the future.

I have been been in talks with Scaleway (French cloud provider that has an in-house domain registrar, see IANA ID: 74) and their support staff patiently investigated and explained me how a) account security procedures and b) abuse report handling work. Unfortunately logistical issues make some ccTLDs an issue but I suspect it will be solved at some point.