Enforcement policies Administrators Banning policy Blocking policy Protection policy .mw-parser-output .navbar{display:inline;font-size:88%;font-weight:normal}.mw-parser-output .navbar-collapse{float:left;text-align:left}.mw-parser-output .navbar-boxtext{word-spacing:0}.mw-parser-output .navbar ul{display:inline-block;white-space:nowrap;line-height:inherit}.mw-parser-output .navbar-brackets::before{margin-right:-0.125em;content:"[ "}.mw-parser-output .navbar-brackets::after{margin-left:-0.125em;content:" ]"}.mw-parser-output .navbar li{word-spacing:-0.125em}.mw-parser-output .navbar a>span,.mw-parser-output .navbar a>abbr{text-decoration:inherit}.mw-parser-output .navbar-mini abbr{font-variant:small-caps;border-bottom:none;text-decoration:none;cursor:inherit}.mw-parser-output .navbar-ct-full{font-size:114%;margin:0 7em}.mw-parser-output .navbar-ct-mini{font-size:114%;margin:0 4em}vte
Gold padlock
Fully-protected

Goldlock

Brown padlock
Interface protected

Redlock

Pink padlock
Template-protected

Pinklock

Silver padlock
Semi-protected

Silverlock

Blue padlock
Create protected

Skybluelock

Green padlock
Move protected

Greenlock

Purple padlock
Upload protected

Purplelock

White padlock
Pending changes protected

Whitelock

Dark blue padlock
Extended confirmed protected

Bluelock

Black padlock
Protected by Office

Blacklock

Turquoise padlock
Cascade protected

Turquoiselock

In some circumstances, pages may need to be protected from modification by certain groups of editors. Pages are protected when a specific damaging event has been identified that can not be prevented through other means such as a block. Otherwise, Wikipedia is built on the principle that anyone can edit it, and it therefore aims to have as many of its pages as possible open for public editing so that anyone can add material and correct errors. This policy states in detail the protection types and procedures for page protection and unprotection and when each protection should and should not be applied.

Protection is a technical restriction applied only by administrators, although any user may request protection. Protection can be indefinite or expire after a specified time. The various levels of protection are detailed below, and they can be applied to the page edit, page move, page create, and file upload actions. Even when a page is protected from editing, the source code (wikitext) of the page can still be viewed and copied by anyone.

A protected page is marked at its top right by a padlock icon, usually added by the ((pp-protected)) template.

Pre-emptive protection

Applying page protection as a preemptive measure is contrary to the open nature of Wikipedia and is generally not allowed if applied solely for these reasons. However, brief periods of an appropriate and reasonable protection level are allowed in situations where blatant vandalism, disruption, or abuse is occurring by multiple users and at a level of frequency that requires its use in order to stop it. The duration of the protection should be set as short as possible, and the protection level should be set to the lowest restriction needed in order to stop the disruption while still allowing productive editors to make changes.

Types of protection

The following technical options are available to administrators for protecting different actions to pages:

The following technical options are available to administrators for adding protection levels to the different actions to pages:

Any type of protection (with the exception of cascading protection) may be requested at Wikipedia:Requests for page protection. Changes to a fully protected page should be proposed on the corresponding talk page, then carried out by an administrator if they are uncontroversial or there is consensus for them.

Except in the case of office actions (see below), Arbitration Committee remedies, or pages in the MediaWiki namespace (see below), administrators may unprotect a page if the reason for its protection no longer applies, a reasonable period has elapsed, and there is no consensus that continued protection is necessary. Editors desiring the unprotection of a page should, in the first instance, ask the administrator who applied the protection unless the administrator is inactive or no longer an administrator; thereafter, requests may be made at Requests for unprotection. Note that such requests will normally be declined if the protecting administrator is active and was not consulted first. A log of protections and unprotections is available at Special:Log/protect.

Interaction of Wikipedia user groups and page protection levels
  Unregistered or Newly registered Confirmed or Auto-confirmed Extended confirmed Template editor Admin Interface admin Appropriate for
