=== WP Security Coat ===
Contributors: leontinashe 
Donate link: http://wpsecuritycoat.com
Tags: security, htaccess, login
Requires at least: 4.0.1
Tested up to: 4.8.1
Stable tag: 4.8
License: GPLv2 or later
License URI: http://www.gnu.org/licenses/gpl-2.0.html

A security plugin mearnt to relieve you from your security issues on your wordpress plugin.

== Description ==

A security plugin mearnt to relieve you from your security issues on your wordpress plugin.

= Plugin Features =

*   Disallow indexing of servcer files
*   Block fake bots
*   Hide worpdress version
*   Remove RSD links and feeds
*   Disable XML-RPC brute Force Attack
*   Disable XML RPC pingback fro DDOS Attacks
*   Disable Login Error Messages
*   Disable WP Rest API Protection From Content Injection Attack
*   Filter suspicious Query String and Non English Character Preventing FRom Sql Injection
*   Protect Website FRom ClicK Jacking Attack
*   enable Browser Blocking of cross site Site Scripting
*   Prevent Content FRom Content Sniffing
*   Block certain HTTP Methods not being used with the website
*   Block Post Method from HTTP 1.0 and HTTP 0.9

A few notes about the sections above:

*   "Contributors" is a comma separated list of wp.org/wp-plugins.org usernames
*   "Tags" is a comma separated list of tags that apply to the plugin
*   "Requires at least" is the lowest version that the plugin will work on
*   "Tested up to" is the highest version that you've *successfully used to test the plugin*. Note that it might work on
higher versions... this is just the highest one you've verified.
*   Stable tag should indicate the Subversion "tag" of the latest stable version, or "trunk," if you use `/trunk/` for
stable.

    Note that the `readme.txt` of the stable tag is the one that is considered the defining one for the plugin, so
if the `/trunk/readme.txt` file says that the stable tag is `4.3`, then it is `/tags/4.3/readme.txt` that'll be used
for displaying information about the plugin.  In this situation, the only thing considered from the trunk `readme.txt`
is the stable tag pointer.  Thus, if you develop in trunk, you can update the trunk `readme.txt` to reflect changes in
your in-development version, without having that information incorrectly disclosed about the current stable version
that lacks those changes -- as long as the trunk's `readme.txt` points to the correct stable tag.

    If no stable tag is provided, it is assumed that trunk is stable, but you should specify "trunk" if that's where
you put the stable version, in order to eliminate any doubt.

== Installation ==


1. Upload `wp-seccoat.php` to the `/wp-content/plugins/` directory
2. Activate the plugin through the 'Plugins' menu in WordPress
3. Go To the Plugin Menu and the activate the features you want to prevent your website from



Here's a link to [WordPress](http://wordpress.org/ "Your favorite software") and one to [Markdown's Syntax Documentation][markdown syntax].
Titles are optional, naturally.

[markdown syntax]: http://daringfireball.net/projects/markdown/syntax
            "Markdown is what the parser uses to process much of the readme file"

Markdown uses email style notation for blockquotes and I've been told:
> Asterisks for *emphasis*. Double it up  for **strong**.

`<?php code(); // goes in backticks ?>`