必须是合法有效的IP地址, 可以是IPv4或者是IPv6, 例如127.0.0.1或者2001:DB8:0:0:8:800:200C:417A
基本信息:

城市(city): Shenzhen

省份(region): Guangdong

国家(country): China

运营商(isp): China Mobile

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

用户上报:
暂无关于此IP的讨论, 沙发请点上方按钮
相同子网IP讨论:
暂无关于此IP所属子网相关IP的讨论.
WHOIS信息:
% [whois.apnic.net]
% Whois data copyright terms    http://www.apnic.net/db/dbcopyright.html

% Information related to '120.192.0.0 - 120.255.255.255'

% Abuse contact for '120.192.0.0 - 120.255.255.255' is 'abuse@chinamobile.com'

inetnum:        120.192.0.0 - 120.255.255.255
netname:        CMNET
descr:          China Mobile Communications Corporation
descr:          Mobile Communications Network Operator in China
descr:          Internet Service Provider in China
country:        CN
org:            ORG-CM1-AP
admin-c:        ct74-AP
tech-c:         HL1318-AP
abuse-c:        AC2006-AP
status:         ALLOCATED PORTABLE
remarks:        service provider
remarks:        --------------------------------------------------------
remarks:        To report network abuse, please contact mnt-irt
remarks:        For troubleshooting, please contact tech-c and admin-c
remarks:        Report invalid contact via www.apnic.net/invalidcontact
remarks:        --------------------------------------------------------
mnt-by:         APNIC-HM
mnt-lower:      MAINT-CN-CMCC
mnt-routes:     MAINT-CN-CMCC
mnt-irt:        IRT-CHINAMOBILE-CN
last-modified:  2020-07-15T13:10:01Z
source:         APNIC

irt:            IRT-CHINAMOBILE-CN
address:        China Mobile Communications Corporation
address:        29, Jinrong Ave., Xicheng District, Beijing, 100032
e-mail:         abuse@chinamobile.com
abuse-mailbox:  abuse@chinamobile.com
admin-c:        CT74-AP
tech-c:         CT74-AP
auth:           # Filtered
remarks:        abuse@chinamobile.com was validated on 2026-03-23
mnt-by:         MAINT-CN-CMCC
last-modified:  2026-08-13T06:25:29Z
source:         APNIC

organisation:   ORG-CM1-AP
org-name:       China Mobile Communications Group Co., Ltd
org-type:       LIR
country:        CN
address:        29, Jinrong Ave.
phone:          +86-10-5268-6688
fax-no:         +86-10-5261-6187
e-mail:         hostmaster@chinamobile.com
mnt-ref:        APNIC-HM
mnt-by:         APNIC-HM
last-modified:  2026-07-31T13:46:41Z
source:         APNIC

role:           ABUSE CHINAMOBILECN
country:        ZZ
address:        China Mobile Communications Corporation
address:        29, Jinrong Ave., Xicheng District, Beijing, 100032
phone:          +000000000
e-mail:         abuse@chinamobile.com
admin-c:        CT74-AP
tech-c:         CT74-AP
nic-hdl:        AC2006-AP
remarks:        Generated from irt object IRT-CHINAMOBILE-CN
remarks:        abuse@chinamobile.com was validated on 2026-03-23
abuse-mailbox:  abuse@chinamobile.com
mnt-by:         APNIC-ABUSE
last-modified:  2026-03-23T00:48:02Z
source:         APNIC

role:           chinamobile tech
address:        29, Jinrong Ave.,Xicheng district
address:        Beijing
country:        CN
phone:          +86 5268 6688
fax-no:         +86 5261 6187
e-mail:         hostmaster@chinamobile.com
admin-c:        HL1318-AP
tech-c:         HL1318-AP
nic-hdl:        ct74-AP
notify:         hostmaster@chinamobile.com
mnt-by:         MAINT-cn-cmcc
abuse-mailbox:  abuse@chinamobile.com
last-modified:  2016-11-29T09:37:27Z
source:         APNIC

person:         haijun li
nic-hdl:        HL1318-AP
e-mail:         hostmaster@chinamobile.com
address:        29,Jinrong Ave, Xicheng district,beijing,100032
phone:          +86 1052686688
fax-no:         +86 10 52616187
country:        CN
mnt-by:         MAINT-CN-CMCC
abuse-mailbox:  abuse@chinamobile.com
last-modified:  2016-11-29T09:38:38Z
source:         APNIC

