Updated
I would not replace Hostinger simply because another hosting brand appears on a shortlist. The decision is whether it is the right infrastructure route for the website work and the people responsible for it.
I currently use Hostinger around website work for hosting and domain infrastructure. That is the job I judge it on. I would not extend that into claims about performance, savings, discounts or rewards without evidence.
Choose the operating route before choosing the provider
Hosting and domains sit underneath a website. The practical question is therefore who will be responsible for that infrastructure and whether Hostinger fits the way the website work is being handled.
My first step would be to identify the person responsible for the website work, then confirm where the hosting and domain infrastructure should sit. Only after that would I choose the provider.
- Who is responsible for the website work?
- Where should the hosting and domain infrastructure sit?
- Does Hostinger fit that chosen route?
- Is there a specific, evidenced reason to use another route?
A different route wins when responsibility sits elsewhere
I would choose another route where the person or team responsible for the website work requires the infrastructure to be handled differently. I would also move away from Hostinger if the work had a defined requirement that the available evidence did not establish it could meet.
That is the limitation of this recommendation. The supplied evidence supports Hostinger as hosting and domain infrastructure used around website work, but it does not support a comparison of performance, support, security, features or price against competitors. I would not manufacture one.
Do not buy it before responsibility is clear
Hostinger is a reasonable route to consider when you need hosting and domain infrastructure around website work and have decided where responsibility will sit. I would not buy it while ownership of that work remains unclear, or when another responsible party has already specified a different route.
My decision rule is simple: define who owns the website work, decide where its hosting and domain infrastructure should sit, and use Hostinger only if it fits that operating choice.