Steward requests/Checkuser

← Requests and proposals

Steward requests (Checkuser)

latest archive→

Checkuser icons
These indicators are used by CheckUsers and stewards for easier skimming of their notes, actions and comments.
{{Confirmed}}:  Confirmed	{{MoreInfo}}:  Additional information needed
{{Likely}}: Likely	{{Deferred}}:  Deferred to
{{Possible}}: Possible	{{Completed}}: Completed
{{Unlikely}}: Unlikely	{{TakeNote}}: Note:
{{Unrelated}}: Unrelated	{{Doing}}: Doing...
{{Inconclusive}}: Inconclusive	{{StaleIP}}: Stale
{{Declined}}:  Declined	{{Fishing}}: CheckUser is not for fishing
{{Pixiedust}}: CheckUser is not magic pixie dust	{{8ball}}: The CheckUser Magic 8-Ball says
{{Duck}}:  It looks like a duck to me	{{Crystalball}}: CheckUser is not a crystal ball

This page is for requesting CheckUser information on a wiki with no local CheckUsers (see also requesting checkuser access). Make sure to follow the following instructions, or your request may not be processed in a timely manner.

Before making a request:

1. Make sure you have a good reason for the check. It will only be accepted to counter vandalism or disruption to Wikimedia wikis. Valid reasons include needing a block of the underlying IP or IP range, disruptive sockpuppetry, vote-stacking, and similar disruption where the technical evidence from running a check would prevent or reduce further disruption.
2. Be specific in your reasons. Ambiguous or insufficient reasons will cause delays. Explain the disruption and why you believe the accounts are related, ideally using diff links or other evidence.
3. Make sure there are no local checkusers.
   • Wikimedia: meta • commons • species • data
   • Wikipedia: ar • bn • ca • cs • da • de • en • es • fa • fi • fr • he • hu • id • it • ja • ko • ml • nl • pl • pt • ro • ru • simple • sl • sr • sv • th • tr • uk • vi • zh
   • Wikibooks: en
   • Wikinews: en
   • Wiktionary: en
4. Please ensure that the check hasn't already been done:

How to make a request

How to make a request: Place your request at the bottom of the section, using the template below (see also {{srcu}} help). === Username@xx.project === {{CU request |status = <!--don't change this line--> |language code = |project shortcut= |user name1 = |user name2 = |user name3 = <!-- Max 10 users --> |discussion = [[Example]]<!-- local confirmation link / local policy link --> |reason = Reasons here. ~~~~ }} For example: === Example@en.wikipedia === {{CU request |status = <!--don't change this line--> |language code = en |project shortcut= w |user name1 = Example |user name2 = Foo |user name3 = Bar <!-- Max 10 users --> |discussion = [[:w:en:Example]]<!-- local confirmation link / local policy link --> |reason = Reasons here. ~~~~ }} Specify the wiki(s) you want to perform the check on.

Cross-wiki requests
CheckUser information Global blocks/locks Permissions (global) Permissions (bot) Permissions (other) Username changes/ usurpation requests Miscellaneous requests URL blacklisting Title/username blacklisting Email blacklisting
Meta-Wiki requests
CheckUser information Deletion Permissions Requests for help

Requests

这个那@zh.wikipedia

Status:    In progress

List of users

没吃完 (contr · deleted · block · log · block log · CA · guc · checkuser · lwcheckuser)

• CU log
• Discussion: zh:Wikipedia:傀儡調查/案件/这个那#2024年6月1日

Reason(s): In the previous local request of 5/21, it has been concluded that 没吃完 is a sock of 这个那 and 没吃完 is therefore blocked by local admin. Further evidences shown in the 6/1 case suggests that logout edits and potential sleepers are used as well. To verify such claim, a check is requested. Thanks in advance. $\int$（☎） 03:34, 7 June 2024 (UTC)

Then you have to present potential sleepers. Otherwise, this request will be closed as fishing.. --Sotiale (talk) 04:36, 7 June 2024 (UTC)

Sorry for the confusing phrasing in the original comment. This check is to check for logout edits. It is already known locally that 这个那 = 没吃完 (from local admin comment on the 5/21 case), yet local administrator only blocked the sock account 没吃完, believing that this would be a one-time incident rather than habitual behavior. There are additional IPs present in the later 6/1 request that suspects a potential of logout edit from the 这个那 group, and a check is therefore requested. $\int$（☎） 06:12, 7 June 2024 (UTC)

Please let me know if you would like to have the IP presented here, if necessary for the check. --$\int$（☎） 06:15, 7 June 2024 (UTC)

See also

• Archives:
  • 2006
  • 2007: 01, 07.
  • 2008: 01, 03.
  • 2009: 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12.
  • 2010: 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12.
  • 2011: 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12
  • 2012: 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12
  • 2013: 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12
  • 2014: 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12
  • 2015: 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12
  • 2016: 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12
  • 2017: 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12
  • 2018: 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12
  • 2019: 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12
  • 2020: 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12
  • 2021: 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12
  • 2022: 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12
  • 2023: 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12
  • 2024: 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12
• CheckUser policy.

General requests for: help from a Meta sysop or bureaucrat · deletion (speedy deletions: local · multilingual) · URL blacklisting · new languages · interwiki map

Personal requests for: username changes · permissions (global) · bot status · adminship on Meta · CheckUser information (local) · local administrator help

Cooperation requests for: comments (local) (global) · translation