No protection normal editing The vast majority of pages. This is the default protection level.
Pending-protection-shackle.svg
Pending changes
all users can edit.
Edits by unregistered or new editors (and any subsequent edits by anyone) are hidden from readers who are not logged in, until reviewed by a pending changes reviewer or admin. Logged-in editors see all edits, whether accepted or not.
Infrequently edited pages with high levels of vandalism, BLP violations, edit-warring, or other disruption from unregistered and new users.
Semi-protection-shackle.svg
Semi
cannot edit normal editing Pages that have been persistently vandalized by anonymous and registered users. Some highly visible templates and modules.
Extended-protection-shackle.svg
Ext. confirmed
cannot edit normal editing* Specific topic areas authorized by ArbCom, pages where semi-protection has failed, or high-risk templates where template protection would be too restrictive.
Template-protection-shackle.svg
Template
cannot edit normal editing High-risk or very-frequently used templates and modules. Some high-risk pages outside of template space.
Full-protection-shackle.svg
Full
cannot edit normal editing Articles under an edit war and content dispute, or with persistent disruption from extended confirmed accounts. Critical templates and modules.
Interface-protection-shackle.svg
Interface
cannot edit normal editing Scripts, stylesheets, and similar objects central to operation of the site or that are in another editor's user space.
* In order to edit through extended confirmed protection, a template editor must also be extended confirmed, but in practice this is essentially always the case.

Other modes of protection:

Full protection

Gold padlock

A fully protected page cannot be edited or moved by anyone except administrators. The protection may be for a specified time or may be indefinite.

Modifications to a fully protected page can be proposed on its talk page (or at another appropriate forum) for discussion. Administrators can make changes to the protected article reflecting consensus. Placing the ((Edit fully-protected)) template on the talk page will draw the attention of administrators for implementing uncontroversial changes.

Content disputes

See also: Wikipedia:Stable version

"WP:PREFER" redirects here. For what title name should be preferred, see Wikipedia:Disambiguation § Primary topic.

While content disputes and edit warring may be addressed with user blocks issued by uninvolved administrators, allowing normal page editing by other editors at the same time, the protection policy provides an alternative approach as administrators have the discretion to temporarily fully protect an article to end an ongoing edit war. This approach may better suit multi-party disputes and contentious content, as it makes talk page consensus a requirement for implementation of requested edits.

When protecting a page because of a content dispute, administrators have a duty to avoid protecting a version that contains policy-violating content, such as vandalism, copyright violations, defamation, or poor-quality coverage of living people. Administrators are deemed to remain uninvolved when exercising discretion on whether to apply protection to the current version of an article, or to an older, stable, or pre-edit-war version.

Protected pages may not be edited except to make changes that are uncontroversial or for which there is clear consensus. Editors convinced that the protected version of an article contains policy-violating content, or that protection has rewarded edit warring or disruption by establishing a contentious revision, may identify a stable version prior to the edit war and request reversion to that version. Before making such a request, editors should consider how independent editors might view the suggestion and recognize that continuing an edit war is grounds for being blocked.

Administrators who have made substantive content changes to an article are considered involved and must not use their advanced permissions to further their own positions. When involved in a dispute, it is almost always wisest to respect the editing policies that bind all editors and call for input from an uninvolved administrator, rather than to invite controversy by acting unilaterally.

"History only" review

If a deleted page is going through deletion review, only administrators are normally capable of viewing the former content of the page. If they feel it would benefit the discussion to allow other users to view the page content, administrators may restore the page, blank it or replace the contents with ((Temporarily undeleted)) template or a similar notice, and fully protect the page to prevent further editing. The previous contents of the page are then accessible to everyone via the page history.

Protected generic file names

Generic file names such as File:Photo.jpg, File:Map.jpg, and File:Sound.wav are fully protected to prevent new versions being uploaded. Furthermore, File:Map.jpg and File:Sound.wav are salted.

Permanent protection

Brown padlock

Administrators cannot change or remove the protection for some areas on Wikipedia, which are permanently protected by the MediaWiki software:

Such protection is called Permanent, Interface, or Indefinite protection; and pages so protected can only be edited by those with Interface Administrator rights.

In addition to hard-coded protection, the following are usually fully protected for an indefinite period of time (though not necessarily with Interface protection):

Template protection

Main page: Wikipedia:Template editor

Pink padlock

A template-protected page can be edited only by administrators or users in the Template editors group. This protection level should be used almost exclusively on high-risk templates and modules. In cases where pages in other namespaces become transcluded to a very high degree, this protection level is also valid.

This is a protection level[1] that replaces full protection on pages that are merely protected due to high transclusion rates, rather than content disputes. It should be used on templates whose risk factor would have otherwise warranted full protection. It should not be used on less risky templates on the grounds that the template editor user right exists—the existence of the right should not result in more templates becoming uneditable for the general editing community. In borderline cases, extended confirmed protection or lower may be applied to high risk templates that the general editing community still needs to edit regularly.

