Commons:Requests for checkuser


Does your request belong here?
This is the place to request sockpuppet checks or other investigations requiring CheckUser privileges. Checkuser is a last resort for difficult cases. Use other methods first. You can try posting on the administrator's noticeboard for example.
Please do not ask us to run checks without good reason:
These indicators are used by CheckUsers to allow easier at-a-glance reading of their notes, actions and comments.
Request completed
Artículo bueno.svg Confirmed Likely
Symbol possible vote.svg Possible Symbol unlikely.svg Unlikely
Symbol unsupport vote.svg Inconclusive Symbol unrelated.svg Unrelated
Symbol redirect vote.svg Completed Time2wait.svg Stale
Request declined
Declined Checkuser is not for fishing.
Checkuser is not magic pixie dust. 8ball The CheckUser Magic 8-Ball says
Cyberduck icon.png It looks like a duck to me Checkuser is not a crystal ball.
Additional information needed Deferred to
 Doing… Pictogram voting info.svg Info
  1. Running a check will only be done to combat disruption on Commons, or as required to assist CheckUser investigations on other Wikimedia wikis.
    • Valid reasons for running a check include vandalism where a block of the underlying IP or IP range is needed, disruptive sockpuppetry, vote-stacking, and similar disruption where the technical evidence from running a check would prevent or reduce further disruption to Wikimedia projects.
  2. Requests to run a check with ambiguous reasoning will result in delays - please provide a rationale at the time you make the request
    • Show what the disruption to the project is, and why you believe the accounts are related.
  3. Requests to run a check on yourself will be declined
  4. The privacy policy does not allow us to make a check that has the effect of revealing IP addresses.
Responses will be brief in order to comply with Wikimedia privacy policy. Due to technical limitations, results are not always clear. Check back regularly to see the outcome of your request. Closed requests are archived after seven days.
Privacy violation?
If you feel that a checkuser has led to a violation of the Wikimedia Foundation privacy policy regarding yourself, please refer the case to the Ombudsman commission.

If this page is displaying outdated contents even after you refresh the page in your browser, please purge this page's cache.

To request a check:

Cases are created on subpages of Commons:Requests for checkuser/Case.

Creating a request
  • Insert the name of the suspected sockpuppeteer (the main account or puppetmaster, not the sockpuppet!) in the box below, leaving out the "User:" prefix. Do not remove the text in the box, add to the end only.
  • Please explain/justify the request by saying what it is you suspect and why it is important that the check be carried out. Indicate the usernames you suspect, using {{checkuser}}. Please do not use this template in the section header, as that makes it difficult to read the account names. Include the diffs or links required to support the request and reason for it.
  • There are people to assist you and help with maintenance of the page. Just ask for help on the admin noticeboard if you really are stuck, or take your best shot and note that you weren't completely sure of what to say.
  • If a case subpage already exists, edit the existing page instead, either adding to the currently open section (if the case is not yet archived) or adding a new section to the top (if the case has been archived). When editing an existing case, be sure to list/transclude the subpage here.
If you want to request a checkuser on User:John Doe, enter the text Commons:Requests for checkuser/Case/John Doe then click "Request a checkuser." You will be taken to a page where you can fill out the request. Please make your request there brief and concise.

Then transclude your subpage on the top of the list at Commons:Requests for checkuser and remove {{Checkuser requests to be listed}} from the top of the case subpage.



Suspected related usersEdit

Rationale, discussion and resultsEdit

All accounts have been recently used to upload copyright violations with a particular focus on Chinese actor Huang Jingyu, most recently using Flickr for license laundering purposes. Previous discussion regarding the first two accounts at Special:Permalink/241753655#Yujoong. The user habitually claims, explicitly or implicitly, to have rights which he/she does not have (license reviewer, OTRS volunteer, administrator). Bint Hafiz has been signing messages as yujoong yet claims to be a different person. I'm not convinced. LX (talk, contribs) 10:04, 23 April 2017 (UTC)

  Confirmed and blocked. --Krd 11:34, 23 April 2017 (UTC)


Suspected related usersEdit

Rationale, discussion and resultsEdit

Reason: New sock of long term sockmaster Aboobacker Amani, MicNode/MicNode News is one of his many fake businesses consisting of a web site only. --Achim (talk) 14:35, 22 April 2017 (UTC)

Γιάννης 10Edit

Suspected related usersEdit

Rationale, discussion and resultsEdit

Reason: Reupload of the same useless file: File:Secondarytile.png. Probable socks of a LTA account. Yann (talk) 11:04, 25 March 2017 (UTC)

  Doing… I'll take a look... Эlcobbola talk 15:31, 3 April 2017 (UTC)
This is just a bizarre request: M.SIVASUBRAMANIAN and Ubix972 are both   Stale, and neither has edited File:Secondarytile.png anyway. العقربان, the only non-stale account is   Unrelated, which seems a DUCK conclusion by language alone. Why are any of these accounts thought to be Γιάννης 10? Эlcobbola talk 15:45, 3 April 2017 (UTC)
Sorry if I was not clear. They all uploaded the same useless file under different names: File:அருமை.png, File:Sergi Barros.png, and File:Secondarytile.png, which was also uploaded by some of the Sockpuppets of Πρώτη Σερρών. Regards, Yann (talk) 20:25, 3 April 2017 (UTC)

For older requests, please see Commons:Requests for checkuser/Archives