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

Region: Shanghai

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 '124.220.0.0 - 124.223.255.255'

% Abuse contact for '124.220.0.0 - 124.223.255.255' is 'abuse@tencent.com'

inetnum:        124.220.0.0 - 124.223.255.255
netname:        TencentCloud
descr:          Tencent cloud computing (Beijing) Co., Ltd.
descr:          Floor 6, Yinke Building, 38 Haidian St, Haidian District Beijing
country:        CN
admin-c:        JT1125-AP
tech-c:         JX1747-AP
abuse-c:        AC1601-AP
status:         ALLOCATED PORTABLE
mnt-by:         MAINT-CNNIC-AP
mnt-irt:        IRT-TENCENTCLOUD-CN
last-modified:  2023-11-28T00:57:04Z
source:         APNIC

irt:            IRT-TencentCloud-CN
address:        9F, FIYTA Building, Gaoxinnanyi Road, Southern
address:        District of Hi-tech Park, Shenzhen
e-mail:         tencent_noc@tencent.com
admin-c:        JT1125-AP
tech-c:         JX1747-AP
abuse-mailbox:  abuse@tencent.com
remarks:        abuse@tencent.com was validated on 2025-10-29
remarks:        tencent_noc@tencent.com was validated on 2025-10-29
auth:           # Filtered
mnt-by:         MAINT-CNNIC-AP
last-modified:  2025-11-18T00:34:40Z
source:         APNIC

role:           ABUSE CNNICCN
country:        ZZ
address:        Beijing, China
phone:          +000000000
e-mail:         ipas@cnnic.cn
admin-c:        IP50-AP
tech-c:         IP50-AP
nic-hdl:        AC1601-AP
remarks:        Generated from irt object IRT-CNNIC-CN
remarks:        ipas@cnnic.cn is invalid
abuse-mailbox:  ipas@cnnic.cn
mnt-by:         APNIC-ABUSE
last-modified:  2025-09-19T17:20:32Z
source:         APNIC

person:         James Tian
address:        9F, FIYTA Building, Gaoxinnanyi Road,Southern
address:        District of Hi-tech Park, Shenzhen
country:        CN
phone:          +86-755-86013388-84952
e-mail:         johnsonqu@tencent.com
nic-hdl:        JT1125-AP
mnt-by:         MAINT-CNNIC-AP
last-modified:  2024-03-19T08:21:31Z
source:         APNIC

person:         Jimmy Xiao
address:        9F, FIYTA Building, Gaoxinnanyi Road,Southern
address:        District of Hi-tech Park, Shenzhen
country:        CN
phone:          +86-755-86013388-80224
e-mail:         klayliang@tencent.com
nic-hdl:        JX1747-AP
mnt-by:         MAINT-CNNIC-AP
last-modified:  2021-09-17T00:38:09Z
source:         APNIC

% Information related to '124.220.0.0/14AS45090'

route:          124.220.0.0/14
origin:         AS45090
descr:          China Internet Network Information Center
                Floor1, Building No.1 C/-Chinese Academy of Sciences
                4, South 4th Street
                Haidian District,
mnt-by:         MAINT-CNNIC-AP
last-modified:  2021-10-11T01:50:32Z
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 <<>> 124.221.236.99
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 64110
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;124.221.236.99.			IN	A

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

