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

Region: Sichuan

Country: China

Internet Service Provider: unknown

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:
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#


NetRange:       129.28.0.0 - 129.28.255.255
CIDR:           129.28.0.0/16
NetName:        APNIC
NetHandle:      NET-129-28-0-0-1
Parent:         NET129 (NET-129-0-0-0-0)
NetType:        Early Registrations, Transferred to APNIC
OriginAS:       
Organization:   Asia Pacific Network Information Centre (APNIC)
RegDate:        2017-08-29
Updated:        2017-08-29
Ref:            https://rdap.arin.net/registry/ip/129.28.0.0

ResourceLink:  https://apps.db.ripe.net/db-web-ui/query
ResourceLink:  whois://whois.apnic.net


OrgName:        Asia Pacific Network Information Centre
OrgId:          APNIC
Address:        PO Box 3646
City:           South Brisbane
StateProv:      QLD
PostalCode:     4101
Country:        AU
RegDate:        
Updated:        2012-01-24
Ref:            https://rdap.arin.net/registry/entity/APNIC

ReferralServer:  whois://whois.apnic.net
ResourceLink:  http://wq.apnic.net/whois-search/static/search.html

OrgAbuseHandle: AWC12-ARIN
OrgAbuseName:   APNIC Whois Contact
OrgAbusePhone:  +61 7 3858 3188 
OrgAbuseEmail:  search-apnic-not-arin@apnic.net
OrgAbuseRef:    https://rdap.arin.net/registry/entity/AWC12-ARIN

OrgTechHandle: AWC12-ARIN
OrgTechName:   APNIC Whois Contact
OrgTechPhone:  +61 7 3858 3188 
OrgTechEmail:  search-apnic-not-arin@apnic.net
OrgTechRef:    https://rdap.arin.net/registry/entity/AWC12-ARIN


#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#



Found a referral to whois.apnic.net.

% [whois.apnic.net]
% Whois data copyright terms    http://www.apnic.net/db/dbcopyright.html

% Information related to '129.28.0.0 - 129.28.255.255'

% Abuse contact for '129.28.0.0 - 129.28.255.255' is 'abuse@tencent.com'

inetnum:        129.28.0.0 - 129.28.255.255
netname:        TENCENT-CN
descr:          Tencent Cloud Computing (Beijing) Co., Ltd
descr:          Floor 6, Yinke Building, 38 Haidian St, Haidian District
country:        CN
org:            ORG-TCCC1-AP
admin-c:        TCA15-AP
tech-c:         TCA15-AP
abuse-c:        AT992-AP
status:         ALLOCATED PORTABLE
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-TENCENT-CN
mnt-routes:     MAINT-TENCENT-CN
mnt-irt:        IRT-TENCENT-CN
last-modified:  2020-07-22T13:11:01Z
source:         APNIC

irt:            IRT-TENCENT-CN
address:        Floor 6, Yinke Building, 38 Haidian St, Haidian District, Beijing Beijing 100080
e-mail:         tencent_noc@tencent.com
abuse-mailbox:  abuse@tencent.com
admin-c:        TCA15-AP
tech-c:         TCA15-AP
auth:           # Filtered
remarks:        abuse@tencent.com was validated on 2026-05-15
remarks:        tencent_noc@tencent.com was validated on 2026-06-05
mnt-by:         MAINT-COMSENZ1-CN
last-modified:  2026-06-05T07:58:46Z
source:         APNIC

organisation:   ORG-TCCC1-AP
org-name:       Tencent Cloud Computing (Beijing) Co., Ltd
org-type:       LIR
country:        CN
address:        309 West Zone, 3F. 49 Zhichun Road. Haidian District.
phone:          +86-10-62671299
fax-no:         +86-10-82602088-41299
e-mail:         tencent_idc@tencent.com
mnt-ref:        APNIC-HM
mnt-by:         APNIC-HM
last-modified:  2023-09-05T02:16:21Z
source:         APNIC

