Google's Search Result Hacked? (So Confused)

[ablife]

I've been doing SEO for many years, but I'm by no means an expert. However, I just stumbled across a problem that I've never seen before and am baffled at what's going on.

Any advice would be greatly appreciated.

I own hostchecka .com which was an affiliate site for hosting that I lost interest in and eventually let die out. If you go directly to that domain now by either typing it in or copy/pasting it, you should see a "Ooops not available" message - https:// d.pr/i/hasxPn

All fine and as it should be.

Now if you go to Google and do the "site:hostchecka .com" search, you'll see something funky. In the title tag it says "Sackinima Forums" and some blurb in the description - https:// d.pr/i/tOOvD5

Now go ahead and click on that link.

It should redirect you to a forum that I've never heard of.

The site is not hosted anymore, I have full control over the DNS in Cloud Flare, the domain is still registered to me and I have control over that too.

So what the hell is going on? I'm so confused.

How is the SERP result hacked and how can I un-hack it?

Again, thank you for any help!

Btw, I never set up that redirect myself. Just noticed it the other day after going through a bunch of domains I own.

 

[Graybeard]

I don't get that? from the US -- there is an https error however (understandable)

ht t ps://w ww. google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=2ahUKEwib9eiOs4TkAhVOs6wKHfiVDp0QFjAAegQIABAB&url=https%3A%2F%2Fwww.hostchecka.com%2F&usg=AOvVaw3yjpZ34rghGcpMKny8zYz6

curl -I -Lv -A "(Mozilla/5.0)" "https://hostchecka.com/"
* Trying 23.202.231.167...
* connect to 23.202.231.167 port 443 failed: Connection refused
* Trying 23.217.138.108...
* connect to 23.217.138.108 port 443 failed: Connection refused
* Failed to connect to hostchecka.com port 443: Connection refused
* Closing connection 0
curl: (7) Failed to connect to hostchecka.com port 443: Connection refused
barry@paragon-DS-7:~$ curl -I -Lv -A "(Mozilla/5.0)" "http://hostchecka.com/"
* Trying 23.202.231.167...
* Connected to hostchecka.com (23.202.231.167) port 80 (#0)
> HEAD / HTTP/1.1
> Host: hostchecka.com
> User-Agent: (Mozilla/5.0)
> Accept: */*
>
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< Date: Thu, 15 Aug 2019 07:58:53 GMT
Date: Thu, 15 Aug 2019 07:58:53 GMT
< Connection: close
Connection: close

<
* Closing connection 0
barry@paragon-DS-7:~$

 

[ablife]

I just fixed it! thank you for the help.

Made the change in Cloud Flare to stop using HTTPS redirect for now and it works. So looks like the old host was hacked somehow because there was an HTTPS header refresh in place.