Page semi-protected

Wikipedia:Sockpuppet investigations

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

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.

  1. 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.)
  2. 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.
  3. 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 numbered 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. 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.
If you are not autoconfirmed, and the case page is protected or does not exist, please click "show" to the right and use the box below.

Cases currently listed at SPI

Investigation Status Filed at (UTC) Last user edit Last clerk/CU edit
User Time (UTC) User Time (UTC)
Spud1002016 In progress 2022-08-13 03:06 Primefac 2022-08-13 05:44 Primefac 2022-08-13 05:44
Nepallivetoday Endorsed 2022-08-06 17:12 TheSandDoctor 2022-08-13 03:52 TheSandDoctor 2022-08-13 03:52
Dolyn Endorsed 2022-08-07 01:00 TheSandDoctor 2022-08-13 03:48 TheSandDoctor 2022-08-13 03:48
Vanderpumpstan Endorsed 2022-08-11 19:09 TheSandDoctor 2022-08-13 03:45 TheSandDoctor 2022-08-13 03:45
Anup Rajbanshi Endorsed 2022-08-12 14:35 TheSandDoctor 2022-08-13 03:47 TheSandDoctor 2022-08-13 03:47
Shikagami03 CU requested 2022-08-08 17:52 Timtrent 2022-08-11 23:08
Proton Dental CU requested 2022-08-09 11:48 Georgethedragonslayer 2022-08-09 11:48
Ishqyk CU requested 2022-08-10 16:49 PravinGanechari 2022-08-12 14:26
Cyber.Eyes.2005 CU requested 2022-08-10 23:05 LouisAragon 2022-08-10 23:06
Dashmax1214plus CU requested 2022-08-11 14:50 Bbb23 2022-08-12 00:25
Pitzzaboy CU requested 2022-08-11 16:39 Bbb23 2022-08-11 18:00
Perf1203 CU requested 2022-08-12 13:13 CockpitJim 2022-08-12 13:13
HariSinghw CU requested 2022-08-12 16:50 KSAWikipedian 2022-08-12 16:50
Andrew5 CU requested 2022-08-12 20:30 Bbb23 2022-08-12 20:30
Usama950 CU requested 2022-08-12 21:52 Robert McClenon 2022-08-12 21:52
Dylan Florida CU requested 2022-08-13 03:48 Binksternet 2022-08-13 04:26
Konguhead CU requested 2022-08-13 06:11 Suneye1 2022-08-13 06:11
Sazmancrpo Awaiting clerk 2022-08-11 15:31 Girth Summit 2022-08-11 23:35 Girth Summit 2022-08-11 23:35
Punjabirockstars Awaiting clerk 2022-08-12 17:18 Jack Frost 2022-08-12 21:54 Jack Frost 2022-08-12 21:54
Pallster CU completed 2022-06-26 18:18 Vanjagenije 2022-07-05 22:46 Vanjagenije 2022-07-05 22:46
Dekodrak CU completed 2022-07-09 21:38 TheSandDoctor 2022-07-31 22:44 TheSandDoctor 2022-07-31 22:44
Chrononem CU completed 2022-07-29 23:39 EdJohnston 2022-07-31 22:35 EdJohnston 2022-07-31 22:35
MarshallKe CU completed 2022-07-31 23:56 Psychologist Guy 2022-08-12 20:41
Kosnsnkjsjsbbs CU completed 2022-08-01 16:43 PravinGanechari 2022-08-10 10:01 AmandaNP 2022-08-02 06:17
Josh Talk CU completed 2022-08-04 17:52 Girth Summit 2022-08-07 12:44 Girth Summit 2022-08-07 12:44
Coolscohan CU completed 2022-08-04 19:40 RoySmith 2022-08-07 19:39 RoySmith 2022-08-07 19:39
Artoriusfadianus CU completed 2022-08-05 21:30 M.Aurelius.Viator 2022-08-05 23:17 RoySmith 2022-08-05 22:54
Nangparbat CU completed 2022-08-06 11:55 Orientls 2022-08-13 07:23 RoySmith 2022-08-12 17:07
SSH remoteserver CU completed 2022-08-08 19:50 Yue 2022-08-11 00:15 Girth Summit 2022-08-09 15:40
WorldCreaterFighter CU completed 2022-08-09 03:02 Hunan201p 2022-08-13 06:33 Blablubbs 2022-08-12 20:29
Eashleyfox CU completed 2022-08-09 18:33 SWinxy 2022-08-11 19:23 Primefac 2022-08-10 12:23
Hoaeter CU completed 2022-08-09 23:03 EdJohnston 2022-08-12 19:44 EdJohnston 2022-08-12 19:44
Anujror CU completed 2022-08-12 09:12 Dreamy Jazz 2022-08-12 15:00 Dreamy Jazz 2022-08-12 15:00
Patricialiew Open 2022-06-17 09:30 0xDeadbeef 2022-07-31 06:03
Nagarukhra Open 2022-07-05 18:32 Gene93k 2022-07-05 18:35
Rolex2022 Open 2022-08-04 07:57 PravinGanechari 2022-08-04 07:57
Bestf123 Open 2022-08-04 11:33 Renewal6 2022-08-05 19:50
Siddhartha sengupta2001 Open 2022-08-09 03:48 TheSandDoctor 2022-08-13 03:55 TheSandDoctor 2022-08-13 03:55
Surajsingh12 Open 2022-08-09 19:48 PravinGanechari 2022-08-10 06:38
M Atif Maqbool Open 2022-08-09 21:59 Bbb23 2022-08-10 13:12 Praxidicae 2022-08-09 21:59
Nair Community Open 2022-08-11 18:55 Dennis Brown 2022-08-11 18:55
21KSchool Open 2022-08-12 00:09 Praxidicae 2022-08-12 00:09 Praxidicae 2022-08-12 00:09
Imranhosen1997 Open 2022-08-12 09:28 ProClasher97 2022-08-12 09:28
GermanKity Open 2022-08-12 13:03 PravinGanechari 2022-08-12 17:17
Sion301 Open 2022-08-12 14:22 FyzixFighter 2022-08-12 14:22
JohnEnglish2020 Open 2022-08-13 01:22 SWinxy 2022-08-13 01:22
Romesh67 Open 2022-08-13 05:06 Storchy 2022-08-13 05:06
Mann 7s Open 2022-08-13 06:24 ProClasher97 2022-08-13 06:24
Mr. Samuel F. Paul Open 2022-08-13 07:28 Lavalizard101 2022-08-13 07:31
Mclarenfan17 CU declined 2022-08-06 22:08 Sir Sputnik 2022-08-06 22:39 Sir Sputnik 2022-08-06 22:39
Prince Of Roblox More info req. 2022-08-04 09:55 Fylindfotberserk 2022-08-06 16:14 Jack Frost 2022-08-04 11:03
יניב הורון On hold (CU) 2021-11-29 00:21 Tamzin 2022-08-13 07:09 Tamzin 2022-08-13 07:09
AresAthenaArtemis On hold (CU) 2022-08-09 03:02 RoySmith 2022-08-09 14:26 RoySmith 2022-08-09 14:26
জাবিরটটক On hold 2022-08-12 10:47 Tamzin 2022-08-12 10:47 Tamzin 2022-08-12 10:47
GTA5Player Closed 2022-07-30 14:57 Tamzin 2022-08-13 07:05 Tamzin 2022-08-13 07:05
Dominicvai Closed 2022-07-31 13:45 Tamzin 2022-08-12 10:41 Tamzin 2022-08-12 10:41
Icewhiz Closed 2022-08-03 20:02 RoySmith 2022-08-11 20:06 RoySmith 2022-08-11 20:06
Nangparbat Closed 2022-08-06 11:55 Orientls 2022-08-13 07:23 RoySmith 2022-08-12 17:07
Dolyn Closed 2022-08-07 01:00 TheSandDoctor 2022-08-13 03:48 TheSandDoctor 2022-08-13 03:48
Karemia Closed 2022-08-07 17:27 Girth Summit 2022-08-07 18:11 Girth Summit 2022-08-07 18:11
TopGun1066 Closed 2022-08-10 12:48 TheSandDoctor 2022-08-13 03:44 TheSandDoctor 2022-08-13 03:44

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:
  • Underlying IPs of an account, where the autoblock has expired or been ineffective.
  • Collateral damage checks for the informed hardblocking of IPs or ranges.
  • IP block exemption checks before granting IPBE (or to verify it is being used constructively).

For threats of harm (to self or others) you must email emergency@wikimedia.org (see the threats of harm page) and not use this page. Requests to investigate and confirm sockpuppetry should be listed in the sockpuppet section above, and not here (such requests will be summarily removed).

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".

==== HEADER ====
{{SPIquick}}
* {{Checkuser|
username}}

Navboxes