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.
Transcluding the request
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.

nothing found

Requests

[edit]

紅磡海濱花園2026年版的攝影作品集

[edit]
[edit]

Rationale, discussion and results

[edit]

Reason: The first uploaded File:紅磡海濱花園與中環廣場.jpg and the second edited its DR (see also that page's history). Please check for sleepers. NguoiDungKhongDinhDanh 23:32, 30 October 2026 (UTC)reply

Several (potential) sleepers found, but  No action since they all have been globally locked. --Lymantria (talk) 08:06, 31 October 2026 (UTC)reply
@Lymantria
zh:LTA:AXXXXK has a habit of reporting his own sockpuppets. I suspect he may be using this pattern to frame unrelated accounts and get them blocked. Could you please check whether the accounts listed below are genuinely connected to him?
Rastinition (talk) 09:58, 31 October 2026 (UTC)reply
Cxdnbh seems Unlikely to this case and to AXXXXK. I cannot comment on the temporary account. --Lymantria (talk) 11:03, 31 October 2026 (UTC)reply
After some discussion I have reblocked Cxdnbh based on behaviour. --Lymantria (talk) 16:22, 31 October 2026 (UTC)reply

Heitor100YT

[edit]
[edit]

Rationale, discussion and results

[edit]

Reason: Indeffed on two other wikis for sockpuppetry. See COM:ANU#Heitor100YT   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 05:37, 29 October 2026 (UTC)reply

Mentioned main account is stale. --Krd 09:53, 30 October 2026 (UTC)reply
@Krd: Can you block based on behavior and the CU indefs on other wikis?   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 14:42, 30 October 2026 (UTC)reply
What exact behaviour is that? Krd 07:57, 31 October 2026 (UTC)reply

TimeoRN24

[edit]


Rationale, discussion and results

[edit]

Reason: Positive duck test on associated TEMP on fr.wp. Username also passes the duck test. Gyrostat (talk) 22:28, 28 October 2026 (UTC)reply

Confirmed Blocked and tagged. --Lymantria (talk) 19:52, 29 October 2026 (UTC)reply

Y22021996

[edit]
[edit]

Rationale, discussion and results

[edit]

Reason: User created an account 8 hours after the master was indeffed. Reuploaded File:JS Kabylie 1946-1947.jpg as File:JS Kabylie team 1946-1947.jpg. Magog the Ogre (talk) (contribs) 21:45, 24 October 2026 (UTC)reply

Results: Confirmed, together with

Blocked and tagged. --Lymantria (talk) 07:51, 25 October 2026 (UTC)reply


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