I am using my website script I have for a new site and so I have purchased new hosting and uploaded my script from my other host debtfreescotland.org.uk to my new hosting using the domain trustdeedweb.com When trying to reach trustdeedweb.com it re-directs to http://www.debtfreescotland.org.uk I'm not sure why it's re-directing, I did have a 404 redirect to that page but I changed this in my .htaccess file..
Did you complete a search replace on the database file to remove the old link and replace it with the new one?
The answer would be: "Because the domain specifically designed to redirect at debtfreescotland.org.uk for both Human (visitor) and Bots (Search Engine)." (Your server work correctly. It didn't redirect domain, the code in your html is) There is META Refresh on the site (index file) <!DOCTYPE HTML> <html> <head> <meta http-equiv="Refresh" content="5; url=http://www.debtfreescotland.org.uk/"> </head> </html> HTML: Look at the trustdeedweb.com/robots.txt and you would see the domain is intentionally redirected to debtfreescotland.org.uk (could be caused by using files from Debtfreescotland.org.uk) Even the sitemap is redirected to trustdeedweb.com/sitemap.xml (could be caused by using files from Debtfreescotland.org.uk). What to do to solve the problem: Just remove the Meta Refresh (if you use html static files) Check the files and remove unnecessary codes/files. Best solution: In your new hosting, just Delete unnecessary files in your home directory (which belong to domain). Before copying the files it is best to modify so many codes. It is not that hard and could be done in just less than few hours (half hour is fastest while two days is longest). You were using static HTML files (Custom site) so it is not that hard to modify the codes. The downside is there would be so much files to modify. I believe you can do this by yourself. Consider to use Canonical to make it easier for SE to rank your site (not very important in your case)
I've seen this before -- to that exact same URL -- you've been hacked by a certain bot. Most likely you had some self modifying code or some other vulnerability. You'll need to do a full code audit first to find all the files that were modified by the hack to get them back to baseline, and then figure out how they got in the door and plug that hole... Is the site built with custom code or an off the shelf system? Does the custom code have injection vulnerabilities -- is the off the shelf system updated to the latest version or is it lagging behind? Is the servers' version of the languages and database engines up to date?