moallemi

the Advanced User Agent Displayer plugin displays the Browser and the operating system of people who commnet on your blog. 
Currently Support for Desktop and moblie operationg systems and browsers. 
Browsers: Internet Explorer, Opera, Firefox, Safari, Chrome, Epiphany, Avant, Maxthon, Konqueror and … 
Platform: Windows (2000, XP, Vista, 7), Linux, Mac, iPhone and …
What’s New in version 2.7.5.2
<pre><code>* Added support for wordpress 4.5
</code></pre>
Translations
<ul>
<li>Persian – <a href="http://www.moallemi.ir/" rel="nofollow ugc">Reza Moallemi</a></li>
<li>French – <a href="http://www.wptrads.fr/" rel="nofollow ugc">Wolforg</a></li>
<li>German – <a href="http://ppfeufer.de" rel="nofollow ugc">Pfeufer</a></li>
</ul>

Advanced User Agent Displayer

Hello dear,
This plugin broke my site. From Author box description to footer </html> everything disappeared in source code. 
Regards,
Gulshan

Broke my site

This wordpress plugin adds user agent information to your blog comments by adding browser and platform icons and lets visitors know the user agent of  …

KNEET

ScraperGuard helps you block known AI scrapers (often called “good bots”) by matching their User-Agent string.
You can:
<ul>
<li>Select specific bots to block, or block all known bots.</li>
<li>Add your own custom User-Agent substrings (one per line).</li>
<li>Block via Apache <code>.htaccess</code> (fast, before WordPress loads) or via WordPress-level blocking (can show basic stats).</li>
</ul>
Important notes:
<ul>
<li>This plugin can block “good bots” that identify themselves. It cannot stop “bad bots” that ignore rules and/or spoof User-Agents. For that you may need additional security measures (WAF, rate limiting, bot protection).</li>
<li><code>.htaccess</code> blocking works on Apache hosting only, and requires a writable <code>.htaccess</code> file.</li>
<li>WordPress-level blocking only affects requests that reach WordPress (it won’t block direct hits to static files unless they route through WordPress).</li>
<li>Country blocking (geo blocking) can use a country header (fast) or an IP lookup (works without Cloudflare but is slower).</li>
</ul>
The settings page is under Tools → ScraperGuard.
<h3>External Services</h3>
This plugin can optionally connect to third-party IP geolocation services to determine the visitor’s country for country-based blocking. This feature is disabled by default and only activates when you explicitly enable “Country blocking” in the settings.
When country blocking is enabled and the “Country detection method” is set to “Auto” or “IP lookup”:
<ul>
<li>Service used: The plugin uses either ipwho.is or ipapi.co (configurable in settings)</li>
<li>Data sent: The visitor’s IP address is sent to the selected service</li>
<li>When data is sent: Only when a request is received and no country header is available from your server/proxy</li>
<li>Purpose: To determine the visitor’s country code (ISO-2) for geo-blocking</li>
<li>Caching: Results are cached locally for 24 hours by default (configurable 1-168 hours) to minimize requests</li>
<li>Privacy: IP addresses are sent to external services. Ensure compliance with your privacy policy and local regulations.</li>
</ul>
ipwho.is (default provider): 
* Service provider: ipwho.is 
* Privacy policy: https://ipwho.is/ 
* Terms of service: https://ipwho.is/ 
* No API key required
ipapi.co (alternative provider): 
* Service provider: ipapi.co 
* Privacy policy: https://ipapi.co/privacy/ 
* Terms of service: https://ipapi.co/terms/ 
* No API key required for basic usage
Important: If you keep the “Country detection method” set to “Header only” (the default), or if you don’t enable country blocking at all, no data is sent to external services.

ScraperGuard – AI Scraper Blocker

Block “good bots” (AI scrapers) by User-Agent. Optional Apache .htaccess rules and WordPress-level blocking with basic stats.

Advanced User Agent Displayer vs ScraperGuard – AI Scraper Blocker