role:           ABUSE TENCENTCN
country:        ZZ
address:        Floor 6, Yinke Building, 38 Haidian St, Haidian District, Beijing Beijing 100080
phone:          +000000000
e-mail:         tencent_noc@tencent.com
admin-c:        TCA15-AP
tech-c:         TCA15-AP
nic-hdl:        AT992-AP
remarks:        Generated from irt object IRT-TENCENT-CN
remarks:        abuse@tencent.com was validated on 2026-05-15
remarks:        tencent_noc@tencent.com was validated on 2026-06-05
abuse-mailbox:  abuse@tencent.com
mnt-by:         APNIC-ABUSE
last-modified:  2026-06-05T07:59:01Z
source:         APNIC

role:           Tencent Cloud administrator
address:        Floor 6, Yinke Building, 38 Haidian St, Haidian District, Beijing Beijing 100080
country:        CN
phone:          +86-10-62671299
e-mail:         tencent_idc@tencent.com
admin-c:        TCA15-AP
tech-c:         TCA15-AP
nic-hdl:        TCA15-AP
mnt-by:         MAINT-AP-DIALPAD
fax-no:         +86-10-62671299
last-modified:  2017-04-04T10:34:03Z
source:         APNIC

% Information related to '129.28.0.0/16AS45090'

route:          129.28.0.0/16
origin:         AS45090
descr:          Tencent Cloud Computing (Beijing) Co., Ltd
                309 West Zone, 3F. 49 Zhichun Road. Haidian District.
mnt-by:         MAINT-TENCENT-CN
last-modified:  2018-01-17T08:22:13Z
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 <<>> 129.28.52.162
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 34381
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;129.28.52.162.			IN	A

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

;; Query time: 7 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jul 15 14:01:17 CST 2026
;; MSG SIZE  rcvd: 106
Host info
Host 162.52.28.129.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 162.52.28.129.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
49.88.112.76 attackbots
Nov 22 09:32:59 sauna sshd[164406]: Failed password for root from 49.88.112.76 port 63302 ssh2
...
2019-11-22 15:49:07
207.180.254.181 attackbotsspam
Nov 19 14:09:18 vpxxxxxxx22308 sshd[15393]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=207.180.254.181  user=r.r
Nov 19 14:09:20 vpxxxxxxx22308 sshd[15393]: Failed password for r.r from 207.180.254.181 port 60006 ssh2
Nov 19 14:09:34 vpxxxxxxx22308 sshd[15412]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=207.180.254.181  user=r.r
Nov 19 14:09:37 vpxxxxxxx22308 sshd[15412]: Failed password for r.r from 207.180.254.181 port 60804 ssh2
Nov 19 14:09:50 vpxxxxxxx22308 sshd[15434]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=207.180.254.181  user=r.r
Nov 19 14:09:52 vpxxxxxxx22308 sshd[15434]: Failed password for r.r from 207.180.254.181 port 33372 ssh2
Nov 19 14:10:09 vpxxxxxxx22308 sshd[15454]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=207.180.254.181  user=r.r

