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: unknown

Region: unknown

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.182.55.90
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 21895
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;39.182.55.90.			IN	A

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

;; Query time: 8 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jul 03 15:52:18 CST 2026
;; MSG SIZE  rcvd: 105
Host info
Host 90.55.182.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 90.55.182.39.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
117.254.186.98 attackspambots
Jan  4 07:19:54 tuxlinux sshd[27310]: Invalid user bzq from 117.254.186.98 port 51740
Jan  4 07:19:54 tuxlinux sshd[27310]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.254.186.98 
Jan  4 07:19:54 tuxlinux sshd[27310]: Invalid user bzq from 117.254.186.98 port 51740
Jan  4 07:19:54 tuxlinux sshd[27310]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.254.186.98 
Jan  4 07:19:54 tuxlinux sshd[27310]: Invalid user bzq from 117.254.186.98 port 51740
Jan  4 07:19:54 tuxlinux sshd[27310]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.254.186.98 
Jan  4 07:19:55 tuxlinux sshd[27310]: Failed password for invalid user bzq from 117.254.186.98 port 51740 ssh2
...
2020-01-04 15:13:32
89.251.66.236 attackbotsspam
DATE:2020-01-04 05:54:05, IP:89.251.66.236, PORT:1433 MSSQL brute force auth on honeypot server (honey-neo-dc)
2020-01-04 14:59:10
195.216.207.98 attack
Jan  4 07:53:30 nextcloud sshd\[12859\]: Invalid user zs from 195.216.207.98
Jan  4 07:53:30 nextcloud sshd\[12859\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.216.207.98
Jan  4 07:53:32 nextcloud sshd\[12859\]: Failed password for invalid user zs from 195.216.207.98 port 53640 ssh2
...
2020-01-04 15:03:24
61.177.172.128 attackspambots
Jan  4 08:06:02 dedicated sshd[10030]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.177.172.128  user=root
Jan  4 08:06:04 dedicated sshd[10030]: Failed password for root from 61.177.172.128 port 31199 ssh2
2020-01-04 15:09:19
3.136.6.36 attackbots
Jan  4 04:53:35 unicornsoft sshd\[9318\]: Invalid user hduser from 3.136.6.36
Jan  4 04:53:35 unicornsoft sshd\[9318\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=3.136.6.36
Jan  4 04:53:37 unicornsoft sshd\[9318\]: Failed password for invalid user hduser from 3.136.6.36 port 57422 ssh2
2020-01-04 15:14:54
45.136.108.126 attackbots
ET CINS Active Threat Intelligence Poor Reputation IP group 34 - port: 7773 proto: TCP cat: Misc Attack
2020-01-04 15:29:52
202.164.48.202 attackbotsspam
Invalid user handall from 202.164.48.202 port 47393
2020-01-04 15:31:54
31.173.85.131 attack
fell into ViewStateTrap:wien2018
2020-01-04 15:03:06
51.89.19.147 attackbots
Automatic report - SSH Brute-Force Attack
2020-01-04 15:23:24
67.247.123.8 attackbots
2020-01-04T07:55:50.797824hz01.yumiweb.com sshd\[30563\]: Invalid user gmod from 67.247.123.8 port 39586
2020-01-04T07:57:30.274079hz01.yumiweb.com sshd\[30565\]: Invalid user appuser from 67.247.123.8 port 42888
2020-01-04T07:59:16.191004hz01.yumiweb.com sshd\[30570\]: Invalid user appuser from 67.247.123.8 port 46218
...
2020-01-04 15:32:40
128.199.253.133 attackspambots
Jan  3 20:55:48 hanapaa sshd\[8080\]: Invalid user mediafire from 128.199.253.133
Jan  3 20:55:48 hanapaa sshd\[8080\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.253.133
Jan  3 20:55:50 hanapaa sshd\[8080\]: Failed password for invalid user mediafire from 128.199.253.133 port 35883 ssh2
Jan  3 20:59:01 hanapaa sshd\[8351\]: Invalid user sshvpn from 128.199.253.133
Jan  3 20:59:01 hanapaa sshd\[8351\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.253.133
2020-01-04 15:29:22
124.61.206.234 attack
Jan  4 05:53:46 v22018076622670303 sshd\[15274\]: Invalid user rator from 124.61.206.234 port 36026
Jan  4 05:53:46 v22018076622670303 sshd\[15274\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.61.206.234
Jan  4 05:53:48 v22018076622670303 sshd\[15274\]: Failed password for invalid user rator from 124.61.206.234 port 36026 ssh2
...
2020-01-04 15:07:05
218.92.0.158 attackbotsspam
(sshd) Failed SSH login from 218.92.0.158 (CN/China/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Jan  4 08:06:39 blur sshd[24768]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.158  user=root
Jan  4 08:06:41 blur sshd[24768]: Failed password for root from 218.92.0.158 port 50590 ssh2
Jan  4 08:06:45 blur sshd[24768]: Failed password for root from 218.92.0.158 port 50590 ssh2
Jan  4 08:06:48 blur sshd[24768]: Failed password for root from 218.92.0.158 port 50590 ssh2
Jan  4 08:06:51 blur sshd[24768]: Failed password for root from 218.92.0.158 port 50590 ssh2
2020-01-04 15:10:39
185.175.93.105 attackbots
ET DROP Dshield Block Listed Source group 1 - port: 43389 proto: TCP cat: Misc Attack
2020-01-04 14:53:34
218.92.0.211 attackspam
Jan  4 06:38:02 eventyay sshd[3289]: Failed password for root from 218.92.0.211 port 27833 ssh2
Jan  4 06:42:22 eventyay sshd[3327]: Failed password for root from 218.92.0.211 port 43352 ssh2
...
2020-01-04 15:04:07

Recently Reported IPs

117.179.152.195 36.4.210.120 124.134.107.102 36.142.152.210
119.166.97.208 1.80.139.87 120.227.73.250 34.78.55.102
118.120.233.40 120.217.218.226 120.227.205.7 113.124.221.89
111.60.203.25 110.167.44.46 2606:4700:10::6816:2124 113.219.33.172
171.106.44.74 123.11.115.154 36.148.88.12 119.39.229.60