Title: Advanced Blocking Help
Last modified: March 21, 2018

---

# Advanced Blocking Help

 *  Resolved [seedy](https://wordpress.org/support/users/seedy/)
 * (@seedy)
 * [8 years, 2 months ago](https://wordpress.org/support/topic/advanced-blocking-help/)
 * I think it’s fair to say that social media sites are parasites, this is especially
   true for photographers. I typically block any Facebook, etc ranges via Live Traffic,
   but now Facebook is apparently using IPV6, which makes blocking their ranges 
   more difficult, e.g this recent entry from Menlo Park…
 * 2a03:2880:1020:6fea:face:b00c:0:8000
 * Clever, eh? Putting that “face” in there was helpful but perhaps not in the way
   that they intended.
 * I do not want any of my sites farmed/harvested/slurped by any of the “free” content
   providers, what is the proper way to block this kind of range? Perhaps a checkbox
   for blocking FB, Pint, etc could be added if there isn’t a way to make an entry
   in Advanced Blocking.

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Plugin Support [wfphil](https://wordpress.org/support/users/wfphil/)
 * (@wfphil)
 * [8 years, 2 months ago](https://wordpress.org/support/topic/advanced-blocking-help/#post-10118752)
 * Hi [@seedy](https://wordpress.org/support/users/seedy/)
 * Currently Facebook’s IP address ranges are whitelisted and can’t be blocked by
   Wordfence. We are looking at improving customization of IP ranges currently whitelisted
   by Wordfence so you may see an enhancement to this in the future.
 * You could do this instead as an example, as long as you are comfortable carrying
   out the following instructions and can undo your changes for any unexpected behaviour.
   Add this code below to the “**.htaccess**” file in the root directory of your
   WordPress installation:
 *     ```
       # BLOCK FACEBOOK USER AGENTS
       RewriteEngine On
       RewriteCond %{HTTP_USER_AGENT} ^.*(facebookexternalhit|Facebot).*$ [NC]
       RewriteRule .* - [F,L]
       ```
   
 * Thanks.
 *  Thread Starter [seedy](https://wordpress.org/support/users/seedy/)
 * (@seedy)
 * [8 years, 2 months ago](https://wordpress.org/support/topic/advanced-blocking-help/#post-10158964)
 * Thank you for the code. Noticing increasing diversity in Live Traffic from most
   slurpers; new locations, IP ranges, etc.Wondering how long it will be before 
   the self-ID of the big ones becomes deceptive. Google has clearly lost any moral
   compass it may have had or thought it had.
 * One thing that would be value-added is a page of checkboxes for blocking slurp
   farms like OVH, Dig Ocean, AWS, etc, as well as the big soc-med monetisers.
 * Appreciate the Live Traffic tool and the insights that can be gained, do wish
   it could suffer fewer redesign efforts. IMO it’s really the standout feature 
   of WF, but I can understand that it’s likely costly.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Advanced Blocking Help’ is closed to new replies.

 * ![](https://ps.w.org/wordfence/assets/icon.svg?rev=2070865)
 * [Wordfence Security - Firewall, Malware Scan, and Login Security](https://wordpress.org/plugins/wordfence/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordfence/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordfence/)
 * [Active Topics](https://wordpress.org/support/plugin/wordfence/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordfence/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordfence/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [seedy](https://wordpress.org/support/users/seedy/)
 * Last activity: [8 years, 2 months ago](https://wordpress.org/support/topic/advanced-blocking-help/#post-10158964)
 * Status: resolved