Wikipedia:Requests for checkuser

(Redirected from Wikipedia:RfCu)


    Read this first


    This is the place to request sockpuppet checks and other investigations requiring access to the Checkuser privilege. Possible alternatives are listed below.


    Requests likely to be accepted

    Code Situation Solution, requirements
    A Blatant attack or vandalism accounts, need IP block Submit new section at #Requests for IP check, below
    B Evading blocks, bans and remedies issued by arbitration committee Submit case subpage, including link to closed arb case
    C Ongoing, serious pattern vandalism with many incidents Submit case subpage, including diffs
    D Vote fraud, closed vote, fraud affects outcome Submit case subpage, including link to closed vote
    E 3RR violation using sockpuppets Submit case subpage, including diffs of violation
    F Evading blocks, bans and remedies issued by community Submit case subpage, including link to evidence of remedy
    G Does not fit above, but you believe check needed Submit case subpage, briefly summarize and justify

    Requests likely to be rejected

    Situation Solution
    Obvious, disruptive sock puppet Block, no checkuser needed
    Disruptive "throwaway" account used only for a few edits Block, no checkuser needed
    Checkuser on yourself to "prove your innocence" Such requests are rarely accepted, please do not ask
    Related to ongoing arbitration case Request checkuser on the arbitration case pages
    Vote fraud, ongoing vote Wait until vote closes before listing, or post at Wikipedia:Suspected sock puppets
    Vote fraud, closed vote, did not affect outcome List at Wikipedia:Administrators' noticeboard/Incidents or Wikipedia:Suspected sock puppets
    Other disruption of articles List at Wikipedia:Administrators' noticeboard/Incidents or Wikipedia:Suspected sock puppets
    Open proxy, IP address already known List at Wikipedia:WikiProject on open proxies
    You want access to the checkuser tool yourself Contact the Arbitration Committee, but such access is granted rarely


    When submitting a request

    • If submitting a new case subpage, use the inputbox below; if adding to an existing case subpage, see WP:RFCU/P#Repeat requests.
    • Choose the code letter that best fits your request. Provide evidence such as diff links as required or requested. Note that some code letters inherently require specific evidence.
    • When listing suspected accounts or IP addresses, use the {{checkuser}} or {{checkip}} templates. Please do not use this template in a section header.
    • You may add your request to the top of the #Outstanding requests section, by adding {{Wikipedia:Requests for checkuser/Case/CASENAMEHERE}}. If you do not, clerks should check for pages in Category:Checkuser requests to be listed and will do this for you.
    • Sign your request.


    After submitting a request


    Privacy violation?

    Indicators and templates   (v  · e)
    These indicators are used by Checkusers, SPI clerks and other patrolling users, to allow easier at-a-glance reading of their notes, actions and comments.
    Case decisions:
     IP blocked  {{IPblock}}  Tagged  {{Stagged}}
     Blocked but awaiting tags  {{Sblock}}  Not possible  {{Impossible}}
     Blocked and tagged  {{Blockedandtagged}}  Blocked without tags  {{Blockedwithouttags}}
     No tags  {{No tags}}  Blocked and tagged. Closing.  {{Blockedtaggedclosing}}
    Information:
     Additional information needed  {{MoreInfo}}  Deferred  {{Deferred}}
    information Note:  {{TakeNote}}  In progress  {{Inprogress}}
    Clerk actions:
     Clerk assistance requested:  {{Clerk Request}}  Clerk note:  {{Clerk-Note}}
     Delisted  {{Delisted}}  Relisted  {{Relisted}}
     Clerk declined  {{Decline}}  Clerk endorsed  {{Endorse}}
    Self-endorsed by clerk for checkuser attention  {{Selfendorse}} CheckUser requested  {{CURequest}}
    Specific to CheckUser:
     Confirmed  {{Confirmed}} Red X Unrelated  {{Unrelated}}
     Confirmed with respect to the named user(s). no No comment with respect to IP address(es).  {{Confirmed-nc}}
     Technically indistinguishable  {{Technically indistinguishable}}
     Likely  {{Likely}}  Unlikely  {{Unlikely}}
     Possible  {{Possible}}  Inconclusive  {{Inconclusive}}
    no Declined  {{Declined}} no Unnecessary  {{Unnecessary}}
     Stale (too old)  {{StaleIP}} no No comment  {{Nocomment}}
    crystal ball CheckUser is not a crystal ball  {{Crystalball}} fish CheckUser is not for fishing  {{Fishing}}
     CheckUser is not magic pixie dust  {{Pixiedust}} magic eight ball The CheckUser Magic 8-Ball says:  {{8ball}}
     Endorsed by a checkuser  {{Cu-endorsed}}  Check declined by a checkuser  {{Cudecline}}
     Possilikely (a mix between possible and likely)  {{possilikely}}


    Outstanding requests

    Declined requests

    Completed requests

    IP/A

    Requests for IP check

    • Vandal and attack accounts may be listed here for the purpose of identifying and blocking the underlying IP address or open proxy. Requests to confirm sockpuppets of known users should be listed in the sockpuppet section above.
    • If you already know the IP address of the suspected open proxy, list it at Wikipedia:Open Proxies instead.
    • Use === Subsections ===; do not create subpages.
    • List user names using the {{checkuser|username}} template. Add new reports to the top of the section.
    • Requests may be acted on or declined according to the discretion of the checkuser admins. Responses will be noted here. Specific evidence of abuse in the form of diffs may be required so as to avoid the impression of fishing for evidence.
    • Answered requests will be moved to Wikipedia:Requests for checkuser/IP check/Archive for 7 days, after which they will be deleted. No separate archive (other than the page history) will be maintained.


    Non-compliant requests

    NC

    Requests that do not follow the instructions at the top of the page will be moved here. Common reasons for noncompliance include:

    • Did not cite a code letter, or cite more than one code letter.
    • Did not cite any supporting diffs if the code letter requires diffs.
    • Included IP addresses.

    The specific deficiencies may be noted with   Additional information needed. Cases which are corrected may be moved back to the pending section. Cases which are not corrected will be deleted after 3 days.

    Please note that meeting these three criteria does not ensure that your check will be run. The checkusers retain final discretion over all cases.