Last modified on 27 November 2014, at 11:20

Commons:Requests for checkuser

Shortcut: COM:CHECK, COM:RFCU

Does your request belong here?
This is the place to request sockpuppet checks or other investigations requiring CheckUser privileges. Checkuser is a last resort for difficult cases. Use other methods first. You can try posting on the administrator's noticeboard for example.
Please do not ask us to run checks without good reason:
These indicators are used by CheckUsers to allow easier at-a-glance reading of their notes, actions and comments.
Request completed
Artículo bueno.svg Confirmed Likely
Symbol possible vote.svg Possible Symbol unlikely.svg Unlikely
Symbol unsupport vote.svg Inconclusive Symbol unrelated.svg Unrelated
Symbol redirect vote.svg Completed Time2wait.svg Stale
Request declined
Declined Checkuser is not for fishing.
Checkuser is not magic pixie dust. 8ball The CheckUser Magic 8-Ball says
Cyberduck icon.png It looks like a duck to me Checkuser is not a crystal ball.
Information
Additional information needed Deferred to
 Doing… Pictogram voting info.svg Info
  1. Running a check will only be done to combat disruption on Commons, or as required to assist CheckUser investigations on other Wikimedia wikis.
    • Valid reasons for running a check include vandalism where a block of the underlying IP or IP range is needed, disruptive sockpuppetry, vote-stacking, and similar disruption where the technical evidence from running a check would prevent or reduce further disruption to Wikimedia projects.
  2. Requests to run a check with ambiguous reasoning will result in delays - please provide a rationale at the time you make the request
    • Show what the disruption to the project is, and why you believe the accounts are related.
  3. Requests to run a check on yourself will be declined
  4. The privacy policy does not allow us to make a check that has the effect of revealing IP addresses.
Outcome
Responses will be brief in order to comply with Wikimedia privacy policy. Due to technical limitations, results are not always clear. Check back regularly to see the outcome of your request. Closed requests are archived after seven days.
Privacy violation?
If you feel that a checkuser has led to a violation of the Wikimedia Foundation privacy policy regarding yourself, please refer the case to the Ombudsman commission.

If this page is displaying outdated contents even after you refresh the page in your browser, please purge this page's cache.

To request a check:

Cases are created on subpages of Commons:Requests for checkuser/Case.

Creating a request
  • Insert the name of the suspected sockpuppeteer (the main account or puppetmaster, not the sockpuppet!) in the box below, leaving out the "User:" prefix. Do not remove the text in the box, add to the end only.
  • Please explain/justify the request by saying what it is you suspect and why it is important that the check be carried out. Indicate the usernames you suspect, using {{checkuser}}. Please do not use this template in the section header, as that makes it difficult to read the account names. Include the diffs or links required to support the request and reason for it.
  • There are people to assist you and help with maintenance of the page. Just ask for help on the admin noticeboard if you really are stuck, or take your best shot and note that you weren't completely sure of what to say.
  • If a case subpage already exists, edit the existing page instead, either adding to the currently open section (if the case is not yet archived) or adding a new section to the top (if the case has been archived). When editing an existing case, be sure to list/transclude the subpage here.
Example
If you want to request a checkuser on User:John Doe, enter the text Commons:Requests for checkuser/Case/John Doe then click "Request a checkuser." You will be taken to a page where you can fill out the request. Please make your request there brief and concise.


Then transclude your subpage on the top of the list at Commons:Requests for checkuser and remove {{Checkuser requests to be listed}} from the top of the case subpage.

New requestsEdit

Completed requestsEdit

KobelEdit

Suspected related usersEdit

RationaleEdit

ResultsEdit

Kobel is stale except for one single appearance, and it is not a global account. It is Symbol possible vote.svg Possible that the named account are related, but evidence is very weak. --Krd 18:00, 22 November 2014 (UTC)

UltimatessayEdit

Suspected related usersEdit

RationaleEdit

  • Reason: Atleast these 4 socks today, and the October one blocked by Mathonius, all uploading an image that advertises essay writing services like ultimateessays.com, or spamming a link to an essay-writing service on the userpage. I blocked 2 stale socks from June: Ultimateessays and Bestassignmentservice. INeverCry 12:32, 24 November 2014 (UTC)

ResultsEdit

Results are Symbol unsupport vote.svg Inconclusive, no sleepers found. --Krd 16:27, 24 November 2014 (UTC)

Thanks for checking that. The behavior is enough to easily find these socks, so no CU results isn't a big deal. I can find them in the user creation log. Helpinessays and Buyassignment are more June 17 socks, Assignmentdoer is a Nov 11 sock. I've seen this spammer before, maybe as much as a year or more ago; I don't remember when or how many socks I blocked... I'll keep an eye out. INeverCry 02:38, 25 November 2014 (UTC)

ArchivesEdit