Editors may request edits to a template-protected page by proposing them on its talk page, using the ((Edit template-protected)) template if necessary to gain attention.

Semi-protection

See also: Wikipedia:Rough guide to semi-protection

Silver padlock

Semi-protected pages cannot be edited by unregistered users (IP addresses), as well as accounts that are not confirmed or autoconfirmed (accounts that are at least four days old and have made at least ten edits to Wikipedia). Semi-protection is useful when there is a significant amount of disruption or vandalism from new or unregistered users, or to prevent sockpuppets of blocked or banned users from editing, especially when it occurs on biographies of living persons who have had a recent high level of media interest. An alternative to semi-protection is pending changes, which is sometimes favored when an article is being vandalized regularly, but otherwise receives a low amount of editing.

Such users can request edits to a semi-protected page by proposing them on its talk page, using the ((Edit semi-protected)) template if necessary to gain attention. If the page in question and its talk page are both protected, please make your edit request at Wikipedia:Requests for page protection instead. New users may also request the confirmed user right at Wikipedia:Requests for permissions/Confirmed.

Guidance for administrators

Administrators may apply indefinite semi-protection to pages that are subject to heavy and persistent vandalism or violations of content policy (such as biographies of living persons, neutral point of view). Semi-protection should not be used as a preemptive measure against vandalism that has not yet occurred or to privilege registered users over unregistered users in (valid) content disputes.

In addition, administrators may apply temporary semi-protection on pages that are:

Today's featured article may be semi-protected just like any other article. However since the article is subject to sudden spurts of vandalism during certain times of day, administrators should semi-protect it for brief periods of time in most instances. For the former guideline, see Wikipedia:Main Page featured article protection.

Creation protection (salting)

Blue padlock

Administrators can prevent the creation of pages. This level of protection is useful for pages that have been deleted but repeatedly recreated. Such protection is case-sensitive. There are several levels of creation protection that can be applied to pages, identical to the levels for edit protection. A list of protected titles may be found at Special:ProtectedTitles (see also historical lists).

Pre-emptive restrictions on new article titles are instituted through the title blacklist system, which allows for more flexible protection with support for substrings and regular expressions.

Pages that have been creation-protected are sometimes referred to as "salted". Editors wishing to re-create a salted title with appropriate content should either contact an administrator (preferably the protecting administrator), file a request at Wikipedia:Requests for page protection#Current requests for reduction in protection level, or use the deletion review process. To make a convincing case for re-creation, it is helpful to show a draft version of the intended article when filing a request.

Administrators should choose the appropriate level of create protection—autoconfirmed, extended-confirmed,[2] or full. Due to the implementation of ACPERM, non-confirmed editors cannot create pages in mainspace; thus, semi-creation protection should be rare, used only for protection of pages outside of mainspace.

While creation-protection is usually permanent, temporary creation protection may be applied if a page is repeatedly recreated by a single user (or sockpuppets of that user, if applicable).

Move protection

Green padlock

Move-protected pages, or more technically, fully move-protected pages, cannot be moved to a new title except by an administrator. Move protection is commonly applied to:

Fully edit-protected pages are also implicitly move-protected.

As with full edit protection, protection because of edit warring should not be considered an endorsement of the current name. When move protection is applied during a requested move discussion, the page should be protected at the location it was at when the move request was started.

All files are implicitly move-protected; only file movers and administrators can rename files.

Upload protection

Purple padlock

Upload-protected files, or more technically, fully upload-protected files, cannot be replaced with new versions except by an administrator. Upload protection does not protect file pages from editing. It may be applied by an administrator to:

As with full edit protection, administrators should avoid favoring one version over another, and protection should not be considered an endorsement of the current version. An exception to this rule is when they are protected due to upload vandalism.

Pending changes protection

Further information: Wikipedia:Pending changes

White padlock

Pending changes protection is a tool used to suppress vandalism and certain other persistent problems while allowing all users to continue to submit edits. Pending changes protection can be used as an alternative to semi-protection to allow unregistered and new users to edit pages, while keeping the edits hidden from most readers until those changes are accepted by a pending changes reviewer.

When a page under pending changes protection is edited by an unregistered (IP addresses) editor or a new user, the edit is not directly visible to the majority of Wikipedia readers, until it is reviewed and accepted by an editor with the pending changes reviewer right. When a page under pending changes protection is edited by an autoconfirmed user, the edit will be immediately visible to Wikipedia readers, unless there are pending edits waiting to be reviewed.

