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-AU5); <<>> DiG 9.10.3-P4-Ubuntu <<>> 162.14.126.236
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 16102
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;162.14.126.236. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026072500 1800 900 604800 86400
;; Query time: 232 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Jul 25 23:30:38 CST 2026
;; MSG SIZE rcvd: 107Host 236.126.14.162.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 236.126.14.162.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 45.136.108.119 | attackbots | Jan 1 16:13:49 debian-2gb-nbg1-2 kernel: \[150960.805638\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=45.136.108.119 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=40795 PROTO=TCP SPT=44793 DPT=419 WINDOW=1024 RES=0x00 SYN URGP=0 |
2020-01-01 23:26:38 |
| 117.248.106.22 | attackspambots | (sshd) Failed SSH login from 117.248.106.22 (IN/India/Maharashtra/Pune/-/[AS9829 National Internet Backbone]): 1 in the last 3600 secs |
2020-01-01 23:19:19 |
| 185.176.27.118 | attackbotsspam | 01/01/2020-10:50:57.246235 185.176.27.118 Protocol: 6 ET SCAN NMAP -sS window 1024 |
2020-01-01 23:51:47 |
| 218.92.0.168 | attack | Jan 1 10:14:10 plusreed sshd[12573]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.168 user=root Jan 1 10:14:12 plusreed sshd[12573]: Failed password for root from 218.92.0.168 port 47489 ssh2 ... |
2020-01-01 23:16:22 |
| 113.239.183.123 | attackbotsspam | Telnet Server BruteForce Attack |
2020-01-01 23:10:45 |
| 195.246.218.11 | attackspam | [portscan] Port scan |
2020-01-01 23:47:02 |
| 222.186.175.155 | attackbots | Jan 1 16:20:53 Ubuntu-1404-trusty-64-minimal sshd\[32283\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.155 user=root Jan 1 16:20:55 Ubuntu-1404-trusty-64-minimal sshd\[32283\]: Failed password for root from 222.186.175.155 port 14296 ssh2 Jan 1 16:21:13 Ubuntu-1404-trusty-64-minimal sshd\[32412\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.155 user=root Jan 1 16:21:15 Ubuntu-1404-trusty-64-minimal sshd\[32412\]: Failed password for root from 222.186.175.155 port 34510 ssh2 Jan 1 16:21:43 Ubuntu-1404-trusty-64-minimal sshd\[32613\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.155 user=root |
2020-01-01 23:24:47 |
| 58.210.169.162 | attackspambots | Automatic report - Banned IP Access |
2020-01-01 23:11:37 |
| 36.7.147.177 | attackspam | Jan 1 15:49:32 dev0-dcde-rnet sshd[14628]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.7.147.177 Jan 1 15:49:34 dev0-dcde-rnet sshd[14628]: Failed password for invalid user noda from 36.7.147.177 port 57546 ssh2 Jan 1 15:54:06 dev0-dcde-rnet sshd[14664]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.7.147.177 |
2020-01-01 23:23:53 |
| 46.166.187.11 | attackbotsspam | \[2020-01-01 10:05:13\] SECURITY\[2857\] res_security_log.c: SecurityEvent="FailedACL",EventTV="2020-01-01T10:05:13.748-0500",Severity="Error",Service="SIP",EventVersion="1",AccountID="011442037698133",SessionID="0x7f0fb447f838",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/46.166.187.11/62427",ACLName="no_extension_match" \[2020-01-01 10:06:34\] SECURITY\[2857\] res_security_log.c: SecurityEvent="FailedACL",EventTV="2020-01-01T10:06:34.542-0500",Severity="Error",Service="SIP",EventVersion="1",AccountID="9011442037698133",SessionID="0x7f0fb4ca4128",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/46.166.187.11/58129",ACLName="no_extension_match" \[2020-01-01 10:09:09\] SECURITY\[2857\] res_security_log.c: SecurityEvent="FailedACL",EventTV="2020-01-01T10:09:09.041-0500",Severity="Error",Service="SIP",EventVersion="1",AccountID="011442037698133",SessionID="0x7f0fb4a2dfd8",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/46.166.187.11/56287",ACLName="no_ex |
2020-01-01 23:23:27 |
| 46.38.144.117 | attackbots | Too many connections or unauthorized access detected from Yankee banned ip |
2020-01-01 23:29:12 |
| 45.136.109.122 | attack | Triggered: repeated knocking on closed ports. |
2020-01-01 23:30:28 |
| 76.10.14.76 | attackbots | Automatic report - SSH Brute-Force Attack |
2020-01-01 23:37:12 |
| 27.62.59.193 | attackbotsspam | 1577890455 - 01/01/2020 15:54:15 Host: 27.62.59.193/27.62.59.193 Port: 445 TCP Blocked |
2020-01-01 23:17:33 |
| 15.185.52.31 | attackbotsspam | fail2ban honeypot |
2020-01-01 23:25:18 |