Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: Zhengzhou

Region: Henan

Country: China

Internet Service Provider: China Mobile

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
% [whois.apnic.net]
% Whois data copyright terms    http://www.apnic.net/db/dbcopyright.html

% Information related to '39.128.0.0 - 39.191.255.255'

% Abuse contact for '39.128.0.0 - 39.191.255.255' is 'abuse@chinamobile.com'

inetnum:        39.128.0.0 - 39.191.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-10-20T00:58:36Z
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

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

;; QUESTION SECTION:
;39.149.23.99.			IN	A

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

;; Query time: 6 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon May 25 03:00:15 CST 2026
;; MSG SIZE  rcvd: 105
Host info
Host 99.23.149.39.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 99.23.149.39.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
95.167.39.12 attackspambots
Feb  6 02:15:02 MK-Soft-Root2 sshd[5792]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=95.167.39.12 
Feb  6 02:15:04 MK-Soft-Root2 sshd[5792]: Failed password for invalid user ndw from 95.167.39.12 port 58842 ssh2
...
2020-02-06 10:05:52
65.182.2.241 attackspambots
Unauthorized connection attempt detected from IP address 65.182.2.241 to port 2220 [J]
2020-02-06 10:01:43
115.75.58.163 attack
1580951653 - 02/06/2020 02:14:13 Host: 115.75.58.163/115.75.58.163 Port: 445 TCP Blocked
2020-02-06 10:40:12
64.225.24.239 attack
Feb  5 16:02:02 hpm sshd\[6820\]: Invalid user ztj from 64.225.24.239
Feb  5 16:02:02 hpm sshd\[6820\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=64.225.24.239
Feb  5 16:02:03 hpm sshd\[6820\]: Failed password for invalid user ztj from 64.225.24.239 port 57970 ssh2
Feb  5 16:05:03 hpm sshd\[7229\]: Invalid user ada from 64.225.24.239
Feb  5 16:05:03 hpm sshd\[7229\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=64.225.24.239
2020-02-06 10:10:29
69.229.6.11 attackspambots
Unauthorized connection attempt detected from IP address 69.229.6.11 to port 2220 [J]
2020-02-06 10:37:15
36.68.169.237 attack
Feb  6 01:14:39 localhost sshd\[28965\]: Invalid user admin from 36.68.169.237 port 42145
Feb  6 01:14:39 localhost sshd\[28965\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.68.169.237
Feb  6 01:14:41 localhost sshd\[28965\]: Failed password for invalid user admin from 36.68.169.237 port 42145 ssh2
...
2020-02-06 10:24:10
61.223.168.65 attackspambots
Feb  6 02:14:17 h2177944 kernel: \[4149743.836994\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=61.223.168.65 DST=85.214.117.9 LEN=52 TOS=0x00 PREC=0x00 TTL=113 ID=49264 DF PROTO=TCP SPT=10096 DPT=3389 WINDOW=64240 RES=0x00 SYN URGP=0 
Feb  6 02:14:17 h2177944 kernel: \[4149743.837008\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=61.223.168.65 DST=85.214.117.9 LEN=52 TOS=0x00 PREC=0x00 TTL=113 ID=49264 DF PROTO=TCP SPT=10096 DPT=3389 WINDOW=64240 RES=0x00 SYN URGP=0 
Feb  6 02:14:18 h2177944 kernel: \[4149744.836815\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=61.223.168.65 DST=85.214.117.9 LEN=52 TOS=0x00 PREC=0x00 TTL=113 ID=49265 DF PROTO=TCP SPT=10096 DPT=3389 WINDOW=64240 RES=0x00 SYN URGP=0 
Feb  6 02:14:18 h2177944 kernel: \[4149744.836828\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=61.223.168.65 DST=85.214.117.9 LEN=52 TOS=0x00 PREC=0x00 TTL=113 ID=49265 DF PROTO=TCP SPT=10096 DPT=3389 WINDOW=64240 RES=0x00 SYN URGP=0 
Feb  6 02:14:20 h2177944 kernel: \[4149746.835996\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=61.223.168.65
2020-02-06 10:34:06
189.112.109.185 attackbots
Feb  5 21:22:06 plusreed sshd[22507]: Invalid user nat from 189.112.109.185
...
2020-02-06 10:30:20
58.71.87.123 attack
20/2/5@20:14:57: FAIL: Alarm-Network address from=58.71.87.123
20/2/5@20:14:58: FAIL: Alarm-Network address from=58.71.87.123
...
2020-02-06 10:14:08
37.9.113.46 attackspam
[Thu Feb 06 08:14:37.103674 2020] [:error] [pid 1635:tid 140262657820416] [client 37.9.113.46:36014] [client 37.9.113.46] ModSecurity: Access denied with code 403 (phase 2). Pattern match "^[\\\\d.:]+$" at REQUEST_HEADERS:Host. [file "/etc/modsecurity/owasp-modsecurity-crs-3.2.0/rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf"] [line "696"] [id "920350"] [msg "Host header is a numeric IP address"] [data "103.27.207.197"] [severity "WARNING"] [ver "OWASP_CRS/3.2.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "OWASP_CRS"] [tag "OWASP_CRS/PROTOCOL_VIOLATION/IP_HOST"] [tag "WASCTC/WASC-21"] [tag "OWASP_TOP_10/A7"] [tag "PCI/6.5.10"] [hostname "103.27.207.197"] [uri "/"] [unique_id "XjtofXFl@3nQo4OTo5IZuQAAAUs"]
...
2020-02-06 10:26:19
103.138.109.76 attackbotsspam
" "
2020-02-06 10:24:41
81.208.35.103 attackspambots
$f2bV_matches
2020-02-06 10:38:37
51.38.225.124 attack
2020-02-05T18:14:29.302767-07:00 suse-nuc sshd[15993]: Invalid user ba from 51.38.225.124 port 55460
...
2020-02-06 10:29:41
31.211.65.102 attack
Feb  6 03:18:32 legacy sshd[10903]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=31.211.65.102
Feb  6 03:18:34 legacy sshd[10903]: Failed password for invalid user nct from 31.211.65.102 port 55242 ssh2
Feb  6 03:22:13 legacy sshd[11078]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=31.211.65.102
...
2020-02-06 10:35:43
45.148.10.93 attackbotsspam
Feb  5 15:58:28 hanapaa sshd\[24063\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.148.10.93  user=root
Feb  5 15:58:30 hanapaa sshd\[24063\]: Failed password for root from 45.148.10.93 port 58394 ssh2
Feb  5 15:59:24 hanapaa sshd\[24130\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.148.10.93  user=root
Feb  5 15:59:26 hanapaa sshd\[24130\]: Failed password for root from 45.148.10.93 port 52268 ssh2
Feb  5 16:00:23 hanapaa sshd\[24202\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.148.10.93  user=root
2020-02-06 10:29:56

Recently Reported IPs

58.17.112.167 124.89.58.98 123.10.133.142 120.230.245.249
120.229.212.245 120.229.113.163 120.219.220.14 117.9.19.134
117.147.72.147 112.49.113.143 101.26.28.107 185.93.89.130
18.188.157.133 199.45.155.105 18.223.33.185 52.87.177.107
3.138.190.115 172.86.113.253 167.88.164.107 111.162.138.31