Pending changes are visible in the page history, where they are marked as pending review. Readers that are not logged in (the vast majority of readers) are shown the latest accepted version of the page; logged-in users see the latest version of the page, with all changes (reviewed or not) applied. When editors who are not reviewers make changes to an article with unreviewed pending changes, their edits are also marked as pending and are not visible to most readers.

A user who clicks "edit this page" is always, at that point, shown the latest version of the page for editing regardless of whether the user is logged in or not.

Reviewing of pending changes should be resolved within reasonable time limits.

When to apply pending changes protection

Pending changes may be used to protect articles against:

Pending changes protection should not be used as a preemptive measure against violations that have not yet occurred. Like semi-protection, PC protection should never be used in genuine content disputes, where there is a risk of placing a particular group of editors (unregistered users) at a disadvantage. Pending changes protection should not be used on articles with a very high edit rate, even if they meet the aforementioned criteria. Instead, semi-protection should be considered.

In addition, administrators may apply temporary pending changes protection on pages that are subject to significant but temporary vandalism or disruption (for example, due to media attention) when blocking individual users is not a feasible option. As with other forms of protection, the time frame of the protection should be proportional to the problem. Indefinite PC protection should be used only in cases of severe long-term disruption.

Removal of pending changes protection can be requested of any administrator, or at requests for unprotection.

The reviewing process is described in detail at Wikipedia:Reviewing pending changes.

Extended confirmed protection

See also: Wikipedia:Rough guide to extended confirmed protection

Dark blue padlock

Extended confirmed protection, also known as 30/500 protection, only allows edits by editors with the extended confirmed user access level, granted automatically to registered users with at least 30 days' tenure and more than 500 edits.

Where semi-protection has proven to be ineffective, administrators may use extended confirmed protection to combat disruption (such as vandalism, abusive sockpuppetry, edit wars, etc.) on any topic. Extended confirmed protection should not be used as a preemptive measure against disruption that has not yet occurred, nor should it be used to privilege extended confirmed users over unregistered/new users in valid content disputes on articles not covered by Arbitration Committee 30/500 rulings. Extended confirmed protection may be applied at the discretion of an administrator when creation-protecting a page.[2] High-risk templates may be extended-confirmed protected at administrator discretion when template protection would be too restrictive and semi-protection would be ineffective to stop widespread disruption.[3]

Until August 12, 2016,[4] 30/500 protection applied only in topic areas determined by the Arbitration Committee, which authorized its use on articles reasonably construed as belonging to the Arab–Israeli conflict;[5] as an arbitration enforcement tool by motion or remedy;[6] or as a result of community consensus.[7] In February 2019, the community authorized uninvolved administrators to place pages reasonably construed as belonging to the India–Pakistan conflict under extended confirmed protection as part of a general sanctions regime.[8] In May 2020 the Arbitration Committee authorized extended confirmed protection to pages related to the history of Jews and antisemitism in Poland during World War II (1933–1945).[9]

As of September 23, 2016, a bot posts a notification in a subsection of AN when this protection level is used.[10] Any protection made as arbitration enforcement must be logged at Wikipedia:Arbitration enforcement log. A full list of the 3819 pages under 30/500 protection can be found here.

Users can request edits to an extended confirmed-protected page by proposing them on its talk page, using the ((Edit extended-protected)) template if necessary to gain attention.

Office actions

See also: Wikipedia:Office actions

Black padlock

As outlined in Meta-Wiki:Office actions#Use of advanced rights by Foundation staff, pages may be protected by Wikimedia Foundation staff in response to issues such as copyright infringement or libel. Such actions override community consensus. Administrators should not edit or unprotect such pages without permission from Wikimedia Foundation staff.[11]

Cascading protection

"WP:CASCADE" redirects here. You may also be looking for Help:Cascading Style Sheets or Wikipedia:Cascade-protected items.

Turquoise padlock

Cascading protection fully protects a page, and extends that full protection automatically to any page that is transcluded onto the protected page, whether directly or indirectly. This includes templates, images and other media that are hosted on the English Wikipedia. Files stored on Commons are not protected by any other wiki's cascading protection and, if they are to be protected, must be either temporarily uploaded to the English Wikipedia or explicitly protected at Commons (whether manually or through cascading protection there). When operational, KrinkleBot cascade-protects Commons files transcluded at Wikipedia:Main Page/Tomorrow, Wikipedia:Main Page/Commons media protection and Main Page. As the bot's response time varies, media should not be transcluded on the main page (or its constituent templates) until after it has been protected. (This is particularly relevant to Template:In the news, for which upcoming images are not queued at Wikipedia:Main Page/Tomorrow.) Cascading protection:

