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 | |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Request declined | |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Information | |
![]() |
![]() |
![]() |
![]() |
Please do not ask us to run checks without good reason; be aware of the following before requesting a check:
- 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.)
- 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.
- 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.
- 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.
Requests
[edit]A3cb1
[edit]- A3cb1 (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log )
Suspected related users
[edit]- Börranga (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log )
- Janken12 (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log )
- Marlongos (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log )
- Toretello (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log )
- Warkury (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log )
Rationale, discussion and results
[edit]Some files uploaded by Börranga are recreations from previous cited known socks. Also, similar main subjects and edit pattern as both master and other socks. -- 80.29.203.133 07:41, 24 September 2025 (UTC)
Tptngnskrm
[edit]- Tptngnskrm (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log )
- Case moved to Ankrhbrbgn (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log ) as oldest account.
Suspected related users
[edit]- Iselbse (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log )
- Tptnkzmturn (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log )
- Djtlrklmajns (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log )
- Oynhbrl (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log )
- Related IP address, if any (talk • contribs • IP address, if any/lookup WHOIS • IP address, if any.html RBL • tools • luxo's • IP address, if any crossblock • block user • block log
Rationale, discussion and results
[edit]Reason: Users uploaded images with same url as source - url took you to a dodgy ecommerce site. Users uploaded one file each. Files have been deleted and users blocked as a precaution but I think a checkuser might be useful to see if I missed any Gbawden (talk) 11:55, 22 September 2025 (UTC)
Results: Not easy to track down more socks. I found a few. Quite Likely to
Confirmed the same are:
- Iselbse (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log )
- Tptnkzmturn (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log )
- Djtlrklmajns (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log )
- Oynhbrl (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log )
- Jpgcnvrt (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log )
- Tptngnskrm (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log )
- Elbshzmt (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log )
- Ankrhbrbgn (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log )
Blocked and tagged. Case moved to Ankrhbrbgn as oldest account. --Lymantria (talk) 20:49, 22 September 2025 (UTC)
ChanComThemPho
[edit]- ChanComThemPho (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log )
Suspected related users
[edit]- Spyonclear thua, PindowsOS Linux chiến thắng (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log )
- Noeruchan thua, Thcsphuninh2006 chiến thắng (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log )
- Ayane Fumihiro is worst, ChanComThemPho is good (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log )
- Noeruchan is not amazing, Thcsphuninh2006 is best (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log )
- Yuki Shiromita is worst, PindowsOS Linux is best (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log )
- JavaDragon62 thua, Thcs phu ninh 2006 thắng (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log )
- Noeruchan xấu, Thcsphuninh2006 tốt (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log )
- Pminh141 loses, Huynhthiminhngoc99 wins (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log )
- Noeruchan is worst, Thcsphuninh2006 is good (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log )
- Linam.cagle is not nice, Thcsphuninh2006 is nice (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log )
- Thcsphuninh2006 đã trở lạis (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log )
- Thcsphuninh2006 đã trở lại (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log )
and probable more...
Rationale, discussion and results
[edit]Reason: Could you please block the range? Or create a filter? Well anything to block them preventively. Yann (talk) 20:43, 20 September 2025 (UTC)
- There are 213 confirmed socks, and the sockmaster is highly resistant to rangeblocks. I'll reach out to someone about seeing if filters are an option. The Squirrel Conspiracy (talk) 02:24, 21 September 2025 (UTC)
- @Yann: As far as I know, this LTA use many proxies to evade lock/ban, so I think filter is the only option. See also this disscussion in viwiki (in Vietnamese). Nvdtn19 (talk) 08:45, 24 September 2025 (UTC)
- For older requests, please see Commons:Requests for checkuser/Archives