........
-----------------------------------------------
https://www.blockli
2019-11-22 16:21:44
1.214.241.18 attackspam
Nov 22 07:31:03 web8 sshd\[4934\]: Invalid user !! from 1.214.241.18
Nov 22 07:31:03 web8 sshd\[4934\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.214.241.18
Nov 22 07:31:05 web8 sshd\[4934\]: Failed password for invalid user !! from 1.214.241.18 port 36296 ssh2
Nov 22 07:35:38 web8 sshd\[7057\]: Invalid user hamlet from 1.214.241.18
Nov 22 07:35:38 web8 sshd\[7057\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.214.241.18
2019-11-22 15:44:23
125.227.130.5 attackspam
Nov 22 07:27:45 vps647732 sshd[29818]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.227.130.5
Nov 22 07:27:46 vps647732 sshd[29818]: Failed password for invalid user dovecot from 125.227.130.5 port 55400 ssh2
...
2019-11-22 16:09:07
222.186.173.215 attackbotsspam
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.215  user=root
Failed password for root from 222.186.173.215 port 33832 ssh2
Failed password for root from 222.186.173.215 port 33832 ssh2
Failed password for root from 222.186.173.215 port 33832 ssh2
Failed password for root from 222.186.173.215 port 33832 ssh2
2019-11-22 15:41:11
159.65.182.7 attackspambots
Nov 22 10:03:28 server sshd\[28823\]: Invalid user sunsby from 159.65.182.7 port 40256
Nov 22 10:03:28 server sshd\[28823\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.182.7
Nov 22 10:03:30 server sshd\[28823\]: Failed password for invalid user sunsby from 159.65.182.7 port 40256 ssh2
Nov 22 10:06:33 server sshd\[13608\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.182.7  user=nobody
Nov 22 10:06:35 server sshd\[13608\]: Failed password for nobody from 159.65.182.7 port 46602 ssh2
2019-11-22 16:22:15
172.246.204.146 attackspam
Fail2Ban Ban Triggered
2019-11-22 16:10:49
192.144.148.163 attackbots
Nov 22 08:28:21 MK-Soft-VM5 sshd[31201]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.144.148.163 
Nov 22 08:28:23 MK-Soft-VM5 sshd[31201]: Failed password for invalid user karie from 192.144.148.163 port 56206 ssh2
...
2019-11-22 15:58:10
95.110.191.109 attackspam
RDP Bruteforce
2019-11-22 16:09:49
51.75.23.62 attackspam
Nov 21 21:36:38 wbs sshd\[9131\]: Invalid user schamp from 51.75.23.62
Nov 21 21:36:38 wbs sshd\[9131\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.ip-51-75-23.eu
Nov 21 21:36:40 wbs sshd\[9131\]: Failed password for invalid user schamp from 51.75.23.62 port 58390 ssh2
Nov 21 21:40:08 wbs sshd\[9526\]: Invalid user test123456 from 51.75.23.62
Nov 21 21:40:08 wbs sshd\[9526\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.ip-51-75-23.eu
2019-11-22 15:57:41
45.162.99.142 attackbots
Automatic report - Port Scan Attack
2019-11-22 16:17:12
51.83.77.224 attack
Nov 22 08:18:15 mout sshd[1771]: Invalid user grebil from 51.83.77.224 port 49284
2019-11-22 16:00:33
54.38.241.171 attack
Nov 22 08:21:29 markkoudstaal sshd[18416]: Failed password for root from 54.38.241.171 port 38594 ssh2
Nov 22 08:25:02 markkoudstaal sshd[18713]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.38.241.171
Nov 22 08:25:03 markkoudstaal sshd[18713]: Failed password for invalid user lsk from 54.38.241.171 port 46576 ssh2
2019-11-22 16:05:43
83.103.98.211 attackbots
SSH auth scanning - multiple failed logins
2019-11-22 15:44:05
92.246.76.193 attack
92.246.76.193 was recorded 13 times by 3 hosts attempting to connect to the following ports: 39274,39664,39606,39988,39722,39681,39253,39697,39221,39583,39010,39071,39839. Incident counter (4h, 24h, all-time): 13, 80, 240
2019-11-22 16:04:23

Recently Reported IPs

192.161.49.2 62.210.142.175 103.40.13.52 110.43.37.145
2606:4700:10::6814:4666 2606:4700:10::6816:2174 14.212.127.100 188.166.96.167
188.166.83.232 2606:4700:10::6814:6602 34.171.81.35 102.129.182.171
69.5.169.85 69.5.169.46 148.153.30.34 34.62.151.12
129.28.98.91 118.25.230.39 1.14.43.34 23.27.199.53