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]紅磡海濱花園2026年版的攝影作品集
[edit]- 紅磡海濱花園2026年版的攝影作品集 (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log)
Suspected related users
[edit]- 紅磡海濱花園2026年版的攝影作品集 (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log)
- 一心亦都可以係一個名字 (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log)
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)
- Several (potential) sleepers found, but
No action since they all have been globally locked. --Lymantria (talk) 08:06, 31 October 2026 (UTC)
- @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)
- Cxdnbh seems
Unlikely to this case and to AXXXXK. I cannot comment on the temporary account. --Lymantria (talk) 11:03, 31 October 2026 (UTC)
- After some discussion I have reblocked Cxdnbh based on behaviour. --Lymantria (talk) 16:22, 31 October 2026 (UTC)
- Cxdnbh seems
Heitor100YT
[edit]- Heitor Fonseca Amaro (Armação do Itapocorói) (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log)
Suspected related users
[edit]- Heitor100YT (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log)
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)
- Mentioned main account is
stale. --Krd 09:53, 30 October 2026 (UTC)
- @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)
- What exact behaviour is that? Krd 07:57, 31 October 2026 (UTC)
- @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)
TimeoRN24
[edit]- TimeoRN24 (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log)
- Jijidu24 (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log)
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)
Confirmed Blocked and tagged. --Lymantria (talk) 19:52, 29 October 2026 (UTC)
Y22021996
[edit]- Y22021996 (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log)
Suspected related users
[edit]- Infinity2046 (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log)
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)
Results:
Confirmed, together with
- JSKEternal (talk • contribs • Luxo • SUL • deleted contribs • logs • block user • block log).
Blocked and tagged. --Lymantria (talk) 07:51, 25 October 2026 (UTC)
- For older requests, please see Commons:Requests for checkuser/Archives