The list of cascading-protected pages can be found at Wikipedia:Cascade-protected items. Requests to add or remove cascading protection on a page should be made at Wikipedia talk:Cascade-protected items as an edit request.

Former deleted protections

Superprotect

See also: Meta-Wiki:Superprotect

Superprotect was a level of protection, allowing editing only by Wikimedia Foundation employees who are in the Staff global group. It was implemented on August 10, 2014 and used the same day to override community consensus regarding the use of the Media Viewer on the German Wikipedia's primary site JavaScript, common.js. It was never used on the English Wikipedia. On November 5, 2015, the WMF decided to remove superprotect from all Wikimedia wikis.

Restricted namespace protections

The Gadget and Gadget definition namespaces have namespace-wide protection, and the permissions to edit them are only available to WMF Staff. There is one page on the English Wikipedia in these namespaces. A request for local access to this namespace has been pending since 2019.

Cascading semi-protection

Cascading semi-protection was formerly possible, but it was disabled in 2007 after users noticed that non-administrators could fully protect any page by transcluding it onto the page to which cascading semi-protection had been applied by an administrator.

Pending changes protection level 2

Originally, two levels of pending changes protection existed, where level 2 required edits by all users who are not pending changes reviewers to be reviewed. Following a community discussion, level 2 was retired from the English Wikipedia in January 2017. It was suggested then that "Pending changes level 1" be referred to in the future as simply "Pending changes".[12]

Protection by namespace

Article talk pages

Modifications to a protected page can be proposed on its talk page (or at another appropriate forum) for discussion. Administrators can make changes to the protected article reflecting consensus. Placing the ((Edit protected)) template on the talk page will draw the attention of administrators for implementing uncontroversial changes.

Talk pages are not usually protected, and are semi-protected only for a limited duration in the most severe cases of vandalism.

User talk pages

User talk pages are rarely protected. However, protection may be applied if there is severe vandalism or abuse. Users whose talk pages are protected may wish to have an unprotected user talk subpage linked conspicuously from their main talk page to allow good-faith comments from users that the protection restricts editing from.

A user's request to have their own talk page protected is not a sufficient rationale by itself to protect the page, although requests may be considered if a reason is provided.

Blocked users

Blocked users' user talk pages should not ordinarily be protected, as this interferes with the user's ability to contest their block through the normal process. It also prevents others from being able to use the talk page to communicate with the blocked editor.

In extreme cases of abuse by the blocked user, such as abuse of the ((unblock)) template, re-blocking the user with talk page access removed should be preferred over applying protection to the page. If the user has been blocked and with the ability to edit their user talk page disabled, they should be informed of this in a block notice, subsequent notice, or message, and it should include information and instructions for appealing their block off-wiki, such as through the UTRS tool interface or, as a last recourse, the Arbitration Committee.

When required, protection should be implemented for only a brief period, not exceeding the duration of the block.

Confirmed socks of registered users should be dealt with in accordance with Wikipedia:Sockpuppetry; their pages are not normally protected.

User pages

Base user pages (for example, the page User:Example, and not User:Example/subpage or User talk:Example) are automatically protected from creation or editing by unconfirmed accounts and anonymous IP users. An exception to this includes an unconfirmed registered account attempting to create or edit their own user page. IP editors and unconfirmed accounts are also unable to create or edit user pages that do not belong to a currently-registered account. This protection is enforced by an edit filter.[13] Users may opt-out of this protection by placing ((unlocked userpage)) anywhere on their own user page.

User pages and subpages within their own user space may be protected upon a request from the user, as long as a need exists. Pages within the user space should not be automatically or pre-emptively protected without good reason or cause.[14][15] Requests for protection specifically at uncommon levels (such as template protection) may be granted if the user has expressed a genuine and realistic need.

When a filter is insufficient to stop user page vandalism, a user may choose to create a ".css" subpage (ex. User:Example/Userpage.css), copy all the contents of their user page onto the subpage, transclude the subpage by putting ((User:Example/Userpage.css)) on their user page, and then ask an administrator to fully protect their user page. Because user space pages that end in ".css", ".js", and ".json" are editable only by the user to which that user space belongs (and interface administrators), this will protect your user page from further vandalism.

Deceased users

See also: Wikipedia:Deceased Wikipedians/Guidelines

