Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a283ff1919afc6f8

Jump to content

Wikipedia:Requests for page protection

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

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.

Reason: Repeated temporary-account edits are adding unsourced elimination results for episodes whose elimination has not yet aired. This occurred last week, when Aaron Potts's elimination was added before the August 6 broadcast revealed it, and temporary accounts are again adding the unresolved Episode 5 result before next week's episode. Requesting temporary semi-protection or pending-changes protection to prevent continued addition of unaired, unverifiable results. Example: https://en.wikipedia.org/w/index.php?title=Project_Runway_season_22&diff=prev&oldid=1368224200 ~2026-43604-12 (talk) 21:33, 7 August 2026 (UTC)reply

Is the concern "unaired and unverifiable" or are these results in fact verifiable (through sources other than the actual episodes,s of course) and the concern spoilers? Because we do not remove information due to the latter. - The Bushranger One ping only 00:57, 8 August 2026 (UTC)reply

Temporary move protection: Page-move vandalism – Repeated undiscussed page moves by multiple editors resulting in a move war. Danners430 tweaks made 07:27, 8 August 2026 (UTC)reply

Move protected for a period of 1 week, after which the page will be automatically unprotected. Callanecc (talkcontribslogs) 03:06, 9 August 2026 (UTC)reply

Temporary semi-protection: Persistent addition of unsourced or poorly sourced content. Danners430 tweaks made 09:46, 8 August 2026 (UTC)reply

Semi-protected for a period of 1 week, after which the page will be automatically unprotected. Callanecc (talkcontribslogs) 03:05, 9 August 2026 (UTC)reply

Temporary semi-protection: Persistent vandalism. User:Namiba 14:52, 8 August 2026 (UTC)reply

DeclinedWarn the user appropriately then report them to AIV or ANI if they continue. Callanecc (talkcontribslogs) 03:03, 9 August 2026 (UTC)reply

Temporary semi-protection: Persistent sockpuppetry – Constant Removal of Monster Inc. and Monsters University from List of Pixar films from Temporary Accounts (User:~2026-43796-32, User:~2026-43432-73 and User:~2026-43366-30). Untamed1910 (talk) 16:07, 8 August 2026 (UTC)reply

Extended confirmed protection: Persistent vandalism. 海盐沙冰 / aka irisChronomia / Talk 17:27, 8 August 2026 (UTC)reply

User(s) blocked: ~2026-43612-92 (talk · contribs) blocked by Mfield. Epicgenius (talk) 01:13, 9 August 2026 (UTC)reply

Reason: High level of disruptive edits: the matter seems to have been raised at WP:ANI but not addressed. Dormskirk (talk) 18:21, 8 August 2026 (UTC)reply

Temporary semi-protection: Persistent vandalism. In solidarity Wikipedian12512 (Talking is fine | contribs) 18:51, 8 August 2026 (UTC)reply

Declined – Not enough recent disruptive activity to justify protection. The last edit was five days ago. I'm also not seeing that the recent edits have been vandalism - if anything, this appears like a sourcing dispute. Epicgenius (talk) 01:12, 9 August 2026 (UTC)reply

Extended confirmed protection: Requesting extended-confirmed protection under WP:RUSUKR. The article already implicates and discusses a Ukrainian munitions plane as well as US intelligence sources pointing to Russia. There have been some anonymous edits on the Leipzig/Halle Airport page, including talk page requests to find evidence of [false flag], and deliberate anon edits after giving warning of WP:RUSUKR topic. Lacanic (talk) 00:31, 9 August 2026 (UTC)reply
More edits (, , ) by anon user after multiple warnings. Lacanic (talk) 01:09, 9 August 2026 (UTC)reply

No one has entered text into this article about "false flag" (and that did not happen in the airport article either).--However, the complaintant is reverting text without any edit comment, including removing "The explosive-laden drone may be part of an attempt at swaying the upcoming German regional elections, according to a media outlet." (Reference, https://www.politico.eu/article/leipzig-drone-incident-fuels-fears-russia-election-meddling/. Politico.eu. Retrieved 2026-08-08).
Edit-protection seems premature. ~2026-42278-84 (talk) 02:23, 9 August 2026 (UTC)reply
Extended confirmed protected indefinitely. and User(s) blocked: ~2026-42278-84 (talk · contribs) blocked. for multiple ECR violations after warning. The Bushranger One ping only 02:29, 9 August 2026 (UTC)reply

Semi-protection: Persistent vandalism – Slow-motion sock warring over the past week. Dylan620 (he/they/she • talkedits) 01:34, 9 August 2026 (UTC)reply

User(s) blocked. Callanecc (talkcontribslogs) 02:56, 9 August 2026 (UTC)reply

Reason: High profile redirect that has been vandalized seven times over the past seven years Duckmather (talk) 02:00, 9 August 2026 (UTC)reply

Declined Once a year is not enough to warrant protection. Callanecc (talkcontribslogs) 02:55, 9 August 2026 (UTC)reply

Indefinite semi-protection: Persistent vandalism. MakaylaHippo1998 (talk) 03:24, 9 August 2026 (UTC)reply

Done by administrators Daniel Quinlan & PhilKnight. Staraction (talk · contribs) 03:32, 9 August 2026 (UTC)reply

Reason: The article concerns an extremist political organization and has experienced edits involving contentious or poorly sourced changes. Semi-protection would help reduce disruption while still allowing established editors to contribute. Oswald Quinsley (talk) 04:03, 9 August 2026 (UTC)reply

Current requests for reduction in protection level

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

Reason: Page has been protected for over 15 years with barely any vandalism, and most if not all of the edit requests by TA's and IP's are constructive, so there is no real reason for the page to be semi-protected anymore. MathMan4 (talk) 03:35, 8 August 2026 (UTC)reply

(Non-administrator comment) This is a high-traffic page (over 5,000 daily page views in the past month) with a long history of vandalism prior to the protection, so if WP:TRYUNPROT is attempted at all, indef PCP seems the safest move. Entranced98 (talk) 08:23, 8 August 2026 (UTC)reply
(Non-administrator comment) barely any vandalism isn't a valid reason for unprotection per the notice above. Recommend pending changes instead full unprotection per Entranced98. Justjourney (talk | contribs) 16:10, 8 August 2026 (UTC)reply

Current requests for edits to a protected page

Request a specific edit be made to a protected page


I request the following sentence be removed from the lead's 2nd paragraph:

"and subsequently annexing the Strait of Hormuz"

This sentence was recently added but is completely unsourced, not in the body, and POV pushing. Although Iran has claimed sovereignty over the strait, there are no sources claiming that it has actually successfully annexed it during the ongoing war or even attempted officially to do so. The linked page on sovereignty in the text which is a new page created by the same user also doesn't even support this wording of annexation. Current talks between Iran and Oman are about shared administration as well, not annexation. ~2026-43592-81 (talk) 07:20, 7 August 2026 (UTC)reply

Replace X "misogynistic and/or racist commentary" with Y "misogynistic and racist commentary." so that the page complies with MOS:ANDOR guidelines. This edit should be uncontroversial, the text is not a quote, there does not appear to be any important "not both" edge case that the author was trying to address, it seems to be only a lack of awareness of guidlines such as MOS:ANDOR as well as MOS:SLASH. -- ~2026-37849-52 (talk) 23:47, 8 August 2026 (UTC)reply

Handled requests

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