Commons:Requests for checkuser

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

Susandema

Status: resolved • view • edit • history • watch
Filed: 04:38, 1 September 2024 (UTC)

• Susandema (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log • checkuser)

Suspected related users

• Tiendangtran (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log • checkuser)

Rationale, discussion and results

Reason: Similar edit pattern of uploading unfree portraits of Vietnamese politician, also made similar edits at w:List of presidents of Vietnam, changing the size of the image just like the sock master did. A1Cafel (talk) 04:38, 1 September 2024 (UTC)

• Highly Likely. Эlcobbola _talk 05:46, 1 September 2024 (UTC)

Shielda

Status: resolved • view • edit • history • watch
Filed: 11:29, 28 August 2024 (UTC)

• Shielda (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log • checkuser)

Suspected related users

• Tonkatie (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log • checkuser)
• Adeonunde (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log • checkuser)

Rationale, discussion and results

Reason: Accounts created within 2 days, all uploading the same kind of files. This looks like fishing for people who got prank calls. Please check for sleepers. Yann (talk) 11:29, 28 August 2024 (UTC)

• No account has edited since 30 April 2024, thus all would be Stale. Эlcobbola _talk 13:49, 28 August 2024 (UTC)

• OK thanks. I blocked the accounts for spamming, and fishing for scams. Yann (talk) 13:54, 28 August 2024 (UTC)

A3cb1

Status: resolved • view • edit • history • watch
Filed: 12:25, 27 August 2024 (UTC)

• A3cb1 (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log • checkuser)

Suspected related users

• Silini22 (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log • checkuser)

Rationale, discussion and results

Usual edit pattern.--2A02:9130:94B6:6308:60B7:DF8E:A3A8:1908 12:29, 27 August 2024 (UTC)

Confirmed. --Krd 13:42, 27 August 2024 (UTC)

PlanespotterA320

Status:  to be archived • view • edit • history • watch
Filed: 13:28, 18 August 2024 (UTC)

• PlanespotterA320 (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log • checkuser)

Suspected related users

• 70.34.229.242 (talk • contribs • WHOIS • RBL • tools • luxo's • crossblock • block user • block log • checkuser)

Rationale, discussion and results

Same behavior of nominating images for deletion based on hypothetical copyright doubts. Highly suspicious that an IP user would be able to discuss obscure aspects of copyright and file deletion requests. --Kges1901 (talk) 13:28, 18 August 2024 (UTC)

• Declined - Please review COM:RFCU, including "The privacy policy does not allow us to make a check that has the effect of revealing IP addresses." Эlcobbola _talk 14:05, 18 August 2024 (UTC)

• IMO this should not apply for banned users. So in view of the evidence, I blocked the IP for a week. Yann (talk) 16:36, 18 August 2024 (UTC)

• The CheckUser policy does not care about your opinion, Yann. Эlcobbola _talk 16:52, 18 August 2024 (UTC)

---

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