Jump to content

Wikipedia:Requests for page protection

Page semi-protected
From Wikipedia, the free encyclopedia
(Redirected from Wikipedia:PAGEPROTECT)
    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 get rid of obvious vandalism.

    Request protection of a page, or increasing the protection level

    Request unprotection of a page, or reducing the protection level

    Request a specific edit to a protected page
    Please request an edit directly on the protected page's talk page before posting here



    Current requests for increase in protection level

    Request protection of a page, or increasing the 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, failing that, the page history. Only recently answered requests are still listed here.


    Temporary semi-protection: Persistent vandalism – persistent WP:CUTPASTE moves. Happily888 (talk) 03:59, 30 June 2025 (UTC)[reply]

    Semi-protected I and a few other admins went through several of these and protected for varying lengths between a week and a month. I'm going to copy-paste this comment into each of the requests here to trigger the bot. @Happily888: I would suggest for this level of disruption that a report to WP:ANI would be easier for admins to handle. Thanks for your reports. Ivanvector (Talk/Edits) 22:48, 30 June 2025 (UTC)[reply]

    Temporary semi-protection: Persistent vandalism – Ip editors kept on adding unsourced content. Cassiopeia talk 05:24, 30 June 2025 (UTC)[reply]

    Already protected by administrator Star Mississippi. Daniel (talk) 02:23, 1 July 2025 (UTC)[reply]

    Temporary pending changes: Persistent edit-warring from IPs. GalStar (talk) (contribs) 07:11, 30 June 2025 (UTC)[reply]

    Indefinite semi-protection: Persistent addition of unsourced or poorly sourced content – Constant addition of unsourced information from various IPs for many years now. DaniloDaysOfOurLives (talk) 09:25, 30 June 2025 (UTC)[reply]

    Already protected by administrator Star Mississippi. Daniel (talk) 02:29, 1 July 2025 (UTC)[reply]

    Temporary pending changes: Persistent disruptive editing – Fairly frequent vandalism, spamming and other nonconstructive edits, seems to be a recurring problem according to the protection log. Entranced98 (talk) 09:39, 30 June 2025 (UTC)[reply]

    Extended confirmed protection: It's a core policy; getting autoconfirmed is so easy. I recommend using ECP or full. Starfall2015 let's talk profile 10:21, 30 June 2025 (UTC)[reply]

    (Non-administrator comment) Pages are not protected preemptively. I don't see any recent vandalism on the page at first glance. I see a lot of good faith editing getting reverted (not vandalism). @Starfall2015: do you have any examples of recent vandalism on this page (or any other disruptive editing examples)? Justjourney (talk | contribs) 15:48, 30 June 2025 (UTC)[reply]
    Declined – No changes to the current protection level are required at this point in time. — rsjaffe 🗣️ 22:54, 30 June 2025 (UTC)[reply]

    Indefinite semi-protection: Persistent disruptive editing – IPs keep adding unnecessary flags against MOS. Vestrian24Bio 12:27, 30 June 2025 (UTC)[reply]

    Already protected by administrator Star Mississippi. Daniel (talk) 02:30, 1 July 2025 (UTC)[reply]

    Indefinite semi-protection: Persistent disruptive editing – IPs have returned after previous protection expired; adding unnecessary flags against MOS and unnecessary tables bloating the page. Indefinite protection required. Vestrian24Bio 12:31, 30 June 2025 (UTC)[reply]

    Already protected by administrator Star Mississippi. Daniel (talk) 02:30, 1 July 2025 (UTC)[reply]

    Reason: Persistent disruptive editing via IP-spam. Fragrant Peony (talk) 12:50, 30 June 2025 (UTC)[reply]

    Reason: high level of IP vandalism regarding the reported transfer Chelsdog (talk) 14:44, 30 June 2025 (UTC)[reply]

    Already protected by administrator Ymblanter. Daniel (talk) 02:30, 1 July 2025 (UTC)[reply]

    Indefinite pending changes protection: Persistent vandalism. Temporary protection in 2023 didn't seem to do much, vandalism has returned in 2025. RaschenTechner (talk) 15:46, 30 June 2025 (UTC)[reply]

    (Non-administrator comment) The irony is not lost on this one. Fallbackintoreality (tc) 16:30, 30 June 2025 (UTC)[reply]
    Declined – Not enough recent disruptive activity to justify protection. Daniel (talk) 02:31, 1 July 2025 (UTC)[reply]

    Temporary semi-protection: Persistent vandalism – Persistently vandalized recently with different IPs. Kind of the same story as #iOS 26 above. Justjourney (talk | contribs) 15:54, 30 June 2025 (UTC)[reply]

    Temporary semi-protection: Persistent vandalism – Same reasons given above for #iOS 26 and #iOS 7. Justjourney (talk | contribs) 15:56, 30 June 2025 (UTC)[reply]

    Temporary semi-protection: Persistent disruptive editing – Edit-warring by Brazil IPs. Binksternet (talk) 16:32, 30 June 2025 (UTC)[reply]

    Temporary semi-protection: This may have crossed the same threshold as Talk:ChatGPT and Talk:Google, where enough inattentive or non-English-speaking users fail to register the massive This is not the place to ask Midjourney a question editnotice and try to ask Midjourney to draw them a picture. Since the start of the year there have been 28 reverted picture requests, and only one genuine comment in that time. Belbury (talk) 17:47, 30 June 2025 (UTC)[reply]

    Temporary semi-protection: Persistent vandalism – new Squid Game releases, new vandalism. Paper9oll (🔔📝) 18:41, 30 June 2025 (UTC)[reply]

    Reason: Constant vandalism 120.147.132.237 (talk) 18:41, 30 June 2025 (UTC)[reply]

    Reason: Vandalism 120.147.132.237 (talk) 18:44, 30 June 2025 (UTC)[reply]

    Reason: Vandalism and information 120.147.132.237 (talk) 18:45, 30 June 2025 (UTC)[reply]

    Temporary semi-protection: BLP policy violations. Binksternet (talk) 18:56, 30 June 2025 (UTC)[reply]

    Reason: Persistent and constant vandalism. Slatersteven (talk) 19:04, 30 June 2025 (UTC)[reply]

    Please semi-protect the article Ismet Asllani due to repeated disruptive and misleading edits by anonymous users. This is a serious biographical article, and I am the main contributor. I request that only autoconfirmed users be allowed to edit it. Thank you.

    Makolli86 (talk) 19:57, 30 June 2025 (UTC)[reply]

    Declined – Not enough recent disruptive activity to justify protection. — rsjaffe 🗣️ 22:48, 30 June 2025 (UTC)[reply]

    Indefinite semi-protection: Persistent sockpuppetry. soetermans. ↑↑↓↓←→←→ B A TALK 20:25, 30 June 2025 (UTC)[reply]

    Already protected by administrator Star Mississippi. Daniel (talk) 02:22, 1 July 2025 (UTC)[reply]

    Indefinite semi-protection: Persistent sockpuppetry. soetermans. ↑↑↓↓←→←→ B A TALK 20:25, 30 June 2025 (UTC)[reply]

    Already protected by administrator Star Mississippi. Daniel (talk) 02:22, 1 July 2025 (UTC)[reply]

    Indefinite semi-protection: Persistent sockpuppetry. soetermans. ↑↑↓↓←→←→ B A TALK 20:26, 30 June 2025 (UTC)[reply]

    Semi-protected for a period of 6 months, after which the page will be automatically unprotected. Daniel (talk) 02:19, 1 July 2025 (UTC)[reply]

    Temporary extended confirmed protection: BLP policy violations – Persistent BLP vio's. many accounts keep removing sourced content. - FlightTime Phone (open channel) 22:02, 30 June 2025 (UTC)[reply]

    @FlightTime Phone: how is it a BLP violation to remove content in this situation? I'm not saying it should be removed (or not), but struggling to understand the logic of calling this a BLP violation. Daniel (talk) 02:18, 1 July 2025 (UTC)[reply]

    Temporary semi-protection: Persistent vandalism. Shadow4dark (talk) 22:11, 30 June 2025 (UTC)[reply]

    Already protected. Daniel (talk) 02:17, 1 July 2025 (UTC)[reply]

    Temporary semi-protection: Frequent removal of sourced information regarding personal life and addition of unsourced info in its place, by anonymous IP editor. NJZombie (talk) 22:37, 30 June 2025 (UTC)[reply]

    Already protected. Daniel (talk) 02:17, 1 July 2025 (UTC)[reply]

    Temporary semi-protection: Persistent vandalism – Recent signing. Sushidude21! (talk) 23:29, 30 June 2025 (UTC)[reply]

    Declined – Not enough recent disruptive activity to justify protection. Daniel (talk) 02:16, 1 July 2025 (UTC)[reply]

    Temporary semi-protection: Persistent vandalism – Recent signing. Sushidude21! (talk) 23:29, 30 June 2025 (UTC)[reply]

    Declined – Not enough recent disruptive activity to justify protection. Daniel (talk) 02:16, 1 July 2025 (UTC)[reply]

    Temporary semi-protection: Persistent vandalism – Recent signing. Sushidude21! (talk) 23:30, 30 June 2025 (UTC)[reply]

    Semi-protected for a period of 1 week, after which the page will be automatically unprotected. Daniel (talk) 02:15, 1 July 2025 (UTC)[reply]

    Temporary semi-protection: Persistent vandalism – Recent signing. Sushidude21! (talk) 23:30, 30 June 2025 (UTC)[reply]

    Semi-protected for a period of 1 week, after which the page will be automatically unprotected. Daniel (talk) 02:13, 1 July 2025 (UTC)[reply]

    Temporary semi-protection: Persistent vandalism – Recent signing. Sushidude21! (talk) 23:30, 30 June 2025 (UTC)[reply]

    Semi-protected for a period of 1 week, after which the page will be automatically unprotected. Daniel (talk) 02:13, 1 July 2025 (UTC)[reply]

    Temporary semi-protection: Persistent vandalism – Recent signing. Sushidude21! (talk) 23:30, 30 June 2025 (UTC)[reply]

    Declined – Not enough recent disruptive activity to justify protection. Daniel (talk) 02:12, 1 July 2025 (UTC)[reply]

    Temporary semi-protection: Persistent vandalism – Recent trade. Sushidude21! (talk) 23:30, 30 June 2025 (UTC)[reply]

    Semi-protected for a period of 1 week, after which the page will be automatically unprotected. Daniel (talk) 02:12, 1 July 2025 (UTC)[reply]

    Temporary semi-protection: Persistent vandalism – Recent trade. Sushidude21! (talk) 23:30, 30 June 2025 (UTC)[reply]

    Declined – Not enough recent disruptive activity to justify protection. Daniel (talk) 02:11, 1 July 2025 (UTC)[reply]

    Temporary semi-protection: Persistent vandalism – Recent signing. Sushidude21! (talk) 23:31, 30 June 2025 (UTC)[reply]

    Declined – Not enough recent disruptive activity to justify protection. Daniel (talk) 02:10, 1 July 2025 (UTC)[reply]

    Temporary semi-protection: Persistent vandalism – Recent signing. Sushidude21! (talk) 23:33, 30 June 2025 (UTC)[reply]

    Declined – Not enough recent disruptive activity to justify protection. Daniel (talk) 02:10, 1 July 2025 (UTC)[reply]

    Temporary semi-protection: Persistent vandalism – Recent signing. Sushidude21! (talk) 23:33, 30 June 2025 (UTC)[reply]

    Declined – Not enough recent disruptive activity to justify protection. Daniel (talk) 02:09, 1 July 2025 (UTC)[reply]

    Temporary semi-protection: Persistent vandalism – Recent signing. Sushidude21! (talk) 23:35, 30 June 2025 (UTC)[reply]

    Declined – Not enough recent disruptive activity to justify protection. Daniel (talk) 02:09, 1 July 2025 (UTC)[reply]

    Temporary semi-protection: Persistent vandalism – Recent signing. Sushidude21! (talk) 23:36, 30 June 2025 (UTC)[reply]

    Declined – Not enough recent disruptive activity to justify protection. Daniel (talk) 02:09, 1 July 2025 (UTC)[reply]

    Temporary semi-protection: Persistent vandalism – Recent signing. Sushidude21! (talk) 23:51, 30 June 2025 (UTC)[reply]

    Semi-protected for a period of 1 week, after which the page will be automatically unprotected. Daniel (talk) 02:08, 1 July 2025 (UTC)[reply]

    Temporary semi-protection: Persistent vandalism – Recent signing. Sushidude21! (talk) 00:10, 1 July 2025 (UTC)[reply]

    Declined – Not enough recent disruptive activity to justify protection. Daniel (talk) 02:08, 1 July 2025 (UTC)[reply]

    Semi-protection: Persistent disruptive editing. Remsense 🌈  00:23, 1 July 2025 (UTC)[reply]

    Declined – Not enough recent disruptive activity to justify protection. Daniel (talk) 02:07, 1 July 2025 (UTC)[reply]

    Temporary semi-protection: Persistent addition of unsourced or poorly sourced content – Recent signing. Sushidude21! (talk) 01:23, 1 July 2025 (UTC)[reply]

    Semi-protected for a period of three days, after which the page will be automatically unprotected. — rsjaffe 🗣️ 02:07, 1 July 2025 (UTC)[reply]

    Semi-protection: Persistent disruptive editing. Remsense 🌈  02:32, 1 July 2025 (UTC)[reply]

    Current requests for reduction in protection level

    Request unprotection of a page, or reducing the protection level

    Before posting, first discuss with the protecting admin on their talk page. Post below only if you receive no reply.

    • To find out the username of the admin who protected the page, click on "history" at the top of the page, then click on "View logs for this page," which is under the title of the page. The protecting admin is the username in blue before the words "protected", "changed protection level" or "pending changes". If there are a number of entries on the log page, you might find it easier to select "Protection log" or "Pending changes log" from the dropdown menu in the blue box.
    • Requests to downgrade full protection to template protection on templates and modules can be directed straight here; you do not need to ask the protecting admin first.
    • Requests for removing create protection on redlinked articles are generally assisted by having a draft version of the intended article prepared beforehand.
    • If you want to make spelling corrections or add uncontroversial information to a protected page, please add {{Edit fully-protected}} to the article's talk page, along with an explanation of what you want to add to the page. If the talk page is protected, please use the section below.

    Check the archives if you cannot find your request. Only recently answered requests are still listed here.

    Reason: This page has been protected for over four years, and no disruption has occurred since 2018. Test to see if protection is still necessary. 2600:1700:C910:2960:A0A6:E1B2:A891:8B7C (talk) 19:28, 28 June 2025 (UTC)[reply]

    Pinging @Wugapodes: Daniel Case (talk) 20:51, 29 June 2025 (UTC)[reply]
    @Daniel Case: Hard no on unprotecting. IP geolocates to the same city as the LTA I mention in the log, making a request here fits the MO of using RFUNPROT, and the IP's /64 shows a lot of edits very clearly in the LTA's topic area. Honestly, the edits look fine, with the reverts looking like good-faith disputes over short descriptions, but banned means banned. On the off-chance this user is unrelated to the LTA, I still think there's enough here to say we keep the protection (and maybe update the log). Wug·a·po·des 00:07, 1 July 2025 (UTC)[reply]

    Reason: This page has been protected for over four years, and no disruption has occurred since 2009. Test to see if protection is still necessary. 2600:1700:C910:2960:A0A6:E1B2:A891:8B7C (talk) 19:29, 28 June 2025 (UTC)[reply]

    Pinging @Wugapodes Daniel Case (talk) 20:52, 29 June 2025 (UTC)[reply]
    I vote no, see my reply to the IP's other request. Wug·a·po·des 00:09, 1 July 2025 (UTC)[reply]

    Reason: This page has been protected for over four years, and no disruption has occurred since 2009. Test to see if protection is still necessary. 2600:1700:C910:2960:A0A6:E1B2:A891:8B7C (talk) 19:29, 28 June 2025 (UTC)[reply]

    Pinging @Wugapodes Daniel Case (talk) 02:02, 30 June 2025 (UTC)[reply]
    I vote no, see my reply to the IP's other request. Wug·a·po·des 00:09, 1 July 2025 (UTC)[reply]

    Unprotection: It's a sensible redirect for Mujeeb Ur Rahman (some sources omit the Ur from his name), so asking that this is unprotected so this redirect can be created, as a "R from alternative name". The protecting admin from 2014 is no longer an admin, and the target redirect is different to whatever spam caused the create protection in 2013/14. Joseph2302 (talk) 13:55, 30 June 2025 (UTC)[reply]

    Unprotection: @JSFarman: says they can't accept the page's draft without it being unsalted first. They previously appealed for such, but removed it after it was declined. Roast (talk) 20:00, 30 June 2025 (UTC)[reply]

    Unprotection: The protection is no longer necessary because this page has been protected for 5 years, and no disruption has occurred since 2020. 72.225.177.190 (talk) 23:38, 30 June 2025 (UTC)[reply]

    Current requests for edits to a protected page

    Request a specific edit to a protected page
    Please request an edit directly on the protected page's talk page before posting here

    Ideally, requests should be made on the article talk page rather than here.

    • Unless the talk page itself is protected, you may instead add the appropriate template among {{Edit protected}}, {{Edit template-protected}}, {{Edit extended-protected}}, or {{Edit semi-protected}} to the article's talk page if you would like to make a change rather than requesting it here. Doing so will automatically place the page in the appropriate category for the request to be reviewed.
    • Where requests are made due to the editor having a conflict of interest (COI; see Wikipedia:Suggestions for COI compliance), the {{Edit COI}} template should be used.
    • Requests to move move-protected pages should be made at Wikipedia:Requested moves, not here.
    • If the discussion page and the article are both protected preventing you from making an edit request, this page is the right place to make that request. Please see the top of this page for instructions on how to post requests.
    • This page is not for continuing or starting discussions regarding content should both an article and its discussion page be protected. Please make a request only if you have a specific edit you wish to make.


    Please correct the Iranian civilian casualties in paragraph three. First it was changed without reason from 200 to 600. Then someone changed and seperated the estimate by Human Rights Activists in Iran News Agency (HRANA) estimate to be over 1,100 civilians killed which is conflating all deaths with civilians. No source was added to support this. The sources currently listed next to these sentences actually say 200 but these are out off date. HRANA's latest figure is actually 431 civilians killed. The source is presently used in the infobox for their own estimate of 1,190 total deaths. The Iranian government hasn't released updated figures so that should be removed until they have an estimate. I suggest adding the following sentence:

    "According to the anti-government Human Rights Activists in Iran News Agency, 1,190 Iranians were killed including at least 431 civilians."

    102.17.120.130 (talk) 11:06, 30 June 2025 (UTC)[reply]

    Handled requests

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