Wikipedia:CheckUser

"WP:CHECK" redirects here. You may be looking for Wikipedia:WikiProject Check Wikipedia.

For how to request CheckUser intervention, please, see Wikipedia:Sockpuppet investigations.

If you need to contact a Checkuser for a sensitive matter, please see Contacting a checkuser below.

This page documents a procedural policy of Wikipedia. The main Wikimedia Foundation policy on CheckUser has been decided on Meta (m:CheckUser#Policy) and nothing here may override that policy without approval there.

Shortcuts: WP:CHK WP:CHECK

On Wikipedia, CheckUser is a tool allowed to be used by a small number of users who are permitted to examine user IP information and other server log data under certain circumstances, for the purposes of protecting Wikipedia against actual and potential disruption and abuse. CheckUser itself simply produces log information for checking; it can require considerable skill and experience to investigate cases even with the tool.

On the English Wikipedia, CheckUser is entrusted to a restricted number of users who can both execute CheckUser inquiries subject to their own discretion and monitor and crosscheck each other's use of the function.

The permission is approved (exceedingly rarely and only with good cause) by the Arbitration Committee following community consultation and vetting by the committee, who handle many privacy-related functions. Users authorized for CheckUser need not be administrators, but must be 18 years of age or older and have provided personal identification to the Wikimedia Foundation. Once this information has been verified, the documents supplied to the Foundation are destroyed.

1 Policy
- 1.1 Grounds for checking
- 1.2 Notifying the account that is checked
2 CheckUser and privacy policy
3 Contacting a checkuser
4 CheckUser operation
5 Users with CheckUser permissions
6 See also

Policy

Main article: m:CheckUser policy

The CheckUser feature is approved for use to prevent disruption, or investigate legitimate concerns of bad faith editing.

Grounds for checking

The tool is to be used to fight vandalism, to check for sockpuppet activity, to limit disruption or potential disruption of any Wikimedia project, and to investigate legitimate concerns of bad faith editing.

The tool should not be used for political control; to apply pressure on editors; or as a threat against another editor in a content dispute.

Note that there are legitimate uses of alternative accounts, so long as they are not used in violation of the policies (for example, to double-vote or to increase the apparent support for any given position).

Some wikis allow an editor's IPs to be checked upon his or her request if, for example, there is a need to provide evidence of innocence against a sockpuppet allegation; note, however, that requesting a checkuser in these circumstances is sometimes part of the attempt to disrupt. Such requests are typically declined on the English Wikipedia.

Notifying the account that is checked

Notification to the account that is checked is permitted but is not mandatory. Similarly, notification of the check to the community is not mandatory, but may be done subject to the provisions of the privacy policy.

CheckUser and privacy policy

Main article: m:Privacy policy

The CheckUser feature accesses non-public information. The Wikimedia Foundation takes privacy of its editors extremely seriously, and there may at times be a conflict between the high priorities given to both protecting the Wiki from damage and disruption, and privacy of even problematic users. This is a very delicate area and at times no solution is ideal; the following cover some of the principles and common practices on English Wikipedia. If in doubt please ask an experienced CheckUser.

CheckUsers have a wide range of discretion to use their access provided it is for legitimate purposes – broadly, those which relate to preventing or reducing potential or actual disruption, and to investigation of legitimate concerns of bad faith editing. (CheckUser policy)
CheckUsers may accept requests publicly or otherwise, as they see fit.
Requests should not be accepted on the basis of "fishing" – that is, requests by users without a good and specific cause. On their own cognisance they may however perform privately as part of their role, any checks within the bounds of CheckUser policy – that is to say, any check which is reasonably performed in order to address issues of disruption or damage to the project.
Disclosure of CheckUser results is subject to privacy policy, which broadly states that identifying information should not be disclosed under any but a few circumstances. These include:
- "With permission of the affected user",
- "Where the user has been vandalising articles or persistently behaving in a disruptive way, data may be released to assist in the targeting of IP blocks, or to assist in the formulation of a complaint to relevant Internet Service Providers", and
- "Where it is reasonably necessary to protect the rights, property or safety of the Wikimedia Foundation, its users or the public."

IP information disclosure

It is not normally considered a breach of privacy policy to state that different named accounts are operated from the same IP or range if details of the range are not given, or if a generic description only is given (country, large ISP etc) that in no way is very likely to identify a specific person. It is undesirable to link an IP to a named account, since an IP is often much more tightly linked to a specific person. (This is often less so for larger IP ranges: the larger the range, the less obvious the connection will often be to any specific person.) CheckUsers will employ a variety of means to avoid doing this, but in some cases it is hard to avoid and "Wikipedia norms are not a suicide pact" – a user who is disruptive and needs to be addressed as such may have to accept that the price of disruption is that their IP becomes linked to their account.

This can happen in several ways:

A user is disruptive through multiple IPs, or a mixture of IPs and accounts. It is hard to block all of these (often on the same article) without obvious inference being drawn by onlookers.
A user is disruptive on multiple accounts, and it is reasonably plausible they will create more accounts, requiring the blocking of the underlying IP range that these accounts are using.

CheckUsers will often use a variety of techniques to avoid drawing such connections (new checkusers should ask and pick these up), but in many cases it is hard to avoid in a practical sense. Users who engage in problematic conduct to the point that requests for administrative action or blocking are raised and considered valid for CheckUser usage, and where CheckUser then determines that the user probably has engaged in such conduct, must expect that the protection of the project is given a higher priority than the protection of those who knowingly breach its policies on editorial conduct, if the two conflict or there is a problematic editing history.

IP information retention

As configured by Wikimedia, CheckUser keeps IP and other information on users for a fixed period, due to privacy concerns related to older log data that is potentially less useful. In general if a matter is not current, it is less likely to require administrative intervention.

Guidance given to CheckUsers

m:CheckUser policy gives this guidance on privacy compliance:

Even if the user is committing abuse, it's best not to reveal personal information if possible.

Generally, do not reveal IPs. Only give information such as same network/not same network or similar. If detailed information is provided, make sure the person you are giving it to is a trusted person who will not reveal it.
If the user has said they're from somewhere and the IP confirms it, it's not releasing private information to confirm it if needed.
If you're in any doubt, give no detail. (m:Help:CheckUser states, "If you're in any doubt at all, give no detail and answer like a Magic 8-Ball.")

A further ideal on English Wikipedia is: if you are requested to perform a check, always ask for the evidence of the user that a check is needed and appropriate, and confirm for yourself that there is indeed a valid basis that you can explain if needed. Do not assume, no matter who asks.

"Fishing"

"Fishing" is broadly defined as performing a check on accounts where there is no credible evidence to suspect sockpuppetry. Checks are inappropriate unless there is evidence suggesting abusive sock-puppetry. Checking an account where the alleged sockmaster is unknown, but there is reasonable suspicion of sockpuppetry is not fishing - a suspected sock-puppet's operator is sometimes unknown until checked. Please note that a check coming up negative does not mean that the original basis for the check was invalid.

Contacting a checkuser

Main pages: Wikipedia:Functionaries and Wikipedia:Sockpuppet investigations

In general terms, checkusers are seasoned and experienced users trusted to handle sensitive and privacy related matters and other user issues. Routine sock-puppet and editing issues requiring checkuser review are handled at Wikipedia:Sockpuppet investigations. Otherwise, and for sensitive issues, Checkusers may be contacted in any of these ways, and using any means that can normally be used to contact other users (on-wiki post, wiki email, IRC, mailing list, etc):

Contact an individual checkuser who will either advise, deal with the matter, or (especially if asked) forward it on to other checkusers for wider discussion.
Contacting the English Wikipedia checkuser team generally. This may often be the best option if you need a checkuser response, possibly other checkusers to be aware, and do not know any checkusers personally to judge which individual to contact. See the functionaries-en mailing list for how to do this. If it is sensitive beyond that, then it may instead be sent to the Arbitration Committee mailing list or any arbitrator.
For matters likely to also be of interest to other projects, such as prolific vandals or sock users, or harassment, privacy or other/'global' concerns that may go beyond English Wikipedia, there is a Wikimedia-wide checkuser mailing list for all checkusers, but you will need to contact an individual checkuser by one of the above means and ask them to forward it since that list is not able to be emailed directly from outside.

CheckUser operation

Usage

A user with CheckUser access will get an extra "CheckUser" option under Special:SpecialPages.

Hints and tips

Main article: m:Help:CheckUser

CheckUser's help page gives the following tips to users:

CheckUser is a technical tool, and requires a significant degree of familiarity with IPs, IP ranges, and related principles, to be correctly used.
CheckUser is not magic wiki pixie dust. Almost all queries about IPs will be because two editors were behaving the same way or an editor was behaving in a way that appears suggestive of possible disruption. An editing pattern match is the important thing; the IP match is really just extra evidence (or not).
Most dialup and a lot of DSL and cable IPs are dynamic. They might change every session, every day, every week, every few months or hardly ever. Unless the access times are right next to each other, be cautious in declaring a match. After a while, you get to know which ISPs change fast or slow. If it's a proxy, it might not be a match, depending on the size of the organisation running the proxy (per whois output). If it's an ISP proxy, it is not so likely to indicate a match. (Note – some users, particularly those involved in technical matters, can help identify whether an IP is likely to be a proxy, or is likely to be static, fast, or slow changing.)
There is both a checkuser mailing list (checkuser-l@lists.wikimedia.org), and a checkuser irc channel (#wikimedia-checkuser), providing means to consult and get advice on checks and their interpretation, especially in the case of more complex vandalism. Both are used by checkusers on all Wikimedia Foundation projects; they are not just for the English Wikipedia. Access to the IRC channel is by invitation only and the checkuser mailing list does not accept correspondence from non-members - users seeking assistance of a local checkuser should see the #Contacting a checkuser section above.

Reasons and communication

CheckUsers are expected to have policy-compliant grounds for CheckUser actions, identification, and blocks, and to discuss openly and fully with other CheckUsers their rationale if asked.

Checkuser blocks

Administrators who hold Checkuser privileges may block users based on non-public information revealed through the checkuser tool, and such an administrative action is generally viewed to be made in the user's capacity as an oversight or checkuser, although the action itself is an administrative one. All such blocks are subject to direct review by the Arbitration Committee, and administrators should not undo or alter any block that is specifically called a "Checkuser" block without first consulting a Checkuser.^[1]^[2]

Log of checks

Example of the checkuser log. (Sample only.)

CheckUser queries cannot be executed on the English Wikipedia without the initiator entering something in the "Reason for check" field, which is akin to the edit summary feature for page-editing. All queries are logged at Special:CheckUser/Log, which is visible only to other CheckUsers through Special:CheckUser. Each entry in the log will show who ran the check, when, the check reason, and what type of data was called (the tool can be used to get IPs, edits from an IP, or users for an IP). The log does not display, nor allow for the retention of, data returned from a check.

Assignment and revocation

Main page: Wikipedia:Arbitration Committee/CheckUser and Oversight

This section, in a nutshell;
The process is not set in stone. Users wishing access should watchlist the Arbcom noticeboard for an announcement, or contact the Committee or an individual arbitrator, and proceed from there. However, only a very small number of appointments are typically made per year.

Users who require the CheckUser permission are typically members of the Arbitration Committee and former Arbitration Committee members. For those users who are not, in order to be approved for the CheckUser flag, a case should be made and sent to the ArbCom mailing list or to any active Arbitrator. Users are advised to initially sound out interest, discuss suitability, and check the current position via an off-list email to any active Arbitration Committee member, understanding that most times, new CheckUsers are not being looked for and an exceptionally good basis would also be required. Appointments that are confirmed by the Arbitration Committee will be posted on Requests for permission on Meta-Wiki, a Steward will assign the permission once identification is confirmed.

Just as the CheckUser permission can be approved, it can be revoked. If the Committee feels that an editor has abused CheckUser, such as by inappropriately performing checks or needlessly disclosing privacy related information from a CheckUser inquiry, they will immediately request a Steward to remove the permission from the editor. This may be done by any of the usual ways, including e-mail or a request on requests for permission on Meta.

Emergency requests based upon clear evidence may also be made in exceptional circumstances, the same way. In an exceptional case, and for good cause, a Steward may temporarily remove the permission, pending a decision by the Committee. The Steward should check the matter is well founded, and make clear immediately that it is a temporary response only, since such an action could lead to controversy.

Complaints and misuse

Main article: m:CheckUser_policy#Removal_of_access

WMF policy on removal states that:

Any user account with CheckUser status that is inactive for more than a year will have their CheckUser access removed.

In case of abusive use of the tool, the Steward or the editor with the CheckUser privilege will immediately have their access removed. This will in particular happen if checks are done routinely on editors without a serious motive to do so (links and proofs of bad behavior should be provided).

Suspicion of abuses of CheckUser should be discussed by each local wiki. On wikis with an approved ArbCom, the ArbCom can decide on the removal of access... Removal can only be done by Stewards. A Steward may not decide to remove access on their own, but can help provide information necessary to prove the abuse (such as logs). If necessary, and in particular in case of lack of respect towards the privacy policy, the Board of [the] Wikimedia Foundation can be asked to declare removal of access as well.

Complaints of abuse of CheckUser or privacy policy breaches may also be brought to the Ombudsman committee.

Complaints involving the release of personally identifying information or other potential violations of the Wikimedia Foundation's Privacy Policy should be made to the Ombudsman committee.

Other complaints or inquiries about potential misuse of the checkuser tool should be referred to the Audit Subcommittee.

Users with CheckUser permissions

An automatic list is available at Special:Listusers/checkuser. As of 7 June 2011, the CheckUser team is:

Current arbitrators: Casliber^[3], Chase me ladies, I'm the Cavalry, Cool Hand Luke^[3], Coren, David Fuchs^[4], Elen of the Roads, Jclemens, John Vandenberg^[4], Kirill Lokshin, Mailer diablo, Newyorkbrad, PhilKnight, Risker^[4], Roger Davies, SirFozzie, Xeno.
Former arbitrators: Deskana^[5], FloNight, Fred Bauder, Jdforrester, Jpgordon.
Non-arbitrators appointed by Arbcom: AGK^[4], Alison, Amalthea, Avraham, Brandon, Courcelles^[4], Elockid, Frank, Hersfold, J.delanoy, Keegan^[4], Luk, MuZemike, Tiptoety, Tnxman307, Versageek, WilliamH.
Developers: Aaron Schulz, Brion VIBBER.
Others: Jimbo Wales, Wikimedia staff members (often prohibited from use by internal policy except in rare exceptions), Wikimedia Ombudsmen^[6].

Developers do not typically patrol the site for violations, and require access to the CheckUser tool mainly for maintenance and enhancement purposes. "Others" includes users who require access for WMF reasons, and WMF officers.

^ CheckUser Mackensen's comment on "Checkuserblocks," and why they should not be lifted.
^ Arbitration Committee statement on Checkuser blocks, 18 July 2010
^ ^a ^b Although this user has the checkuser tool, they generally use it for review only, and do not typically carry out checks themselves.
^ ^a ^b ^c ^d ^e ^f Current member of the Audit Subcommittee
^ This user was appointed as a CheckUser prior to joining the Committee.
^ Ombudsman commission members have global CheckUser access in order to investigate allegations related to breach of WMF privacy policy (cf. full list)

Academic Dictionaries and Encyclopedias

Wikipedia:CheckUser

Contents