懒的狠，直接粘来。 自己看
分类： 未分类
常见的洗钱方法
常见的洗钱方法有：
- 旅行支票：海关会对于通关者携带的现金要求申报，未申报者超过限制者没收，但不会对携带旅行支票者做金额的限制，重点在于无背书转让给第三者，因为支票被存入银行兑现，最终会回到原发票人的手中。
- 在赌场以代币间接兑换：在赌场中兑换成代币，再将代币直接交付给洗钱的受益人。再由他去将代币兑换回现金（通常需要5%左右的手续费），在外可声称在赌场内赌赢的。这样可以避免透过纸钞上的编号直接追查到洗钱的受益人。常用于各国可将代币兑换回现金的职业赌场。
- 购买已经中奖的彩票或马票：与银行勾结，以高价向得主私下购买已得奖的票券，并公开兑换。
- 购买无记名债券或期货
- 购买古董珠宝或具价值收藏品、高价中古精品：利用低买高卖的假买卖，将钱以合法的交易方式，洗到目的账号。此方式亦常用于收贿的收钱方式；或购买具价值的古董珠宝或收藏品，再讹称为自家收藏品在市场上放售，一般会购买没有记号的物品如文物、邮票或历史悠久的名厂乐器。或私下购买多部名车，中古私人飞机，珠宝名牌等高价值物转售。
- 纸上公司的假买卖：用空壳、信用不良、股份公司做假交易、股票投资、偿还债务等方式洗钱。
- 购买保险：将大笔金额投保，期间亦可不断提升保金，转换保险计划，待一定年数后取回，届时可疑的因素已遭淡化。
- 基金会：不肖政客，成立基金会，假捐赠给基金会，诱骗企业捐款，再掏空。企业或财团，利用假捐赠给自己能掌控的基金会，左手搬钱到右手，逃漏所得税。政客或企业利用赈灾名义募款，可是募到的善款私自挪用，或用各种名目扣住善款于私人户头。在跨国洗钱活动中，以各地不同慈善名义的基金会中互相转换款额。
- 跨国多次转汇与结清旧账户：利用转汇的相关单据有保存期限的漏洞。
- 直接跨国搬运：利用专机或具有海关免验的身份者，直接把钱搬到外国，常用100美元的纸钞方式运送。
- 人头账户：由于最怕黑吃黑，怕人头到银行声称存折与提款卡与印章丢失，另行申请新的存折与提款卡并变更印鉴，进行盗领。所以通常用于人头本身所不知的外国开户。
- 外币活存账户：使用多次小额存款的方式存入，再到外国提领外币。俗称“蚂蚁搬砖”，常配合“人头账户”使用。
- 跨国交易：常见于无实体商品的产业。利用交易金额造假灌水的方式，先透过合法的方式将金钱汇往外国掮客的账户，再通过外国账户分钱，分清原本的交易金额、掮客的佣金与原本要洗出去的钱；或利用各地的商品贸易，例如以过高金额购买普通消费品，将大量款项汇到国外账户，装作用以支付买货款项。反过来亦可将商品高价出售，让国外的洗钱伙伴将款项汇进国内。
- 地下汇兑：常见于不肖的卖珠宝金饰的银楼。除了非法兑换外币以外，甚至可将现金兑换为外国的无记名与背书的支票，供客户至外国的账户存入。
- 跨国企业的资金调度：常见于金融业，银行或保险业等，常以大批的现金纸钞进行跨国搬运。例如以麻绳捆绑、纸箱方式搬运。
- 百货公司的礼券：具有高度的流通性，但由于具有不易兑换回现金的特性，故需有一定的人脉，才方便消化礼券。例如转卖给各公司的员工福利机构，将礼券做为其各公司员工的节假日奖金方式发放。就这样把礼券洗到不知情的第三者手中，原礼券持有人则取回接近等值的现金。
- 人头炒楼：使用人头购买房地产，向承包商或开发商以市价五至七折买入，以现金支付。然后在短期内快速脱手（例如预售屋在交屋前），获利约50%－100%。
- 假借贷：常用于收贿或贪污。收钱的人持有对方开立的远期兑现的本票或支票。即使被查到这张本票或支票，可声称为借贷关系。等风头过了或不在其位，没有明显的对价关系时，再把本票或支票转手给第三者，或是扎进银行兑现。或是贪污被揭发的人说要还钱，但开立本票或支票，只要没有兑现，就没有真正的还钱。
- 伪币或伪钞：将伪币或伪钞，通过多次小金额消费行为，或是利用自动贩卖机找零行为，或是纸钞兑换成硬币的机器。将伪币或伪钞洗成真钱。
- 黑道：购入价值的毒品贩毒、地下枪械等。将赃款转嫁给他人。
- 比特币（Bitcoin）等加密货币：基于比特币等加密货币的匿名性，且可自由、不记名的产生不同的比特币钱包，搭配混币服务，难以追踪真实身份，是近年来常见的洗钱工具。
- 第三方或者第四方支付平台：部分第三方支付平台存在账户未实名注册、管理不规范等问题，致使一些账号可以在网络上直接买卖，部分平台沦为电信诈骗团伙套取、漂白非法资金的“绿色通道”。诈骗团伙利用第三方支付平台转移赃款和洗钱的手段一般有3种：通过第三方支付平台发行的商户POS机虚构交易套现；将诈骗得手的资金转移到第三方支付平台账户，在线购买游戏点卡、比特币等物品后转卖套现；将赃款在银行账户和第三方支付平台之间多次转账切换，逃避公安追查。
禁用software_reporter_tool.exe 解决CPU高占用率的问题
今天开机后，从几分钟到半个小时之间，感觉机器反应有些慢，发现CPU占用80-90%。查看任务管理器，
有一个 software_reporter_tool.exe 的程序占用了一半的CPU使用率。 转到文件所在文件夹查看，发现是 Google Chrome 使用的一个文件。
查询该文件，发现 software_reporter_tool.exe 会扫描系统，类似
Chrome 的一个计划任务，每周启动扫描 一次，运行大约20-25分钟。它会扫描
Google Chrome 浏览器 未能正常运行的程序问题，比如多次未正常关闭
Chrome ，或某些恶意软件或应用程序导致Chrome浏览器运行中出现错误，它就会扫面检查问题通知你并删除该受感染程序。
简单来说，Software Reporter Tool 是 Chrome 清理报告工具 ， 帮助维持Google Chrome正常运行。但是效率上的低下，让我感觉到系统延迟，要想办法让他以后停止执行。
文件位置： C：\ Users \ {您的用户名} \ AppData \ Local \ Google \ Chrome \用户数据\ SwReporter \ {版本号}\ software_reporter_tool.exe
网上看到方法是，修改 Chrome 设置，“ 将使用情况统计信息和崩溃报告自动发送给 Google ”的选项关闭，我看了我的设置本身就是关闭的。解决无效，然后自己找到了用最简单的方法，
C:\Users\Administrator\AppData\Local\Google\Chrome\User Data\SwReporter\36.184.200 下编辑 manifest.json文件：
“allow-reporter-logs”: true 修改为 “allow-reporter-logs”: false
这样它会自己停止运行，并且下次不再启动。
CentOS Install .NET Core
.NET Tutorial – Hello World in 10 minutes
https://www.microsoft.com/net/learn/get-started-with-dotnet-tutorial
Add the dotnet product feed
Before installing .NET, you’ll need to register the Microsoft key, register the product repository, and install required dependencies. This only needs to be done once per machine.
Open a command prompt and run the following commands:
sudo rpm -Uvh https://packages.microsoft.com/config/rhel/7/packages-microsoft-prod.rpm
Install .NET Core SDK on Linux CentOS / Oracle
https://www.microsoft.com/net/download/linux-package-manager/centos/sdk-current
sudo yum update sudo yum install dotnet-sdk-2.1
Install .NET Core Runtime on Linux CentOS / Oracle
https://www.microsoft.com/net/download/linux-package-manager/centos/runtime-current
sudo yum update sudo yum install aspnetcore-runtime-2.1
穆斯林黑客在行动
9-21日，在.TD域名的管理机构，www.nic.td 查询域名时 ，发现有条不显眼的标题 “HaCkEd by CrashBandicot”。
一个国家顶级域名的管理机构被入侵，很显然，还是让人感觉不错的~ 。。。
顺便在 Bing 查下这 “HaCkEd by CrashBandicot”。 还查到不少被他们改页面的站点。
这个就是地处主要战场的阿勒颇，阿勒颇的水x局？！ 我宁可相信这是域名劫持， 很难相信叙利亚一个政府网站会放在一个美国主机
http://bohu.net/dns/?doquery=1&question=www.aleppowater.gov.sy&type=A&server=8.8.8.8&port=53
www.aleppowater.gov.sy has IPv4 address: 66.63.181.105(美国加利福尼亚州洛杉矶QuadraNet网络公司)
下面这个图文声色，做工精美，特别是背景音乐还是不错的。（MP3： http://www.4shared.com/embed/412420232/f5ca175c）
http://bohu.net/dns/?doquery=1&question=paintersadelaide.net&type=A&server=8.8.8.8&port=53
paintersadelaide.net has IPv4 address: 103.9.169.121(澳大利亚)
“CrashBandicot”应该是中东的穆斯林黑客团体（Muslim Hacker ）所为，更具体可能为巴勒斯坦或亲叙利亚政府的黑客，他们标榜和宣扬自己的muslim hacker身份，并为此自豪。看到一个留有网站“crash-bandicot.co.cc”， 但是无内容。
Bing | Google 一下，还有不少：
www.aru-edu.com，kasbah-sable-dor.net，world-of-empathy.org，www.cadumotos.com.br
。。。 。。。
。。。
竟然还有一中国政府网站 bm.ml.gov.cn ， 这个应该是注入进入的，没改首页藏的很深。
最后在 http://evuln.com/labs/hackedby/1882/ 看到一个清单：
eVuln Labs. The list of websites with the following signature:
# Hacked By CrashBandicot #
Discovered Website Hoster 2013-07-25 ***osalvomendes.com.br 2013-06-16 ***osalvomendes.com.br dialhost.com.br 2013-01-15 ***ordios.com 2013-01-12 ***ld-of-empathy.org ispfr.net 2013-01-10 ***internacional.com smart-hosts.net 2013-01-06 ***theredge.com weatheredge.com 2013-01-03 ***ehpraise.com 2012-12-24 ***juvenilalianzacri stiana.org smart-hosts.net 2012-12-24 ***bridgeconstructio n.co.uk justhost.com 2012-12-24 ***ica.fr kundenserver.de 2012-12-19 ***kmakerenemy.com bookmakerenemy.com 2012-12-19 ***hura.org lunarpages.com 2012-12-19 ***-account.com 2012-12-18 ***ejan.com ispfr.net 2012-12-18 ***ionalachieverscon gressbonus.com justhost.com 2012-12-18 ***ear.net cluster010.ovh.net 2012-12-18 ***webblog.com 2012-12-18 ***imuktaxback.com justhost.com 2012-12-18 ***klascoop.net 2012-12-18 ***thingvillage.com extendcp.co.uk 2012-12-18 ***dengarage.co.uk justhost.com 2012-12-18 ***fitswebdesign.co.uk justhost.com 2012-12-18 ***hatvnova.com 2012-12-18 ***aciznatury.com justhost.com 2012-12-18 ***ances-privees.com 2012-12-18 ***skiprawniklondyn. co.uk justhost.com Total 27 websites
看了 eVuln Lab 的统计列表，才知道 “CrashBandicot” 只是个小喽啰。 大神是 “AnonGhost”，有自己公开的网站www.anonghost.com ，以反以著称。
Latest most active defacers.
Websites defaced Signature 1295 HaCked by AnonGhost 747 Hacked By International Force 678 Hacked By Dark Knight Sparda 563 Hacked By ReZK2LL Team 202 HACKED BY KRAD XIN 100 Hacked By # brkod # aLsha67 88 ҳ̸Ҳ̸ҳ Hacked By Maniak k4sur ҳ̸Ҳ̸ҳ 84 Hacked By.White Hat 83 Hacked By Afghan Cyber 72 Hacked By RooT HaXor 68 .:: Hacked By : T3RMiNaL 63 Hacked By Afghan Cyber Army 62 HacKed By Jack Riderr [ Johor Hacking Crew ] 62 hacked by saif ule est, web sniper, saif ule est 52 HackeD By h4x0r HuSsY 47 hacked by VIRTUAL 35 hacked by Sa-Dz 34 Hacked by Kosova Warriors Group 32 Hacked By Lionel MajDii 30 HackeD By Crack kid 29 Hacked by Panda Dot ID 28 Hacked by Dr.SaFa7 & Shi6an 7rb kuwait hackers 26 —==[ Hacked By ALFA TEaM ]==— 23 Hacked by Krad Xin RSS Feed 23 Hacked By 3xp1r3 Cr4Ck 20 Hacked by LORDOFDARKNES 14 Hacked by WaRLoCK 13 hacked by w7sh.syria 13 Hacked by Hank Sandlep 13 Hacked By .. brkod 11 hacked by Amirh03in 10 Hacked By NightMare 10 Hacked by xLitleonZ
HaCked by AnonGhost 的“作品”赏析：
等等 。。。 。。。 （Bing 、 Google 自己搜吧）
文件大小换算
1 Mio file = 1 mebioctet* = 220 octets = 1,024 Kio = 1,048,576 octets
10 Mio file = 10 mebioctet = 10 x 220 octets = 10,240 Kio = 10,485,760 octets
100 Mio file = 100 mebioctet = 100 x 220 octets = 102,400 Kio = 104,857,600 octets
1 Gio file = 1 gibioctet = 230 octets = 1,024 Mio = 1,073,741,824 octets
10 Gio file = 10 gibioctet = 10 x 230 octets = 10,240 Mio = 10,737,418,240 octets
1 Mbit file = 1 megabit = 106 bits = 1,000 kbit = 1,000,000 bits
10 Mbit file = 10 megabit = 107 bits = 10,000 kbit = 10,000,000 bits
100 Mbit file = 100 megabit = 108 bits = 100,000 kbit = 100,000,000 bits
1 Gbit file = 1 gigabit = 109 bits = 1,000 Mbit = 1,000,000,000 bits
10 Gbit file = 10 gigabit = 1010 bits = 10,000 Mbit = 10,000,000,000 bits
IANA IPv4 地址空间注册表
IANA IPv4 Address Space Registry
- Last Updated
- 2013-03-22
- Description
-
The allocation of Internet Protocol version 4 (IPv4) address space to various registries is listed here. Originally, all the IPv4 address spaces was managed directly by the IANA. Later parts of the address space were allocated to various other registries to manage for particular purposes or regional areas of the world. RFC 1466 [RFC1466] documents most of these allocations.
This registry is also available in plain text.
| Prefix | Designation | Date | Whois | Status [1] | Note |
|---|---|---|---|---|---|
| 000/8 | IANA – Local Identification | 1981-09 | RESERVED | [2] | |
| 001/8 | APNIC | 2010-01 | whois.apnic.net | ALLOCATED | |
| 002/8 | RIPE NCC | 2009-09 | whois.ripe.net | ALLOCATED | |
| 003/8 | General Electric Company | 1994-05 | LEGACY | ||
| 004/8 | Level 3 Communications, Inc. | 1992-12 | LEGACY | ||
| 005/8 | RIPE NCC | 2010-11 | whois.ripe.net | ALLOCATED | |
| 006/8 | Army Information Systems Center | 1994-02 | LEGACY | ||
| 007/8 | Administered by ARIN | 1995-04 | whois.arin.net | LEGACY | |
| 008/8 | Level 3 Communications, Inc. | 1992-12 | LEGACY | ||
| 009/8 | IBM | 1992-08 | LEGACY | ||
| 010/8 | IANA – Private Use | 1995-06 | RESERVED | [3] | |
| 011/8 | DoD Intel Information Systems | 1993-05 | LEGACY | ||
| 012/8 | AT&T Bell Laboratories | 1995-06 | LEGACY | ||
| 013/8 | Xerox Corporation | 1991-09 | LEGACY | ||
| 014/8 | APNIC | 2010-04 | whois.apnic.net | ALLOCATED | [4] |
| 015/8 | Hewlett-Packard Company | 1994-07 | LEGACY | ||
| 016/8 | Digital Equipment Corporation | 1994-11 | LEGACY | ||
| 017/8 | Apple Computer Inc. | 1992-07 | LEGACY | ||
| 018/8 | MIT | 1994-01 | LEGACY | ||
| 019/8 | Ford Motor Company | 1995-05 | LEGACY | ||
| 020/8 | Computer Sciences Corporation | 1994-10 | LEGACY | ||
| 021/8 | DDN-RVN | 1991-07 | LEGACY | ||
| 022/8 | Defense Information Systems Agency | 1993-05 | LEGACY | ||
| 023/8 | ARIN | 2010-11 | whois.arin.net | ALLOCATED | |
| 024/8 | ARIN | 2001-05 | whois.arin.net | ALLOCATED | |
| 025/8 | UK Ministry of Defence | 1995-01 | whois.ripe.net | LEGACY | |
| 026/8 | Defense Information Systems Agency | 1995-05 | LEGACY | ||
| 027/8 | APNIC | 2010-01 | whois.apnic.net | ALLOCATED | |
| 028/8 | DSI-North | 1992-07 | LEGACY | ||
| 029/8 | Defense Information Systems Agency | 1991-07 | LEGACY | ||
| 030/8 | Defense Information Systems Agency | 1991-07 | LEGACY | ||
| 031/8 | RIPE NCC | 2010-05 | whois.ripe.net | ALLOCATED | |
| 032/8 | AT&T Global Network Services | 1994-06 | LEGACY | ||
| 033/8 | DLA Systems Automation Center | 1991-01 | LEGACY | ||
| 034/8 | Halliburton Company | 1993-03 | LEGACY | ||
| 035/8 | Administered by ARIN | 1994-04 | whois.arin.net | LEGACY | |
| 036/8 | APNIC | 2010-10 | whois.apnic.net | ALLOCATED | |
| 037/8 | RIPE NCC | 2010-11 | whois.ripe.net | ALLOCATED | |
| 038/8 | PSINet, Inc. | 1994-09 | LEGACY | ||
| 039/8 | APNIC | 2011-01 | whois.apnic.net | ALLOCATED | |
| 040/8 | Administered by ARIN | 1994-06 | whois.arin.net | LEGACY | |
| 041/8 | AFRINIC | 2005-04 | whois.afrinic.net | ALLOCATED | |
| 042/8 | APNIC | 2010-10 | whois.apnic.net | ALLOCATED | |
| 043/8 | Administered by APNIC | 1991-01 | whois.apnic.net | LEGACY | |
| 044/8 | Amateur Radio Digital Communications | 1992-07 | LEGACY | ||
| 045/8 | Administered by ARIN | 1995-01 | whois.arin.net | LEGACY | |
| 046/8 | RIPE NCC | 2009-09 | whois.ripe.net | ALLOCATED | |
| 047/8 | Administered by ARIN | 1991-01 | whois.arin.net | LEGACY | |
| 048/8 | Prudential Securities Inc. | 1995-05 | LEGACY | ||
| 049/8 | APNIC | 2010-08 | whois.apnic.net | ALLOCATED | |
| 050/8 | ARIN | 2010-02 | whois.arin.net | ALLOCATED | |
| 051/8 | UK Government Department for Work and Pensions | 1994-08 | whois.ripe.net | LEGACY | |
| 052/8 | E.I. duPont de Nemours and Co., Inc. | 1991-12 | LEGACY | ||
| 053/8 | Cap Debis CCS | 1993-10 | LEGACY | ||
| 054/8 | Administered by ARIN | 1992-03 | whois.arin.net | LEGACY | |
| 055/8 | DoD Network Information Center | 1995-04 | LEGACY | ||
| 056/8 | US Postal Service | 1994-06 | LEGACY | ||
| 057/8 | SITA | 1995-05 | LEGACY | ||
| 058/8 | APNIC | 2004-04 | whois.apnic.net | ALLOCATED | |
| 059/8 | APNIC | 2004-04 | whois.apnic.net | ALLOCATED | |
| 060/8 | APNIC | 2003-04 | whois.apnic.net | ALLOCATED | |
| 061/8 | APNIC | 1997-04 | whois.apnic.net | ALLOCATED | |
| 062/8 | RIPE NCC | 1997-04 | whois.ripe.net | ALLOCATED | |
| 063/8 | ARIN | 1997-04 | whois.arin.net | ALLOCATED | |
| 064/8 | ARIN | 1999-07 | whois.arin.net | ALLOCATED | |
| 065/8 | ARIN | 2000-07 | whois.arin.net | ALLOCATED | |
| 066/8 | ARIN | 2000-07 | whois.arin.net | ALLOCATED | |
| 067/8 | ARIN | 2001-05 | whois.arin.net | ALLOCATED | |
| 068/8 | ARIN | 2001-06 | whois.arin.net | ALLOCATED | |
| 069/8 | ARIN | 2002-08 | whois.arin.net | ALLOCATED | |
| 070/8 | ARIN | 2004-01 | whois.arin.net | ALLOCATED | |
| 071/8 | ARIN | 2004-08 | whois.arin.net | ALLOCATED | |
| 072/8 | ARIN | 2004-08 | whois.arin.net | ALLOCATED | |
| 073/8 | ARIN | 2005-03 | whois.arin.net | ALLOCATED | |
| 074/8 | ARIN | 2005-06 | whois.arin.net | ALLOCATED | |
| 075/8 | ARIN | 2005-06 | whois.arin.net | ALLOCATED | |
| 076/8 | ARIN | 2005-06 | whois.arin.net | ALLOCATED | |
| 077/8 | RIPE NCC | 2006-08 | whois.ripe.net | ALLOCATED | |
| 078/8 | RIPE NCC | 2006-08 | whois.ripe.net | ALLOCATED | |
| 079/8 | RIPE NCC | 2006-08 | whois.ripe.net | ALLOCATED | |
| 080/8 | RIPE NCC | 2001-04 | whois.ripe.net | ALLOCATED | |
| 081/8 | RIPE NCC | 2001-04 | whois.ripe.net | ALLOCATED | |
| 082/8 | RIPE NCC | 2002-11 | whois.ripe.net | ALLOCATED | |
| 083/8 | RIPE NCC | 2003-11 | whois.ripe.net | ALLOCATED | |
| 084/8 | RIPE NCC | 2003-11 | whois.ripe.net | ALLOCATED | |
| 085/8 | RIPE NCC | 2004-04 | whois.ripe.net | ALLOCATED | |
| 086/8 | RIPE NCC | 2004-04 | whois.ripe.net | ALLOCATED | |
| 087/8 | RIPE NCC | 2004-04 | whois.ripe.net | ALLOCATED | |
| 088/8 | RIPE NCC | 2004-04 | whois.ripe.net | ALLOCATED | |
| 089/8 | RIPE NCC | 2005-06 | whois.ripe.net | ALLOCATED | |
| 090/8 | RIPE NCC | 2005-06 | whois.ripe.net | ALLOCATED | |
| 091/8 | RIPE NCC | 2005-06 | whois.ripe.net | ALLOCATED | |
| 092/8 | RIPE NCC | 2007-03 | whois.ripe.net | ALLOCATED | |
| 093/8 | RIPE NCC | 2007-03 | whois.ripe.net | ALLOCATED | |
| 094/8 | RIPE NCC | 2007-07 | whois.ripe.net | ALLOCATED | |
| 095/8 | RIPE NCC | 2007-07 | whois.ripe.net | ALLOCATED | |
| 096/8 | ARIN | 2006-10 | whois.arin.net | ALLOCATED | |
| 097/8 | ARIN | 2006-10 | whois.arin.net | ALLOCATED | |
| 098/8 | ARIN | 2006-10 | whois.arin.net | ALLOCATED | |
| 099/8 | ARIN | 2006-10 | whois.arin.net | ALLOCATED | |
| 100/8 | ARIN | 2010-11 | whois.arin.net | ALLOCATED | [5] |
| 101/8 | APNIC | 2010-08 | whois.apnic.net | ALLOCATED | |
| 102/8 | AFRINIC | 2011-02 | whois.afrinic.net | ALLOCATED | |
| 103/8 | APNIC | 2011-02 | whois.apnic.net | ALLOCATED | |
| 104/8 | ARIN | 2011-02 | whois.arin.net | ALLOCATED | |
| 105/8 | AFRINIC | 2010-11 | whois.afrinic.net | ALLOCATED | |
| 106/8 | APNIC | 2011-01 | whois.apnic.net | ALLOCATED | |
| 107/8 | ARIN | 2010-02 | whois.arin.net | ALLOCATED | |
| 108/8 | ARIN | 2008-12 | whois.arin.net | ALLOCATED | |
| 109/8 | RIPE NCC | 2009-01 | whois.ripe.net | ALLOCATED | |
| 110/8 | APNIC | 2008-11 | whois.apnic.net | ALLOCATED | |
| 111/8 | APNIC | 2008-11 | whois.apnic.net | ALLOCATED | |
| 112/8 | APNIC | 2008-05 | whois.apnic.net | ALLOCATED | |
| 113/8 | APNIC | 2008-05 | whois.apnic.net | ALLOCATED | |
| 114/8 | APNIC | 2007-10 | whois.apnic.net | ALLOCATED | |
| 115/8 | APNIC | 2007-10 | whois.apnic.net | ALLOCATED | |
| 116/8 | APNIC | 2007-01 | whois.apnic.net | ALLOCATED | |
| 117/8 | APNIC | 2007-01 | whois.apnic.net | ALLOCATED | |
| 118/8 | APNIC | 2007-01 | whois.apnic.net | ALLOCATED | |
| 119/8 | APNIC | 2007-01 | whois.apnic.net | ALLOCATED | |
| 120/8 | APNIC | 2007-01 | whois.apnic.net | ALLOCATED | |
| 121/8 | APNIC | 2006-01 | whois.apnic.net | ALLOCATED | |
| 122/8 | APNIC | 2006-01 | whois.apnic.net | ALLOCATED | |
| 123/8 | APNIC | 2006-01 | whois.apnic.net | ALLOCATED | |
| 124/8 | APNIC | 2005-01 | whois.apnic.net | ALLOCATED | |
| 125/8 | APNIC | 2005-01 | whois.apnic.net | ALLOCATED | |
| 126/8 | APNIC | 2005-01 | whois.apnic.net | ALLOCATED | |
| 127/8 | IANA – Loopback | 1981-09 | RESERVED | [6] | |
| 128/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 129/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 130/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 131/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 132/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 133/8 | Administered by APNIC | 1997-03 | whois.apnic.net | LEGACY | |
| 134/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 135/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 136/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 137/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 138/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 139/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 140/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 141/8 | Administered by RIPE NCC | 1993-05 | whois.ripe.net | LEGACY | |
| 142/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 143/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 144/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 145/8 | Administered by RIPE NCC | 1993-05 | whois.ripe.net | LEGACY | |
| 146/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 147/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 148/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 149/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 150/8 | Administered by APNIC | 1993-05 | whois.apnic.net | LEGACY | |
| 151/8 | Administered by RIPE NCC | 1993-05 | whois.ripe.net | LEGACY | |
| 152/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 153/8 | Administered by APNIC | 1993-05 | whois.apnic.net | LEGACY | |
| 154/8 | Administered by AFRINIC | 1993-05 | whois.afrinic.net | LEGACY | |
| 155/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 156/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 157/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 158/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 159/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 160/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 161/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 162/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 163/8 | Administered by APNIC | 1993-05 | whois.apnic.net | LEGACY | |
| 164/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 165/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 166/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 167/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 168/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 169/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | [7] |
| 170/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | |
| 171/8 | Administered by APNIC | 1993-05 | whois.apnic.net | LEGACY | |
| 172/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | [8] |
| 173/8 | ARIN | 2008-02 | whois.arin.net | ALLOCATED | |
| 174/8 | ARIN | 2008-02 | whois.arin.net | ALLOCATED | |
| 175/8 | APNIC | 2009-08 | whois.apnic.net | ALLOCATED | |
| 176/8 | RIPE NCC | 2010-05 | whois.ripe.net | ALLOCATED | |
| 177/8 | LACNIC | 2010-06 | whois.lacnic.net | ALLOCATED | |
| 178/8 | RIPE NCC | 2009-01 | whois.ripe.net | ALLOCATED | |
| 179/8 | LACNIC | 2011-02 | whois.lacnic.net | ALLOCATED | |
| 180/8 | APNIC | 2009-04 | whois.apnic.net | ALLOCATED | |
| 181/8 | LACNIC | 2010-06 | whois.lacnic.net | ALLOCATED | |
| 182/8 | APNIC | 2009-08 | whois.apnic.net | ALLOCATED | |
| 183/8 | APNIC | 2009-04 | whois.apnic.net | ALLOCATED | |
| 184/8 | ARIN | 2008-12 | whois.arin.net | ALLOCATED | |
| 185/8 | RIPE NCC | 2011-02 | whois.ripe.net | ALLOCATED | |
| 186/8 | LACNIC | 2007-09 | whois.lacnic.net | ALLOCATED | |
| 187/8 | LACNIC | 2007-09 | whois.lacnic.net | ALLOCATED | |
| 188/8 | Administered by RIPE NCC | 1993-05 | whois.ripe.net | LEGACY | |
| 189/8 | LACNIC | 1995-06 | whois.lacnic.net | ALLOCATED | |
| 190/8 | LACNIC | 1995-06 | whois.lacnic.net | ALLOCATED | |
| 191/8 | Administered by LACNIC | 1993-05 | whois.lacnic.net | LEGACY | |
| 192/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | [9][10] |
| 193/8 | RIPE NCC | 1993-05 | whois.ripe.net | ALLOCATED | |
| 194/8 | RIPE NCC | 1993-05 | whois.ripe.net | ALLOCATED | |
| 195/8 | RIPE NCC | 1993-05 | whois.ripe.net | ALLOCATED | |
| 196/8 | Administered by AFRINIC | 1993-05 | whois.afrinic.net | LEGACY | |
| 197/8 | AFRINIC | 2008-10 | whois.afrinic.net | ALLOCATED | |
| 198/8 | Administered by ARIN | 1993-05 | whois.arin.net | LEGACY | [11] |
| 199/8 | ARIN | 1993-05 | whois.arin.net | ALLOCATED | |
| 200/8 | LACNIC | 2002-11 | whois.lacnic.net | ALLOCATED | |
| 201/8 | LACNIC | 2003-04 | whois.lacnic.net | ALLOCATED | |
| 202/8 | APNIC | 1993-05 | whois.apnic.net | ALLOCATED | |
| 203/8 | APNIC | 1993-05 | whois.apnic.net | ALLOCATED | [12] |
| 204/8 | ARIN | 1994-03 | whois.arin.net | ALLOCATED | |
| 205/8 | ARIN | 1994-03 | whois.arin.net | ALLOCATED | |
| 206/8 | ARIN | 1995-04 | whois.arin.net | ALLOCATED | |
| 207/8 | ARIN | 1995-11 | whois.arin.net | ALLOCATED | |
| 208/8 | ARIN | 1996-04 | whois.arin.net | ALLOCATED | |
| 209/8 | ARIN | 1996-06 | whois.arin.net | ALLOCATED | |
| 210/8 | APNIC | 1996-06 | whois.apnic.net | ALLOCATED | |
| 211/8 | APNIC | 1996-06 | whois.apnic.net | ALLOCATED | |
| 212/8 | RIPE NCC | 1997-10 | whois.ripe.net | ALLOCATED | |
| 213/8 | RIPE NCC | 1993-10 | whois.ripe.net | ALLOCATED | |
| 214/8 | US-DOD | 1998-03 | LEGACY | ||
| 215/8 | US-DOD | 1998-03 | LEGACY | ||
| 216/8 | ARIN | 1998-04 | whois.arin.net | ALLOCATED | |
| 217/8 | RIPE NCC | 2000-06 | whois.ripe.net | ALLOCATED | |
| 218/8 | APNIC | 2000-12 | whois.apnic.net | ALLOCATED | |
| 219/8 | APNIC | 2001-09 | whois.apnic.net | ALLOCATED | |
| 220/8 | APNIC | 2001-12 | whois.apnic.net | ALLOCATED | |
| 221/8 | APNIC | 2002-07 | whois.apnic.net | ALLOCATED | |
| 222/8 | APNIC | 2003-02 | whois.apnic.net | ALLOCATED | |
| 223/8 | APNIC | 2010-04 | whois.apnic.net | ALLOCATED | |
| 224/8 | Multicast | 1981-09 | RESERVED | [13] | |
| 225/8 | Multicast | 1981-09 | RESERVED | [13] | |
| 226/8 | Multicast | 1981-09 | RESERVED | [13] | |
| 227/8 | Multicast | 1981-09 | RESERVED | [13] | |
| 228/8 | Multicast | 1981-09 | RESERVED | [13] | |
| 229/8 | Multicast | 1981-09 | RESERVED | [13] | |
| 230/8 | Multicast | 1981-09 | RESERVED | [13] | |
| 231/8 | Multicast | 1981-09 | RESERVED | [13] | |
| 232/8 | Multicast | 1981-09 | RESERVED | [13] | |
| 233/8 | Multicast | 1981-09 | RESERVED | [13] | |
| 234/8 | Multicast | 1981-09 | RESERVED | [13][14] | |
| 235/8 | Multicast | 1981-09 | RESERVED | [13] | |
| 236/8 | Multicast | 1981-09 | RESERVED | [13] | |
| 237/8 | Multicast | 1981-09 | RESERVED | [13] | |
| 238/8 | Multicast | 1981-09 | RESERVED | [13] | |
| 239/8 | Multicast | 1981-09 | RESERVED | [13][15] | |
| 240/8 | Future use | 1981-09 | RESERVED | [16] | |
| 241/8 | Future use | 1981-09 | RESERVED | [16] | |
| 242/8 | Future use | 1981-09 | RESERVED | [16] | |
| 243/8 | Future use | 1981-09 | RESERVED | [16] | |
| 244/8 | Future use | 1981-09 | RESERVED | [16] | |
| 245/8 | Future use | 1981-09 | RESERVED | [16] | |
| 246/8 | Future use | 1981-09 | RESERVED | [16] | |
| 247/8 | Future use | 1981-09 | RESERVED | [16] | |
| 248/8 | Future use | 1981-09 | RESERVED | [16] | |
| 249/8 | Future use | 1981-09 | RESERVED | [16] | |
| 250/8 | Future use | 1981-09 | RESERVED | [16] | |
| 251/8 | Future use | 1981-09 | RESERVED | [16] | |
| 252/8 | Future use | 1981-09 | RESERVED | [16] | |
| 253/8 | Future use | 1981-09 | RESERVED | [16] | |
| 254/8 | Future use | 1981-09 | RESERVED | [16] | |
| 255/8 | Future use | 1981-09 | RESERVED | [16][17] |
Footnotes
| [1] |
Indicates the status of address blocks as follows: RESERVED: designated by the IETF for specific non-global-unicast purposes as noted. LEGACY: allocated by the central Internet Registry (IR) prior to the Regional Internet Registries (RIRs). This address space is now administered by individual RIRs as noted, including maintenance of WHOIS Directory and reverse DNS records. Assignments from these blocks are distributed globally on a regional basis. ALLOCATED: delegated entirely to specific RIR as indicated. UNALLOCATED: not yet allocated or reserved. |
| [2] |
0.0.0.0/8 reserved for self-identification [RFC1122], section 3.2.1.3. Reserved by protocol. For authoritative registration, see [IANA registry iana-ipv4-special-registry]. |
| [3] |
Reserved for Private-Use Networks [RFC1918]. Complete registration details for 10.0.0.0/8 are found in [IANA registry iana-ipv4-special-registry]. |
| [4] |
This was reserved for Public Data Networks [RFC1356]. See [IANA registry public-data-network-numbers]. It was recovered in February 2008 and was subsequently allocated to APNIC in April 2010. |
| [5] |
100.64.0.0/10 reserved for Shared Address Space [RFC6598]. Complete registration details for 100.64.0.0/10 are found in [IANA registry iana-ipv4-special-registry]. |
| [6] |
127.0.0.0/8 reserved for Loopback [RFC1122], section 3.2.1.3. Reserved by protocol. For authoritative registration, see [IANA registry iana-ipv4-special-registry]. |
| [7] |
169.254.0.0/16 reserved for Link Local [RFC3927]. Reserved by protocol. For authoritative registration, see [IANA registry iana-ipv4-special-registry]. |
| [8] |
172.16.0.0/12 reserved for Private-Use Networks [RFC1918]. Complete registration details are found in [IANA registry iana-ipv4-special-registry]. |
| [9] |
192.0.2.0/24 reserved for TEST-NET-1 [RFC5737]. Complete registration details for 192.0.2.0/24 are found in [IANA registry iana-ipv4-special-registry]. 192.88.99.0/24 reserved for 6to4 Relay Anycast [RFC3068] Complete registration details for 192.88.99.0/24 are found in [IANA registry iana-ipv4-special-registry]. 192.88.99.2/32 reserved for 6a44 Relay Anycast [RFC6751] (possibly collocated with 6to4 Relay at 192.88.99.1/32 - see [RFC3068] section 2.4) 192.168.0.0/16 reserved for Private-Use Networks [RFC1918]. Complete registration details for 192.168.0.0/16 are found in [IANA registry iana-ipv4-special-registry]. |
| [10] |
192.0.0.0/24 reserved for IANA IPv4 Special Purpose Address Registry [RFC5736]. Complete registration details for 192.0.0.0/24 are found in [IANA registry iana-ipv4-special-registry]. |
| [11] |
198.18.0.0/15 reserved for Network Interconnect Device Benchmark Testing [RFC2544]. Complete registration details for 198.18.0.0/15 are found in [IANA registry iana-ipv4-special-registry]. 198.51.100.0/24 reserved for TEST-NET-2 [RFC5737]. Complete registration details for 198.51.100.0/24 are found in [IANA registry iana-ipv4-special-registry]. |
| [12] |
203.0.113.0/24 reserved for TEST-NET-3 [RFC5737]. Complete registration details for 203.0.113.0/24 are found in [IANA registry iana-ipv4-special-registry]. |
| [13] |
Multicast (formerly "Class D") [RFC5771] registered in [IANA registry multicast-addresses] |
| [14] |
Unicast-Prefix-Based IPv4 Multicast Addresses [RFC6034] |
| [15] |
Administratively Scoped IP Multicast [RFC2365] |
| [16] |
Reserved for future use (formerly "Class E") [RFC1112]. Reserved by protocol. For authoritative registration, see [IANA registry iana-ipv4-special-registry]. |
| [17] |
255.255.255.255 is reserved for "limited broadcast" destination address [RFC919] and [RFC922]. Complete registration details for 255.255.255.255/32 are found in [IANA registry iana-ipv4-special-registry]. |
相关资源:
- IANA IPv4 Address Registry – Current Issues – http://www.cidr-report.org/images/iana-v4.html
- Global IPv4 Address Space Allocations (IANA) – http://www.bgp4.as/ipv4-address-space
IANA IPv4 专用地址注册表
IANA IPv4 Special-Purpose Address Registry
Created
2009-08-19
Last Updated
2013-03-03
This registry is also available in plain text.
Registry included below
* IANA IPv4 Special Purpose Address Registry
IANA IPv4 Special Purpose Address Registry
Registration Procedure(s)
IETF Review
Reference
[RFC5736][RFC-bonica-special-purpose-07]
Note
The IETF has reserved the address block of 192.0.0.0/24 for use for
special purposes relating to protocol assignments. This registry
contains the current assignments made by the IETF from this address
block.
Address prefixes listed in the Special Purpose Address Registry are
not guaranteed routability in any particular local or global context.
| Address Block | Name | RFC | Allocation Date |
| 0.0.0.0/8 | “This” Network | [RFC1122], section 3.2.1.3 | 1981-09 |
| 10.0.0.0/8 | Private-Use | [RFC1918] | 1996-02 |
| 100.64.0.0/10 | Shared Address Space | [RFC6598] | 2012-04 |
| 127.0.0.0/8 | Loopback | [RFC1122], section 3.2.1.3 | 1981-09 |
| 169.254.0.0/16 | Link Local | [RFC3927] | 2005-05 |
| 172.16.0.0/12 | Private-Use | [RFC1918] | 1996-02 |
| 192.0.0.0/24[2] | IETF Protocol Assignments | [RFC-bonica-special-purpose-07], section 2.1 | 2010-01 |
| 192.0.0.0/29 | DS-Lite | [RFC6333] | 2011-06 |
| 192.0.2.0/24 | Documentation (TEST-NET-1) | [RFC5737] | 2010-01 |
| 192.88.99.0/24 | 6to4 Relay Anycast | [RFC3068] | 2001-06 |
| 192.168.0.0/16 | Private-Use | [RFC1918] | 1996-02 |
| 198.18.0.0/15 | Benchmarking | [RFC2544] | 1999-03 |
| 198.51.100.0/24 | Documentation (TEST-NET-2) | [RFC5737] | 2010-01 |
| 203.0.113.0/24 | Documentation (TEST-NET-3) | [RFC5737] | 2010-01 |
| 240.0.0.0/4 | Reserved | [RFC1112], section 4 | 1989-08 |
| 255.255.255.255/32 | Limited Broadcast | [RFC919], section 7 | 1984-10 |
Footnotes
[1] Several protocols have been granted exceptions to this rule. For
examples, see [RFC4379] and [RFC5884].
[2] Not useable unless by virtue of a more specific reservation.
用shazam 听歌找歌 听歌识别歌曲
看到一个视频的配乐, 很好听. 听歌词查了好久, 但还是不知道歌曲名字.
最后在wp手机上安装了shazam(音乐雷达), 真心的好使! 查到演唱者和歌名再搜就好找多了!
shazam(音乐雷达) 简介:
突然出现悦己心神的音乐作品。而自己又不知道是什么音乐时，Shazam就能告诉玩家音乐信息，当然玩家需要让Shazam也听10秒钟。是的Shazam就是如此神奇！
P.S. 奉上找的那首音乐
Yuna – Lullabies (adventure club remix)
IP-BGP 以及 BGP Monitoring / BGP 监测
IP-BGP
Introduction
A couple services have been established for mapping IP numbers to BGP prefixes and ASNs:
- Whois (TCP 43)
- DNS (UDP 53)
Three modes are supported origin, peer, and prefix. The data returned is basically the same except that the peer mode also lists the BGP peers for the ASN.
The data to support these services are collected from the following sources:
- AS Names: http://bgp.potaroo.net/as1221/asnames.txt
- BGP Feed: http://routeviews.org/
Whois
The whois interface is used as follows:
Whois/Origin
$ whois -h asn.shadowserver.org origin 17.112.152.32 714 | 17.112.0.0/16 | APPLE-ENGINEERING | US | APPLE.COM | APPLE COMPUTER INC
The output is as follows
ASN | Prefix | AS Name | CN | Domain | ISP
Whois/Peer
Using the peer mode is very similar:
$ whois -h asn.shadowserver.org peer 17.112.152.32 3356 7018 | 714 | 17.112.0.0/16 | APPLE-ENGINEERING | US | APPLE.COM | APPLE COMPUTER INC
The output is as follows
Peer(s) | ASN | Prefix | AS Name | CN | Domain | ISP
A more verbose mode is also available:
$ whois -h asn.shadowserver.org peer 4.5.6.4 verbose 3356 | 4.0.0.0/9 | LEVEL3 | US | DSL-VERIZON.NET | GTE.NET LLC 209 ASN-QWEST Qwest 293 ESNET Energy Sciences Network 701 UUNET MCI Communications Services, Inc. d/b/a Verizon Business 702 AS702 Verizon Business EMEA - Commercial IP service provider in Europe 1239 SPRINTLINK Sprint 1668 AOL-ATDN AOL Transit Data Network 2497 JPNIC-ASBLOCK AP JPNIC 2828 XO-AS15 XO Communications 2914 NTT-COMMUNICATIONS-2 NTT America, Inc. 3257 TISCALI BACKBONE Tiscali Intl Network BV 3303 SWISSCOM Swisscom Solutions Ltd 3333 RIPE-NCC AS RIPE Network Coordination Centre 3356 LEVEL3 Level 3 Communications 3549 GBLX Global Crossing Ltd. 3561 SAVVIS Savvis 4513 Globix Corporation 4637 REACH Reach Network Border AS 5459 LINX AS London Internet Exchange Ltd. 5511 OPENTRANSIT France Telecom 6079 RCN-AS RCN Corporation 6395 BROADWING Broadwing Communications Services, Inc. 6453 GLOBEINTERNET VSNL International 6461 MFNX MFN - Metromedia Fiber Network 7018 ATT-INTERNET4 AT&T WorldNet Services 8075 MICROSOFT-CORP---MSN Microsoft Corp 12956 TELEFONICA Telefonica Backbone Autonomous System
Whois/Prefix
$ whois -h asn.shadowserver.org prefix 8075 64.4.0.0/18 65.54.8.0/22 65.54.48.0/20 65.54.74.0/23 65.54.80.0/23 65.54.83.0/24 65.54.86.0/23 65.54.92.0/23 65.54.94.0/23 65.54.96.0/20 65.54.120.0/21 65.54.128.0/19 <<CHOPPED>>
Whois Batch Mode
The Whois server also supports batch mode where a list of IP addresses can be handled. For example:
begin origin 4.5.4.3 17.112.152.32 208.77.188.166 end
Use netcat, telnet, or perl to send your list to the whois server:
$ netcat asn.shadowserver.org 43 < /tmp/list 3356 | 4.0.0.0/9 | LEVEL3 | US | DSL-VERIZON.NET | GTE.NET LLC 714 | 17.112.0.0/16 | APPLE-ENGINEERING | US | APPLE.COM | APPLE COMPUTER INC 40528 | 208.77.188.0/22 | ICANN-LAX | - | - | -
DNS
The format for a DNS based origin lookup is:
$ dig +short 32.152.112.17.origin.asn.shadowserver.org TXT "714" "|" "17.112.0.0/16" "|" "APPLE-ENGINEERING" "|" "US" "|" "APPLE.COM" "|" "APPLE" "COMPUTER" "INC"
And the format for a ”peer’ lookup is:
$ dig +short 32.152.112.17.peer.asn.shadowserver.org TXT "3356" "7018" "|" "714" "|" "17.112.0.0/16" "|" "APPLE-ENGINEERING" "|" "US" "|" "APPLE.COM" "|" "APPLE" "COMPUTER" "INC"
http://www.shadowserver.org/wiki/pmwiki.php/Services/IP-BGP
Other Res : BGP Monitoring http://www.team-cymru.org/Monitoring/BGP/
