Wikipedia:Requests for page protection
 | This page has an administrative backlog that requires the attention of willing administrators. Please replace this notice with {{no admin backlog}} when the backlog is cleared. |
| Welcome—request protection of a page, file, or template here. | ||
|---|---|---|
|
Before requesting, read the protection policy. Full protection is used to stop edit warring between multiple users or to prevent vandalism to high-risk templates; semi-protection and pending changes are usually used to prevent IP and new user vandalism (see the rough guide to semi-protection); and move protection is used to stop pagemove revert wars. Extended confirmed protection is used where semi-protection has proved insufficient (see the rough guide to extended confirmed protection). After a page has been protected, it is listed in the page history and logs with a short rationale, and the article is listed on Special:ProtectedPages. In the case of full protection due to edit warring, admins should not revert to specific versions of the page, except to remove obvious vandalism.
Request addition of protection to a page, or increasing the current protection level
Request removal of protection from a page, or reducing the current protection level
Request a specific edit be made to a protected page
Request the non-urgent protection of multiple pages that do not require immediate administrator attention
| ||
Current requests for increase in protection level
Place requests for protection increases at the BOTTOM of this section. If you cannot find your request, check the archive of requests or the page history. Only recently answered requests are still listed here.
Reason: Most of the article appears to fall underWP:CT/IMH. FDW777 (talk) 10:36, 1 August 2026 (UTC)
Indefinite create protection: Repeatedly recreated – As one user has repeatedly recreated this template under multiple names, please set to require at least WP:TPE to create if not admin only. Zackmann (Talk to me/What I been doing) 14:05, 1 August 2026 (UTC)
Temporary semi-protection: Persistent addition of unsourced or poorly sourced content – Persistent unsourced additions of a possible football transfer. • Quinn (talk • it/its) 17:19, 1 August 2026 (UTC)
Pending changes protection: Persistent addition of unsourced/poorly-sourced material + sockpuppetry + vandalism. TA edits are rarely consecutive in this article. So I think it would be a good idea to put all non-autoconfirmed edits under review. Giovanni Potage (talk) 19:31, 1 August 2026 (UTC)
Temporary semi-protection: Persistent vandalism – TA hopping vandal. at least 3 today. Jackjd0 (talk) 19:53, 1 August 2026 (UTC)
Temporary semi-protection: Persistent vandalism. 海盐沙冰 / aka irisChronomia / Talk 04:55, 2 August 2026 (UTC)
Temporary semi-protection: Persistent sockpuppetry – Vandalism edits by TA/IP Address. Gunther : Talk 04:58, 2 August 2026 (UTC)
Temporary semi-protection, vandalism, persistent removal and distortion of the well-sourced content. Vuzorg (talk) 10:10, 2 August 2026 (UTC)
Temporary semi-protection: Persistent sockpuppetry. Peterxy（talk） 10:24, 2 August 2026 (UTC)
Temporary pending changes: Persistent disruptive editing. Entranced98 (talk) 12:01, 2 August 2026 (UTC)
- Hyderabad Disaster Response and Asset Protection Agency (edit | talk | history | links | watch | logs)
Temporary semi-protection: Persistent disruptive editing – An IP user keeps on coming with different temporary accounts and continues bolding a certain section in the lead "Enforcement Vigilance and Disaster Management Department (EV&DM)" unnecessarily. It's not per MOS:BOLD. I tried contacting them in all instances to get their inputs on this. No response has been received. Even their edit summary doesn't say anything. Requesting temporary semi protection due to the disruptive editing by a non-responsive user. Wikipicked (talk) 13:26, 2 August 2026 (UTC)
Extended confirmed protection: Persistent disruptive editing – Doing promotions with new accounts. Niasoh ❯❯❯ Wanna chat? 15:31, 2 August 2026 (UTC)
Temporary semi-protection: Persistent vandalism. HanTsî (talk) 16:55, 2 August 2026 (UTC)
Indefinite extended confirmed protection: Persistent sockpuppetry – An account, that has been deleted; however, has a username that is not one that a user would use, has been making edits on this page. User:~2026-42591-98. its a bot. please see the accounts linked to this user: https://en.wikipedia.org/wiki/Special:Contributions/~2026-42591-98. The article that alerted me to this bot account was 5-Minute Crafts. best. To save you some work: https://en.wikipedia.org/wiki/Special:CentralAuth?target=~2026-42591-98. Dillard421♂♂ (talk to me) 17:08, 2 August 2026 (UTC)
- (Non-administrator comment) @Dillard421: This is a temporary account, not a bot. I don't see anything problematic in this edit. –LaundryPizza03 (dc̄) 18:41, 3 August 2026 (UTC)
Temporary semi-protection: Persistent vandalism. Tbhotch™ (CC BY-SA 4.0) 18:27, 2 August 2026 (UTC)
Temporary semi-protection: Persistent addition of unsourced or poorly sourced content – Repeated attempts at adding a Fandom-backed TV inclusion. In solidarity, Jalen Barks (Woof) 19:11, 2 August 2026 (UTC)
Reason: There is frequent disruption from TAs, some related to ARBPIA and some related to his nationality/ethnicity/identity Rainsage (talk) 20:29, 2 August 2026 (UTC)
Reason: Indefinite semi-protection. Persistent IP and SPA vandalism for more than a year . Some BLP violations too . WP:ARBGSCT and WP:CT/BLP apply here. V. S. Video (talk) 23:38, 2 August 2026 (UTC)
Reason: Persistent addition of negative content to an article covered under WP:BLP. Has been occurring for at least 2 years at this stage. Homeostasis07 (talk/contributions) 01:47, 3 August 2026 (UTC)
Reason: Non-constructive edits by temp accounts, see Special:Diff/1367454370, Special:Diff/1363931829, and Special:Diff/1363131690. Musashi1600 (talk) 09:31, 3 August 2026 (UTC)
Reason: High level of recent temporary account vandalism. ~2026-42834-99 (talk) 13:58, 3 August 2026 (UTC)
Temporary semi-protection: Persistent sockpuppetry – Persistent block evasion. MrOllie (talk) 14:41, 3 August 2026 (UTC)
Create protection: Repeatedly recreated – LTA hoax. –LaundryPizza03 (dc̄) 16:24, 3 August 2026 (UTC)
Reason: WP:CT/IMH pattersonuwu njz (talk) 17:23, 3 August 2026 (UTC)
Semi-protection: Persistent vandalism – Possible sockpuppets as well. –Skywatcher68 (talk) 17:36, 3 August 2026 (UTC)
Reason: Potential edit warring over a contribution to the Controversies section. Removals of the passage in question have been reverted, several times by unregistered editors. There are three sections in the Talk page dedicated to discussing this, all in disapproval.
Issues with the contribution include possible use of AI, lack of a neutral point of view, lack of notability, use of niche terms, and overall disregard for Wikipedia's style guide and policies.
I'm not confident on the best ways to prevent edit warring besides making a protection request, feel free to deny or to grant the lowest possible protection. Yahyehoku (talk) 17:39, 3 August 2026 (UTC)
Declined – Content dispute. Please use the article's talk page or other forms of dispute resolution. Yue🌙 (talk) 07:50, 4 August 2026 (UTC)
Semi-protection: Disruption (including vandalism) from multiple temporary accounts. SNUGGUMS (talk / edits) 18:18, 3 August 2026 (UTC)
Temporary semi-protection: Persistent sockpuppetry – Use of multiple accounts by blocked editor CurtisPalazola. Full details can be found at Wikipedia:Administrators'_noticeboard/Incidents#CurtisPalazola_–_Competence_issue/multiple_policy_violations. Sock edits can be seen here: , , , . Betty Logan (talk) 20:04, 3 August 2026 (UTC)
Semi-protection: Persistent disruptive editing. -- Alex talk 23:16, 3 August 2026 (UTC)
Reason: Temporary account vandalism in ctop aesurias (ping me in your reply, or I won't see it) (talk) 03:02, 4 August 2026 (UTC)
- Vandalism continues. aesurias (ping me in your reply, or I won't see it) (talk) 10:45, 4 August 2026 (UTC)
Semi-protection: Persistent disruptive editing – Over the past couple weeks, various TAs and newly-registered editors have been attempting to use the subject's own birthplace myth as undisputed fact. –Skywatcher68 (talk) 05:08, 4 August 2026 (UTC)
Reason: He (my brother) has died. NAQW93 (talk) 05:29, 4 August 2026 (UTC)
- (Non-administrator comment) Correction: User:NAQW93 is the page to be protected. –LaundryPizza03 (dc̄) 07:29, 4 August 2026 (UTC)
Semi-protection: Persistent sockpuppetry – Contrary to WP:NOTLIST, SPA continues to add store locations despite the registered account (Daniel Mansell (talk · contribs)) being blocked from editing live pages. –Skywatcher68 (talk) 05:50, 4 August 2026 (UTC)
Reason: High level of new editors to this page with a particular POV following off-wiki encouragement of editing https://x.com/lesthecroc/status/2084310295846019318 Bgkc4444 (talk) 07:51, 4 August 2026 (UTC)
Semi-protected for a period of 4 days, after which the page will be automatically unprotected. Yue🌙 (talk) 08:13, 4 August 2026 (UTC)
Temporary semi-protection: Persistent vandalism – Player changed his name, editors adding back the old one. Kante4 (talk) 08:02, 4 August 2026 (UTC)
Reason: Temp account vandalism, frequent reverts Mitchsavl (talk) 09:04, 4 August 2026 (UTC)
- Semi-protected indefinitely. Favonian (talk) 09:39, 4 August 2026 (UTC)
Current requests for reduction in protection level
Unprotection: 8 years have passed since this should have been an issue, seeing how there's been no disruption basically on the other lists of deaths of Wikipedians by year in more recent years, unprotection should be okay. MakaylaHippo1998 (talk) 07:07, 31 July 2026 (UTC)
- See the instructions. You're supposed to contact the protecting admin before making a request here. In this case that admin is Oshwah, who is active today. ~Anachronist (who / me) (talk) 14:34, 31 July 2026 (UTC)
@Anachronist not necessarily only contact admin first you can also do – ping–@ to Oshwah he will respond on this page either this have two options either contact to protected admin or ping instead which ever one. ~2026-42820-77 (talk) 05:38, 2 August 2026 (UTC)
- Pinging is not approprate. You are only supposed to post here at all
only if the protecting administrator is inactive or after you have already asked them and have not received a response
, as the bright yellow highlighted text at the top of the page, that is still not read by far too many people, says. - The Bushranger One ping only 08:09, 2 August 2026 (UTC)
Reason: unupdated page since June https://www.thestatesman.com/world/iran-power-struggle-erupts-as-khamenei-corners-pezeshkian-hands-irgc-chief-control-over-us-policy-report-1503624119.html https://gulfnews.com/world/mena/irans-power-struggle-is-mojtaba-khamenei-sidelining-pezeshkian-over-the-strait-of-hormuz-dispute-over-approach-to-us-1.500629776 https://www.aljazeera.com/news/2026/8/3/trump-blasts-duplicitous-iran-after-tehran-denies-it-is-in-talks-with-the-us https://www.nbcnews.com/world/iran/trump-iran-talks-attacks-canceled-hormuz-nuclear-rcna590535 https://www.theguardian.com/world/2026/aug/03/trump-meets-his-obstinate-match-in-irans-hardball-regime ~2026-42895-18 (talk) 07:08, 4 August 2026 (UTC)
Unprotection: This article was intended to be semi-protected for only one week, not indefinitely, as stated in the protection request a week ago. Seems to be a recurring issue where some articles intended to be protected temporarily were somehow not set to expire. This also happened to the Dzhankoi article; it is intended to be extended confirmed protected for one year (see also here), but the protection wasn't set to expire initially. BriDash9000 (talk) 07:36, 4 August 2026 (UTC)
Not done – Contact the protecting admin. Favonian (talk) 07:52, 4 August 2026 (UTC)
Current requests for edits to a protected page
| − | * '''Per | + | * '''Per [[World Health Organization|WHO]]:'''
** 3,375 killed
*** 33,806 injured |
I request that the death and wounded estimate sourced to OCHA for Iranian casualties in the Infobox be corrected to the correct source which is the WHO. The current cited OCHA source says for all it's figures are "as reported by WHO Middle East Conflict Situation Report #9, 11 June 2026)". I also request the cite be changed directly to WHO's latest report from July 22 and the figures be corrected as OCHA actually misrepresents the WHO figures as "civilians" and even has the wrong numbers. The updated WHO report to cite is: Middle East Escalation of Conflict, Global external situation report #10 - 22 July 2026. It states 3,375 killed and 33,806 wounded as totals for all Iranians killed and not only civilians. The WHO total is also similar Iran and HRANA's figure of total deaths. OCHA also misrepresented the earlier June report, claiming they reported 3.4k killed whereas the WHO report from June 11 actually says 3,375. ~2026-42928-97 (talk) 09:28, 4 August 2026 (UTC)
Handled requests
A historical archive of previous protection requests can be found at Wikipedia:Requests for page protection/Archive.