David Artiss

Michael Adams (mdawaffe)

Some people really like that WordPress sends pings from your own site to your own site when you write posts; it gives them a trail of related posts.
Some people do not like this behavior; it clutters up their comments.
This plugin disables intra-blog pinging.
Once activated, there’s nothing for you to do. However, head to Settings -> Discussion and you’ll find a field in which you can, if you wish, specify more domains that won’t be pinged. Why? Well, maybe you often refer to other sites that you maintain or, particularly, you run a multi-site and don’t want each blog pinging the other – specify a list here and you’re sorted.
This plugin was originally developed by the awesome <a href="https://profiles.wordpress.org/mdawaffe/" rel="nofollow ugc">Michael D. Adams</a> and the iconography is courtesy of the very talented <a href="https://www.fiverr.com/jankirathore" rel="nofollow ugc">Janki Rathod</a>.
Please visit the <a href="https://github.com/dartiss/no-self-ping" title="Github" rel="nofollow ugc">Github page</a> for the latest code development, planned enhancements and known issues

No Self Ping

Keeps WordPress from sending pings to your own site.

Pascal CESCATO

Secure your site’s XML-RPC by removing some methods, instead of disabling totally XML-RPC, which is needed by some plugins (eg. Jetpack) and some mobile apps.
<h4>Features</h4>
Removes the following methods from XML-RPC interface.
<ul>
<li>system.multicall</li>
<li>system.listMethods</li>
<li>system.getCapabilities</li>
<li>pingback.extensions.getPingbacks</li>
<li>pingback.ping</li>
<li>X-Pingback from HTTP headers</li>
</ul>
This is not perfect, but it will help prerventing attacks
<h4>Requirements</h4>
<ul>
<li>WordPress 5.0 or higher.</li>
</ul>

stop XML-RPC Attacks

Secure your site's XML-RPC by removing some methods, while you can still use XML-RPC.

No Self Ping vs stop XML-RPC Attacks