In the event of the confirmed death of a user, the user's user page (but not the user talk page) should be fully protected.

Protection of templates

See also: Wikipedia:High-risk templates and Wikipedia:Template documentation

Highly visible templates – those used on a large number of pages or frequently substituted – are often edit protected based on the degree of visibility, type of use, content, and other considerations.

Protected templates should normally have the ((documentation)) template. It loads the unprotected /doc page, so that non-admins and IP-users can edit the documentation, categories and interwiki links. It also automatically adds ((pp-template)) to protected templates, which displays a small padlock in the top right corner and categorizes the template as protected. Only manually add ((pp-template)) to protected templates that don't use ((documentation)) (mostly the flag templates).

Cascading protection should generally not be applied directly to templates, as it will not protect transclusions inside <includeonly> tags or transclusions that depend on template parameters, but will protect the template's documentation subpage. Instead, consider any of the following:

Note: All editnotice templates (except those in userspace) are already protected via MediaWiki:Titleblacklist. They can be edited by admins, template editors and page movers only.

Sandboxes

See also: Wikipedia:About the sandbox

Sandboxes should not ordinarily be protected since their purpose is to let new users test and experiment with wiki syntax. Most sandboxes are automatically cleaned every 12 hours, although they are frequently overwritten by other testing users. The Wikipedia:Sandbox is cleaned every hour. Those who use sandboxes for malicious purposes, or to violate policies such as no personal attacks, civility, or copyrights, should instead be warned and/or blocked.

Available templates

The following templates may be added at the very top of a page to indicate that it is protected:

On redirect pages, use the ((Redirect category shell)) template, which automatically categorizes by protection level, below the redirect line. A protection template may also be added below the redirect line, but it will serve only to categorize the page, as it will not be visible on the page, and it will have to be manually removed when protection is removed.

See also

Notes

  1. ^ Created October 2013 as a result of Wikipedia:Requests for comment/Template editor user right‎
  2. ^ a b Wikipedia:Requests for comment/Extended confirmed protection policy 2
  3. ^ Should we use ECP on templates? discussion at the village pump.
  4. ^ Wikipedia:Requests for comment/Extended confirmed protection policy
  5. ^ Wikipedia:Arbitration/Requests/Case/Palestine-Israel articles 4#ARBPIA General Sanctions (Note: This sanction was originally authorised in Wikipedia:Arbitration/Requests/Case/Palestine-Israel articles 3).
  6. ^ Arbitration motions regarding extended confirmed protection
  7. ^ Wikipedia:Village pump (proposals)/Archive 129#New usergroup with autopromotion to implement arbitration "30-500" bans as a page protection
  8. ^ AN discussion authorizing India-Pakistan general prohibition
  9. ^ Antisemitism in Poland: Motion (May 2020)
  10. ^ Wikipedia talk:Protection Policy discussion to remove manual posting requirement
  11. ^ Unlike with WP:SUPERPROTECT, admins technically can still edit or unprotect these pages, however, they should not do so without permission.
  12. ^ VPR RfC to remove PC2
  13. ^ Please refer to Wikipedia:Requests for comment/Protect user pages by default and its talk page for community discussion related to a preventative measure for user pages.
  14. ^ Per discussion at Wikipedia talk:Protection policy/Archive 15#Own userspace pages protection policy, June 2013
  15. ^ Per discussion at Wikipedia:Administrators' noticeboard/Archive314#Protecting an editor's user page or user space per their request, September 2019
https://db0nus869y26v.cloudfront.net/en/Wikipedia:Protection_policy
db0nus869y26v.cloudfront.net
crawl=CC-MAIN-2022-27
192736
application/http; msgtype=response
sha1:X6IIWQSDGP2SPSWA7TYADS5TD7EXGTQX
<urn:uuid:960f83c0-b748-4f8e-b8dc-2ef6eb623b54>
2022-07-06T05:06:00Z
13.249.46.212
text/html
sha1:HAW3EJXOEJPEFHVA2JYGAZGHIB4CJ6QK
<urn:uuid:d2bf56aa-766f-4390-9d5a-fd9913132906>
https://db0nus869y26v.cloudfront.net/en/Wikipedia:Protection_policy
response
<urn:uuid:4a698624-b6a6-4fbb-9e96-f10ff1843490>
isPartOf: CC-MAIN-2022-27
publisher: Common Crawl
description: Wide crawl of the web for June/July 2022
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-49
software: Apache Nutch 1.18 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.3-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/