IP編集:プライバシー保護と荒らし行為軽減/IP 情報機能

This page is a translated version of the page IP Editing: Privacy Enhancement and Abuse Mitigation/IP Info feature and the translation is 61% complete.

趣旨は、管理者、不正行為の対策者、パワーユーザーの皆さんに IP アドレスに関する情報の入手を簡略化することです。

IP 情報機能の試行模型





本日付で、IP 情報機能をベータ機能としてすべてのウィキに実装


  • MaxMindのデータ品質に対するフィードバックは最多で重要度が最も高いものでした。MaxMindのデータ品質は、プロキシデータに限ると、よくありません。これに関してMaxmindに連絡をとりましたし、Spurからは先方のデータフィード提供を交渉しました。Spurのデータフィールドを入手した段階で機能に組み込み、複数の情報源由来の情報を提示できる見込みです。
  • We heard about the interface being unclear about what information is available and what isn't. We are working on improving the labels and providing better guidance about the information displayed.
  • We heard a request about expanding the tool to include global information and also include information about IPs that have not made any edits on the given wiki. We will be looking more into both of these requests. We have done some prior investigation into showing global information.

We would love to hear more feedback about the feature. Please feel free to leave feedback as you use the feature. Your feedback will help improve the tool.






There are two levels of access to IP information. Users with Autoconfirmed will be able to access the Basic information. Users with advanced privileges (admin, sysop, bureaucrat, checkuser) will be able to access the Advanced information. Advanced information includes City, State, ISP, Organization + Basic. Everything else displayed in the above screenshot will be available in Basic.



In order to activate IP Info the user will need to agree to a disclaimer stating that this information is being accessed for anti-vandalism purposes only. Once activated, the user will be able to access both the IP Info popup (on log, history and recent changes pages) and the IP Info infobox (on contributions page). There will be a log to keep track of how IP information is being accessed. This is purely for Legal purposes. Only WMF Trust & Safety staff will have access to this log for the time being.


There are two places to access this information: the popup and the infobox. The popup is intended to be a quick way to access specific IP details which can help while patrolling on the recent changes, log or history pages. The full infobox will be available on Special:Contributions. Clicking on the popup will lead to the infobox.


When the tool is available on all projects there will be a link to provide feedback directly through the feature itself. This will allow for structured feedback to be collected in multiple languages. In the meantime, please reach out to us on the talk page and provide feedback.


  • What did you like about this tool?
  • What did you find confusing or missing?
  • How else can we improve this feature?



  • Identifying and incorporating new streams of information into the feature. This can include sources like Spur that we have discussed in the past. This will also help us get better coverage for IPs in different parts of the world.
  • Bringing this information into CheckUser. Checkusers will benefit from having this key information at their fingertips.

We don’t have a firm timeline for when we will be working on these. We want to ensure the tool is useful in its current state before adding new features. Our top priority is to build a feature that patrollers across different projects use and find helpful.


The Anti-Harassment Tools team has recently wrapped up its work on delivering key changes to SecurePoll and assisting with the Wikimedia Foundation Board of Trustees elections 2021. We are back to working on IP Info and hopefully this page will see many more updates in the near future. Since we were gone, here's the big updates on this project:

  • We received MaxMind access. It took longer than anticipated but we finally have access to all the key data we needed.
  • We are currently working on delivering on the mocks we referred to in our last update. One key addition to the data has been the inclusion of a data point indicating whether the IP address is v4 or v6.


IP Info product development is well underway. We wanted to take this opportunity to tell you about where we are at and get your feedback on the direction.

User interviews & task model

We conducted user interviews to understand how editors currently patrol IPs. This gave us a rough understanding of the IP patrolling process, information required and tools used. Based on this research we came up with a model of how the task of IP patrolling is usually conducted. After a few rounds of feedback from design, engineers, research and T&S folks here is what we came up with:

Task model for IP Info workflow

As we understand it now, the IP patrolling process usually starts from RecentChanges, an editor’s Watchlist or from a page that the editor knows gets vandalized often. When looking at the edits of such a page the patroller first looks for clear red flags like edit flooding, lack of edit summary, large deletions etc. They then look for more specific on-wiki information like if the IP has a talk page, if it has ever been blocked in the past, its global and local contributions, and in the case of English Wikipedia, if there is a mention of the IP on the LTA page.

Based on this initial research they decide if an IP is worth looking into further. If it is, they use external tools to find more information about the IP, like: location, proxy usage and organization that the IP might be linked to. This process is not completely accurate since different databases have different information on the same IP. Oftentimes, based on the location of the IP and the location of the IP tool, the information given might be very different.

Finally, based on the information collected they decide which action would be most appropriate. Again, this decision takes into account various factors like the policies of that wiki, the scale of the collateral damage caused by a range block, consistency in editing patterns etc.


Based on feedback from the first round of user interviews, we have settled on the following product approach.

IP情報 最低限必要とされる利用者権限
位置 管理者 / チェックユーザー
ISP/ドメイン 管理者 / チェックユーザー
ASN 管理者 / チェックユーザー
組織 管理者 / チェックユーザー
接続種別 自動承認された利用者
利用者種別 自動承認された利用者
プロキシ情報 自動承認された利用者
静的 / 動的 自動承認された利用者
IPの利用者数 自動承認された利用者

Since the patrollers need on-wiki information about the IP before they decide to investigate it we are going to add a popup that shows block and contribution information. The popup would be accessible by clicking an information icon next to the IP address on pages like RecentChanges, Watchlist and History.

If the patroller decides to dig deeper into an IP address by going to their Contributions page, they'll be able to see a collapsible box that shows more IP related information.

Access to information and risk to anonymous editors