% Information related to '120.224.0.0/12AS9808'

route:          120.224.0.0/12
descr:          China Mobile communications corporation
origin:         AS9808
mnt-by:         MAINT-CN-CMCC
last-modified:  2008-11-05T07:40:19Z
source:         APNIC

% This query was served by the APNIC Whois Service version 1.88.48 (WHOIS-AU4)
DIG信息:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 120.229.126.129
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 41436
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;120.229.126.129.		IN	A

;; AUTHORITY SECTION:
.			30	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2026090701 1800 900 604800 86400

;; Query time: 8 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Sep 08 15:32:47 CST 2026
;; MSG SIZE  rcvd: 108
HOST信息:
Host 129.126.229.120.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 129.126.229.120.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
192.3.48.122 attack
2020-05-08T20:45:46.281065abusebot-6.cloudsearch.cf sshd[31017]: Invalid user aziz from 192.3.48.122 port 54610
2020-05-08T20:45:46.290994abusebot-6.cloudsearch.cf sshd[31017]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.3.48.122
2020-05-08T20:45:46.281065abusebot-6.cloudsearch.cf sshd[31017]: Invalid user aziz from 192.3.48.122 port 54610
2020-05-08T20:45:49.137505abusebot-6.cloudsearch.cf sshd[31017]: Failed password for invalid user aziz from 192.3.48.122 port 54610 ssh2
2020-05-08T20:49:31.803637abusebot-6.cloudsearch.cf sshd[31206]: Invalid user beni from 192.3.48.122 port 53770
2020-05-08T20:49:31.813195abusebot-6.cloudsearch.cf sshd[31206]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.3.48.122
2020-05-08T20:49:31.803637abusebot-6.cloudsearch.cf sshd[31206]: Invalid user beni from 192.3.48.122 port 53770
2020-05-08T20:49:33.881874abusebot-6.cloudsearch.cf sshd[31206]: Failed password fo
...
2020-05-09 06:12:55
222.186.30.57 attack
May  9 08:00:50 localhost sshd[1233192]: Disconnected from 222.186.30.57 port 48485 [preauth]
...
2020-05-09 06:04:55
51.83.98.104 attackspambots
...
2020-05-09 05:51:37
51.161.12.231 attackspam
May  8 23:50:13 debian-2gb-nbg1-2 kernel: \[11233492.276709\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=51.161.12.231 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=238 ID=10978 PROTO=TCP SPT=32767 DPT=8545 WINDOW=1024 RES=0x00 SYN URGP=0
2020-05-09 05:52:36
159.65.147.235 attackspambots
SSH Invalid Login
2020-05-09 06:00:17
140.143.233.133 attack
2020-05-08T16:26:33.9628831495-001 sshd[48851]: Invalid user postgres from 140.143.233.133 port 49840
2020-05-08T16:26:33.9658891495-001 sshd[48851]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.233.133
2020-05-08T16:26:33.9628831495-001 sshd[48851]: Invalid user postgres from 140.143.233.133 port 49840
2020-05-08T16:26:35.1916371495-001 sshd[48851]: Failed password for invalid user postgres from 140.143.233.133 port 49840 ssh2
2020-05-08T16:32:08.4918931495-001 sshd[49078]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.233.133  user=root
2020-05-08T16:32:11.0425551495-001 sshd[49078]: Failed password for root from 140.143.233.133 port 50210 ssh2
...
2020-05-09 06:00:46
152.32.222.196 attack
SSH Invalid Login
2020-05-09 05:49:41
46.38.144.32 attack
May  8 23:33:29 relay postfix/smtpd\[14183\]: warning: unknown\[46.38.144.32\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
May  8 23:33:38 relay postfix/smtpd\[6576\]: warning: unknown\[46.38.144.32\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
May  8 23:34:05 relay postfix/smtpd\[10878\]: warning: unknown\[46.38.144.32\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
May  8 23:34:14 relay postfix/smtpd\[6165\]: warning: unknown\[46.38.144.32\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
May  8 23:34:41 relay postfix/smtpd\[13138\]: warning: unknown\[46.38.144.32\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-05-09 05:35:01
121.229.2.190 attackspambots
May  8 20:48:39 ip-172-31-61-156 sshd[21797]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.229.2.190  user=root
May  8 20:48:41 ip-172-31-61-156 sshd[21797]: Failed password for root from 121.229.2.190 port 34136 ssh2
May  8 20:53:40 ip-172-31-61-156 sshd[21951]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.229.2.190  user=root
May  8 20:53:42 ip-172-31-61-156 sshd[21951]: Failed password for root from 121.229.2.190 port 58526 ssh2
May  8 20:58:37 ip-172-31-61-156 sshd[22112]: Invalid user stupid from 121.229.2.190
...
2020-05-09 05:57:37
51.75.208.179 attackspam
May  8 22:49:05 ns382633 sshd\[12692\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.75.208.179  user=root
May  8 22:49:07 ns382633 sshd\[12692\]: Failed password for root from 51.75.208.179 port 36710 ssh2
May  8 22:50:20 ns382633 sshd\[13213\]: Invalid user administrador from 51.75.208.179 port 42194
May  8 22:50:20 ns382633 sshd\[13213\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.75.208.179
May  8 22:50:22 ns382633 sshd\[13213\]: Failed password for invalid user administrador from 51.75.208.179 port 42194 ssh2
2020-05-09 05:36:45
185.36.81.150 attackspam
firewall-block, port(s): 8088/tcp
2020-05-09 05:37:22
183.82.121.34 attack
May  8 21:40:55 ip-172-31-62-245 sshd\[29650\]: Failed password for root from 183.82.121.34 port 52089 ssh2\
May  8 21:44:58 ip-172-31-62-245 sshd\[29667\]: Invalid user nr from 183.82.121.34\
May  8 21:45:00 ip-172-31-62-245 sshd\[29667\]: Failed password for invalid user nr from 183.82.121.34 port 54952 ssh2\
May  8 21:48:58 ip-172-31-62-245 sshd\[29691\]: Invalid user test from 183.82.121.34\
May  8 21:49:01 ip-172-31-62-245 sshd\[29691\]: Failed password for invalid user test from 183.82.121.34 port 57813 ssh2\
2020-05-09 05:52:21
144.21.103.14 attackbots
SSH invalid-user multiple login try
2020-05-09 05:50:46
54.36.150.123 attack
[Sat May 09 03:50:08.046003 2020] [:error] [pid 6963:tid 139913183377152] [client 54.36.150.123:58972] [client 54.36.150.123] ModSecurity: Access denied with code 403 (phase 2). Matched phrase "AhrefsBot" at REQUEST_HEADERS:User-Agent. [file "/etc/modsecurity/owasp-modsecurity-crs-3.2.0/rules/REQUEST-913-SCANNER-DETECTION.conf"] [line "183"] [id "913102"] [msg "Found User-Agent associated with web crawler/bot"] [data "Matched Data: AhrefsBot found within REQUEST_HEADERS:User-Agent: mozilla/5.0 (compatible; ahrefsbot/6.1; +http://ahrefs.com/robot/)"] [severity "CRITICAL"] [ver "OWASP_CRS/3.2.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-reputation-crawler"] [tag "OWASP_CRS"] [tag "OWASP_CRS/AUTOMATION/CRAWLER"] [tag "WASCTC/WASC-21"] [tag "OWASP_TOP_10/A7"] [tag "PCI/6.5.10"] [tag "paranoia-level/2"] [hostname "karangploso.jatim.bmkg.go.id"] [uri "/index.php/pelayanan-jasa/868-klimatologi/agroklimatologi/kalender-tanam-katam-terpadu/kalender-ta
...
2020-05-09 05:48:40
218.75.210.46 attackbotsspam
web-1 [ssh] SSH Attack
2020-05-09 05:41:47

最近上报的IP列表

120.230.23.146 120.228.201.150 112.51.216.194 112.37.215.97
112.226.155.252 112.0.152.195 111.60.176.117 101.26.28.205
52.180.152.102 200.219.11.144 39.148.116.158 36.36.19.78
223.91.114.123 223.89.227.241 223.73.20.44 20.84.64.100
120.242.140.212 120.230.23.8 120.221.12.43 112.7.86.142