City: Chengdu
Region: Sichuan
Country: China
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
#
# 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: 162.14.0.0 - 162.14.255.255
CIDR: 162.14.0.0/16
NetName: APNIC
NetHandle: NET-162-14-0-0-1
Parent: NET162 (NET-162-0-0-0-0)
NetType: Early Registrations, Transferred to APNIC
OriginAS:
Organization: Asia Pacific Network Information Centre (APNIC)
RegDate: 2018-01-16
Updated: 2018-01-16
Ref: https://rdap.arin.net/registry/ip/162.14.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 '162.14.0.0 - 162.14.255.255'
% Abuse contact for '162.14.0.0 - 162.14.255.255' is 'abuse@tencent.com'
inetnum: 162.14.0.0 - 162.14.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:00Z
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 '162.14.0.0/16AS45090'
route: 162.14.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:23:45Z
source: APNIC
% This query was served by the APNIC Whois Service version 1.88.48 (WHOIS-AU4); <<>> DiG 9.10.3-P4-Ubuntu <<>> 162.14.98.58
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 52394
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;162.14.98.58. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026072500 1800 900 604800 86400
;; Query time: 6 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Jul 25 23:31:35 CST 2026
;; MSG SIZE rcvd: 105Host 58.98.14.162.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 58.98.14.162.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 148.70.111.66 | attackbotsspam | firewall-block, port(s): 8040/tcp |
2019-11-09 21:03:55 |
| 124.104.5.110 | attackbotsspam | 124.104.5.110 was recorded 5 times by 1 hosts attempting to connect to the following ports: 15941. Incident counter (4h, 24h, all-time): 5, 5, 5 |
2019-11-09 21:20:16 |
| 165.22.195.163 | attackbotsspam | Wordpress brute-force |
2019-11-09 21:00:05 |
| 167.114.157.86 | attackspam | Nov 9 13:21:15 SilenceServices sshd[6911]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.114.157.86 Nov 9 13:21:17 SilenceServices sshd[6911]: Failed password for invalid user 1234567 from 167.114.157.86 port 41989 ssh2 Nov 9 13:24:47 SilenceServices sshd[7944]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.114.157.86 |
2019-11-09 20:53:23 |
| 138.68.50.18 | attack | Nov 9 13:48:23 nextcloud sshd\[19215\]: Invalid user csx from 138.68.50.18 Nov 9 13:48:23 nextcloud sshd\[19215\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.50.18 Nov 9 13:48:25 nextcloud sshd\[19215\]: Failed password for invalid user csx from 138.68.50.18 port 41384 ssh2 ... |
2019-11-09 21:19:47 |
| 112.85.42.237 | attackbots | Nov 9 11:43:37 localhost sshd[5329]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.237 user=root Nov 9 11:43:39 localhost sshd[5329]: Failed password for root from 112.85.42.237 port 10504 ssh2 Nov 9 11:43:37 localhost sshd[5329]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.237 user=root Nov 9 11:43:39 localhost sshd[5329]: Failed password for root from 112.85.42.237 port 10504 ssh2 Nov 9 11:43:43 localhost sshd[5329]: Failed password for root from 112.85.42.237 port 10504 ssh2 |
2019-11-09 20:44:57 |
| 91.67.43.182 | attackspambots | Nov 9 13:29:58 XXX sshd[58109]: Invalid user ofsaa from 91.67.43.182 port 59894 |
2019-11-09 21:06:14 |
| 111.231.89.162 | attackbotsspam | $f2bV_matches |
2019-11-09 21:14:43 |
| 114.67.98.243 | attack | SSH Brute-Force reported by Fail2Ban |
2019-11-09 21:13:10 |
| 106.54.194.194 | attack | 2019-11-09T08:58:41.943056abusebot-4.cloudsearch.cf sshd\[10356\]: Invalid user akanistha from 106.54.194.194 port 52048 |
2019-11-09 20:54:53 |
| 45.136.110.26 | attackbots | Nov 9 12:20:27 h2177944 kernel: \[6174014.816551\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=45.136.110.26 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=2128 PROTO=TCP SPT=48057 DPT=3527 WINDOW=1024 RES=0x00 SYN URGP=0 Nov 9 12:23:25 h2177944 kernel: \[6174193.067527\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=45.136.110.26 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=60602 PROTO=TCP SPT=48057 DPT=3596 WINDOW=1024 RES=0x00 SYN URGP=0 Nov 9 12:34:03 h2177944 kernel: \[6174831.290227\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=45.136.110.26 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=51970 PROTO=TCP SPT=48057 DPT=3632 WINDOW=1024 RES=0x00 SYN URGP=0 Nov 9 12:49:33 h2177944 kernel: \[6175760.671381\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=45.136.110.26 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=49508 PROTO=TCP SPT=48057 DPT=3639 WINDOW=1024 RES=0x00 SYN URGP=0 Nov 9 12:54:42 h2177944 kernel: \[6176070.120941\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=45.136.110.26 DST=85.214.117.9 |
2019-11-09 21:19:26 |
| 46.105.112.107 | attack | Failed password for invalid user info from 46.105.112.107 port 38264 ssh2 pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.105.112.107 user=root Failed password for root from 46.105.112.107 port 48952 ssh2 Invalid user or from 46.105.112.107 port 59628 pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.105.112.107 |
2019-11-09 21:10:13 |
| 193.70.43.220 | attack | 2019-11-09T12:27:21.0690011240 sshd\[25210\]: Invalid user login from 193.70.43.220 port 44372 2019-11-09T12:27:21.0722771240 sshd\[25210\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.70.43.220 2019-11-09T12:27:23.3152691240 sshd\[25210\]: Failed password for invalid user login from 193.70.43.220 port 44372 ssh2 ... |
2019-11-09 21:09:14 |
| 179.83.194.167 | attackbotsspam | Automatic report - Port Scan Attack |
2019-11-09 20:55:40 |
| 106.13.38.59 | attackspambots | Nov 9 13:49:37 server sshd\[332\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.38.59 user=root Nov 9 13:49:40 server sshd\[332\]: Failed password for root from 106.13.38.59 port 47934 ssh2 Nov 9 14:13:35 server sshd\[6562\]: Invalid user ielectronics from 106.13.38.59 Nov 9 14:13:35 server sshd\[6562\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.38.59 Nov 9 14:13:37 server sshd\[6562\]: Failed password for invalid user ielectronics from 106.13.38.59 port 59954 ssh2 ... |
2019-11-09 21:05:58 |