407:
statement could not lead to another person divining the personal identity of the user accounts in question, such disclosure would be permissible. However, on the
English Knowledge, checkusers are discouraged from making a public statement that connects one or more IP addresses to one or more named accounts, since an IP address is often much more tightly linked to a specific person. (In the case of larger IP ranges, this discouragement is not as great because larger ranges mean a less specific connection can be drawn.) When announcing the results of their checks, checkusers will employ a variety of means to avoid connecting a user to an IP address, but in some cases it is hard to avoid doing so. This policy encourages English Knowledge checkusers not to allow such connections to be made from their results, but the global privacy policy allows them to do so in the case of serious disruption, and this policy allows checkusers to prioritise compliance with Knowledge policy over the personal privacy of a user who has abusively edited the encyclopedia.
555:, checkusers are authorized to receive contact by other means, like on their user talk pages, by email, on IRC or a mailing list, and so on. If an incident is of a private or sensitive nature, you should never use public means of contact. If an incident is of an urgent nature, you should contact a checkuser you know to be online, or contact multiple active CheckUsers. If an incident is an emergency, you should contact the Wikimedia Foundation. If you require an editor with checkuser access, you may contact:
507:"Fishing" is to check an account where there is no credible evidence to suspect sockpuppetry. Checks are inappropriate unless there is evidence suggesting abusive sockpuppetry. For example, it is not fishing to check an account where the alleged sockmaster is unknown, but there is reasonable suspicion of sockpuppetry, and a suspected sockpuppet's operator is sometimes unknown until a CheckUser investigation is concluded. Checks with a negative result do not mean the check was initially invalid.
598:, which co-ordinates between checkusers on all WMF projects (and stewards, for small wikis with no local checkusers) in the checkuser-l mailing list. The inter-project team is ideal for matters concerning prolific vandals or sock users, privacy-related incidents or harassment, and other global matters of interest beyond English Knowledge. The Wikimedia-wide checkuser mailing list does not receive mail from non-subscribers, so you will need to contact a checkuser by other means (like IRC).
120:
704:
check users will learn to recognise if an ISP changes frequently or occasionally. Proxy IP addresses 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.)
411:
difficult to block the accounts and then the IP addresses without an obvious inference being drawn by onlookers from the series of blocks being made in a short period of time. When a user abusively uses several accounts and it is reasonably plausible they will create more accounts, the underlying IP range must be blocked so further abusive accounts cannot be made. The IP addresses and user accounts must therefore be blocked together.
38:
860:
1521:
66:
1354:
608:
713:
582:
472:
On the
English Knowledge, checkusers asked to run a check must have clear evidence that a check is appropriate and necessary. The onus is on an individual checkuser to explain, if challenged, why a check was run. The CheckUser log is regularly examined by arbitrators. All actions associated with the
703:
Most dialup and many DSL and cable IP addresses are dynamic, meaning they might change every session, every day, every week, every few months, or hardly ever. Unless the access times are immediately before and after each other, be cautious in declaring a match based on IP address alone. Experienced
348:
Unsubstantiated requests will be declined and a check will not be run (typically using the slogan "CheckUser is not for fishing"). On their own cognisance, checkusers may nonetheless privately make any check that falls within the bounds of CheckUser policy; this might include a check that they have
344:
Checkusers often receive requests from non-checkusers that they check an account (though many checks are also initiated by the checkuser without direction, for instance because the checkuser has noticed a suspicious account). Where a check is initiated as a result of a request from a non-checkuser,
457:
Generally, don't reveal IP addresses when announcing their results. Only give generalized results, such as that one account uses the same network (or a different network) to another account. If detailed information is provided, make sure the person you are giving it to is a trusted person who will
173:
and the additional restrictions placed by this policy. After completing an investigation with the CheckUser tool, most checkusers release their findings in generalised form (such as with a statement that "account A is, is not, or may be the same as accounts B or C"); on the
English Knowledge, the
414:
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 a checkuser then determines the user probably has engaged in such conduct—must expect the protection of the project to be given a
406:
Checkusers may state that different named accounts are operated from the same IP or range, so long as the actual IP address(es) are not specified, or if only non-specific details are given (such as the name of the country, region, or large ISP associated with the IP address). If the checkuser's
335:
The CheckUser feature facilitates access to non-public information. The
Wikimedia Foundation takes the privacy of its users extremely seriously, and there may at times be tension between protecting Knowledge from damage and disruption, and protecting the privacy of users (even disruptive ones).
410:
In some situations, while checkusers can endeavour to avoid explicitly connecting an account to an IP address, they will find it difficult or impossible not to do so. For instance, when a user edits disruptively using multiple IPs, or a mixture of IPs and accounts, the checkuser will find it
364:
Where the user has been vandalising articles or persistently behaving in a disruptive way, data may be released to non-checkusers to allow the making of IP blocks or rangeblocks, or to assist in the formulation of a complaint to relevant
Internet Service Providers or network operators;
954:
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
841:. However, all checkuser blocks are subject to direct review and significant scrutiny by the other checkusers and the Arbitration Committee. Users whose block log summary indicates a checkuser action may appeal the block, and are expected to do so on-wiki using the
933:, a steward may temporarily remove the permission, pending a decision by the Committee. The steward should check that the matter is well-founded, and make clear immediately that it is a temporary response only, since such an action could lead to controversy.
340:
Checkusers are given discretion to check an account, but must always do so for legitimate purposes. Broadly, checks must be made only in order to prevent or reduce potential or actual disruption, or to investigate credible, legitimate concerns of bad faith
901:. While many users with checkuser permissions are or were members of the Arbitration Committee, the Arbitration Committee also appoints a number of editors as checkusers, typically around once a year. Users interested in obtaining access should add the
197:
before being appointed. The use of the CheckUser tool on the
English Knowledge is monitored and controlled by the Arbitration Committee, and checkusers may have their permissions revoked by the Arbitration Committee for misuse or abuse of the tool.
700:. Almost all queries about IPs will be because two editors were behaving the same way or an editor was behaving in a way that suggests disruption. An editing pattern match is the important thing; the IP match is really just extra evidence (or not).
193:. While there is no formal requirement that checkusers also be administrators, the Arbitration Committee has traditionally restricted applications to users who are currently administrators. Checkusers must be 18 years of age or older and have
290:
On some
Wikimedia projects, an editor's IP addresses may be checked upon their request, typically to prove innocence against a sockpuppet allegation. Such checks are not allowed on the English Knowledge and such requests will not be granted.
737:
above. Checkusers also have access to a private wiki where they can share data with other members of the global checkuser team. It can also be used to store historical CheckUser data, typically in cases of long-term or complex sockpuppetry.
423:
Information about users (like their IP address) is retained for a limited period on
Wikimedia Foundation sites. Data retention is limited in this way because incidents or actions that are not current rarely require investigation.
729:), 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
837:, or similar templates. These blocks must not be reversed by non-checkusers. Administrators must not undo nor loosen any block that is specifically called a "checkuser block" without first consulting a checkuser or the
920:
or for cause. 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 request a
174:
release of actual private data (like "account D is connecting through IP address 0.1.2.3") is exceptionally rare. Conclusions derived from CheckUser data have limited usefulness, and a negative finding by a checkuser
802:
may be used for this purpose. However, in the case of such blocks, checkusers are not required to explain to non-checkusers the specific evidence at play (and are prohibited from doing so by the privacy policy).
477:, or both. Checkusers who run checks based on an unsubstantiated accusation may be cautioned or subject to sanctions, up to and including the revocation of their permissions; for a previous example of this, see
157:
an IP address or range (which includes edits by accounts while on the IP address or range), or a list of all user accounts that have used an IP address or range. They may also view a log of CheckUser actions at
572:, which can be suitable if you need other checkusers to be aware or you do not know any checkusers personally to judge which individual to contact. You may do so by emailing the English Knowledge checkuser
458:
not reveal it. Typically, such information should not be given to people who are not functionaries or experienced administrators; it would be best to deal with the abusive accounts with other checkusers.
269:
where the alternative accounts are not being used to violate site policy (such as by double voting or by giving the impression there is more support for a position in a discussion or content dispute).
336:
Checkusers must perpetually weigh these opposing concerns. In order to reach the optimal result, checkusers on the English Knowledge are required to adhere to the following conventions and practices:
879:. 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
733:. 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
299:
Checkusers are permitted, but not required, to inform an editor that their account has been checked. The result of a check may be disclosed to the community (on a community process page like
817:
Checkusers can block accounts based on technical (checkuser) evidence. They will make clear in the block log summary that they have blocked as a "checkuser action", usually by including the
1963:
756:
Checkusers who are executing a CheckUser query should remember that anonymity tools can spoof headers, including the useragent, which may make it appear that a good-faith editor with
917:
1419:
1397:
376:
These conventions arise out of practice that has emerged in the years since the checkuser tool was created, and in some cases out of rulings or "statements of best practice" by the
345:
that request may be received in public or in private. Requests received privately may be directed by the checkuser to be made publicly if the checkuser so desires, and vice versa.
2218:
1958:
1904:
636:
special pages, along with other similar functions. On the English Knowledge, checkusers also receive access to the checkuser-l global mailing list, are subscribed to the
2131:
543:
Checkusers are seasoned, experienced users, who are thoroughly vetted and highly trusted to handle sensitive and private matters, as well as other user issues. Routine
478:
219:
The CheckUser tool may be used only to prevent disruptive editing on the English Knowledge or to investigate legitimate, credible concerns of bad-faith editing or
1444:
996:
892:
473:
CheckUser tool, especially public or off-wiki actions, are subject to public view and can result in a complaint being filed with the Arbitration Committee, the
2095:
867:
CheckUser queries cannot be executed on the English Knowledge without the initiator entering something into the "Reason for check" field, which is akin to the
2059:
2107:
2047:
1711:
2202:
958:
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
905:
to their watchlists for an announcement or should contact the Committee. Appointments that are confirmed by the Arbitration Committee will be posted on
2155:
2011:
1975:
969:
Complaints involving the release of personally identifying information or other potential violations of the WMF's Privacy Policy should be made to the
461:
If the user has said they're from a certain region and their IP address confirms that, you are permitted to declare that CheckUser verifies they are.
2358:
1999:
693:
CheckUser is a technical tool, and requires a significant degree of familiarity with IPs, IP ranges, and related principles, to be correctly used.
1754:
1651:
2296:
926:
453:
advises that even if the user is committing abuse, personal information should if possible not be revealed. Checkusers are advised as follows:
368:
Where it could reasonably be thought necessary to protect the rights, property or safety of the Wikimedia Foundation, its users or the public.
2254:
2119:
2071:
1327:
1987:
1553:
929:
on Meta. Emergency requests based upon clear evidence may also be made in exceptional circumstances, the same way. In an exceptional case,
563:
2143:
1810:
1721:
266:
1312:
149:
Checkusers are able to view a list of all IP addresses used by a user account to edit the English Knowledge, a list of all edits made
2338:
1749:
194:
1679:
769:
Checkusers must be able to provide a valid reason to another checkuser (or the Arbitration Committee) for all checks they conduct.
427:
1567:
2353:
2083:
1776:
1298:
No guarantee is given that any of these scripts are currently functional, under active development, or actively being maintained.
2436:
2301:
562:
who will either advise, deal with the matter, or (especially if asked) forward it on to other checkusers for wider discussion.
1575:
961:
Complaints of infringement of CheckUser, Access to Nonpublic Information Policy or Privacy Policy breaches are handled by the
2451:
2054:
1836:
1689:
1603:
977:
772:
Checkusers should clearly mark as a "checkuser block" any block based on findings that involve checkuser data. The templates
383:
17:
2102:
2023:
1982:
1848:
1525:
906:
418:
294:
139:
used by a Knowledge user account, as well as other technical data stored by the server about a user account or IP address.
2249:
2242:
2126:
1771:
656:
548:
538:
300:
52:
988:
There are currently 51 users with the CheckUser permission on the English Knowledge. A complete listing is available at
951:
Any user account with CheckUser status that is inactive for more than one year will have their CheckUser access removed.
2237:
1953:
1928:
1598:
2259:
925:
to remove the permission from the editor. This may be done by any of the usual ways, including e-mail or a request on
812:
2441:
2385:
2230:
2167:
2035:
1583:
1477:
588:. Not all checkusers are subscribed to this list. If it is sensitive beyond that, then it may instead be sent to the
2446:
2190:
1894:
1884:
1546:
725:
73:
2278:
1783:
1684:
898:
838:
831:
796:
652:
186:
886:
764:
2348:
2162:
2090:
1822:
1716:
1694:
1409:
743:
265:
The primary purpose of CheckUser is the prevention of sockpuppetry, but community policy provides for several
2368:
2333:
2283:
1465:
942:
2405:
2326:
2078:
2030:
1940:
1916:
1832:
1699:
1593:
1563:
1434:
1429:
786:
644:
83:
983:
306:
2431:
2390:
2042:
1841:
1827:
1766:
1706:
1646:
1539:
989:
356:, which requires that identifying information not be disclosed except under the following circumstances:
182:
1516:– more detailed description of how the feature works and how to install the extension on one's own wiki.
1379:
936:
909:
on Meta-Wiki; a steward will assign the permission once the user has completed and signed the necessary
1493:
1793:
1265:
members have global CheckUser access in order to investigate allegations related to the breach of WMF
185:
who can execute CheckUser inquiries at their own discretion. The permission is granted by Knowledge's
142:
Knowledge's checkuser team uses the tool to establish whether two or more accounts are being operated
2343:
2150:
2006:
1970:
1889:
1853:
1739:
1663:
1641:
976:
Other complaints or inquiries about potential misuse of the checkuser tool should be referred to the
662:
2321:
2313:
2185:
1945:
1863:
1858:
1805:
1424:
992:. As of 26 September 2024, the following editors form the CheckUser team on the English Knowledge:
552:
2288:
1994:
1658:
821:
776:
637:
534:
220:
175:
143:
397:
2395:
1879:
1798:
1278:
1034:
868:
474:
1503:
template to indicate you have the checkuser user right – adds a category to page automatically
1385:
1225:
806:
498:
441:
353:
170:
2375:
2225:
2197:
1923:
1624:
1588:
1456:
1219:
1042:
676:
625:
524:
320:
1788:
1450:
1262:
970:
962:
189:, after community consultation and vetting of the editor by the committee's members and the
2269:
2114:
2066:
2018:
1744:
1210:
1202:
872:
633:
621:
281:
166:
159:
1367:
450:
214:
8:
2400:
2380:
2213:
1899:
1817:
1759:
1634:
1608:
1484:
1054:
484:
235:
226:
106:
854:
2138:
1911:
1345:
1190:
1182:
947:
The Wikimedia Foundation policy on revocation of CheckUser access states in part that:
668:
516:
490:
433:
389:
312:
273:
99:
91:
1439:
1266:
686:
510:
330:
2410:
1500:
1070:
1026:
876:
730:
629:
195:
signed the Wikimedia Foundation's confidentiality agreement for nonpublic information
1531:
1324:
1114:
1074:
1014:
845:
1629:
1198:
1126:
1110:
1102:
1030:
1018:
910:
352:
The disclosure of actual CheckUser data (such as IP addresses) is subject to the
190:
697:
602:
415:
higher priority than the protection of those who knowingly breach its policies.
2363:
1308:
1162:
1154:
1078:
1006:
902:
757:
640:
mailing list, and receive access to the private IRC channels at their request.
544:
377:
2425:
1178:
1150:
1138:
1130:
1058:
720:
573:
1513:
202:
1174:
1106:
748:
589:
465:
165:
CheckUser data is never accessed or released except in accordance with the
922:
1206:
1186:
1166:
1134:
1098:
1086:
1046:
1022:
1010:
1002:
620:
A user with CheckUser access will get an extra "CheckUser" option under
615:
1471:– a userbox to indicate having checkuser permission with period of time
1158:
1142:
1122:
1094:
1082:
1050:
136:
135:). The tool allows its users to determine from Knowledge's servers the
80:
It documents various processes by which the English Knowledge operates.
119:
1413:
1194:
1170:
1118:
1066:
883:
display, nor allow for the retention of, data returned from a check.
146:, and to protect Knowledge against disruptive or abusive behaviour.
24:
1062:
1038:
231:
CheckUser data may be used to investigate, prevent, or respond to:
643:
Several scripts exist for English Knowledge checkusers, including
244:
Disruption (or potential disruption) of any Wikimedia project; and
1398:
Knowledge:Arbitration Committee/CheckUser and Oversight elections
1382:– used by the arbitration committee to request usergroup addition
131:
tool is used by a small group of trusted Knowledge users (called
1353:
859:
1520:
1416:
for requesting checks that take place in more than one project.
1223:(prohibited from use by internal policy except in rare cases),
1459:– by Anthere on April 22, 2006, includes a historic background
607:
547:
and editing issues requiring checkuser review are handled at
261:
Threaten another editor into compliance in a content dispute.
1447:– Local roles, appointments, and complaints about tool usage
464:
If you're in any doubt, give no detail – and "answer like a
123:
Logo for the Knowledge CheckUser tool and the checkuser team
624:, "check IP addresses" and "recent user checks" options on
181:
On the English Knowledge, CheckUser access is entrusted to
23:
For the encyclopedic article about the CheckUser tool, see
1336:
916:
Checkuser permissions can be revoked for not meeting the
611:
A screenshot of the CheckUser form with the Vector skin.
1445:
Knowledge:Arbitration Committee/CheckUser and Oversight
893:
Knowledge:Arbitration Committee/CheckUser and Oversight
1487:
template to indicate you have the checkuser user right
1315:
on checkuser blocks and why they should not be lifted.
208:
82:
This local policy supplements—but cannot override—the
1561:
1285:
871:
feature for page-editing. All queries are logged at
16:"WP:CHECK" redirects here. For the WikiProject, see
1388:– shows CheckUser assignments and removals. Enter
1253:Held prior to appointment to Arbitration Committee
2423:
911:non-public information confidentiality document
875:, which is visible to other checkusers through
380:(now disbanded) and the Arbitration Committee.
1547:
51:. Otherwise, to open an investigation, go to
1453:– Global oversight of the tool for all wikis
813:Knowledge:Blocking policy § CheckUser blocks
689:gives checkusers the following information:
247:Legitimate concerns about bad-faith editing.
1328:statement on checkuser blocks, 18 July 2010
741:Checkusers also have access to the channel
734:
205:and applies only to the English Knowledge.
48:
45:contact a checkuser about sensitive matters
1712:On privacy, confidentiality and discretion
1554:
1540:
897:Checkuser permissions are assigned by the
760:is actually a sock of a disruptive editor.
361:With the permission of the affected user;
858:
707:There is both a checkuser mailing list (
606:
118:
1420:RfC: Community expectation of Checkuser
1249:
1247:
1245:
1243:
1241:
1239:
1237:
267:legitimate uses of alternative accounts
2424:
943:m:CheckUser policy § Removal of access
475:Wikimedia Foundation Ombuds Commission
349:elsewhere or earlier declined to make.
1652:Usernames for administrator attention
1535:
1256:
295:Notifying the account that is checked
18:Knowledge:WikiProject Check Knowledge
1234:
570:The English Knowledge checkuser team
564:A list of recently active checkusers
183:a restricted number of trusted users
144:by one individual or group of people
60:
32:
657:User:GeneralNotability/spihelper.js
549:Knowledge:Sockpuppet investigations
539:Knowledge:Sockpuppet investigations
301:Knowledge:Sockpuppet investigations
53:Knowledge:Sockpuppet investigations
13:
1777:UTRS Unblock Ticket Request System
590:Arbitration Committee mailing list
255:Exert political or social control;
14:
2463:
84:global community CheckUser policy
1519:
1352:
984:Users with checkuser permissions
711:
580:
307:CheckUser and the privacy policy
64:
36:
2339:Editorial oversight and control
1343:This page is referenced in the
653:MediaWiki:Gadget-markblocked.js
258:Apply pressure on an editor; or
251:The tool may never be used to:
1680:Password strength requirements
1318:
1301:
1292:
1277:The list above is served from
30:Procedural policy of Knowledge
1:
2437:Knowledge procedural policies
1220:Some Foundation staff members
2452:Knowledge user access levels
1435:Knowledge:User access levels
1430:Knowledge:IP block exemption
1410:m:Steward requests/Checkuser
696:CheckUser is not magic wiki
645:User:Amalthea/culoghelper.js
596:The interwiki checkuser team
428:Guidance given to checkusers
201:This policy supplements the
7:
1690:Personal security practices
1604:IP addresses are not people
990:Special:Listusers/checkuser
965:for all Wikimedia projects.
481:by the Audit Subcommittee.
10:
2468:
940:
890:
810:
666:
532:
514:
488:
431:
387:
328:
310:
271:
212:
89:
22:
15:
2312:
2268:
2178:
1939:
1872:
1772:Guide to appealing blocks
1730:
1695:Two-factor authentication
1672:
1617:
1574:
1380:m:Requests for permission
887:Assignment and revocation
765:Reasons and communication
712:
581:
384:IP information disclosure
2442:Knowledge glossary items
2127:Pending changes reviewer
1954:Requests for permissions
1731:Blocks, bans, sanctions,
1478:User wikipedia/Checkuser
1425:Knowledge:Identification
907:Requests for permissions
735:§ Contacting a checkuser
687:Meta checkuser help page
419:IP information retention
2447:Knowledge functionaries
2386:Policies and guidelines
2238:Interface administrator
2168:Volunteer Response Team
1576:Unregistered (IP) users
927:requests for permission
560:An individual checkuser
535:Knowledge:Functionaries
479:this 2009 investigation
203:global checkuser policy
1895:Vandalism-only account
1885:Single-purpose account
1584:Why create an account?
1279:Template:Functionaries
967:
918:minimum activity level
864:
832:checkuserblock-account
797:checkuserblock-account
649:User:Amalthea/cufilter
612:
511:Contacting a checkuser
178:obvious sockpuppetry.
124:
72:This page documents a
49:Contacting a checkuser
2279:Arbitration Committee
1784:Blocking IP addresses
1685:User account security
1325:Arbitration Committee
978:Arbitration Committee
949:
937:Complaints and misuse
899:Arbitration Committee
863:Example CheckUser log
862:
839:Arbitration Committee
626:Special:Contributions
610:
187:Arbitration Committee
122:
2349:Wikimedia Foundation
2179:Advanced user groups
2163:Global rights policy
1722:How to not get outed
1717:Compromised accounts
1659:Unified login or SUL
1528:at Wikimedia Commons
1466:User checkuser since
1457:CheckUser (thoughts)
1394:in the "Target" box.
1391:User:USERNAME@enwiki
999:community checkusers
873:Special:CheckUserLog
726:#wikimedia-checkuser
634:Special:CheckUserLog
628:, and access to the
622:Special:SpecialPages
227:Grounds for checking
167:Wikimedia Foundation
160:Special:CheckUserLog
2334:Formal organization
2284:Bot approvals group
2226:Edit filter manager
2091:Mass message sender
1873:Related to accounts
1526:MediaWiki CheckUser
1451:m:Ombuds commission
1091:Current arbitrators
787:checkuserblock-wide
719:), and a checkuser
717:lists.wikimedia.org
663:Guide to checkusers
603:CheckUser operation
2432:Knowledge policies
2406:Dispute resolution
2055:Extended confirmed
2031:Edit filter helper
1959:Admin instructions
1946:global user groups
1917:Courtesy vanishing
1833:Contentious topics
1823:Personal sanctions
1707:Committed identity
1594:Request an account
1368:m:CheckUser policy
1346:Knowledge Glossary
1147:Former arbitrators
931:and for good cause
903:ArbCom noticeboard
865:
744:#wikimedia-privacy
613:
592:or any arbitrator.
551:. In keeping with
451:m:CheckUser policy
378:Audit Subcommittee
215:m:CheckUser policy
125:
2419:
2418:
2103:New page reviewer
2043:Event coordinator
1828:General sanctions
1767:Appealing a block
1664:Alternate account
1647:Changing username
1599:IPs are human too
1589:Create an account
1524:Media related to
1494:Checkuser topicon
1386:m:User rights log
1282:
1263:Ombuds commission
1035:Materialscientist
971:Ombuds commission
963:Ombuds commission
877:Special:CheckUser
731:English Knowledge
630:Special:CheckUser
553:WP:NOTBUREAUCRACY
117:
116:
74:procedural policy
59:
58:
2459:
1983:(Auto) confirmed
1849:Indef ≠infinite
1673:Account security
1618:Registered users
1556:
1549:
1542:
1533:
1532:
1523:
1498:
1492:
1482:
1476:
1470:
1464:
1440:m:Privacy policy
1392:
1374:CheckUser access
1356:
1348:
1330:
1322:
1316:
1305:
1299:
1296:
1276:
1270:
1260:
1254:
1251:
1228:
1226:Wikimedia Ombuds
1222:
1043:NinjaRobotPirate
850:
844:
836:
830:
826:
820:
807:CheckUser blocks
801:
795:
791:
785:
781:
775:
746:
728:
718:
716:
715:
714:
679:
659:, among others.
587:
585:
584:
583:
527:
501:
444:
400:
331:m:Privacy policy
323:
284:
191:functionary team
176:rarely precludes
109:
102:
68:
67:
61:
40:
39:
33:
2467:
2466:
2462:
2461:
2460:
2458:
2457:
2456:
2422:
2421:
2420:
2415:
2344:Quality control
2308:
2264:
2174:
2151:Template editor
2079:IP block exempt
2007:AutoWikiBrowser
1971:Account creator
1935:
1890:Sleeper account
1868:
1854:Long-term abuse
1740:Blocking policy
1726:
1668:
1642:Username policy
1635:Reset passwords
1613:
1570:
1560:
1496:
1490:
1480:
1474:
1468:
1462:
1390:
1359:
1358:
1357:
1350:
1344:
1339:
1334:
1333:
1323:
1319:
1306:
1302:
1297:
1293:
1288:
1274:
1273:
1261:
1257:
1252:
1235:
1224:
1218:
1211:Salvio giuliano
1203:RickinBaltimore
986:
945:
939:
895:
889:
857:
848:
842:
834:
828:
824:
818:
815:
809:
799:
793:
789:
783:
779:
773:
767:
742:
724:
710:
708:
683:
682:
675:
671:
665:
638:functionaries-l
618:
605:
579:
578:checkuser-en-wp
577:
541:
531:
530:
523:
519:
513:
505:
504:
497:
493:
487:
448:
447:
440:
436:
430:
421:
404:
403:
398:WP:CUIPDISCLOSE
396:
392:
386:
333:
327:
326:
319:
315:
309:
297:
288:
287:
280:
276:
229:
217:
211:
113:
112:
105:
98:
94:
81:
65:
37:
31:
28:
21:
12:
11:
5:
2465:
2455:
2454:
2449:
2444:
2439:
2434:
2417:
2416:
2414:
2413:
2408:
2403:
2398:
2393:
2388:
2383:
2378:
2373:
2372:
2371:
2366:
2361:
2359:Founder's seat
2356:
2346:
2341:
2336:
2331:
2330:
2329:
2322:Administration
2318:
2316:
2310:
2309:
2307:
2306:
2305:
2304:
2299:
2291:
2286:
2281:
2275:
2273:
2266:
2265:
2263:
2262:
2257:
2252:
2247:
2246:
2245:
2235:
2234:
2233:
2223:
2222:
2221:
2207:
2206:
2205:
2195:
2194:
2193:
2182:
2180:
2176:
2175:
2173:
2172:
2171:
2170:
2160:
2159:
2158:
2148:
2147:
2146:
2136:
2135:
2134:
2124:
2123:
2122:
2112:
2111:
2110:
2100:
2099:
2098:
2088:
2087:
2086:
2076:
2075:
2074:
2064:
2063:
2062:
2052:
2051:
2050:
2040:
2039:
2038:
2028:
2027:
2026:
2016:
2015:
2014:
2004:
2003:
2002:
1992:
1991:
1990:
1980:
1979:
1978:
1968:
1967:
1966:
1961:
1950:
1948:
1943:
1937:
1936:
1934:
1933:
1932:
1931:
1921:
1920:
1919:
1909:
1908:
1907:
1897:
1892:
1887:
1882:
1876:
1874:
1870:
1869:
1867:
1866:
1864:Global actions
1861:
1859:Standard offer
1856:
1851:
1846:
1845:
1844:
1839:
1830:
1825:
1815:
1814:
1813:
1811:ArbCom appeals
1806:Banning policy
1803:
1802:
1801:
1796:
1791:
1781:
1780:
1779:
1774:
1764:
1763:
1762:
1757:
1752:
1747:
1736:
1734:
1733:global actions
1732:
1728:
1727:
1725:
1724:
1719:
1714:
1709:
1704:
1703:
1702:
1692:
1687:
1682:
1676:
1674:
1670:
1669:
1667:
1666:
1661:
1656:
1655:
1654:
1649:
1639:
1638:
1637:
1627:
1621:
1619:
1615:
1614:
1612:
1611:
1606:
1601:
1596:
1591:
1586:
1580:
1578:
1572:
1571:
1559:
1558:
1551:
1544:
1536:
1530:
1529:
1517:
1510:
1509:
1505:
1504:
1488:
1472:
1460:
1454:
1448:
1442:
1437:
1432:
1427:
1422:
1417:
1406:
1405:
1401:
1400:
1395:
1383:
1376:
1375:
1371:
1370:
1364:
1363:
1351:
1342:
1341:
1340:
1338:
1335:
1332:
1331:
1317:
1300:
1290:
1289:
1287:
1284:
1272:
1271:
1267:privacy policy
1255:
1232:
1231:
1230:
1229:
1216:
1213:
1148:
1145:
1092:
1089:
1055:Reaper Eternal
1000:
985:
982:
941:Main article:
938:
935:
888:
885:
856:
853:
822:checkuserblock
808:
805:
777:checkuserblock
766:
763:
762:
761:
754:
753:
752:
705:
701:
694:
681:
680:
672:
667:
664:
661:
617:
614:
604:
601:
600:
599:
593:
567:
529:
528:
520:
515:
512:
509:
503:
502:
494:
489:
486:
483:
470:
469:
462:
459:
446:
445:
437:
432:
429:
426:
420:
417:
402:
401:
393:
388:
385:
382:
374:
373:
372:
371:
370:
369:
366:
362:
354:privacy policy
350:
346:
342:
329:Main article:
325:
324:
316:
311:
308:
305:
296:
293:
286:
285:
277:
272:
263:
262:
259:
256:
249:
248:
245:
242:
239:
228:
225:
213:Main article:
210:
207:
171:privacy policy
115:
114:
111:
110:
103:
95:
90:
87:
79:
78:
69:
57:
56:
41:
29:
9:
6:
4:
3:
2:
2464:
2453:
2450:
2448:
2445:
2443:
2440:
2438:
2435:
2433:
2430:
2429:
2427:
2412:
2409:
2407:
2404:
2402:
2399:
2397:
2394:
2392:
2389:
2387:
2384:
2382:
2379:
2377:
2374:
2370:
2367:
2365:
2362:
2360:
2357:
2355:
2352:
2351:
2350:
2347:
2345:
2342:
2340:
2337:
2335:
2332:
2328:
2325:
2324:
2323:
2320:
2319:
2317:
2315:
2311:
2303:
2302:ArbCom clerks
2300:
2298:
2295:
2294:
2292:
2290:
2289:Functionaries
2287:
2285:
2282:
2280:
2277:
2276:
2274:
2271:
2267:
2261:
2258:
2256:
2253:
2251:
2248:
2244:
2241:
2240:
2239:
2236:
2232:
2229:
2228:
2227:
2224:
2220:
2217:
2216:
2215:
2211:
2208:
2204:
2201:
2200:
2199:
2196:
2192:
2189:
2188:
2187:
2186:Administrator
2184:
2183:
2181:
2177:
2169:
2166:
2165:
2164:
2161:
2157:
2154:
2153:
2152:
2149:
2145:
2142:
2141:
2140:
2137:
2133:
2130:
2129:
2128:
2125:
2121:
2118:
2117:
2116:
2113:
2109:
2106:
2105:
2104:
2101:
2097:
2094:
2093:
2092:
2089:
2085:
2082:
2081:
2080:
2077:
2073:
2070:
2069:
2068:
2065:
2061:
2058:
2057:
2056:
2053:
2049:
2046:
2045:
2044:
2041:
2037:
2034:
2033:
2032:
2029:
2025:
2022:
2021:
2020:
2017:
2013:
2010:
2009:
2008:
2005:
2001:
1998:
1997:
1996:
1995:Autopatrolled
1993:
1989:
1986:
1985:
1984:
1981:
1977:
1974:
1973:
1972:
1969:
1965:
1962:
1960:
1957:
1956:
1955:
1952:
1951:
1949:
1947:
1942:
1938:
1930:
1927:
1926:
1925:
1922:
1918:
1915:
1914:
1913:
1910:
1906:
1903:
1902:
1901:
1898:
1896:
1893:
1891:
1888:
1886:
1883:
1881:
1878:
1877:
1875:
1871:
1865:
1862:
1860:
1857:
1855:
1852:
1850:
1847:
1843:
1840:
1838:
1834:
1831:
1829:
1826:
1824:
1821:
1820:
1819:
1816:
1812:
1809:
1808:
1807:
1804:
1800:
1797:
1795:
1792:
1790:
1787:
1786:
1785:
1782:
1778:
1775:
1773:
1770:
1769:
1768:
1765:
1761:
1758:
1756:
1753:
1751:
1750:Admin's guide
1748:
1746:
1743:
1742:
1741:
1738:
1737:
1735:
1729:
1723:
1720:
1718:
1715:
1713:
1710:
1708:
1705:
1701:
1698:
1697:
1696:
1693:
1691:
1688:
1686:
1683:
1681:
1678:
1677:
1675:
1671:
1665:
1662:
1660:
1657:
1653:
1650:
1648:
1645:
1644:
1643:
1640:
1636:
1633:
1632:
1631:
1628:
1626:
1623:
1622:
1620:
1616:
1610:
1607:
1605:
1602:
1600:
1597:
1595:
1592:
1590:
1587:
1585:
1582:
1581:
1579:
1577:
1573:
1569:
1565:
1557:
1552:
1550:
1545:
1543:
1538:
1537:
1534:
1527:
1522:
1518:
1515:
1512:
1511:
1507:
1506:
1502:
1495:
1489:
1486:
1479:
1473:
1467:
1461:
1458:
1455:
1452:
1449:
1446:
1443:
1441:
1438:
1436:
1433:
1431:
1428:
1426:
1423:
1421:
1418:
1415:
1411:
1408:
1407:
1404:Related pages
1403:
1402:
1399:
1396:
1393:
1387:
1384:
1381:
1378:
1377:
1373:
1372:
1369:
1366:
1365:
1361:
1360:
1355:
1347:
1329:
1326:
1321:
1314:
1310:
1304:
1295:
1291:
1283:
1280:
1268:
1264:
1259:
1250:
1248:
1246:
1244:
1242:
1240:
1238:
1233:
1227:
1221:
1217:
1214:
1212:
1208:
1204:
1200:
1196:
1192:
1191:Mailer diablo
1188:
1184:
1183:KrakatoaKatie
1180:
1176:
1172:
1168:
1164:
1160:
1156:
1152:
1149:
1146:
1144:
1140:
1136:
1132:
1128:
1124:
1120:
1116:
1112:
1108:
1104:
1100:
1096:
1093:
1090:
1088:
1084:
1080:
1076:
1072:
1068:
1064:
1060:
1056:
1052:
1048:
1044:
1040:
1036:
1032:
1028:
1024:
1020:
1016:
1012:
1008:
1004:
1001:
998:
995:
994:
993:
991:
981:
979:
974:
972:
966:
964:
959:
956:
952:
948:
944:
934:
932:
928:
924:
919:
914:
912:
908:
904:
900:
894:
884:
882:
878:
874:
870:
861:
855:Log of checks
852:
847:
840:
833:
823:
814:
804:
798:
788:
778:
770:
759:
755:
750:
745:
740:
739:
736:
732:
727:
722:
706:
702:
699:
695:
692:
691:
690:
688:
678:
674:
673:
670:
660:
658:
654:
650:
646:
641:
639:
635:
631:
627:
623:
609:
597:
594:
591:
586:wikipedia.org
575:
571:
568:
566:is available.
565:
561:
558:
557:
556:
554:
550:
546:
540:
536:
526:
522:
521:
518:
508:
500:
499:WP:NOTFISHING
496:
495:
492:
482:
480:
476:
467:
463:
460:
456:
455:
454:
452:
443:
442:WP:MAGIC8BALL
439:
438:
435:
425:
416:
412:
408:
399:
395:
394:
391:
381:
379:
367:
363:
360:
359:
358:
357:
355:
351:
347:
343:
339:
338:
337:
332:
322:
318:
317:
314:
304:
302:
292:
283:
279:
278:
275:
270:
268:
260:
257:
254:
253:
252:
246:
243:
241:Sockpuppetry;
240:
237:
234:
233:
232:
224:
222:
216:
206:
204:
199:
196:
192:
188:
184:
179:
177:
172:
168:
163:
161:
156:
152:
147:
145:
140:
138:
134:
130:
121:
108:
104:
101:
97:
96:
93:
88:
85:
77:
76:of Knowledge.
75:
70:
63:
62:
54:
50:
46:
42:
35:
34:
26:
19:
2396:Noticeboards
2376:WikiProjects
2209:
1929:Quiet return
1880:Sockpuppetry
1799:Open proxies
1789:Range blocks
1514:mw:CheckUser
1389:
1320:
1303:
1294:
1275:
1258:
1071:Stwalkerster
1027:Girth Summit
987:
975:
968:
960:
957:
953:
950:
946:
930:
915:
896:
880:
869:edit summary
866:
816:
771:
768:
749:oversighters
684:
677:WP:PIXIEDUST
648:
642:
619:
595:
569:
559:
542:
533:Main pages:
525:WP:CONTACTCU
506:
471:
466:Magic 8-Ball
449:
422:
413:
409:
405:
375:
334:
321:WP:CUPRIVACY
298:
289:
264:
250:
230:
221:sockpuppetry
218:
200:
180:
164:
154:
150:
148:
141:
137:IP addresses
132:
128:
126:
71:
44:
2272:and related
1964:Admin guide
1941:User groups
1924:Clean start
1700:2FA for AWB
1625:New account
1115:HJ Mitchell
1075:Vanamonde93
1015:Dreamy Jazz
891:Main page:
709:checkuser-l
2426:Categories
2314:Governance
2297:SPI clerks
2270:Committees
2260:Researcher
2198:Bureaucrat
2115:Page mover
2067:File mover
1630:Logging in
1568:governance
1562:Knowledge
1412:– page at
1307:Checkuser
1199:PhilKnight
1127:Moneytrees
1111:Guerillero
1103:CaptainEek
1031:Ivanvector
1019:EdJohnston
955:provided).
851:template.
811:See also:
698:pixie dust
545:sockpuppet
282:WP:CHECKME
133:checkusers
2401:Consensus
2391:Petitions
2381:Elections
2369:Proposals
2364:Meta-Wiki
2214:Oversight
2210:CheckUser
1900:Wikibreak
1818:Sanctions
1760:Autoblock
1609:IP hopper
1508:Technical
1362:CheckUser
1309:Mackensen
1163:Callanecc
1155:Barkeep49
1079:Versageek
1007:Blablubbs
997:Appointed
723:channel (
576:queue at
236:Vandalism
169:'s (WMF)
129:CheckUser
92:Shortcuts
25:CheckUser
2255:Importer
2139:Rollback
1912:Retiring
1905:Enforcer
1564:accounts
1501:top icon
1414:metawiki
1337:See also
1179:Jpgordon
1151:AmandaNP
1139:ToBeFree
1131:Primefac
1059:RoySmith
747:, as do
669:Shortcut
517:Shortcut
491:Shortcut
434:Shortcut
390:Shortcut
341:editing.
313:Shortcut
274:Shortcut
107:WP:CHECK
2411:Reforms
2293:Clerks
2250:Founder
2243:Request
2231:Request
2219:Request
2084:Request
2036:Request
2024:Request
1485:userbox
1313:comment
1175:Joe Roe
1107:Firefly
923:Steward
846:unblock
485:Fishing
1215:Others
1207:Risker
1187:Ks0stm
1167:Drmies
1135:Sdrqaz
1099:Cabayi
1087:Zzuuzz
1047:Oshwah
1023:Ferret
1011:DatGuy
1003:Alison
655:, and
209:Policy
100:WP:CHK
47:, see
2354:Board
1842:Essay
1755:Tools
1286:Notes
1159:Bradv
1143:Z1720
1123:Maxim
1095:Aoidh
1083:Yamla
1051:Ponyo
616:Usage
2212:and
2156:PERM
2144:PERM
2132:PERM
2120:PERM
2108:PERM
2096:PERM
2072:PERM
2060:PERM
2048:PERM
2012:PERM
2000:PERM
1988:PERM
1976:PERM
1944:and
1835:and
1794:IPv6
1566:and
1499:– a
1483:– a
1195:Mkdw
1171:Izno
1119:L235
1067:ST47
792:and
758:IPBE
685:The
632:and
537:and
155:from
127:The
2327:FAQ
2203:RfB
2191:RfA
2019:Bot
1837:Log
1745:FAQ
1311:'s
1063:SQL
1039:Mz7
881:not
721:irc
574:VRT
365:and
303:).
153:or
43:To
2428::
1497:}}
1491:{{
1481:}}
1475:{{
1469:}}
1463:{{
1236:^
1209:,
1205:,
1201:,
1197:,
1193:,
1189:,
1185:,
1181:,
1177:,
1173:,
1169:,
1165:,
1161:,
1157:,
1153:,
1141:,
1137:,
1133:,
1129:,
1125:,
1121:,
1117:,
1113:,
1109:,
1105:,
1101:,
1097:,
1085:,
1081:,
1077:,
1073:,
1069:,
1065:,
1061:,
1057:,
1053:,
1049:,
1045:,
1041:,
1037:,
1033:,
1029:,
1025:,
1021:,
1017:,
1013:,
1009:,
1005:,
980:.
973:.
913:.
849:}}
843:{{
835:}}
829:{{
827:,
825:}}
819:{{
800:}}
794:{{
790:}}
784:{{
782:,
780:}}
774:{{
651:,
647:,
468:"!
223:.
162:.
151:by
1555:e
1548:t
1541:v
1349:.
1281:.
1269:.
751:.
238:;
86:.
55:.
27:.
20:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
