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