Jump to content

Wikipedia:Requests for page protection

Page semi-protected
From Wikipedia, the free encyclopedia
    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
    Please add an edit request to the talk page of the protected page before adding an edit request here


    Current requests for increase in protection level

    Request addition of protection to a page, or increasing the current 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.

    Indefinite semi-protection: Persistent disruptive editing – Five edit requests this month from TAs/new users to change a sentence that was decided on in an RfC, despite a notice at the top of the talk page. I2Overcome talk 07:19, 28 February 2026 (UTC)[reply]

    Semi-protection: Persistent vandalism – LTA. Sugar Tax (talk) 10:39, 28 February 2026 (UTC)[reply]

    Not done Moot as AfD has been closed. - The Bushranger One ping only 21:23, 28 February 2026 (UTC)[reply]

    Semi-protection: Persistent sockpuppetry. Sugar Tax (talk) 10:55, 28 February 2026 (UTC)[reply]

    Not done Moot as AfD has been closed. - The Bushranger One ping only 21:22, 28 February 2026 (UTC)[reply]

    Pending changes: Persistent disruptive editing. Sugar Tax (talk) 11:11, 28 February 2026 (UTC)[reply]

    Pending-changes protected Note I have also removed the sysop-locked move protection as unnecessary; it appears it was set in 2006, reset in 2008, and since then forgotten, despite (as far as I can tell) the page only ever having had one move-remove cycle, in good faith, months before it was applied for the first time. The Bushranger One ping only 23:50, 28 February 2026 (UTC)[reply]

    Temporary move protection: To stop moves without concensus by new-comers. Agent 007 (talk) 11:26, 28 February 2026 (UTC)[reply]

    DeclinedPages are not protected preemptively. The Bushranger One ping only 21:20, 28 February 2026 (UTC)[reply]

    Reason: Article is linked in 2026 Israeli–United States strikes on Iran, which is the top-trending current event; there has already been at least one instance of vandalism. Ronnnaldo7 (talk) 16:52, 28 February 2026 (UTC)[reply]

    Declined – Not enough recent disruptive activity to justify protection. Pages are not protected pre-emptively., - The Bushranger One ping only 21:12, 28 February 2026 (UTC)[reply]

    Indefinite extended confirmed protection: I feel all pages accessible from the main menu should be Extended-confirmed-protected. hiiameverett (talk) 20:35, 28 February 2026 (UTC)[reply]

    DeclinedPages are not protected preemptively. The Bushranger One ping only 21:08, 28 February 2026 (UTC)[reply]

    Reason: We have had this protected before but can we please have infinite confirmed users only please for this article? A user who may be connected with the subject keeps trying to remove information. It keeps getting reverted. Accounts that edit claim that information isn't accurate however it's all linked to correct sources. Thank you. YamaLama9 (talk) 20:55, 28 February 2026 (UTC)[reply]

    Declined – Likely collateral damage as one or several users who are making improvements would be affected by the requested protection. I only see occasional removals of sourced information, but what appear to be significant constructive contributions by TAs. (Note also that any form of protection to this page would also stop you from editing it.) The Bushranger One ping only 21:02, 28 February 2026 (UTC)[reply]

    Semi-protection: Persistent disruptive editing – Same unsourced content which prompted the previous protection.   –Skywatcher68 (talk) 21:06, 28 February 2026 (UTC)[reply]

    Declined – Not enough recent disruptive activity to justify protection. No disruption in several days. The Bushranger One ping only 23:40, 28 February 2026 (UTC)[reply]
    @The Bushranger: I just reverted another one.   –Skywatcher68 (talk) 06:57, 1 March 2026 (UTC)[reply]

    Indefinite extended confirmed protection: Arbitration enforcement – Due to Iran affecting USA, possible ECP for now. Bryce M (talk) 22:52, 28 February 2026 (UTC)[reply]

    Declined – Not enough recent disruptive activity to justify protection. — rsjaffe 🗣️ 23:02, 28 February 2026 (UTC)[reply]

    Temporary semi-protection: Persistent vandalism. MakaylaHippo1998 (talk) 23:07, 28 February 2026 (UTC)[reply]

    Semi-protected for a period of two days, after which the page will be automatically unprotected. - The Bushranger One ping only 23:39, 28 February 2026 (UTC)[reply]

    Reason: Per Wikipedia:Contentious topics/Iranian politics, high-risk template, and at least 1 apparent instance of vandalism by a temp account. Departure– (talk) 23:32, 28 February 2026 (UTC)[reply]

    Declined – Not enough recent disruptive activity to justify protection. The Bushranger One ping only 23:37, 28 February 2026 (UTC)[reply]
    I should have also clarified the parent article Ali Khamenei is full-protected. Does this affect your verdict? Departure– (talk) 23:55, 28 February 2026 (UTC)[reply]

    Indefinite move protection: Page-move vandalism – No reason for this to ever be moved. SuperPianoMan9167 (talk) 23:51, 28 February 2026 (UTC)[reply]

    Not done Page was moved by a LTA sock. Unless they repeat the action, Revert, ignore, and move on. - The Bushranger One ping only 23:54, 28 February 2026 (UTC)[reply]

    Reason: Requesting increase to extended-confirmed protection – high amount of vandalism. Reports starting to come out that he was also eliminated in a strike so it's likely that vandalism will only get worse. aesurias (ping me in your reply, or I won't see it) (talk) 23:52, 28 February 2026 (UTC)[reply]

    Already protected by administrator Connormah. The Bushranger One ping only 23:55, 28 February 2026 (UTC)[reply]
    That is semi-protection not extended confirmed aesurias (ping me in your reply, or I won't see it) (talk) 00:01, 1 March 2026 (UTC)[reply]
    Ah, I misread. Still, seeing as there hasn't been any disruption since that protection... - The Bushranger One ping only 00:04, 1 March 2026 (UTC)[reply]

    Semi-protection: Persistent disruptive editing by multiple temp accounts. Annh07 (talk) 00:52, 1 March 2026 (UTC)[reply]

    Semi-protection: Persistent vandalism. Donnowin1 (talk) 01:08, 1 March 2026 (UTC)[reply]

    Semi-protection: Persistent vandalism – Same user is repeatedly breaking the page. Zackmann (Talk to me/What I been doing) 01:27, 1 March 2026 (UTC)[reply]

    Already protected by administrator ToBeFree. The Bushranger One ping only 04:11, 1 March 2026 (UTC)[reply]

    Temporary semi-protection: Persistent vandalism. LuniZunie(talk) 01:33, 1 March 2026 (UTC)[reply]

    User(s) blocked: ~2026-13325-39 (talk · contribs) blocked by Lofty abyss. The Bushranger One ping only 04:10, 1 March 2026 (UTC)[reply]

    Reason: Likely sockpuppet continually trying to mass-revert to an alternate history version of the European army, with paragraphs full of incomprehensible phrasing aesurias (ping me in your reply, or I won't see it) (talk) 02:10, 1 March 2026 (UTC)[reply]

    Semi-protected for a period of two weeks, after which the page will be automatically unprotected. The Bushranger One ping only 04:07, 1 March 2026 (UTC)[reply]

    Reason: Not three days since 3m semi expired, LTA is back at it again. Request indef semi protection. Jclemens (talk) 02:31, 1 March 2026 (UTC)[reply]

    Semi-protected for a period of six months, after which the page will be automatically unprotected. Ordinarly I'd say 'wait and see if they return' vs protecting after just one, but given the nature of this LTA... The Bushranger One ping only 04:05, 1 March 2026 (UTC)[reply]

    Temporary semi-protection: Persistent vandalism. Death hoaxes. MakaylaHippo1998 (talk) 02:53, 1 March 2026 (UTC)[reply]

    Semi-protected for a period of two weeks, after which the page will be automatically unprotected. The Bushranger One ping only 04:03, 1 March 2026 (UTC)[reply]

    Reason: High level of IP vandalism. I think that it would be best if ONLY registered users can edit the article. Indigault (talk) 04:13, 1 March 2026 (UTC)[reply]

    Semi-protected for a period of one week, after which the page will be automatically unprotected. The Bushranger One ping only 05:10, 1 March 2026 (UTC)[reply]

    Reason: Falls under under WP:A-I, Extended confirmed, and also IP vandalism is starting to take place. shane (talk to me if you want!) 04:30, 1 March 2026 (UTC)[reply]

    DeclinedPages are not protected preemptively. This article only tangentially falls under PIA/A-I; in cases like this, enforcing the ECR is done by manually reverting edits by non-XC editors to the portions falling under it instead of ECPing the entire article. If TA disruption intensifies, please re-request on that basis. - The Bushranger One ping only 05:09, 1 March 2026 (UTC)[reply]

    Temporary semi-protection: Persistent vandalism – Got vandalism again after protection expired. Tim (talk) 05:36, 1 March 2026 (UTC)[reply]

    Already protected by administrator Materialscientist. Malcolmxl5 (talk) 11:15, 1 March 2026 (UTC)[reply]

    Temporary semi-protection: Persistent vandalism – TA frequently altering the name to trump K. center. 海盐沙冰 / aka irisChronomia / Talk 06:23, 1 March 2026 (UTC)[reply]

    Indefinite extended confirmed protection: Persistent sockpuppetry – Continual ban evasion in the past 3 months. Trailblazer101🔥 (discuss · contribs) 06:50, 1 March 2026 (UTC)[reply]

    Temporary extended confirmed protection: Persistent sockpuppetry – I know protection is typically not necessary for drafts, but this one has been subject to persistent abuse from a sockmaster with no signs of them ceasing anytime soon. It is admittedly exhaustive to revert each time they come back with a new puppet account, and we should prevent this SPA from having access to this highly edited draft for a major forthcoming film. It is a waste of constructive editors' time and needs to be stopped. Trailblazer101🔥 (discuss · contribs) 06:54, 1 March 2026 (UTC)[reply]

    Temporary semi-protection: Persistent Disruptive Editing. Staraction (talk · contribs) 06:58, 1 March 2026 (UTC)[reply]

    Done by Materialscientist. Staraction (talk · contribs) 08:12, 1 March 2026 (UTC) (Non-administrator comment)[reply]
    Already protected. Malcolmxl5 (talk) 11:13, 1 March 2026 (UTC)[reply]

    Temporary full protection: Content dispute/edit warring. Absolutiva 07:10, 1 March 2026 (UTC)[reply]

    User(s) blocked. User:DNASeer blocked by Fences and windows. --Malcolmxl5 (talk) 11:03, 1 March 2026 (UTC)[reply]

    Temporary full protection: Content dispute/edit warring. Absolutiva 07:13, 1 March 2026 (UTC)[reply]

    User(s) blocked. User:DNASeer blocked by Fences and windows. --Malcolmxl5 (talk) 11:05, 1 March 2026 (UTC)[reply]

    Temporary extended-confirmed protection: Arbitration enforcement. hit by an iranian projectile. NeoSyria\Freedoxm (talk · contribs) 07:23, 1 March 2026 (UTC)[reply]

    Reason: Persistent unreferenced edits. Hotwiki (talk) 07:24, 1 March 2026 (UTC)[reply]

    Reason: Persistent Vandalism. SteamManx (talk) 08:17, 1 March 2026 (UTC)[reply]

    Temporary semi-protection: Persistent vandalism – Nonsense edits from an IP range that's too broad to block. Chrisahn (talk) 08:49, 1 March 2026 (UTC)[reply]

    Already protected by administrator Materialscientist. Malcolmxl5 (talk) 10:59, 1 March 2026 (UTC)[reply]

    Reason: Semi protection until 1/31/2027 was removed entirely accidentally. MakaylaHippo1998 (talk) 09:17, 1 March 2026 (UTC)[reply]

    Reason: Request page protection after vandalism by IP address, as per WP:CT/KURD PawWiki2 (talk) 09:56, 1 March 2026 (UTC)[reply]

    Reason: Changes in conflict with source again. Shortly after 1-year PP expired. Adakiko (talk) 12:00, 1 March 2026 (UTC)[reply]

    Temporary semi-protection: Contentious topic restriction. New interim leader of Iran, requesting protection per WP:CT/IRP ScrubbedFalcon (talk) 12:39, 1 March 2026 (UTC)[reply]

    Semi-protection: Persistent sockpuppetry – Target of LTA. enbi [they/them] • [talk] 14:23, 1 March 2026 (UTC)[reply]

    Indefinite semi-protection: Persistent vandalism – Why should a page that literally has "vandalism" in it's name and a long history of vandalism not be indefinitely semi-protected. --Prothe1st (leave me a message)-- 14:36, 1 March 2026 (UTC)[reply]

    Reason: Lots of vandalism right now, including grossly insulting content. Generalrelative (talk) 15:23, 1 March 2026 (UTC)[reply]

    Current requests for reduction in protection level

    Request removal of protection from a page, or reducing the current protection level

    Before posting a request for unprotection, please discuss it with the protecting administrator first. You can create a request below only if you receive no response from them.

    To find out which administrator protected the page, go to the page's edit history and click on the "View logs for this page" link (located underneath the page's title). The protecting administrator is listed in the protection log entry, next to the words "protected", "changed protection level", or "configured pending changes". If there are a large number of log entries on the page, use the drop-down menu near the top of the page and select "Protection log" or "Pending changes log" to filter the logs accordingly.

    DO NOT request a reduction in protection if...

    • ...you are being prevented from editing the page. A desire to change content is not a valid reason for unprotection. Instead:
      • If you can edit the article's talk page, use the WP:Edit Request Wizard to propose a change on the article's talk page. Include an explanation of the exact content that you want to change, and what the content will be afterward.
      • If the article's talk page is protected, you may propose a change at Wikipedia:Requests for page protection/Edit.
    • ...your reasoning for reducing protection is that the article has not been vandalized. That simply means the protection is working as intended.
    • ...your reasoning for reducing protection is basically "a long time has passed" without supporting details.
    • ...you haven't contacted the protecting administrator.

    You may request a protection reduction below if...

    • ...you want to change the protection level of a template or module from full protection to template protection. You may add the request to this page without having to discuss it with the protecting administrator first.
    • ...you need to remove creation protection from a location where no page exists (redlinked pages) after a draft version of the intended article is prepared beforehand and ready to be published.
    • ...you are proposing a trial reduction in protection for a page that has been protected for several years, provided the proposal is supported by evidence such as talk page activity, page views, page traffic, number of watchers, frequency of edit requests, and prior history of vandalism.
    • ...the protecting administrator is inactive or has not responded to you in several days.

    If you cannot locate your request, make sure to check the request archives to see if it's been moved there. Only requests that have been recently answered will still be listed here.

    Reason: remove hacker coding ~2026-13096-90 (talk) 07:40, 28 February 2026 (UTC)[reply]

    This request is extremely vague. What do you mean by "hacker coding"? —Jéské Couriano v^_^v threads critiques 15:09, 28 February 2026 (UTC)[reply]
    Not unprotected – Please use an edit request to request specific changes to be made to the protected page. ~Anachronist (who / me) (talk) 20:50, 28 February 2026 (UTC)[reply]

    Reason: to remove havker coding ~2026-13096-90 (talk) 07:41, 28 February 2026 (UTC)[reply]

    As above, this request is extremely vague, and the same question applies. —Jéské Couriano v^_^v threads critiques 15:10, 28 February 2026 (UTC)[reply]
    Not done, nothing to do here, the article isn't protected. ~Anachronist (who / me) (talk) 20:52, 28 February 2026 (UTC)[reply]

    Reason: I have a question about important information that could be added to the article? I'm not sure if the protection level should be reduced but I don't know where else to ask about this? ~2026-13315-49 (talk) 23:53, 28 February 2026 (UTC)[reply]

    Not unprotected – Please use an edit request to request specific changes to be made to the protected page. ~Anachronist (who / me) (talk) 02:42, 1 March 2026 (UTC)[reply]

    Comment:: The talk page is not protected. Making a edit request does not require unprotection. Sumanuil. (talk to me) 02:37, 1 March 2026 (UTC)[reply]

    After declining this request, I noticed that the requested page Talk:Kiwifarms doesn't redirect to Talk:Kiwi Farms like the article page does. I have just fixed that. Maybe that was the anon's concern. ~Anachronist (who / me) (talk) 02:46, 1 March 2026 (UTC)[reply]

    Unprotection: Reason for protection (edit warring over the death of Khamenei) no longer applies. SuperPianoMan9167 (talk) 02:52, 1 March 2026 (UTC)[reply]

    Already unprotected by administrator Rsjaffe. Malcolmxl5 (talk) 14:52, 1 March 2026 (UTC)[reply]

    Unprotection: Intended to be protected a decade when protected in 2010 but changed to indefinite a few months later so that "it can always be unprotected later", but that has accidentally extended the protection by nearly six years. MakaylaHippo1998 (talk) 08:06, 1 March 2026 (UTC)[reply]

    Current requests for edits to a protected page

    Request a specific edit be made to a protected page
    Please add an edit request to the talk page of the protected page before adding an edit request here

    Requests for specific edits should be made on the talk page of the protected article. You can create an edit request below only if the talk page is also protected, preventing you from adding a request there.

    Otherwise, this is the correct place to use in order to add an edit request if you are unable to add one to the article's talk page. Please see the top of this page for instructions on how to properly add a request.


    Kosovo's President "Vjosa Osmani" "unwaveringly stands with the United States and its allies in defending freedom, peace, security, and stability." and also "Strongly condemn the attacks of the Iranian regime against our allies in the Middle East" https://x.com/VjosaOsmaniPRKS/status/2027717696704463244 MalKasemi (talk) 20:00, 28 February 2026 (UTC)[reply]

    In lead of article is "Operation Epstein Fury", should be "Operation Epic Fury". Thanks. KKE ~2026-46277-1 (talk) 21:29, 28 February 2026 (UTC)[reply]

    Not done The page does not exist, and 2026 Israeli–United States strikes on Iran doesn't appear to have that vandalism in its history. - The Bushranger One ping only 22:01, 28 February 2026 (UTC)[reply]

    After Khamenei died JUST TODAY, Please, Mark Khamenei on the "Commanders and Leaders" template Assassinated (https://www.bbc.com/news/live/cn5ge95q6y7t) Sam Asadollahi (talk) 23:13, 28 February 2026 (UTC)[reply]

    Not done until there is actual confirmation. - The Bushranger One ping only 23:31, 28 February 2026 (UTC)[reply]

    I would like to request that the (grammatical) error(s) where 28/02/2026 is notated as February 28 2026 and ‘a unnamed Israeli official’ is present in the subsection ‘Supreme Leader (1989-present) be changed to ‘February 28, 2026’ and ‘an unnamed Israeli official’ in respective order. Bear in mind the above edit was rejected, despite its uncontroversial nature, on grounds of a completely unrelated matter. Please fix this as soon as possible. ThanksKdjdks (talk) 23:51, 28 February 2026 (UTC)[reply]

    Done, with the date changed to 28 February 2026 based on the established day-month-year style throughout the article. Fixed the grammar issue too, of course! Thanks a lot! Chaotic Enby (talk · contribs) 00:53, 1 March 2026 (UTC)[reply]

    Ali Khemenei

    Change "in which the US will be lead by Steve Witkoff" to "in which the US will be led by Steve Witkoff" ~2026-13259-94 (talk) 08:05, 1 March 2026 (UTC)[reply]

    Already done. --Malcolmxl5 (talk) 15:48, 1 March 2026 (UTC)[reply]

    Bahrain International Airport was targeted by Iran as well, not just Kuwait and the UAE (Source: https://www.newsofbahrain.com/bahrain/127615.html) However, damage was a bit more minor. MomedWiki (talk) 09:46, 1 March 2026 (UTC)[reply]

    Under casualties and losses, add 1 person injured by strikes on Duqm Port Abu Isa 🇴🇲 11:14, 1 March 2026 (UTC)[reply]

    Sources:
    Khaleej Times: https://www.khaleejtimes.com/world/gulf/one-injured-drones-target-oman-duqm-port?_refresh=true
    Reuters https://www.reuters.com/world/middle-east/several-loud-blasts-heard-over-dubai-doha-second-day-witnesses-say-2026-03-01/
    Turkiye Today: https://www.turkiyetoday.com/region/omans-duqm-port-hit-by-drones-breaking-mediation-immunity-3215356
    Gulf News: https://gulfnews.com/world/gulf/oman/drone-attack-targets-omans-duqm-port-one-worker-injured-1.500459511 Abu Isa 🇴🇲 11:17, 1 March 2026 (UTC)[reply]
    Al Jazeera: https://www.aljazeera.com/news/liveblog/2026/2/28/live-israel-launches-attacks-on-iran-multiple-explosions-heard-in-tehran?update=4349885 Abu Isa 🇴🇲 11:19, 1 March 2026 (UTC)[reply]

    change of title from "2026 Israeli–United States strikes on Iran" to "2026 Iran War" as this conflict can be considered as a war since the Ayatollah, a member of the cabinet and a commander of the IRGC was killed by the strikes and not to mention the primary agenda here being to overthrow the clerical islamic regime FallenSnow111 (talk) 11:30, 1 March 2026 (UTC)[reply]

    Not done This would require a discussion you would not be allowed to participate in at this time, and I would not be surprised if the (provisional) page title is already under discussion in some capacity. —Jéské Couriano v^_^v threads critiques 15:32, 1 March 2026 (UTC)[reply]

    Cyprus had missiles that we’re heading towards its direction (source example: https://www.ekathimerini.com/politics/foreign-policy/1296667/missiles-launched-toward-cyprus-intercepted-uk-defense-secretary-says/) before getting intercepted by the UK and Israel. I was thinking maybe we could add Cyprus or Akrotiri and Dhekelia to the “Defense Only” section. If not, that’s totally fine. I’m just making a suggestion. Thanks :) -CypriotDistributist CypriotDistributist (talk) 13:55, 1 March 2026 (UTC)[reply]

    Add United States 3 killed ~2026-13290-64 (talk) 15:06, 1 March 2026 (UTC)[reply]

    Handled requests

    A historical archive of previous protection requests can be found at Wikipedia:Requests for page protection/Archive.