Website Hijacked/Redirecting

[Admin]

From the article: Why does my domain redirect to suspendeddomain.org / suspended-website.com

@Admin

You are moving the domain to another hosting provider

If you are trying to move your website to another hosting provider, you’ve probably already set up the account with your new provider, updated your domain’s nameservers and removed the domain name from your InfinityFree account.

However, after updating your domain name, it can take up to 72 hours for everyone to connect to your website at the new hosting provider. This is caused by a process called DNS Caching, which is explained in more detail in this article .

Because of this process, you, and many of your visitors, are still connecting to our hosting servers, even though your domain has been configured to send people somewhere else. And because you already removed the domain from your InfinityFree account, they will see the suspendeddomain.org page.

Unfortunately, there is nothing anyone can do to force everyone to connect to your new hosting provider. Everyone is at the mercy of the network settings of the visitors of your website.

But there are ways to soften the effects on your website.

First of all, when moving your domain elsewhere, you should keep the old account active for a few more days while the traffic moves over. You can continue to serve your old website on the old account (although you risk losing data if people make changes on the old account), or you can replace your website with a maintenance page telling them about the migration. In any case, keeping the old site active for a few more days allows you to choose what your visitors will see while you’re moving the domain.

If you’ve already removed the domain, you can add the domain again to your old account. It’s very important you use the same account that had the domain name before. If you have other accounts, they may have different IP addresses, which are not the IP addresses your visitors are still connecting to.

This is completely normal. It’s caused by DNS cache, and we don’t have any control over that.