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.

Lars Koudal

cleverplugins

Prevent your WordPress site from participating and being a victim of pingback denial of service attacks. After activation the plugin automatically disables XML-RPC. There’s no need to configure anything.
By disabling the XML-RPC pingback you’ll: 
* lower your server CPU usage 
* prevent malicious scripts from using your site to run pingback denial of service attacks 
* prevent malicious scripts to run denial of service attacks on your site via pingback
From sucuri.net:
<blockquote>
Any WordPress site with Pingback enabled (which is on by default) can be used in DDOS attacks against other sites.
</blockquote>
<h4>Learn More</h4>
<ul>
<li><a href="http://wptavern.com/how-to-prevent-wordpress-from-participating-in-pingback-denial-of-service-attacks" rel="nofollow ugc">How To Prevent WordPress From Participating In Pingback Denial of Service Attacks</a> – wptavern.com</li>
<li><a href="http://blog.sucuri.net/2014/03/more-than-162000-wordpress-sites-used-for-distributed-denial-of-service-attack.html" rel="nofollow ugc">More Than 162,000 WordPress Sites Used for Distributed Denial of Service Attack</a> – sucuri.net</li>
<li><a href="http://hackguard.com/xmlrpc-php-ping-backs-hackers-denial-service-attacks" rel="nofollow ugc">xmlrpc.php and Pingbacks and Denial of Service Attacks, Oh My!</a> – hackguard.com</li>
</ul>
<h4>Is Your Site Attacking Others?</h4>
Use <a href="http://labs.sucuri.net/?is-my-wordpress-ddosing" rel="nofollow ugc">Sucuri’s WordPress DDOS Scanner</a> to check if your site is DDOS’ing other websites
<h4>Why Not Just Disable XMLRPC Altogether?</h4>
Yes, you can choose to do that, but if you use popular plugins like JetPack (that use XMLRPC) then those plugins will stop working. That is why this small plugin exists.

Remove & Disable XML-RPC Pingback

Great plugin, super easy to install and just sits there doing it's job. Very light as well, so has no effects that I could see, on site speed or memory usage. Can't think of a reason why you wouldn't be using this to be honest. Thanks for developing it!

Just what I needed

Prevent pingback, XML-RPC and denial of service DDOS attacks by disabling the XML-RPC pingback functionality.

No Self Ping vs Remove & Disable XML-RPC Pingback