pontocinza

<p>When a post is published or updated, Internal Pingback Comments scans its content, finds all internal links, and creates a pingback-style comment on each linked post. It mimics native WordPress pingback behavior but eliminates the need for XML-RPC or outbound network requests.</p>
<p>Works with posts only. No settings page, no configuration.</p>
<p><strong>How it works</strong></p>
<p>The plugin parses post content with DOMDocument — not regex — so it handles real-world HTML correctly: nested tags, encoded entities, relative and protocol-relative URLs. For each internal link found, it inserts a pingback comment on the target post. The comment includes a short excerpt from the source post, with image captions (figcaption) stripped so they do not bleed into the pingback text.</p>
<p>Duplicate detection is precise: the source permalink is stored as private comment meta, and the plugin queries that meta before every insert. Republishing or updating a post never creates duplicate comments. New links added to an existing post will generate their own pingbacks on the next save.</p>
<p><strong>What the pingback looks like to your theme</strong></p>
<p>The comment is stored with <code>comment_type = 'pingback'</code> and auto-approved. Your theme renders it exactly as it would render a native pingback. If your theme does not display pingbacks, the comment will be stored in the database but remain hidden on the front end.</p>
<h3>Disclaimer</h3>
<p>This plugin is provided “as is”, without warranty of any kind. While best efforts have been made to ensure reliability and security, the author is not liable for any damages or losses resulting from its use.</p>


Internal Pingback Comments

Detects internal links in posts and automatically inserts a pingback-style comment on each linked post. No XML-RPC required.

Lars Koudal

cleverplugins

<p>Prevent your WordPress site from participating and being a victim of pingback denial of service attacks. <strong>After activation the plugin automatically disables XML-RPC. There’s no need to configure anything.</strong></p>
<p>By disabling the XML-RPC pingback you’ll:<br />
* lower your server CPU usage<br />
* prevent malicious scripts from using your site to run pingback denial of service attacks<br />
* prevent malicious scripts to run denial of service attacks on your site via pingback</p>
<p>From sucuri.net:</p>
<blockquote>
<p>Any WordPress site with Pingback enabled (which is on by default) can be used in DDOS attacks against other sites.</p>
</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>
<p>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</p>
<h4>Why Not Just Disable XMLRPC Altogether?</h4>
<p>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.</p>


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.

Internal Pingback Comments vs Remove & Disable XML-RPC Pingback