View source for Responding to threats
You do not have permission to edit this page, for the following reasons:
- This page has been protected to prevent editing or other actions.
- {| style="width: 100%;"
|-
| style="padding: 10px 15px; border-top: 4px solid #67440F; background-color: #FFF2F6;" | Your username and/or IP address has/have been blocked from editing.
This block, which affects 35.171.0.0/16, was made by MirahezeGDPR 16fc0f3be9aee9d47751a49c79ecd7f6 at 20:54, 11 March 2023.
The reason given is:
Web host or open proxy. Contact cvt[at]miraheze.org if affected
This block will be set to expire at: 20:54, 11 March 2025.
Even when blocked, you can still edit your talk page. You can discuss this block by requesting an unblock request at your talk page or by contacting MirahezeGDPR 16fc0f3be9aee9d47751a49c79ecd7f6 or another administrator to discuss the block. You can use the "Email this user" feature if a valid email address is specified in your preferences and you have not been blocked from using it. Your current IP address is 35.171.164.77, and the block ID is #134297. Please include all above details in any queries you make.
|- |
|} - Your IP address is in a range which has been blocked on all wikis.
The block was made by MirahezeGDPR 16fc0f3be9aee9d47751a49c79ecd7f6.
The reason given is Web host or open proxy. Contact cvt[at]miraheze.org if affected.
- Start of block: 20:54, 11 March 2023
- Expiration of block: 20:54, 11 March 2025
You can view and copy the source of this page.
Return to Responding to threats.