CloudFlare, the Secret Client and PBN Killer

Posted by ExecPBN Sales Team In: Blog & News No comments

Editor note: This lesson applies to any issue with nameserver diversity on your network.

We’ve noticed that a lot of newer PBN owners are using popular nameservers to hide their PBN in the crowd. After all, it’s near impossible to track your network sites solely from similar nameservers or even Whois data if it’s shared with thousands or even millions of other domains. With CloudFlare, and in turn using their nameserver to utilize their service, there is also the benefit of gaining a little SEO power boost by having a great site speed from a Content Delivery Network. So that service in particular appears on the surface to have twice the benefit.

Hiding in the crowd appears to work when avoid patterns between your network sites. Although it may be extremely difficult to link your network just from nameserver or Whois settings, things change when you consider the footprint you are creating to the sites you link to from your network.

The issue occurs when you inadvertently pass the same types of referring domains to your client sites from your network. Google has spam algorithms it can check and spot the patterns between the root nameservers of your referring domains.


Doesn’t Link Diversity Solve This Issue?    

Although some might argue that these will naturally become diluted as you add more links from sources other than your network. However, when we analyze the figures you realize how easy it is to set off an unnatural links algorithm penalty, or at the very least have those link discounted or diminished, for your clients.

VeriSign[1] states the total number of registered domain names is approximately 299 million worldwide across all top-level domains (TLDs) as of Sept. 30, 2015. Some may argue that some of these don’t contain active website, which is very true. We struggled to find the total number of active domains. Netscraft[2] found 901,002,770 sites active on the internet, but that includes every hostname on an IP, which includes every distinctive subdomain etc. available on the web.

Also not all domains are used as nameservers either, it would be foolish to suggest otherwise, but if we know how many sites use a certain domain as a nameserver, could we make an estimate based on the possibility of the rest of the internet not be included on a nameserver?

CloudFlare claims to have 2 Million web properties under their service as of January 2016. If we discount a third of Verisign domains numbers to domain sellers and inactive sites, we arrive at a figure of 200 million domains that could be used as a name server.

That assumes an estimate of 1% of domains on the internet use a CloudFlare nameserver.

So one would also assume that an average natural backlink profile would not on average contain any more than 1% percent of referring domains utilizing CloudFlare’s nameservers. Let’s presume, and it is a big presumption, that Google might allow 10 times the average percentage of nameservers. That means that 10 in 100 of your client’s referring domains would be allowed to come from CloudFlare nameservers before alarms are set off. If you use large quantities of nameservers of lesser known services right across your network, you could potentially be ready to bury your client sites in record time.

When we’re creating patterns and penalties to our clients, we in turn are risking having our network deindexed too. Patterns can trigger manual reviews; manual reviews mean you’re a sitting duck to have those site removed from the Google index. If we’ve create a penalty for a client or site that we don’t actively manage, a reclusion request that we are unaware about can have all our network brought further to the web spam team’s attention.


Ways to tackle

The solution is pretty obvious once you’ve identified the problem, diversification of your nameservers!

We’ve written a comprehensive guide here to help any PBN owners that need help in this area.


Performance solutions for WordPress?

If you’re concerned about the loss of site speed of moving away from a CDN, why not opt for some classic performance WordPress plugins to get your network sites firing?

WP Super Cache –

W3 Total Cache –

Zen Cache –

WP Fastest Cache –


How ExecPBN can help with identification and monitoring of patterns?

Not only does ExecPBN help you identify and monitor potential nameserver patterns on your network as a whole, you can also view the patterns you’re creating to each client. This allows you to take action at a macro and micro level to ensure that you don’t create patterns. There’s also the added benefit of monitoring any potential patterns that arise as your empire expands.

You minimize the risk of losing your investment domains and their content, and also creating issues for client that would result in the loss of revenue.

This is one of over 40 features that ExecPBN can utilize to help accelerate your SEO’s business. Ready to get started?






Subscribe to our mailing list

* indicates required

Comments: 0

There are not comments on this post yet. Be the first one!

Leave a comment