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

Region: Chongqìng

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-2025, 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:  https://apps.db.ripe.net/db-web-ui/query

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

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


#
# 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-2025, 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 'tencent_noc@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:  tencent_noc@tencent.com
admin-c:        TCA15-AP
tech-c:         TCA15-AP
auth:           # Filtered
remarks:        tencent_noc@tencent.com is invalid
mnt-by:         MAINT-COMSENZ1-CN
last-modified:  2025-09-24T13:09:40Z
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:        tencent_noc@tencent.com is invalid
abuse-mailbox:  tencent_noc@tencent.com
mnt-by:         APNIC-ABUSE
last-modified:  2025-09-24T13:10:34Z
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.36-SNAPSHOT (WHOIS-AU5)
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 162.14.207.48
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 13065
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;162.14.207.48.			IN	A

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

;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Sep 26 10:30:45 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 48.207.14.162.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 48.207.14.162.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
106.13.115.197 attack
Sep 29 07:08:28 venus sshd\[16411\]: Invalid user sabra from 106.13.115.197 port 50151
Sep 29 07:08:28 venus sshd\[16411\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.115.197
Sep 29 07:08:30 venus sshd\[16411\]: Failed password for invalid user sabra from 106.13.115.197 port 50151 ssh2
...
2019-09-29 15:14:06
186.156.177.115 attack
Sep 29 07:16:06 lnxded64 sshd[11382]: Failed password for root from 186.156.177.115 port 50594 ssh2
Sep 29 07:16:06 lnxded64 sshd[11382]: Failed password for root from 186.156.177.115 port 50594 ssh2
2019-09-29 15:12:12
139.199.133.160 attackbotsspam
Sep 29 06:55:16 MK-Soft-Root2 sshd[17073]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.199.133.160 
Sep 29 06:55:18 MK-Soft-Root2 sshd[17073]: Failed password for invalid user danilo from 139.199.133.160 port 58808 ssh2
...
2019-09-29 15:05:50
149.56.89.123 attackspam
Invalid user support from 149.56.89.123 port 59900
2019-09-29 15:14:29
142.44.160.173 attack
Sep 29 06:14:18 sshgateway sshd\[28764\]: Invalid user monitor from 142.44.160.173
Sep 29 06:14:18 sshgateway sshd\[28764\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.44.160.173
Sep 29 06:14:20 sshgateway sshd\[28764\]: Failed password for invalid user monitor from 142.44.160.173 port 46732 ssh2
2019-09-29 15:25:48
106.12.125.27 attackbots
Invalid user ncs from 106.12.125.27 port 33466
2019-09-29 14:49:17
18.140.165.118 attackbots
2019-09-28T23:43:07.5756801495-001 sshd\[36885\]: Failed password for invalid user permit from 18.140.165.118 port 44374 ssh2
2019-09-28T23:54:28.2400961495-001 sshd\[37752\]: Invalid user 123 from 18.140.165.118 port 43182
2019-09-28T23:54:28.2476071495-001 sshd\[37752\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ec2-18-140-165-118.ap-southeast-1.compute.amazonaws.com
2019-09-28T23:54:30.2889731495-001 sshd\[37752\]: Failed password for invalid user 123 from 18.140.165.118 port 43182 ssh2
2019-09-29T00:00:14.6106771495-001 sshd\[38228\]: Invalid user splashmc123 from 18.140.165.118 port 58498
2019-09-29T00:00:14.6180931495-001 sshd\[38228\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ec2-18-140-165-118.ap-southeast-1.compute.amazonaws.com
...
2019-09-29 15:24:20
119.28.222.88 attackbotsspam
Sep 29 02:40:27 TORMINT sshd\[5939\]: Invalid user testing from 119.28.222.88
Sep 29 02:40:27 TORMINT sshd\[5939\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.28.222.88
Sep 29 02:40:29 TORMINT sshd\[5939\]: Failed password for invalid user testing from 119.28.222.88 port 38934 ssh2
...
2019-09-29 14:56:43
31.210.65.150 attack
Sep 28 20:40:31 eddieflores sshd\[4624\]: Invalid user test from 31.210.65.150
Sep 28 20:40:31 eddieflores sshd\[4624\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=31.210.65.150
Sep 28 20:40:33 eddieflores sshd\[4624\]: Failed password for invalid user test from 31.210.65.150 port 44543 ssh2
Sep 28 20:46:15 eddieflores sshd\[5058\]: Invalid user changem from 31.210.65.150
Sep 28 20:46:15 eddieflores sshd\[5058\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=31.210.65.150
2019-09-29 14:57:11
183.111.227.5 attackbotsspam
Sep 29 09:08:08 vps647732 sshd[21739]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.111.227.5
Sep 29 09:08:10 vps647732 sshd[21739]: Failed password for invalid user 123456 from 183.111.227.5 port 51060 ssh2
...
2019-09-29 15:11:49
167.71.236.0 attackbots
Sep 29 07:19:27 meumeu sshd[27336]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.236.0 
Sep 29 07:19:29 meumeu sshd[27336]: Failed password for invalid user patrick from 167.71.236.0 port 47930 ssh2
Sep 29 07:24:34 meumeu sshd[27965]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.236.0 
...
2019-09-29 15:06:45
192.42.116.15 attackbots
Sep 29 05:52:42 rotator sshd\[30603\]: Invalid user general from 192.42.116.15Sep 29 05:52:44 rotator sshd\[30603\]: Failed password for invalid user general from 192.42.116.15 port 36210 ssh2Sep 29 05:52:48 rotator sshd\[30605\]: Invalid user genie from 192.42.116.15Sep 29 05:52:50 rotator sshd\[30605\]: Failed password for invalid user genie from 192.42.116.15 port 44486 ssh2Sep 29 05:52:54 rotator sshd\[30607\]: Invalid user geosolutions from 192.42.116.15Sep 29 05:52:56 rotator sshd\[30607\]: Failed password for invalid user geosolutions from 192.42.116.15 port 54092 ssh2
...
2019-09-29 14:52:03
51.38.238.87 attack
Sep 29 07:51:04 dedicated sshd[27096]: Invalid user spark from 51.38.238.87 port 42986
2019-09-29 15:01:07
118.24.101.182 attackspam
Sep 29 10:16:16 server sshd\[6844\]: Invalid user sw from 118.24.101.182 port 43438
Sep 29 10:16:16 server sshd\[6844\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.101.182
Sep 29 10:16:18 server sshd\[6844\]: Failed password for invalid user sw from 118.24.101.182 port 43438 ssh2
Sep 29 10:22:02 server sshd\[1669\]: Invalid user sales2 from 118.24.101.182 port 54360
Sep 29 10:22:02 server sshd\[1669\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.101.182
2019-09-29 15:26:44
217.243.172.58 attackbotsspam
2019-09-29T07:58:38.646215  sshd[7449]: Invalid user laurice from 217.243.172.58 port 48722
2019-09-29T07:58:38.660689  sshd[7449]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.243.172.58
2019-09-29T07:58:38.646215  sshd[7449]: Invalid user laurice from 217.243.172.58 port 48722
2019-09-29T07:58:40.788674  sshd[7449]: Failed password for invalid user laurice from 217.243.172.58 port 48722 ssh2
2019-09-29T08:02:28.182254  sshd[7551]: Invalid user dmu from 217.243.172.58 port 32814
...
2019-09-29 15:10:45

Recently Reported IPs

211.158.26.133 61.142.42.201 20.64.105.169 192.168.74.23
138.197.15.182 125.94.174.65 185.177.72.13 183.7.149.126
192.168.31.63 172.71.154.145 168.119.246.192 45.82.78.116
122.119.4.95 10.3.244.16 10.100.100.250 4.227.36.67
10.165.54.222 203.84.143.141 205.185.125.20 209.132.243.173