By making the IP information so readily available we hope to remove some of the barriers that our non-technical patrollers might be facing in reliably getting this information. At the same time, we hope this streamlines the process for users who are currently relying on external tools. We also recognize that easy access to this information might be putting our anonymous editors at risk, especially because some of the IP information, like location and organization, can easily help in identifying a person.

We need to balance the concerns of ease of use and risk to anonymous editors. To do this we plotted the different pieces of IP information on a graph with Risk on the Y axis and Usefulness to patrolling on the X axis:

Risk vs Usefulness of IP Information

This exercise wasn't completely scientific and was based on the learnings from research and estimates of the team (please see the questions below if you'd like to contribute). Two possible clusters appeared, the high risk one mostly containing information that could reveal an editor’s location.

We are planning to show all on-wiki information to all editors that are auto-confirmed and above. Auto-confirmed and above editors will also have access to IP information that doesn't reveal possibly personal information about anonymous editors. This would include things like proxy and static/dynamic-ness of the IP. Finally, Admins and Checkusers will have access to more IP information like location, organization and domain.


  • Is there any other information you look at before deciding to investigate an IP?
  • When investigating an IP what kinds of information do you look for? Which page are you likely on when looking for this information?
  • What kinds of IP information do you find most useful?
  • What kinds of IP information when shared, do you think could put our anonymous editors at risk?


The project is currently under backend development as we are looking into sources to pull IP Information from and what kind of information we should display and to whom. We have a mockup ready for your feedback. Would love to hear your feedback on the talk page.


  • We have done an initial technical investigation into this project. Follow along on phab:T248525.
  • We are currently looking into the various services that provide information about IP addresses. Follow along on phab:T251933.


コミュニティにおける IP アドレス情報の有用性とは


Research:Patrolling on Wikipedia/Report も参照

Single-address blocks bar a single IP address from editing the site, or specific pages in the case of partial blocks, for a specified duration. MediaWiki also allows administrators to block IP ranges, which is helpful for dynamic IPs or covering a small range frequently used for vandalism. Administrators are expected to check the coverage of ranges they intend to block in order to assess collateral damage.

特定の種別の範囲ないしは単一のIPブロックは、アドレスの種別に応じてそれぞれ個別の対応をするか、テンプレートをタグ付けします。一例として、特定のIPアドレスが荒らしを行い、それが特定の教育機関に所属する場合には、管理者は特段の配慮をしてTemplate:SchoolblockTemplate:SharedIPEDUなどを付与します。その重要性は特筆するべきであり、指導要項の一環として教員がウィキペディアの編集を課題として生徒や学生に与えた場合であり、過去にその教育機関をブロックした経歴があるとすると、テンプレートが表示されて先方の管理者に問い合わせるように指示が表示されます。この種のテンプレートは他にも、公共のアドレスと判断した場合のTemplate:Shared IP address (public)(英語版)があります。これは必ずしもブロックに用いるのではなく、先制して使うと、メッセージの受信者に心当たりのない指摘、あるいは登録利用者限定の機能の案内を通知しないようにして、混乱を防ぐ役に立ちます。これらのテンプレートは英語版ウィキペディア固有ではなく、同種のものは他言語版もしくは他のプロジェクトでたくさん採用しています。

The IP blocking workflow of administrators currently relies on some IP information, usually the registered organization, geographic location, and ASN. This information generally comes from third-party IP information providers, with no standard service and therefore, different degrees of accuracy and reliability. For example, an edit from an IP address registered to a residential ISP should be handled differently to an edit from an IP registered to a government organization.

IP addresses are also used in AbuseFilter in conjunction with other settings and targets to make very specific blocks, so as to minimize disrupting the experience of regular users.











  • 特定のIPアドレスの高度な地理的位置情報
  • IPアドレスの保持者
  • 当該のIPアドレスがプロキシもしくはTorノードの背後にあるかどうか
  • 他のウェブサイトで当該のIPアドレスに悪意を認識したかどうか



  • IP アドレスに関して、皆さんが詳細情報を調べる場面とは?
  • ぜひ知りたい情報とはなんですか?
  • 情報を目にする場所として、どこが良いでしょうか?
  • この情報はどうお役に立ちそうですか? さっそく何かに使ってみるとして、それはどんな作業でしょうか?




  • 簡便な巡回:この機能は、利用者が IP アドレスを複写する外部ツールを必要とせずに済むよう、および利用者が必要とする情報を引き出すにあたり少ない作業で行えるよう導きます。
  • 迅速な巡回:本機能を介し、必要とされる情報の素早い提供により編集者の時間短縮を図ります。
  • 信頼性を高める:財団が外部ウェブサイトと契約するなら、先方は信頼性が高度で定期的に翻訳の更新を続けるところになります。プロジェクト自体、財団が保守管理するため、現状で一部の利用者が依拠するウェブサイド群よりも信頼性の安定を図ることもできそうです。
  • 低い技術的障壁:新たな管理者と監査役に IP アドレスに関する情報を引き出す手法について深い理解を要せずとも容易に行えるよう図ります。こうして少数弱者の利用者に強力で長期に渡り活躍の機を促します。


  • 個人情報のリスク:個別の IP アドレスの文字列からどんな情報が得られるか、インターネット利用者全員が意識しているわけではありません。そこで登録しないまま編集を行ったために指紋を残し、それが自分を探し出すことに使われる可能性に気づいていない 利用者がしばしばいます。同様に、このことの知識がない編集者も大勢います。この事態により登録していない利用者には意図しない個人情報の秘匿に結びつきます(Security through obscurity。)この機能により得られる情報が誰に可視化されるかによって、以前よりも多くの利用者が当該のデータを目にするという、深刻なリスクが存在します。