| If you suspect sockpuppetry by an administrator, or if you need to submit off-wiki evidence for some other reason, you must email the checkuser team to open an investigation. Private information, emails, logs, and other sensitive evidence must not be posted on Wikipedia. All evidence related to a sockpuppet investigation must otherwise be posted on the designated page. | ||
| ←What is a sockpuppet? | ||
This page is for requesting that we investigate whether two or more Wikipedia accounts are being abusively operated by the same person.
Before opening an investigation, you need good reason to suspect sockpuppetry.
- Evidence is required. When you open the investigation, you must immediately provide evidence that the suspected sock puppets are connected. The evidence will need to include diffs of edits that suggest the accounts are connected. (This requirement is waived if the edits in question are deleted; in this case just provide the names of the pages that the accounts have been editing.)
- You must provide this evidence in a clear way. Vaguely worded submissions will not be investigated. You need to actually show why your suspicion that the accounts are connected is reasonable.
- Concision is key. Evidence should be presented in a concise format. Because of the length of the backlog, cases with clear and concise explanations and evidence are handled the most quickly.
Investigations are conducted by a clerk or an administrator, who will compare the accounts' behaviour and determine whether they are probably connected; this is a behavioural evidence investigation. Upon request, investigations can also be conducted by a checkuser, who can look at the physical location of the accounts (and other technical data) in order to determine how likely it is they are connected; this is a technical evidence investigation.
Due to Wikipedia's CheckUser policy, checkusers will conduct a technical investigation only if clear, behavioural evidence of sockpuppetry is also submitted; if you ask for technical evidence to be looked at but do not provide behavioural evidence, the investigation may not be allowed to proceed. Additionally, checkusers will not publicly connect an account with an IP address per the privacy policy except in extremely rare circumstances.
How to open an investigation:
| ||
|---|---|---|
|
To open an investigation (or case), enter the user name (or if there isn't one, IP address) of the oldest-created account (the "sockmaster"), or the previous case name, in the box below, then click "Submit". Note: Do not include "User:" or any other commentary. For example, if the case name is about User:John Doe or a prior case was at Wikipedia:Sockpuppet investigations/John Doe, you should enter John Doe in the box below. You will then be taken to another page containing a form you must complete to open the investigation. The process for opening a subsequent investigation on the same user is the same as for creating a new case. Again, do not include "User:" in any of the sock or ip fields. If you also wish a checkuser to investigate, change |checkuser=no to |checkuser=yes in the edit box on the next page and explain why you are requesting it. Note: You can also open an investigation using Twinkle if you are autoconfirmed. After installing Twinkle, an "ARV" option will appear in the "TW" tab on any user, user talk, or user contributions page. Clicking on this option and selecting either "Sockpuppeteer" or "Sockpuppet" will allow you to fill in a few simple fields to file a report. The report will be automatically formatted for you.
|
Cases currently listed at SPI
| Investigation | Status | Filed at (UTC) | Last user edit | Last clerk/CU edit | ||
|---|---|---|---|---|---|---|
| User | Time (UTC) | User | Time (UTC) | |||
| RJII | Awaiting admin | 2022-02-09 03:05 | Tamzin | 2022-02-11 18:18 | Tamzin | 2022-02-11 18:18 |
| 76.69.7.202 | Awaiting clerk | 2022-02-07 06:25 | TheresNoTime | 2022-02-10 11:09 | TheresNoTime | 2022-02-10 11:09 |
| 101.118.135.146 | Awaiting clerk | 2022-02-08 16:26 | Tamzin | 2022-02-10 03:36 | Tamzin | 2022-02-10 03:36 |
| Ehr1Ros2 | Awaiting clerk | 2022-02-09 21:25 | Jack Frost | 2022-02-12 00:35 | Jack Frost | 2022-02-12 00:35 |
| Zessede | Awaiting clerk | 2022-02-10 12:52 | RoySmith | 2022-02-11 23:56 | RoySmith | 2022-02-11 23:56 |
| Yeu aga maj | CU completed | 2022-01-31 14:49 | RoySmith | 2022-02-01 20:39 | RoySmith | 2022-02-01 20:39 |
| Swarup Kumar Solanki | CU completed | 2022-02-04 12:55 | RoySmith | 2022-02-05 20:06 | RoySmith | 2022-02-05 20:06 |
| KJ332 | CU completed | 2022-02-07 20:11 | Dreamy Jazz | 2022-02-11 22:03 | Dreamy Jazz | 2022-02-11 22:03 |
| Stevieseay | CU completed | 2022-02-08 01:11 | TheresNoTime | 2022-02-10 11:26 | TheresNoTime | 2022-02-10 11:26 |
| XxNoXxx | CU completed | 2022-02-11 18:25 | Girth Summit | 2022-02-11 19:24 | Girth Summit | 2022-02-11 19:24 |
| Best known for IP | Open | 2022-02-07 19:56 | Wizzito | 2022-02-12 00:35 | Ponyo | 2022-02-10 23:37 |
| Garfield 3185 | Open | 2022-02-09 04:04 | RoySmith | 2022-02-11 15:58 | RoySmith | 2022-02-11 15:58 |
| Spreadmediaglobal | Open | 2022-02-11 14:55 | Girth Summit | 2022-02-11 15:12 | Girth Summit | 2022-02-11 15:12 |
| Poledlimps | Open | 2022-02-11 17:47 | Praxidicae | 2022-02-11 17:47 | ||
| Ineedtostopforgetting | Open | 2022-02-11 23:17 | Chipmunkdavis | 2022-02-12 00:07 | ||
| 192.157.116.135 | CU declined (CU) | 2022-02-11 22:30 | Oshwah | 2022-02-11 23:17 | Oshwah | 2022-02-11 23:17 |
| GoogleMeNowPlease | More info req. | 2022-02-10 10:41 | Tamzin | 2022-02-11 21:44 | Tamzin | 2022-02-11 21:44 |
| CharmenderDeol | On hold (CU) | 2022-02-11 15:20 | Blablubbs | 2022-02-11 17:17 | Blablubbs | 2022-02-11 17:17 |
| Problemsmith | On hold | 2022-02-09 08:15 | Tamzin | 2022-02-09 12:19 | Tamzin | 2022-02-09 12:19 |
| Jiboner&to | On hold | 2022-02-11 00:24 | Blablubbs | 2022-02-11 00:51 | Blablubbs | 2022-02-11 00:51 |
| ARTPR001 | Closed | 2022-01-29 00:05 | RoySmith | 2022-02-11 02:39 | RoySmith | 2022-02-11 02:39 |
| Best known for IP | Closed | 2022-02-07 19:56 | Wizzito | 2022-02-12 00:35 | Ponyo | 2022-02-10 23:37 |
| Sidbidmidlid | Closed | 2022-02-07 20:46 | Jack Frost | 2022-02-12 00:30 | Jack Frost | 2022-02-12 00:30 |
| UmairYokaimon | Closed | 2022-02-08 00:37 | Tamzin | 2022-02-11 19:05 | Tamzin | 2022-02-11 19:05 |
| Elkridge | Closed | 2022-02-08 10:51 | Spicy | 2022-02-11 00:25 | Spicy | 2022-02-11 00:25 |
| Bule Cloud | Closed | 2022-02-08 19:09 | Spicy | 2022-02-11 20:43 | Spicy | 2022-02-11 20:43 |
| Ehr1Ros2 | Closed | 2022-02-09 21:25 | Jack Frost | 2022-02-12 00:35 | Jack Frost | 2022-02-12 00:35 |
| 040280BSSM | Closed | 2022-02-09 23:31 | Spicy | 2022-02-11 12:57 | Spicy | 2022-02-11 12:57 |
| Zessede | Closed | 2022-02-10 12:52 | RoySmith | 2022-02-11 23:56 | RoySmith | 2022-02-11 23:56 |
| Wikiabirras | Closed | 2022-02-11 18:28 | Girth Summit | 2022-02-11 19:34 | Girth Summit | 2022-02-11 19:34 |
| Blue Mango Juice | Closed | 2022-02-11 19:44 | RoySmith | 2022-02-11 20:06 | RoySmith | 2022-02-11 20:06 |
| Anti-propaganda-man | Closed | 2022-02-11 23:32 | Sir Sputnik | 2022-02-12 00:42 | Sir Sputnik | 2022-02-12 00:42 |
| Doprowik | Closed | 2022-02-11 23:45 | Bbb23 | 2022-02-12 01:58 | ||
Quick CheckUser requests
Use this section to request checkuser information relating to a situation that does not involve sock puppetry. You could use this section to request, for example:
For threats of harm (to self or others) you must email emergency To make a request here, copy the following template and paste it to the end of this section (quick link to edit) – replacing "header" with an informative title, and adding underneath the template any relevant information – then sign using "~~~~", preview, and click "save".
|
wikimedia.org