;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Apr 07 08:00:51 CST 2026
;; MSG SIZE  rcvd: 107
Host info
Host 99.236.221.124.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 99.236.221.124.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
125.215.207.40 attackspambots
Apr 26 10:17:47 mail sshd[22513]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.215.207.40
Apr 26 10:17:48 mail sshd[22513]: Failed password for invalid user svn from 125.215.207.40 port 49079 ssh2
Apr 26 10:26:26 mail sshd[24122]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.215.207.40
2020-04-26 16:39:57
160.16.215.93 attackspambots
"Unauthorized connection attempt on SSHD detected"
2020-04-26 16:43:14
158.69.222.2 attackbots
Apr 26 05:50:23 pve1 sshd[18912]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=158.69.222.2 
Apr 26 05:50:25 pve1 sshd[18912]: Failed password for invalid user jeus from 158.69.222.2 port 38192 ssh2
...
2020-04-26 16:59:50
106.12.185.161 attack
Apr 26 02:11:59 ny01 sshd[16105]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.185.161
Apr 26 02:12:01 ny01 sshd[16105]: Failed password for invalid user tom from 106.12.185.161 port 50536 ssh2
Apr 26 02:15:48 ny01 sshd[16609]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.185.161
2020-04-26 16:59:07
171.110.123.41 attack
Apr 26 03:47:17 ip-172-31-61-156 sshd[16068]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=171.110.123.41  user=root
Apr 26 03:47:19 ip-172-31-61-156 sshd[16068]: Failed password for root from 171.110.123.41 port 57606 ssh2
Apr 26 03:50:22 ip-172-31-61-156 sshd[16192]: Invalid user ajenti from 171.110.123.41
Apr 26 03:50:22 ip-172-31-61-156 sshd[16192]: Invalid user ajenti from 171.110.123.41
...
2020-04-26 17:04:59
175.123.253.220 attack
Invalid user jt from 175.123.253.220 port 47316
2020-04-26 17:19:04
113.53.110.173 attack
Failed password for invalid user root from 113.53.110.173 port 50150 ssh2
2020-04-26 17:12:16
198.108.67.83 attackspam
firewall-block, port(s): 8595/tcp
2020-04-26 17:01:27
192.99.34.42 attack
LGS,WP GET /wp-login.php
2020-04-26 17:01:44
122.51.125.71 attackbots
SSH Bruteforce attack
2020-04-26 17:17:12
122.176.52.13 attack
Apr 26 11:09:10 server sshd[14619]: Failed password for root from 122.176.52.13 port 18738 ssh2
Apr 26 11:14:50 server sshd[15135]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.176.52.13
Apr 26 11:14:52 server sshd[15135]: Failed password for invalid user dgr from 122.176.52.13 port 53860 ssh2
...
2020-04-26 17:16:42
43.227.66.140 attackbotsspam
2020-04-26T08:39:29.524594shield sshd\[8504\]: Invalid user sas from 43.227.66.140 port 36636
2020-04-26T08:39:29.527280shield sshd\[8504\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.227.66.140
2020-04-26T08:39:31.095824shield sshd\[8504\]: Failed password for invalid user sas from 43.227.66.140 port 36636 ssh2
2020-04-26T08:43:20.369616shield sshd\[8930\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.227.66.140  user=root
2020-04-26T08:43:21.983385shield sshd\[8930\]: Failed password for root from 43.227.66.140 port 47686 ssh2
2020-04-26 16:56:54
162.243.133.220 attackbots
Scan ports
2020-04-26 16:38:35
145.239.78.59 attackspam
Invalid user ubuntu from 145.239.78.59 port 35150
2020-04-26 17:06:32
66.70.173.63 attackbotsspam
(sshd) Failed SSH login from 66.70.173.63 (US/United States/ip63.ip-66-70-173.net): 2 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Apr 26 10:05:24 ubnt-55d23 sshd[30707]: Invalid user serge from 66.70.173.63 port 47586
Apr 26 10:05:26 ubnt-55d23 sshd[30707]: Failed password for invalid user serge from 66.70.173.63 port 47586 ssh2
2020-04-26 17:13:03

Recently Reported IPs

216.118.251.134 109.162.251.235 110.77.187.161 2606:4700:10::6814:7438
2606:4700:10::6814:9332 2606:4700:10::6816:3544 2606:4700:10::ac43:2053 2606:4700:10::ac43:1717
2606:4700:10::6816:1445 2606:4700:10::6814:6399 2606:4700:10::6814:7388 202.213.129.125
109.22.68.15 109.22.68.67 221.247.208.14 176.228.83.170
213.89.250.79 216.118.251.94 107.170.46.98 104.199.4.112