Jump to content

Commons:Requests for checkuser

From Wikimedia Commons, the free media repository

Shortcuts: COM:CHECK • COM:RFCU • COM:SOCK

This is the place to request investigations of abuse of multiple accounts or of other circumstances that require use of checkuser privileges.

Requesting a check

These indicators are used by CheckUsers to allow easier at-a-glance reading of their notes, actions and comments.
Request completed
Confirmed  Technically indistinguishable
Likely  Possilikely
Possible Unlikely
Inconclusive Unrelated
 No action Stale
Request declined
Declined Checkuser is not for fishing
Checkuser is not magic pixie dust. 8ball The CheckUser Magic 8-Ball says
 It looks like a duck to me Checkuser is not a crystal ball.
Information
Additional information needed Deferred to
 Doing…  Info

Please do not ask us to run checks without good reason; be aware of the following before requesting a check:

  1. Checkuser is a last resort for difficult cases; pursue other options first, such as posting on the administrator's noticeboard. (This is not a venue for requesting administrative action such as blocks or file clean-up.)
  2. 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, for example: vandalism where a block of the underlying IP or IP range is needed and suspected block evasion, vote-stacking, or other disruption where technical evidence would prevent or reduce further disruption.
    • Requests to check accounts already confirmed on other projects may be declined as redundant.
    • Requests to run a check on yourself will be declined.
  3. Evidence is required. When you request a check, you must include a rationale that demonstrates (e.g., by including diffs) what the disruption to the project is, and why you believe the accounts are related.
    • Requests to run a check without evidence or with ambiguous reasoning will result in delays or the request not being investigated.
  4. The privacy policy does not allow us to make a check that has the effect of revealing IP addresses.

Outcome

Responses will be brief in order to comply with Wikimedia privacy policy. Due to technical limitations, results are not always clear. Closed requests are archived after seven days.

Privacy concerns

If you feel that a checkuser request has led to a violation of the Wikimedia Foundation privacy policy regarding yourself, please refer the case to the Ombuds 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 using {{subst:Commons:Requests for checkuser/Inputbox/Sample}} (if the case has been archived). When editing an existing case, be sure to list/transclude the subpage here.
Example
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.

Checkuser requests to be listed (empty)
nothing found

Requests

[edit]

Harold Foppele

[edit]

Status: resolved • view • edit • history • watch
Filed: 17:09, 4 March 2026 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Johnwilliamsiii has uploaded several images sourced from https://freetocopy.co.nl/, which is otherwise largely a personal collection of images which have been uploaded to commons by Harold Foppele - e.g. the images in "Quantum" include images like File:Artistic impression of an atom 2a.png and File:Redfield equation (non Markovian).png. This seems like an odd sort of license laundering. Omphalographer (talk) 17:09, 4 March 2026 (UTC)[reply]

The CU results are Inconclusive. --Lymantria (talk) 06:34, 5 March 2026 (UTC)[reply]
I am inclined to block based on the behavioral match. Pi.1415926535 (talk) 19:38, 5 March 2026 (UTC)[reply]
@Pi.1415926535 that of course is possible. --Lymantria (talk) 06:30, 6 March 2026 (UTC)[reply]

Nv7801

[edit]

Status: open • view • edit • history • watch
Filed: 21:22, 3 March 2026 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: New user that is very interested in renaming files created by @HoosierMan1816: , see Special:Diff/1175218239, Special:Diff/1175217564 or Special:Diff/1175217875. The same thing they did under the account User:HoosietMan1816, Special:Diff/1013434633, back in March 2025. Presumably the latest sock from User:Nv7801 is at work here. Please also look for other possible socks. Thank you very much. זיו「Ziv」 • For love letters and other notes 21:22, 3 March 2026 (UTC)[reply]

Unrelated I am unable to connect Alohun9191 to any of Nv7801, Jurisdrew, or Crimea Republic - the three flag LTAs that are frequently confused for one another. However, that shouldn't stop you from placing a behavioral block. The Squirrel Conspiracy (talk) 23:09, 3 March 2026 (UTC)[reply]


Worvandae

[edit]

Status: resolved • view • edit • history • watch
Filed: 00:16, 1 March 2026 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: Special:Diff/1173766670 claims that the master is Đăng Đàn Cung.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 00:16, 1 March 2026 (UTC)[reply]

I find the discussion page unhelpful when someone wants to view it. However:
They edited pages related to Trung Kính Hạ and Vũ Phạm Hàm, for examle [1]. --Henry (dat) 00:54, 1 March 2026 (UTC)[reply]

Results: Confirmed to earlier socks in this case and to each other:

All blocked and tagged. Based on behaviour we all tag these accounts to globally banned user Đăng Đàn Cung = Musée Annam as (suspected) sock master. --Lymantria (talk) 08:28, 1 March 2026 (UTC)[reply]

Arken-B

[edit]

Status:  to be archived • view • edit • history • watch
Filed: 17:20, 27 February 2026 (UTC)

[edit]

Rationale, discussion and results

[edit]

Reason: It started with Commons:Help_desk/Archive/2025/06#Maloosak and led to the disruptive behavior of Arken-B which led to an indefinite block. Then sockpuppetry and vandalism started by creating multiple accounts. Hanooz 17:20, 27 February 2026 (UTC)[reply]

Results: The users listed are Confirmed to each other. Although Arken-B is Stale on behaviour it is Likely they are sockmaster. Additionally I found:

All blocked if necessary, and tagged. --Lymantria (talk) 08:08, 28 February 2026 (UTC)[reply]

For older requests, please see Commons:Requests for checkuser/Archives
Retrieved from "https://commons.wikimedia.org/w/index.php?title=Commons:Requests_for_checkuser&oldid=1176576157"