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

Region: Beijing

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:
% [whois.apnic.net]
% Whois data copyright terms    http://www.apnic.net/db/dbcopyright.html

% Information related to '101.42.0.0 - 101.43.255.255'

% Abuse contact for '101.42.0.0 - 101.43.255.255' is 'abuse@tencent.com'

inetnum:        101.42.0.0 - 101.43.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:10:59Z
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 '101.42.0.0/15AS45090'

route:          101.42.0.0/15
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:  2020-02-24T07:34:27Z
source:         APNIC

% This query was served by the APNIC Whois Service version 1.88.48 (WHOIS-AU4)
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 101.42.1.32
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 223
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;101.42.1.32.			IN	A

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

;; Query time: 9 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jun 30 19:01:34 CST 2026
;; MSG SIZE  rcvd: 104
Host info
Host 32.1.42.101.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 32.1.42.101.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
203.75.119.14 attackbotsspam
Jun 23 08:18:06 piServer sshd[7662]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.75.119.14 
Jun 23 08:18:08 piServer sshd[7662]: Failed password for invalid user tarcisio from 203.75.119.14 port 59622 ssh2
Jun 23 08:21:09 piServer sshd[7912]: Failed password for root from 203.75.119.14 port 51428 ssh2
...
2020-06-23 14:58:57
185.176.27.86 attack
06/23/2020-02:51:41.145361 185.176.27.86 Protocol: 6 ET DROP Dshield Block Listed Source group 1
2020-06-23 14:56:33
134.175.119.208 attackspam
Invalid user nan from 134.175.119.208 port 18012
2020-06-23 15:28:19
139.59.58.115 attackbotsspam
 TCP (SYN) 139.59.58.115:55217 -> port 4233, len 44
2020-06-23 14:59:18
129.204.147.84 attackbotsspam
Jun 22 21:49:03 server1 sshd\[13459\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.147.84  user=root
Jun 22 21:49:04 server1 sshd\[13459\]: Failed password for root from 129.204.147.84 port 47794 ssh2
Jun 22 21:54:07 server1 sshd\[17125\]: Invalid user murai from 129.204.147.84
Jun 22 21:54:07 server1 sshd\[17125\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.147.84 
Jun 22 21:54:08 server1 sshd\[17125\]: Failed password for invalid user murai from 129.204.147.84 port 47364 ssh2
...
2020-06-23 15:34:07
184.105.139.67 attack
 UDP 184.105.139.67:23394 -> port 161, len 113
2020-06-23 15:22:56
185.153.196.230 attack
Automatic report - Banned IP Access
2020-06-23 14:56:51
192.241.209.81 attack
Unauthorized connection attempt detected from IP address 192.241.209.81 to port 1433
2020-06-23 15:00:20
192.144.155.63 attackspam
Jun 23 06:42:32 localhost sshd\[22009\]: Invalid user postgres from 192.144.155.63
Jun 23 06:42:32 localhost sshd\[22009\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.144.155.63
Jun 23 06:42:34 localhost sshd\[22009\]: Failed password for invalid user postgres from 192.144.155.63 port 53358 ssh2
Jun 23 06:46:59 localhost sshd\[22267\]: Invalid user testuser from 192.144.155.63
Jun 23 06:46:59 localhost sshd\[22267\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.144.155.63
...
2020-06-23 15:17:44
185.176.27.2 attackspambots
 TCP (SYN) 185.176.27.2:50240 -> port 7389, len 44
2020-06-23 15:37:05
189.179.127.205 attackbots
Automatic report - XMLRPC Attack
2020-06-23 15:23:15
188.166.208.131 attackspambots
$f2bV_matches
2020-06-23 15:37:42
192.241.212.152 attack
IP 192.241.212.152 attacked honeypot on port: 9000 at 6/22/2020 10:28:27 PM
2020-06-23 14:53:41
81.182.254.124 attackbots
Invalid user zzl from 81.182.254.124 port 42256
2020-06-23 15:18:36
59.3.93.107 attack
Jun 22 21:40:48 raspberrypi sshd[5662]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.3.93.107 
Jun 22 21:40:50 raspberrypi sshd[5662]: Failed password for invalid user hduser from 59.3.93.107 port 34741 ssh2
Jun 22 21:49:53 raspberrypi sshd[5802]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.3.93.107 
...
2020-06-23 15:02:07

Recently Reported IPs

23.225.255.39 93.123.72.183 47.94.98.89 2606:4700:10::ac43:2712
2606:4700:10::6816:71 2606:4700:10::6816:3934 125.71.97.44 47.95.209.4
91.231.89.29 34.78.172.3 2606:4700:10::6816:2776 2606:4700:10::ac43:2601
2606:4700:10::ac43:64e 94.72.110.148 20.219.18.20 170.106.110.129
74.249.177.110 2606:4700:10::6814:6403 112.86.225.36 45.55.131.172