Subdomain stopped working overnight – wrong IP not resolving

Website URL

https://pop-grafika.xo.je/

Error Message

ERR_CONNECTION_TIMED_OUT (initially)
After debugging with curl:
curl -I -v http://pop-grafika.xo.je
HTTP/1.1 403 Forbidden
X-SPS-Security-Policy-Result: business-sec

Other Information

dig pop-grafika.xo.je +short

Output:

167.206.37.145

But in the control panel, it should point to:

185.27.134.55

When I try to connect:

curl -I -v http://pop-grafika.xo.je

Output:

HTTP/1.1 403 Forbidden
X-SPS-Security-Policy-Result: business-sec

This looks like a completely different server (possibly ISP/security filtering), not InfinityFree.

What I’ve already tested

  • Tried different networks (WiFi + mobile data)

  • Used dig and curl for debugging

  • Confirmed account is active in panel

  • Verified correct IP in control panel


Questions

  1. Why is my xo.je domain resolving to a completely different IP (167.206.37.145)?

  2. Is this a DNS backend issue or something wrong with my account configuration?

Additional note

I’m currently on the free plan, and I was actually considering upgrading to premium.
However, this issue is a bit concerning since both domains stopped working suddenly without any changes on my side.

Is this something that can happen on free hosting, or should I expect more stability on premium?

Any help would be appreciated — thank you!

It means that something on your end is interfering with the DNS resolution. It can be your company, your school, your ISP, your antivirus…
But it’s not the hosting because it works for me. Our nameservers are responding the records correctly. DNS records for pop-grafika.xo.je from nslookup.io
So you must contact whoever is making this block to get the problem resolved.

As a workaround you can try changing your DNS resolvers to Google’s 8.8.8.8 or Cloudflare’s 1.1.1.1.

7 Likes

The incorrect IP (167.206.37.145) belongs to my ISP (Cablevision/Optimum), confirmed via WHOIS. Public DNS (Google/Cloudflare) returns the correct IP. It appears my ISP is intercepting DNS requests. CRAZY!!!

1 Like

ISPs have a duty of care which many take to include blocking suspect domains.

Unfortunately because free hosting domains gets a bad rep, these domains sometimes end up on block lists.

Usually you can contact your isp and ask them to remove the block though

4 Likes