Deprecated: Joomla\Input\Input implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /homepages/13/d380392445/htdocs/Jlive/libraries/vendor/joomla/input/src/Input.php on line 41

Deprecated: Return type of Joomla\Input\Input::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/13/d380392445/htdocs/Jlive/libraries/vendor/joomla/input/src/Input.php on line 170

Deprecated: Joomla\CMS\Input\Input implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /homepages/13/d380392445/htdocs/Jlive/libraries/src/Input/Input.php on line 31

Deprecated: Joomla\CMS\Input\Cookie implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /homepages/13/d380392445/htdocs/Jlive/libraries/src/Input/Cookie.php on line 21

Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /homepages/13/d380392445/htdocs/Jlive/libraries/src/Uri/Uri.php on line 141
Issue Tracker Guide :: Passive Protection

Deprecated: F0FInput implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /homepages/13/d380392445/htdocs/Jlive/libraries/f0f/input/input.php on line 35

Deprecated: Joomla\CMS\Input\Files implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /homepages/13/d380392445/htdocs/Jlive/libraries/src/Input/Files.php on line 21

Passive Protection

This typically includes techniques such as IP Blocks, White-lists and Black-Lists and Content Scanners.  The spam is intended to insert links into your site. Passive protection focuses on using content scanners which validate the content, the source & method of delivery against extensive databases of bad links, emails, content, blacklisted IPs & domains to stop the spammer from getting his input in.

These checking databases are fed input from a huge number of sites and users that subscribe to using the databases and they in turn report malicious content.  The important thing about these databases are that they are updated continuously and are true to the spirit of open source being contributed to on a everyday basis making them a comprehensive source of information.

There are many examples of such databases and include Akismet, Mollom, Project Honey Pot, Bad Behavior to came but a few.

This 'Captcha less' Spam protection can be very effective mainly since in most cases it helps the system become even more stronger.  One downside is that on a busy site it can add some considerable overhead to the processing load, and possibly slow the user's site experience. 

Go To Top

Joomla! Debug Console

Session

Profile Information

Memory Usage

Database Queries