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

城市(city): Huzhou

省份(region): Zhejiang

国家(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 '117.144.0.0 - 117.159.255.255'

% Abuse contact for '117.144.0.0 - 117.159.255.255' is 'abuse@chinamobile.com'

inetnum:        117.144.0.0 - 117.159.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:  2025-12-05T04:13:54Z
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-03-23T00:47:53Z
source:         APNIC

organisation:   ORG-CM1-AP
org-name:       China Mobile
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:  2023-09-05T02:14:48Z
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 '117.148.0.0/15AS9808'

route:          117.148.0.0/15
descr:          China Mobile communications corporation
origin:         AS9808
mnt-by:         MAINT-CN-CMCC
last-modified:  2008-09-04T07:55:15Z
source:         APNIC

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

;; QUESTION SECTION:
;117.148.123.253.		IN	A

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

;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed May 06 17:10:16 CST 2026
;; MSG SIZE  rcvd: 108
HOST信息:
Host 253.123.148.117.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 253.123.148.117.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
117.78.9.16 attackbotsspam
Port scan on 3 port(s): 2376 2377 4243
2019-11-24 21:46:37
148.70.218.43 attackbotsspam
Nov 24 08:55:55 herz-der-gamer sshd[1456]: Invalid user brasis from 148.70.218.43 port 34672
Nov 24 08:55:55 herz-der-gamer sshd[1456]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.218.43
Nov 24 08:55:55 herz-der-gamer sshd[1456]: Invalid user brasis from 148.70.218.43 port 34672
Nov 24 08:55:57 herz-der-gamer sshd[1456]: Failed password for invalid user brasis from 148.70.218.43 port 34672 ssh2
...
2019-11-24 21:52:14
173.214.176.75 attackbotsspam
Automatic report - XMLRPC Attack
2019-11-24 21:27:01
107.175.80.223 attackspambots
(From eric@talkwithcustomer.com) Hey,

You have a website whatcomchiropractic.com, right?

Of course you do. I am looking at your website now.

It gets traffic every day – that you’re probably spending $2 / $4 / $10 or more a click to get.  Not including all of the work you put into creating social media, videos, blog posts, emails, and so on.

So you’re investing seriously in getting people to that site.

But how’s it working?  Great? Okay?  Not so much?

If that answer could be better, then it’s likely you’re putting a lot of time, effort, and money into an approach that’s not paying off like it should.

Now… imagine doubling your lead conversion in just minutes… In fact, I’ll go even better.
 
You could actually get up to 100X more conversions!

I’m not making this up.  As Chris Smith, best-selling author of The Conversion Code says: Speed is essential - there is a 100x decrease in Leads when a Lead is contacted within 14 minutes vs being contacted within 5 minutes.

He’s backed up by a
2019-11-24 21:29:42
172.217.18.163 attackbotsspam
TCP Port Scanning
2019-11-24 21:53:40
85.132.100.24 attackspambots
Nov 24 02:40:50 ny01 sshd[26637]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=85.132.100.24
Nov 24 02:40:51 ny01 sshd[26637]: Failed password for invalid user maderna from 85.132.100.24 port 41734 ssh2
Nov 24 02:45:15 ny01 sshd[27051]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=85.132.100.24
2019-11-24 21:17:14
134.209.90.220 attackspam
Nov 24 03:18:06 vps46666688 sshd[28374]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.90.220
Nov 24 03:18:09 vps46666688 sshd[28374]: Failed password for invalid user rules from 134.209.90.220 port 34878 ssh2
...
2019-11-24 21:44:36
46.229.168.141 attackspam
Malicious Traffic/Form Submission
2019-11-24 21:49:10
167.114.145.139 attack
Brute force attempt
2019-11-24 21:27:53
2.202.9.75 attackbotsspam
Automatic report - SSH Brute-Force Attack
2019-11-24 21:48:46
46.185.69.208 attackbotsspam
fell into ViewStateTrap:wien2018
2019-11-24 21:38:49
94.70.246.212 attackspambots
24.11.2019 07:18:55 - RDP Login Fail Detected by 
https://www.elinox.de/RDP-Wächter
2019-11-24 21:16:45
92.63.194.26 attack
Nov 24 13:56:39 vpn01 sshd[16077]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.63.194.26
Nov 24 13:56:41 vpn01 sshd[16077]: Failed password for invalid user admin from 92.63.194.26 port 46698 ssh2
...
2019-11-24 21:40:57
45.82.153.135 attackspambots
Nov 24 14:31:33 relay postfix/smtpd\[22894\]: warning: unknown\[45.82.153.135\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 24 14:31:56 relay postfix/smtpd\[18484\]: warning: unknown\[45.82.153.135\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 24 14:33:25 relay postfix/smtpd\[23519\]: warning: unknown\[45.82.153.135\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 24 14:33:42 relay postfix/smtpd\[22894\]: warning: unknown\[45.82.153.135\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 24 14:47:01 relay postfix/smtpd\[23519\]: warning: unknown\[45.82.153.135\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2019-11-24 21:52:36
62.210.149.143 attack
2019-11-24T10:03:33.783068host3.slimhost.com.ua sshd[4161292]: Invalid user bot1 from 62.210.149.143 port 40767
2019-11-24T10:03:33.794555host3.slimhost.com.ua sshd[4161292]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=62-210-149-143.rev.poneytelecom.eu
2019-11-24T10:03:33.783068host3.slimhost.com.ua sshd[4161292]: Invalid user bot1 from 62.210.149.143 port 40767
2019-11-24T10:03:35.823792host3.slimhost.com.ua sshd[4161292]: Failed password for invalid user bot1 from 62.210.149.143 port 40767 ssh2
2019-11-24T10:03:36.763896host3.slimhost.com.ua sshd[4161366]: Invalid user bot2 from 62.210.149.143 port 42588
2019-11-24T10:03:36.768201host3.slimhost.com.ua sshd[4161366]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=62-210-149-143.rev.poneytelecom.eu
2019-11-24T10:03:36.763896host3.slimhost.com.ua sshd[4161366]: Invalid user bot2 from 62.210.149.143 port 42588
2019-11-24T10:03:38.543439host3.slimhost.co
...
2019-11-24 21:40:18

最近上报的IP列表

160.119.76.110 85.8.182.169 2606:4700:10::6816:3908 14.207.194.33
43.98.160.223 8.219.254.41 152.183.115.132 35.205.114.199
115.197.71.232 2408:843f:3a10:4134:182b:9272:98a6:60ad 45.3.39.214 137.184.132.70
134.199.175.53 216.48.98.252 14.0.39.15 2606:4700:10::6814:7356
81.30.98.72 153.194.24.38 248.222.212.207 133.28.159.142