This guide explains the difference between traffic obfuscation and cloaking, and what is (and isn’t) supported on our platform.

🔍 What Is Traffic Obfuscation?

Traffic obfuscation is the process of disguising, masking, or manipulating traffic behavior to make it look natural or to hide its true source. Common obfuscation techniques include:

• Referrer spoofing – Hiding or faking the HTTP referrer header

• Proxy chaining – Routing traffic through different proxies or domains

• Click or behavior simulation – Using bots or scripts to simulate human engagement

• Script-based masking – Modifying what analytics or tracking systems can see

Why people use it: Often done for CTR manipulation, stealth SEO strategies, or traffic laundering.

❌ Is this supported at PBN LTD?
No, PBN LTD does not support or provide traffic obfuscation tools, proxies, or click simulators as part of our hosting infrastructure. If you require these kinds of setups, you’ll need to implement them externally on your own systems or through third-party services.

🛡️ What Is Cloaking?

Cloaking is when a website shows different content to different users or bots based on their IP address, user-agent, or behavior. It’s typically used to:

• Serve one version of a page to search engines (e.g. clean content for indexing)

• Show a different version to real visitors (e.g. an affiliate or sales page)

This can be done with:

• JavaScript-based cloaking scripts

• PHP-based user-agent filtering

• Server-side cloaking systems (depending on your setup)

✅ Is cloaking supported at PBN LTD?
Yes. While we don’t offer native cloaking features, you’re free to install and run cloaking software or scripts within your websites just like on any standard host. Whether you’re using a custom-built system or a popular third-party cloaker, you can add this functionality directly within your static site or WordPress setup.

🧠 Important: The setup, testing, and maintenance of cloaking is your responsibility. If it breaks or misbehaves, we’re happy to help at the hosting level—but we don’t debug cloaking code itself.