Skip to content
puluno

Explorer & cloud

Hosting blocks cloud scan

Explorer on puluno.io cannot fetch the homepage — timeout, empty response, or OG finding “hosting blocked”. What to do.

Typical symptom

Scan failed / timeout from cloud but the site loads in your browser. Finding og_image_hosting_blocked.

Puluno modules

GuardSEO

Undo change

No — info / hosting only

Issue codes

og_image_hosting_blocked, og_image_unreachable

What you see

  • Explorer reports scan failed, timeout, or missing OG/meta.
  • Findings og_image_hosting_blocked or og_image_unreachable.
  • In your browser the site loads fine.
  • With the Puluno WP plugin: Center shows plugin facts, but cloud scan without the plugin fails.

Why it happens

Explorer fetches from the Puluno cloud VPS (167.233.253.72), not your laptop.

On shared hosting (e.g. FastComet FastCloud Extra), Imunify360 / CSF / firewall run for the whole node. The host usually will not whitelist one account’s IP list — that is not a Puluno bug.

Typical cases:

  • Datacenter IP looks like a bot — TCP timeout, 403, Imunify HTML challenge.
  • Too many rapid requests from the same IP to the same domain — automated protection blocks them.
  • Geo / ModSecurity rules.
  • Site works otherwise — block targets automated fetch only.

What Puluno does

PhaseWhat happens
DiagnoseExplorer separates timeout vs 403 vs Imunify HTML vs missing OG
Load limitsCloud caps scan frequency per IP and per domain (fewer false blocks)
WordPress + pluginPuluno SEO sends OG/meta from admin — cloud may skip homepage fetch
VerifyAfter plugin install or a pause, same URL in Explorer again

Puluno does not bypass WAF — on shared hosting, do not expect a permanent VPS IP whitelist.

Step by step

  1. Confirm browser vs Explorer — cloud-only issue.
  2. Do not open a “whitelist IP” ticket on FastComet shared — typical answer: not available on shared; reduce scan rate or use the plugin / client VPS.
  3. Client WordPress: install Puluno SEO — Center and heartbeat send facts without public VPS fetch. Main path for FastComet client sites.
  4. Wait a few minutes between rescans — do not hammer “Refresh” ten times per minute.
  5. Deep sitemap sample only when needed — each URL is another VPS request.
  6. Social OG: Facebook Sharing Debugger — different IP than Puluno.
  7. Verify: same URL in Explorer after plugin or pause.

If the client insists on whitelist

  • Their own cloud VPS / dedicated — CSF whitelist is manageable there.
  • You do not need to move Puluno infra — the limit is the client’s shared hosting policy.

Rollback — undo the change

No Apply change — nothing to roll back.

When it is not Puluno

  • Site is actually down — Guard uptime.
  • Cloudflare Under Attack — CF settings.
  • Audit without cloud — WP Center on the full site.

Related: OG image, Google not indexing.

Related situations

Search Console connection & property →