Title: Snitch
Author: pluginkollektiv
Published: <strong>Èrèlé  12, 2013</strong>
Last modified: Ẹrẹ́nà 14, 2026

---

Ṣàwárí àwọn plugin

![](https://ps.w.org/snitch/assets/banner-772x250.png?rev=2993186)

![](https://ps.w.org/snitch/assets/icon-256x256.png?rev=2993186)

# Snitch

 Láti ọwọ́ [pluginkollektiv](https://profiles.wordpress.org/pluginkollektiv/)

[Ṣe ìgbàsílẹ̀](https://downloads.wordpress.org/plugin/snitch.1.2.1.zip)

 * [Àwọn àlàyé](https://yor.wordpress.org/plugins/snitch/#description)
 * [Àwọn àgbéyẹ̀wò](https://yor.wordpress.org/plugins/snitch/#reviews)
 *  [Ìgbéwọlẹ̀](https://yor.wordpress.org/plugins/snitch/#installation)
 * [Ìdàgbàsókè](https://yor.wordpress.org/plugins/snitch/#developers)

 [Ìrànlọ́wọ́](https://wordpress.org/support/plugin/snitch/)

## Àpèjúwe

Network monitor for WordPress with connection overview for controlling and regulating
data traffic from your site.

### Trust, But Verify

_Snitch_ monitors and logs the outgoing data stream of your WordPress site. It records
every outbound connection from WordPress and provides a log table for administrators.

_Snitch_ does not only log connection requests, but enables you to block future 
requests either by target URL (internet address being called in the background),
or by script (file being executed to open up a connection). Once blocked, a connection
will be visually highlighted. Blocked entries can be unblocked with a simple click.

_Snitch_ is a perfect tool to “listen in” on outbound communication. It is also 
suitable to early recognize any malware and tracking software installed. You can
youse _Snitch_ to make sure you comply with GDPR.

### Summary

_Snitch_ writes a log of both authorized and blocked attempts of connectivity. An
overall view provides transparency and lets you control outgoing connections initialized
by plugins, themes, or WordPress.

### In A Nutshell

 * neat interface
 * displays target URL and source file
 * features grouping, sorting, searching
 * visual highlighting of blocked requests
 * show POST variables with a simple click
 * block/unblock connections by domain/file
 * monitors communication in back-end and front-end
 * delete all entries by pressing a button
 * free of charge, no advertising

### Support

 * Community support via the [support forums on wordpress.org](https://wordpress.org/support/plugin/snitch)
 * We don’t handle support via e-mail, Twitter, GitHub issues etc.

### Contribute

 * Active development of this plugin is handled [on GitHub](https://github.com/pluginkollektiv/snitch).
 * Pull requests for documented bugs are highly appreciated.
 * If you think you’ve found a bug (e.g. you’re experiencing unexpected behavior),
   please post at the [support forums](https://wordpress.org/support/plugin/snitch)
   first.
 * If you want to help us translate this plugin you can do so [on WordPress Translate](https://translate.wordpress.org/projects/wp-plugins/snitch).

### Credits

 * Author: [Sergej Müller](https://sergejmueller.github.io/)
 * Maintainers: [pluginkollektiv](https://pluginkollektiv.org/)

## Àwọn àwòrán ìbòjú

[⌊Snitch connection list⌉⌊Snitch connection list⌉[

Snitch connection list

## Ìgbéwọlẹ̀

 * If you don’t know how to install a plugin for WordPress, [here’s how](https://codex.wordpress.org/Managing_Plugins#Installing_Plugins).

## FAQ

### Snitch creates a lot of database entries

_Snitch_ is designed to log any outgoing connection in WordPress. If the database
fills fast, you should look up the cause. Why does your WordPress and plugins communicate
so often to the outside that the database table fills? Is this communication really
necessary?

As a reminder: _Snitch_ is designed to help you improve your WordPress performance
by detecting and displaying connections as bottleneck. The task for the blog administrator
is to eliminate the source of the cause (plugin, theme, etc.).

_Snitch_ automatically ensures that there are not more than 200 entries are kept
in the database. If it is nevertheless necessary to remove _Snitch_ entries from
the database manually, two smart database commands could help:

    ```
    sql
    DELETE FROM wp_postmeta` WHERE `post_id` IN ( SELECT `ID` FROM `wp_posts` WHERE `post_type` = 'snitch' )
    ```

DELETE FROM `wp_posts` WHERE `post_type` = ‘snitch’
 `

### Are connections monitored in the front end?

_Snitch_ catches any connection that leaves the blog via [WordPress HTTP API](https://codex.wordpress.org/HTTP_API)(
internal WordPress interface for data communication). This affects both the back-
end and the front-end of a WordPress installation.

### Why does Snitch list WordPress cronjobs?

WordPress calls internal Cronjobs via [WordPress HTTP API](https://codex.wordpress.org/HTTP_API)
Ìtumọ̀ Yorùbá: – exactly this interface is monitored by _Snitch_ and also records
Cronjob accesses accordingly.

If cronjobs are listed too often, something possibly isnÌtumọ̀ Yorùbá: ’t correct.
Therefore, it is recommend to check the list of scheduled cronjob jobs.

The following code snippet in the WordPress configuration file `wp-config.php` switches
off the logging of the internal WordPress queries:

    ```
    php
    define('SNITCH_IGNORE_INTERNAL_REQUESTS', true);
    ```

### Why are Snitch entries indexed by Google?

_Snitch_ stores its entries as [WordPress Custom Post Types](https://codex.wordpress.org/Post_Types).
Important step: By a WordPress attribute Snitch marks all log entries as private,
therefore not public. So far, the ideology with private and inaccessible entries
would work if there were not WordPress plugins that would carry all Ìtumọ̀ Yorùbá:–
including private Ìtumọ̀ Yorùbá: – Custom Post Types into the world and communicate
with search engines. With fatal consequences for the blogger.

And so it quickly happens that Google suddenly hits _Snitch_ entries (as blog pages)
which are not intended for public access. For example, because _Snitch_ entries 
appear in the sitemap XML of the blog, as a sitemap XML plugin is of the opinion
that it is also necessary to add private entries and to have them released for indexing.
There is also no help to block via `robots.txt` because the `robots.txt` file does
not prevent the indexing of the pages.

### Automatic Shares go crazily

The fact that every new _Snitch_ entry automatically sends a message to Facebook
and/or Twitter, is clearly not due to _Snitch_. Rather, the cause is to be found
in the inserted Auto-Tweet-Facebook-Plugin, which faulty triggers an automatic event
at every Ìtumọ̀ Yorùbá: – also non-public Ìtumọ̀ Yorùbá: – [WordPress Custom Post Type](https://codex.wordpress.org/Post_Types).
And thatÌtumọ̀ Yorùbá: ’s wrong. The usage of such Plugins should be reconsidered.

A complete documentation is available on the [Snitch website](https://snitch.pluginkollektiv.org/documentation/).

### Where do I report security bugs found in this plugin?

Please report security bugs found in the source code of the Snitch plugin through
the [Patchstack Vulnerability Disclosure Program](https://patchstack.com/database/vdp/a690b1e7-428e-4bc5-a01d-2353ebf45f7b).
The Patchstack team will assist you with verification, CVE assignment, and notify
the developers of this plugin.

## Àwọn àgbéyẹ̀wò

![](https://secure.gravatar.com/avatar/5e9d8750f5c584a637890fe41fce5f6d6c48fe461c610fa01ed9b8e40ae9bd89?
s=60&d=retro&r=g)

### 󠀁[Catch all the callbacks redhanded Ìtumọ̀ Yorùbá: – GOTCHA!](https://wordpress.org/support/topic/catch-all-the-callbacks-redhanded-gotcha/)󠁿

 [JimJam](https://profiles.wordpress.org/unrealnfs/) Ẹrẹ́nà 9, 2024

Earlier i had to manually monitor the QueryMonitorÌtumọ̀ Yorùbá: ’s HTTP API Calls
area to find all the callbacks. Now with this great plugin i donÌtumọ̀ Yorùbá: ’
t have to do it manually as the “SNITCH” plugin does the monitoring for me Ìtumọ̀
Yorùbá: — what a great help. Thanks for this great plugin. Please ignore those who
rate it anything other than 5 stars. For me this plugin goes on each WordPress stack
Ìtumọ̀ Yorùbá: — a-must-have 5 STAR plugin! God bless. Cheers.

![](https://secure.gravatar.com/avatar/7871663f78e217285c30accbce606d5e5f352c2dc9b5076ad6d127c0fa00b016?
s=60&d=retro&r=g)

### 󠀁[Crashed mein Blog (WP 6.4.1)](https://wordpress.org/support/topic/crashed-mein-blog-wp-6-4-1/)󠁿

 [Daniel XAG](https://profiles.wordpress.org/fibmyefriblot_doj/) Bélú 10, 2023

Das Plugin hat wiederholt meine Site zum erliegen gebracht: ein paar Minuten nach
der Aktivierung hat die eingebaute Fehlererkennung von WP eine eMail geschickt: „
In diesem Fall hat WordPress einen Fehler in einem deiner Plugins, Snitch, abgefangen“.
Das Log von Snitch war dabei nicht hilfreich: da fand der Fehler keine Erwähnung.
WordPress-Version 6.4.1 Aktives Theme: Twenty Twenty-Two (Version 1.6) Aktuelles
Plugin: Snitch (Version 1.2.0) PHP-Version 8.1.22

![](https://secure.gravatar.com/avatar/872f7b0ff0552e27463396ddb0eb60a368e2627a8e75b3de2c323d3862c380f1?
s=60&d=retro&r=g)

### 󠀁[EPIC <3](https://wordpress.org/support/topic/epic-3-2/)󠁿

 [mrwolfinformatica](https://profiles.wordpress.org/mrwolfinformatica/) Ọwẹ́wẹ̀ 
14, 2022

Simply epic. Lightweight, ultra simple UI. Really, really, really thz for that.

![](https://secure.gravatar.com/avatar/6c573cb7b9fc191efca3ceaee2479d21ca526f89efe8774df6e995dbf7487f3c?
s=60&d=retro&r=g)

### 󠀁[Can help site owners make better choices regarding which plugins they use](https://wordpress.org/support/topic/can-help-site-owners-make-better-choices-regarding-which-plugins-they-use/)󠁿

 [Carike](https://profiles.wordpress.org/carike/) Èrèlé 3, 2022

This plugin isnÌtumọ̀ Yorùbá: ’t for everyone. It should be, but it not. Such is
life. For me, this is a critical tool that I have relied on since I found it a couple
of years ago. It lets me identify plugins that phone home (or elsewhere) without
permission, without needing to examine every line of code in the plugin (and those
can be huge). It lets me make better decisions with regards to which plugins to 
support. It lets me report plugins when necessary Ìtumọ̀ Yorùbá: – and encourage
public accountability by leaving 1-star reviews for plugins who do act without permission.
And if it is not possible to replace those plugins with others with similar functionality,
it lets me block the calls to domains, or calls made by specific files. This plugin
really deserves my first five star review. 😉

![](https://secure.gravatar.com/avatar/d249480e163b77db7cd2597c9b63b91b87df3ad709933dcbccc70bc6858725c0?
s=60&d=retro&r=g)

### 󠀁[Error](https://wordpress.org/support/topic/error-1495/)󠁿

 [kotyarashop](https://profiles.wordpress.org/kotyarashop/) Ẹrẹ́nà 15, 2021 2 àwọn
ìdáhùn

The plugin or its settings caused an error in Woocommerce: mod_fcgid: stderr: PHP
Fatal error: Uncaught Error: Call to a member function get_type() on bool in /wp-
content/plugins/woocommerce/includes/admin/meta-boxes/views/html-product-data-panel.
php:20

![](https://secure.gravatar.com/avatar/ae0a95435fb1761bf57b409dc4b5dd01d1d58e56dac4b3c8eff1b7db1a54250c?
s=60&d=retro&r=g)

### 󠀁[Exacly what i needed](https://wordpress.org/support/topic/exacly-what-i-needed/)󠁿

 [Rui Oliveira](https://profiles.wordpress.org/hackerinos2/) Òkúdù 17, 2020

I needed to block a useless (and stupid) HTTP API CALL from a specific URL, this
plugin worked like a charm.

 [ Ka gbogbo àwọn àgbéyẹ̀wò 27 ](https://wordpress.org/support/plugin/snitch/reviews/)

## Àwọn Olùkópa & Olùgbéejáde

“Snitch” jẹ́ ètò ìṣàmúlò orísun ṣíṣí sílẹ̀. Àwọn ènìyàn wọ̀nyí ti ṣe ìkópa sí plugin
yìí.

Àwọn Olùkópa

 *   [ pluginkollektiv ](https://profiles.wordpress.org/pluginkollektiv/)

A ti túmọ̀ “Snitch” sí àwọn èdè agbègbè 9. Ọpẹ́lọpẹ́ fún [àwọn atúmọ̀ èdè](https://translate.wordpress.org/projects/wp-plugins/snitch/contributors)
fún àwọn ìkópa wọn.

[Túmọ̀ “Snitch” sí èdè rẹ.](https://translate.wordpress.org/projects/wp-plugins/snitch)

### Ṣe o nífẹ̀ẹ́ sí ìdàgbàsókè?

[Ṣàwárí koodu](https://plugins.trac.wordpress.org/browser/snitch/), ṣàyẹ̀wò [ibi ìpamọ́ SVN](https://plugins.svn.wordpress.org/snitch/),
tàbí ṣe àgbékalẹ̀ sí [àkọsílẹ̀ ìdàgbàsókè](https://plugins.trac.wordpress.org/log/snitch/)
nípasẹ̀ [RSS](https://plugins.trac.wordpress.org/log/snitch/?limit=100&mode=stop_on_copy&format=rss).

## Àkọsílẹ̀ àwọn àyípadà

### 1.2.1

 * Tested up to WordPress 6.8
 * Minor code-style adjustments
 * Add plural translation to “seconds”
 * Slashes in file paths are no longer removed (output issues on Windows systems)
 * Added link to Patchstack mVDP

### 1.2.0

 * Shows schema of request (http/https)
 * No “jerking” in the retrieval list during mouse over
 * Remove `lang` folder in favor of translations via translate.wordpress.org
 * Support for WordPress 6.4

### 1.1.8

 * Support for WordPress 5.2
 * Bugfix: Deprected Non-static call

### 1.1.7

 * Updated README
 * Improved user interface
 * Support for WordPress 4.9

### 1.1.6

 * Updated README
 * Updated [plugin authors](https://pluginkollektiv.org/hello-world/)

### 1.1.5 / 06.05.2015

 * [GitHub Repository](https://github.com/pluginkollektiv/snitch)

### 1.1.4

 * Support for WordPress 4.2
 * Nice to have: `admin_url()` for `edit.php` requests

### 1.1.3

 * Support for WordPress 4.1

### 1.1.2

 * Feature: english translation for the readme file
 * Feature: russian translation for plugin files

### 1.1.1

 * Feature: status code “-1” for failing connections

### 1.1.0

 * Feature: execution time as metric (thanks [Matthias Kilian](https://www.gaertner.de)
   for the idea)

For the complete changelog, check out our [GitHub repository](https://github.com/pluginkollektiv/snitch).

## Àkójọpọ̀ Meta

 *  Ẹ̀yà **1.2.1**
 *  Ìgbàgbọ́hùn tó kẹ́yìn **oṣù 5 sẹ́yìn**
 *  Àwọn ìgbéwọlẹ̀ tó ṣiṣẹ́ **800+**
 *  Ẹ̀yà WordPress ** 3.8 tàbí ju bẹ́ẹ̀ lọ **
 *  Dánwò dé **6.9.6**
 *  Ẹ̀yà PHP ** 5.2.4 tàbí ju bẹ́ẹ̀ lọ **
 *  Àwọn èdè
 * [Dutch](https://nl.wordpress.org/plugins/snitch/), [English (US)](https://wordpress.org/plugins/snitch/),
   [German](https://de.wordpress.org/plugins/snitch/), [German (Austria)](https://de-at.wordpress.org/plugins/snitch/),
   [German (Switzerland)](https://de-ch.wordpress.org/plugins/snitch/), [Portuguese (Portugal)](https://pt.wordpress.org/plugins/snitch/),
   [Russian](https://ru.wordpress.org/plugins/snitch/), [Spanish (Chile)](https://cl.wordpress.org/plugins/snitch/),
   [Spanish (Spain)](https://es.wordpress.org/plugins/snitch/), àti [Swedish](https://sv.wordpress.org/plugins/snitch/).
 *  [Túmọ̀ sí èdè rẹ](https://translate.wordpress.org/projects/wp-plugins/snitch)
 * Àwọn àmì
 * [firewall](https://yor.wordpress.org/plugins/tags/firewall/)[GDPR](https://yor.wordpress.org/plugins/tags/gdpr/)
   [monitoring](https://yor.wordpress.org/plugins/tags/monitoring/)[network](https://yor.wordpress.org/plugins/tags/network/)
   [sniffer](https://yor.wordpress.org/plugins/tags/sniffer/)
 *  [Ìwòye Tó Péye](https://yor.wordpress.org/plugins/snitch/advanced/)

## Àwọn ìbò

 4 lára àwọn ìràwọ̀ 5.

 *  [  20 5-star reviews     ](https://wordpress.org/support/plugin/snitch/reviews/?filter=5)
 *  [  0 4-star reviews     ](https://wordpress.org/support/plugin/snitch/reviews/?filter=4)
 *  [  1 3-star review     ](https://wordpress.org/support/plugin/snitch/reviews/?filter=3)
 *  [  0 2-star reviews     ](https://wordpress.org/support/plugin/snitch/reviews/?filter=2)
 *  [  6 1-star reviews     ](https://wordpress.org/support/plugin/snitch/reviews/?filter=1)

[Your review](https://wordpress.org/support/plugin/snitch/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/snitch/reviews/)

## Àwọn Olùkópa

 *   [ pluginkollektiv ](https://profiles.wordpress.org/pluginkollektiv/)

## Ìrànlọ́wọ́

Nǹkan wà tí o fẹ́ sọ? Ṣé o nílò ìrànlọ́wọ́?

 [Wo àpéjọ ìrànlọ́wọ́](https://wordpress.org/support/plugin/snitch/)

## Ṣe ìtọrẹ

Ṣé o fẹ́ ṣe àtìlẹ́yìn fún ìlọsíwájú plugin yìí?

 [ Ṣe ìtọrẹ sí plugin yìí ](https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=TD4AMD2D8EMZW)