Cloakd, the developer behind FluxBeam, stated on X that its Name.com representative maintained the DNS hijacking incident originated with third-party issuers rather than Name.com itself