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 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.


    Reason: (Extended confirmed protection) Recent vandalism, he is related to Wars in Gaza and Ukraine. The Seal F1 (talk) 13:50, 27 March 2025 (UTC)[reply]

    Reason: Edit warring and possible sock-puppetry. Bored kittycat (talk) 13:56, 27 March 2025 (UTC)[reply]

    Already protected by administrator Yamaguchi先生. Daniel Quinlan (talk) 22:10, 27 March 2025 (UTC)[reply]

    Reason: This is the second time I am requesting for this article to protected. My reason this time is still the same disruptive editing. Please, I want this article to be fully protected from this Vandalism. If this article remains not protected many harms will be done to it. Thank you. 2RDD (talk) 15:00, 27 March 2025 (UTC)[reply]

    Declined – Not enough recent disruptive activity to justify protection. Daniel Quinlan (talk) 22:11, 27 March 2025 (UTC)[reply]

    Semi-protection: Persistent disruptive editing. Skitash (talk) 15:30, 27 March 2025 (UTC)[reply]

    Declined – Content dispute. Please use the article's talk page or other forms of dispute resolution. Daniel Quinlan (talk) 22:12, 27 March 2025 (UTC)[reply]

    Indefinite semi-protection: Persistent vandalism – Returned after five years of protection. Entranced98 (talk) 15:32, 27 March 2025 (UTC)[reply]

    Semi-protected indefinitely. Daniel Quinlan (talk) 22:16, 27 March 2025 (UTC)[reply]

    Semi-protection: Persistent vandalism. Filmssssssssssss (talk) 18:31, 27 March 2025 (UTC)[reply]

    Pending-changes protected for a period of 1 year, after which the page will be automatically unprotected. Daniel Quinlan (talk) 22:18, 27 March 2025 (UTC)[reply]

    Temporary protection: LTA vandalism Yoshi24517 (Chat) (Very Busy) 19:02, 27 March 2025 (UTC)[reply]

    Already protected by administrator Lofty abyss. @Lofty abyss: Indefinite seems a bit long for an article averaging about 11 edits per year for the last 5 years. Perhaps we could protect it for several years instead? Daniel Quinlan (talk) 22:29, 27 March 2025 (UTC)[reply]

    Reason: IP BLP Vandalism. Suggest at least a two-week silver lock pbp 19:17, 27 March 2025 (UTC)[reply]

    Already protected by administrator Cullen328. Protected for 1 week. Daniel Quinlan (talk) 22:30, 27 March 2025 (UTC)[reply]

    Temporary full protection: Inappropriate use of user talk page while blocked – Hacked account being used as a sockpuppet spamming the talk page with defamation and WP:BLP violations. Please can someone temp full lock it while they're sockpuppet investigation is taking place?. SummersRising (talk) 19:20, 27 March 2025 (UTC)[reply]

    @SummersRising has only edited the Baron Teynham and Pylewell Park pages in its lifetime, and has stated on their user talk page that they have visited the residence as a teenager, suggesting a close connection or that they are the subject: https://en.wikipedia.org/wiki/User_talk:SummersRising
    Despiste many attempts, they have not provided reliable sources confirming that Pylewell Park is the family seat. Pylewell Park is in Hampshire not Teynham, used commercially for weddings, and was only inherited in 1988 per its website: https://www.pylewellpark.com/about/our-story/ The Baron Teynham is from 1616, and the current Baron does not live there, so it cannot be considered the family seat.
    The user has also deleted information, relevant to public interest. The current Baron Teynham and son has been accused of domestic violance and financial abuse, which dozens of sources supporting the claims. The user @SummersRising has not provided evidence to state the contrary. Instead of engaging with the content concerns, @SummersRising has continued to revert, attack, and accuse anyone who speaks up of sockpuppetry.
    The issue has been escalated to the Conflict of Interest Noticeboard for review:
    https://en.wikipedia.org/wiki/Wikipedia:Conflict_of_interest/Noticeboard#User:SummersRising_–_Possible_COI_and_Promotional_Editing_(Baron_Teynham_/_Pylewell_Park)
    I ask that the user @SummersRisingis stopped from reverting and making changes until sources are provided. Aksnahar (talk) 20:15, 27 March 2025 (UTC)[reply]
    Just an FYI anyone sweeping by, @Aksnahar was warned by an admin and their report rejected: https://en.wikipedia.org/w/index.php?title=User_talk:Aksnahar&oldid=1282662396
    SockPuppet investigation is still pending: https://en.wikipedia.org/wiki/Wikipedia:Sockpuppet_investigations/Preloenber SummersRising (talk) 21:38, 27 March 2025 (UTC)[reply]
    Extended confirmed protected for a period of 1 year, after which the page will be automatically unprotected. ~ ToBeFree (talk) 22:20, 27 March 2025 (UTC)[reply]

    Reason: High level of IP vandalism. Adding unsourced content claiming that a third female was born, this vandalizing has been done since at least September 2024. Fin 19:34, 27 March 2025 (UTC)[reply]

    Semi-protected for a period of 6 months, after which the page will be automatically unprotected. Daniel Quinlan (talk) 22:32, 27 March 2025 (UTC)[reply]

    Indefinite extended confirmed protection: Arbitration enforcement – Relevant to WP:ARBPIA, thanks in advance. Smallangryplanet (talk) 19:35, 27 March 2025 (UTC)[reply]

    Reason: Persistent LTA disruptive editing. Johnj1995 (talk) 20:02, 27 March 2025 (UTC)[reply]

    Temporary semi-protection: Persistent sockpuppetry – This AFD is being flooded by IP addresses. See report at WP:ANI. Robert McClenon (talk) 20:18, 27 March 2025 (UTC)[reply]

    Semi-protected for a period of 3 days, after which the page will be automatically unprotected. The Bushranger One ping only 21:22, 27 March 2025 (UTC)[reply]

    Reason: Persistent, long-term vandalism from many IPs. Dream is protected so I don't see why this shouldn't be. Wildfireupdateman :) (talk) 20:47, 27 March 2025 (UTC)[reply]

    Reason: persistent disruptive editing through sockpuppetry by cbanned user on various ip ranges. Nyamo Kurosawa (talk) 21:01, 27 March 2025 (UTC)[reply]

    Semi-protected for a period of three months, after which the page will be automatically unprotected. — rsjaffe 🗣️ 21:41, 27 March 2025 (UTC)[reply]

    Temporary semi-protection: Persistent disruptive editing – Repeated addition of poorly-sourced chatbot-generated material by new accounts. --Finngall talk 21:22, 27 March 2025 (UTC)[reply]

    Reason: High level of IP vandalism. RedPatch (talk) 21:30, 27 March 2025 (UTC)[reply]

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

    Temporary semi-protection: Persistent vandalism – Can we PLEASE put this article under semi-protection? An apparent LTA is repeatedly adding unsourced content and POV statements against editorial consensus & against WP guidelines/policies. Shearonink (talk) 22:02, 27 March 2025 (UTC)[reply]

    Semi-protected for a period of 1 month, after which the page will be automatically unprotected. Ymblanter (talk) 22:11, 27 March 2025 (UTC)[reply]

    Temporary semi-protection: I request a Temporary semi-protection on this page due to repeated test edits by IP users. Pri2000 (talk) 22:31, 27 March 2025 (UTC)[reply]

    Semi-protection: Persistent vandalism – Same dumb meme edits every time protection lapses. Nswix (talk) 22:34, 27 March 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.

    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.


    In paragraph titled "Eastern India" change "In Gangetic belt mainly in Uttar Pradesh and Bihar, Saraswat Brahmins were landlords and priests. They follow Shakta tradition, Vaishnavism and Shaivism." TO "In Gangetic belt mainly in Uttar Pradesh and Bihar, Saraswat Brahmins were landlords and priests. They follow Shakta tradition, Vaishnavism and Shaivism. Vaidya community of Bengal, a unique close-knit and aristocratic community, is a branch of this Saraswat Brahmin community with predominatly Shukla-Yajurvedi Kanva-shakha heritage .(It should be noted that Vaidya surname and some exclusive gotras like Dhanvantari are only found among Saraswats of other places, also many Saraswats claim descent from a Rajarshi Raja Rattan Sen) They were traditional teachers and practitioners of Ayurveda and it had become a family-tradition. The first flow of Vaidyas into Bengal came from South-western India via Orissa in early 11th century. They were called “Ambastha-Brahmin” because Ambastha was a place in Punjab where many Saraswat Brahmins including vaidyas resided . They named themselves after the name of their ancestral place. Ashwapati Sen, Adishur, Samanta Sen, the kings of the Sena dynasties were all Vaidyas coming from southern India. Later , king Adishur invited four more Vaidya pandits(of Dhanvantari, Shaktri, Moudgalya and Kashyapa gotra) from Kannauj (UP)." Raygs2810 (talk) 17:27, 27 March 2025 (UTC)[reply]

    Not done – Please use an edit request to request specific changes to be made to the protected page. Talk:Baidya is not protected. Favonian (talk) 17:46, 27 March 2025 (UTC)[reply]

    Misleading and lacking infomation on the content of Mr. Cave's comments.

    Lots of guilt by association, and not included that Murro has been rehabilitated 31.205.73.15 (talk) 19:58, 27 March 2025 (UTC)[reply]

    Not done – Please use an edit request to request specific changes to be made to the protected page. Talk:Homeland Party (United Kingdom) is not protected. Favonian (talk) 21:36, 27 March 2025 (UTC)[reply]

    Handled requests

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