CheckUser policy - Meta-Wiki

CheckUser policy - Meta-Wiki
Jump to content
From Meta, a Wikimedia project coordination wiki
(Redirected from
Checkuser
Translate this page
; This page contains
changes
which are not marked for translation.
Other languages:
Acèh
Bahasa Indonesia
Esperanto
Nederlands
Tiếng Việt
Türkçe
azərbaycanca
català
dansk
hrvatski
italiano
kurdî
magyar
occitan
oʻzbekcha / ўзбекча
polski
português
português do Brasil
română
shqip
sicilianu
slovenčina
suomi
svenska
čeština
български
македонски
русский
українська
עברית
العربية
تۆرکجه
فارسی
کٲشُر
अंगिका
मराठी
हिन्दी
বাংলা
ગુજરાતી
తెలుగు
മലയാളം
ไทย
中文
ꠍꠤꠟꠐꠤ
한국어
Policies and guidelines
CheckUser policy
This page provides information about CheckUser access and outlines the policy on its use. It was discussed in September and October 2005, and went live in November 2005.
The following page documents an official
global policy
This page has been developed and approved by the community and its compliance is mandatory for all projects. It must not be modified without prior
community approval
For legal and security reasons, the
Wikimedia Foundation
requires
two-factor authentication
for this role. This is also enforced by the software (users who don't have 2FA enabled
will not be able
to use their permissions).
CheckUser status
CheckUser is an interface for users with the
checkuser
permission. A user with the
checkuser
permission on a wiki can, in particular, check if a user is a
sockpuppet
of another user on that wiki (not on all wikis). By using it, users are able to:
Determine from which IP addresses an account has performed edits, logged actions, or password resets on the Wikimedia wiki;
Determine all edits, logged actions, login attempts, and password resets that were performed on the Wikimedia wiki from a specific IP address (including users who were logged in with an account);
Determine whether the account being checked has sent an email using the MediaWiki interface to any other user. The time of the event is logged; the destination email address and destination account is obscured.
This information is only stored for a short period (
currently 90 days
), so edits made prior to that will not be shown via the CheckUser tool. A log is kept of who has made queries using the tool. This log is available to those with the
checkuser-log
permission:
00:46, 23 April 2026,
CheckUser
got IP addresses for
Example
talk
contribs
block
(a very good reason for looking at their IPs)
00:46, 23 April 2026,
CheckUser
got users for 127.0.0.1
(another good reason)
See
Help:CheckUser
for the user manual.
Use of the tool
The tool is to be used to fight vandalism, spamming, to check for sockpuppet abuse, and to limit disruption of the project. It must be used only to prevent damage to any of the Wikimedia projects.
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. There must be a valid reason to use the CheckUser tools to investigate a user. Note that alternative accounts are not forbidden, so long as they are not used in violation of the policies (examples of violations include double-voting, increasing the apparent support for any given position, or to evade blocks or bans).
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.
Some wikis allow an editor's IPs to be checked upon their 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.
Main articles:
and
Access to nonpublic personal data policy
On
Wikimedia
projects,
considerations are of tremendous importance. Unless someone is violating policy with their actions (
e.g.
massive bot vandalism or spam) and revealing information about them is necessary to stop the disruption, it is a violation of the privacy policy to reveal their IP, whereabouts, or other information sufficient to identify them, unless they have already revealed this information themselves on the project.
Information release
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 and will not reveal it themselves.
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.
Access to CheckUser
Approved candidates for CheckUser permissions must sign, before being granted such permissions, a
confidentiality agreement for nonpublic information
pursuant the
access to nonpublic personal data policy
Only
stewards
ombuds
, some Wikimedia Foundation staff, and a very small number of other users are allowed to have CheckUser access. Users can only have CheckUser status locally (except for the ombuds and those staff members with access).
If local CheckUsers exist in a project, checks should generally be handled by those. In emergencies, or for multi-project CheckUser checks (as in the case of cross-wiki vandalism), stewards may perform local checks. Stewards should remove their own CheckUser access on the projects upon completion of the checks and notify the local CheckUsers or the CheckUser e-mail list.
If no local CheckUsers exist for a project, requests will need to be made to the stewards to perform checks (such as "is UserX a sockpuppet of UserY"). To do so, simply add the request to
Steward requests/Checkuser
listing these users and explain the need for the check (with links). Depending on the nature of the request, the steward may deny it, may ask for more information, or may answer about the likelihood of the users in question having the same IP, same proxy, same network, same country, or being completely unrelated (
see discussion for what the steward should more precisely say to the editor
).
Appointing local CheckUsers
On any wiki, there must be at least two users with CheckUser status, or none at all. This is so that they can mutually control and confirm their actions. In the case where only one CheckUser is left on a wiki (when the only other one retires, or is removed), the community must appoint a new CheckUser immediately (so that the number of CheckUsers is at least two).
On wikis with an Arbitration Committee (ArbCom) whose members have been elected with the support of at least 25–30 members of the local community, CheckUsers may be directly appointed by the Arbitrators. After agreement, a member of the Committee should simply list the candidate on
Steward requests/Permissions
On a wiki without an Arbitration Committee that meets the criterion above, or in a project where there is a preference for independent elections, the community may approve local CheckUsers (stewards not counting as local CheckUsers) per consensus. The candidate must request the CheckUser status within the local community and advertise this request properly (village pump, mailing list when available, special request page, etc.). The candidate must be familiar with the
. After gaining consensus (at least 70%–80% in pro/con voting or the highest number of votes in multiple choice elections) in the local community, and with at least 25–30 editors' approval, the successful candidate should request access at
Steward requests/Permissions
with a link to the page with the community's decision. If there are an insufficient number of votes for at least two CheckUsers on a wiki, there will be no CheckUsers on that wiki.
Mailing list
There is a closed mailing list (
CheckUser-l
) to which all stewards and CheckUsers should have access. Email the list moderators to gain access. Use this mailing list to ask for help, ideas and second opinions if you're not sure what the data means.
IRC channel
There is a private IRC channel (
#wikimedia-checkuser
connect
) to which all stewards and CheckUsers who use
IRC
should have access. This channel serves the same purpose as the
mailing list
, but in real-time. Contact any channel member to gain access; a channel manager will grant permanent access. Ask a steward if you need help gaining access.
Removal of access
Any user account with CheckUser status that is inactive(*) for more than one 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. On wikis without an approved ArbCom, the community can vote removal of access.
Complaints of infringement of CheckUser, Access to Nonpublic Information Policy or Privacy Policy breaches are handled by the
Ombuds commission
for all Wikimedia projects.
(*) See
Requests for comment/CheckUser activity RFC
Users with CheckUser access
Edit
(last updated: 2026-04-22)
Everywhere
Stewards
– upon
request
or their own initiative, stewards use it by briefly granting the right to themselves; this
is logged
(see
global group
Some
Staff members
of the Wikimedia Foundation (see
global group
Members of the
Ombuds commission
(see
global group
):
Ameisenigel
Arcticocean
Chinmayee Mishra
Faendalimas
Jnanaranjan sahu
Mehman
MrJaroslavik
Nehaoua
Revi C.
RoySmith
Teles
Zafer
Members of the
Universal Code of Conduct/Coordinating Committee
(see
global group
) have the technical ability to view the checkuser log:
Ajraddatz
Barkeep49
BRPever
Civvì
Dbeef
Ghilt
Ibrahim.ID
Luke081515
Arabic Wikipedia
Automatically generated checkusers list
Dr-Taher
Meno25
باسم
علاء
فيصل
Bengali Wikipedia
Automatically generated checkusers list
Local policy mandates that only users who gain at least 25 votes in favor and 80% support can be appointed (applications will open for no fewer than 30 days).
NahidSultan
RiazACU
Catalan Wikipedia
Automatically generated checkusers list
Jmrebes
Joutbis
Czech Wikipedia
Automatically generated checkusers list
Martin Urbanec
OJJ
Danish Wikipedia
Automatically generated checkusers list
Kaare
KnudW
Sir48
Dutch Wikipedia
Automatically generated checkusers list
Appointed by ArbCom
Daniuu
Groucho NL
Jcb
Natuur12
XXBlackburnXx
English Wikibooks
Automatically generated checkusers list
Local policy
mandates that Stewards are explicitly allowed to process non-emergency CheckUser requests.
MarcGarver
Xania
English Wikipedia
Automatically generated checkusers list
Appointed by ArbCom
AmandaNP
Aoidh
Asilvering
Barkeep49
Blablubbs
Cabayi
Callanecc
CaptainEek
Daniel
Daniel Quinlan
DatGuy
Dbeef
Dreamy Jazz
EdJohnston
Elli
Girth Summit
Guerillero
HJ Mitchell
HouseBlaster
Ivanvector
Izno
Jpgordon
KrakatoaKatie
L235
Mailer diablo
Materialscientist
Moneytrees
Mz7
NinjaRobotPirate
Oshwah
PhilKnight
Ponyo
Primefac
Reaper Eternal
Risker
RoySmith
Salvio giuliano
ScottishFinnishRadish
Sdrqaz
SilverLocust
Stwalkerster
Theleekycauldron
ToBeFree
Vanamonde93
Yamla
Zzuuzz
English Wikivoyage
Local policy
states that stewards are explicitly allowed to process non-emergency checkuser requests.
Automatically generated checkusers list
OhanaUnited
SHB2000
SelfieCity
English Wiktionary
Automatically generated checkusers list
Chuck Entz
Surjection
Finnish Wikipedia
Automatically generated checkusers list
Anr
Ejs-80
Harriv
French Wikipedia
Automatically generated checkusers list
Appointed by NomCom
Under the
local policy
, CheckUsers are appointed for six-month terms.
Durifon
LD
Le chat perché
Lewisiscrazy
Linedwell
German Wikipedia
Automatically generated checkusers list
Under the
local policy
, CheckUsers are elected for one- or two-year terms. The policy mandates that only users who gain at least 50 votes in favor and 70% support are elected, while there is a minimum of 3 CheckUsers.
Codc
Count Count
MBq
Squasher
Hebrew Wikipedia
Automatically generated checkusers list
Barak a
PurpleBuffalo
TheStriker
דגש
יונה בנדלאק
Hungarian Wikipedia
Automatically generated checkusers list
requests
and
policy
Csigabi
FoBe
Grin
Pallerti
Tgr
Indonesian Wikipedia
Automatically generated checkusers list
policy
and
requests
Janorovic Volkov
Meursault2004
Nohirara
Wagino 20100516
Italian Wikipedia
Automatically generated checkusers list
Ask21
Elwood
Gac
Melos
Mtarch11
Ruthven
Sakretsu
Shivanarayana
Superspritz
Titore
Japanese Wikipedia
Automatically generated checkusers list
policy
Dragoniez
Infinite0694
W.CC
さかおり
柏尾菓子
Korean Wikipedia
Automatically generated checkusers list
policy
and
requests
Dmthoth
Sotiale
이강철
Persian Wikipedia
Automatically generated checkusers list
Huji
Ladsgroup
Polish Wikipedia
Automatically generated checkusers list
Local policy
allows for users to be elected with 25 votes in favor and 85% support..
AramilFeraxa
Masti
Msz2001
Nux
Ptjackyll
Portuguese Wikipedia
Automatically generated checkusers list
Under the
local policy
, CheckUsers are elected for two-year terms.
Albertoleoncio
Conde Edmond Dantès
Little Sunshine
Érico
Russian Wikipedia
Automatically generated checkusers list
Appointed by ArbCom
DR
Q-bit array
Ле Лой
Serbian Wikipedia
Automatically generated checkusers list
Djordjes
Dungodung
Обрадовић Горан
Simple English Wikipedia
Automatically generated checkusers list
BRPever
Bsadowski1
Eptalon
Fr33kman
Peterdownunder
Vermont
Slovene Wikipedia
Automatically generated checkusers list
A09
MZaplotnik
Spanish Wikipedia
Automatically generated checkusers list
Local policy mandates that only users who gain at least 30 votes in favor and 80% support can be appointed.
Alhen
Bernard
BetoCG
BlackBeast
Jake Park
Montgomery
Rastrojo
Swedish Wikipedia
Automatically generated checkusers list
Julle
Stigfinnare
Tegel
Thai Wikipedia
Automatically generated checkusers list
Geonuch
Just Sayori
Siam2019
Timekeepertmk
Turkish Wikipedia
Automatically generated checkusers list
Elmacenderesi
Uncitoyen
Vincent Vega
Ukrainian Wikipedia
Automatically generated checkusers list
Appointed by ArbCom
Andriy.v
Goo3
Mykola7
NickK
Vietnamese Wikipedia
Automatically generated checkusers list
DHN
Mxn
Wikimedia Commons
Automatically generated checkusers list
· (
information page
and
requests page
Elcobbola
Jameslwoodward
Krd
Lymantria
The Squirrel Conspiracy
Wikispecies
Automatically generated checkusers list
Faendalimas
Koavf
Meta
Automatically generated checkusers list
· (
information page
and
requests page
Ajraddatz
AramilFeraxa
EPIC
Hasley
Infinite0694
Johannnes89
Minorax
Mtarch11
Sotiale
Superpes15
Vermont
Xaosflux
Wikidata
Automatically generated checkusers list
· (
information page
and
requests page
1997kB
Jasper Deng
Lymantria
Sotiale
علاء
See also
Ombuds commission
(processes complaints of privacy violations)
Requests for
CheckUser information
and
CheckUser status
Local policies of the projects
Help:CheckUser
user manual
[Foundation-l] CheckUser (thoughts)
, by Anthere on April 22, 2006, includes a historic background
User groups
Local
groups
On Meta
Without global effects
Account creators
Autopatrollers
Bots
Bureaucrats
CheckUsers
Community Wishlist managers
Confirmed users
Event organizers
Flood flag
Importers
IP block exemptions
Users blocked from the IP Information tool
Oversighters
Patrollers
Transwiki importers
Temporary account IP viewers
Uploaders
With global effects
Administrators
Central notice administrators
Global renamers
Interface administrators
MassMessage senders
OAuth administrators
Push subscription managers
Translation administrators
WMF Office IT
WMF Trust and Safety
On some wikis
Uploaders
Autopatrollers
Patrollers
Reviewers
Rollbackers
Autochecked users
Extended confirmed users
File movers
Interface editors
Abuse filter editors
Template editors
Eliminators
Translation administrators
MassMessage senders
Arbitration committee members
Extended movers
Bots with administrator rights
Flooders
Curators
Election clerks
On one wiki
(except Meta)
Noratelimit accounts
Engineers
Upload Wizard campaign editors
Image reviewers
Test wiki administrators
Property creators
Wikidata staff
Researchers
IP block exemption grantors
Movers
Functioneers
Maintainers
Wikifunctions staff
On all wikis
Blocked users
Unregistered users
Newly-registered users
Registered users
Confirmed users
Autoconfirmed users
Account creators
Bots
Administrators
Interface administrators
Bureaucrats
Oversighters
CheckUsers
IP block exemptions
Importers
Transwiki importers
Temporary account IP viewers
Users blocked from the IP Information tool
Structured Discussions bots
Historical groups
Extended uploaders
Course coordinators, Instructors, Online volunteers and Campus volunteers
ZeroRatedMobileAccess administrators
WMF ops monitoring
GWToolset users
Global
groups
Locked accounts
Unified accounts
Abuse filter helpers
Abuse filter maintainers
API high limit requestors
CAPTCHA exemptions
Founder
Global bots
Global deleters
Global Flow creators
Global interface editors
Global IP block exemptions
Global rollbackers
Global sysops
Global temporary account IP viewers
New wikis importers
Ombuds
Recursive export
Staff
Stewards
System administrators
U4C members
VRT permissions agents
wmf-email-block-override
WMF researchers
Links in
italic
are separate account statuses that are not assigned through user groups.
See also:
Wikimedia user groups
Retrieved from "
Categories
Global policies
User groups that require two-factor authentication
User groups
CheckUser
CheckUser policy
Add topic