Zero Footprints.
Real Infrastructure.

How We Eliminate Footprints and Protect Your PBN

Every PBN host claims “zero footprints” on the marketing page. Most are lying by omission — their IPs, name servers, or SOA records still point straight back to a hosting pool of other PBN customers, and Google clusters that pool in a single pass.

LaunchCDN is built differently. We don’t own the IPs you deploy to. We don’t run the DNS you resolve through. We aren’t named on the SSL certificates. Every layer sits on real CDN infrastructure that millions of legitimate websites already use.

Here’s exactly what that means, footprint by footprint:

• SOA records. We use the DNS provider’s default SOA email, never one that resolves back to LaunchCDN. Sites on Amazon Route 53 get Amazon’s default, sites on Cloudflare get Cloudflare’s, and so on. Check any domain with our free SOA Checker tool.
• Name servers. We use the CDN providers’ own DNS (Route 53, Cloudflare) with randomised name servers per domain, plus other major third-party DNS hosts that serve thousands of unrelated domains. Your sites blend into the crowd instead of clustering.
• Datacenter footprints. CDNs inherently distribute your site across every datacenter they operate, serving from the node closest to each visitor. There’s no single datacenter to cluster sites by.
• IP ownership. LaunchCDN doesn’t own a single IP address used to serve your PBN to the public. Visitors always see a CDN’s IP — Amazon CloudFront, Cloudflare, and more — never ours.
• No dedicated IPs. Some competitors spin up VPSes on DigitalOcean, Vultr, or Linode and call it “cloud PBN hosting.” Every site on a dedicated VPS IP is another PBN customer’s site — a bad neighbourhood by definition. We always use the shared CDN pools that serve the rest of the internet.
• Outbound connections masked. Every outbound request from your WordPress sites (pingbacks, plugin updates, webhook traffic) rotates through masked IPs, so the origin server stays hidden even from passive observation.
• MX records. No MX record is itself a footprint — real businesses have real email. We either set up free mail forwarding through a popular provider or let you point the MX records at Fastmail, Proton, Google Workspace, or any other real email host.
• Real neighbourhoods. Cloudflare now sits in front of roughly a fifth of the entire web, and Amazon CloudFront serves a huge chunk of the rest. When you deploy to them through LaunchCDN, your PBN sits on the same IP ranges as Fortune 500 sites, major SaaS apps, and millions of small businesses.

Defeating IP-Leak Tools Targeting Cloudflare

A handful of tools claim they can reveal the real origin IP behind a CDN, usually targeting Cloudflare. They all rely on the same handful of leaks — and we’ve closed every one:

• Historic DNS data. Crimeflare-style tools look at DNS records from before the CDN was enabled and expose the original origin IP. On LaunchCDN, every site is born with the CDN enabled — there’s no “before” to leak.
• Direct access to non-proxied ports. Cloudflare doesn’t proxy traffic to standard cPanel ports, so cPanel-based hosts leak their origin IP through those ports. We don’t use cPanel servers, so there’s nothing to probe.
• Extra DNS records. Subdomain enumerators scan for records like mail., cpanel., ftp., or webmail. that often bypass the CDN. We only deploy the records needed to serve your site — protected by the CDN — plus optional real email records pointing at third-party providers. Nothing leaks back to the server.