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

Region: Anhui

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 '123.52.0.0 - 123.55.255.255'

% Abuse contact for '123.52.0.0 - 123.55.255.255' is 'anti-spam@chinatelecom.cn'

inetnum:        123.52.0.0 - 123.55.255.255
netname:        MAINT-CHINANET-HA
descr:          CHINANET HENAN PROVINCE NETWORK
descr:          henan Telecom Corporation
descr:          97 # Zhongyuan Street, Zhengzhou,henan,Chinese
country:        CN
admin-c:        HZ149-AP
tech-c:         HZ149-AP
abuse-c:        AC1573-AP
status:         ALLOCATED PORTABLE
remarks:        Henan Telecom Corporation hostmaster
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-CHINANET-HA
mnt-routes:     MAINT-CHINANET-HA
mnt-irt:        IRT-CHINANET-CN
last-modified:  2021-06-15T08:05:56Z
source:         APNIC

irt:            IRT-CHINANET-CN
address:        No.31 ,jingrong street,beijing
address:        100032
e-mail:         anti-spam@chinatelecom.cn
abuse-mailbox:  anti-spam@chinatelecom.cn
admin-c:        CH93-AP
tech-c:         CH93-AP
auth:           # Filtered
remarks:        anti-spam@chinatelecom.cn was validated on 2025-11-13
mnt-by:         MAINT-CHINANET
last-modified:  2026-03-13T07:12:20Z
source:         APNIC

role:           ABUSE CHINANETCN
country:        ZZ
address:        No.31 ,jingrong street,beijing
address:        100032
phone:          +000000000
e-mail:         anti-spam@chinatelecom.cn
admin-c:        CH93-AP
tech-c:         CH93-AP
nic-hdl:        AC1573-AP
remarks:        Generated from irt object IRT-CHINANET-CN
remarks:        anti-spam@chinatelecom.cn was validated on 2025-11-13
abuse-mailbox:  anti-spam@chinatelecom.cn
mnt-by:         APNIC-ABUSE
last-modified:  2025-11-13T14:15:15Z
source:         APNIC

person:         Hongbiao Zhang
nic-hdl:        HZ149-AP
e-mail:         ip@hntele.com
address:        97# Zhongyuan Street, Zhengzhou City, China
phone:          +86 371 65310018
fax-no:         +86 371 65310015
country:        CN
mnt-by:         MAINT-CHINANET-HA
last-modified:  2008-09-04T07:29:40Z
source:         APNIC

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

;; QUESTION SECTION:
;123.53.56.17.			IN	A

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

;; Query time: 8 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Mar 16 03:00:24 CST 2026
;; MSG SIZE  rcvd: 105
Host info
Host 17.56.53.123.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 17.56.53.123.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
188.173.97.144 attackspam
web-1 [ssh] SSH Attack
2020-04-05 14:05:31
218.92.0.171 attackbots
[MK-VM2] SSH login failed
2020-04-05 14:24:00
91.209.54.54 attackbotsspam
(sshd) Failed SSH login from 91.209.54.54 (RU/Russia/host-54.briz.net.ru): 2 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Apr  5 07:54:53 ubnt-55d23 sshd[16003]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.209.54.54  user=root
Apr  5 07:54:53 ubnt-55d23 sshd[16001]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.209.54.54  user=root
2020-04-05 14:28:30
123.206.7.96 attack
SSH authentication failure x 6 reported by Fail2Ban
...
2020-04-05 13:53:09
139.59.90.0 attackspambots
Invalid user user from 139.59.90.0 port 59782
2020-04-05 14:07:15
92.118.38.82 attack
Apr  5 07:38:31 mail postfix/smtpd\[18962\]: warning: unknown\[92.118.38.82\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Apr  5 08:09:02 mail postfix/smtpd\[19607\]: warning: unknown\[92.118.38.82\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Apr  5 08:09:35 mail postfix/smtpd\[19656\]: warning: unknown\[92.118.38.82\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Apr  5 08:10:09 mail postfix/smtpd\[19607\]: warning: unknown\[92.118.38.82\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
2020-04-05 14:13:40
182.254.186.229 attackbots
ssh brute force
2020-04-05 14:03:25
157.230.219.73 attackspam
IP blocked
2020-04-05 13:58:36
163.172.137.10 attack
Apr  5 07:14:12 pkdns2 sshd\[55276\]: Address 163.172.137.10 maps to vds.nbrz.ru, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!Apr  5 07:14:14 pkdns2 sshd\[55276\]: Failed password for root from 163.172.137.10 port 46614 ssh2Apr  5 07:17:48 pkdns2 sshd\[55448\]: Address 163.172.137.10 maps to vds.nbrz.ru, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!Apr  5 07:17:50 pkdns2 sshd\[55448\]: Failed password for root from 163.172.137.10 port 58046 ssh2Apr  5 07:21:29 pkdns2 sshd\[55635\]: Address 163.172.137.10 maps to vds.nbrz.ru, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!Apr  5 07:21:31 pkdns2 sshd\[55635\]: Failed password for root from 163.172.137.10 port 41108 ssh2
...
2020-04-05 14:15:00
103.45.107.226 attackbotsspam
$f2bV_matches
2020-04-05 14:32:44
46.101.19.133 attack
SSH bruteforce
2020-04-05 13:54:39
148.72.212.161 attack
SSH login attempts.
2020-04-05 14:30:10
112.35.57.139 attackbots
2020-04-05T05:47:49.362401struts4.enskede.local sshd\[850\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.35.57.139  user=root
2020-04-05T05:47:52.767252struts4.enskede.local sshd\[850\]: Failed password for root from 112.35.57.139 port 34704 ssh2
2020-04-05T05:51:47.727500struts4.enskede.local sshd\[996\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.35.57.139  user=root
2020-04-05T05:51:50.139202struts4.enskede.local sshd\[996\]: Failed password for root from 112.35.57.139 port 41022 ssh2
2020-04-05T05:53:51.769992struts4.enskede.local sshd\[1096\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.35.57.139  user=root
...
2020-04-05 14:28:03
49.247.206.0 attackspam
Apr  5 07:29:05 ns382633 sshd\[12634\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.247.206.0  user=root
Apr  5 07:29:07 ns382633 sshd\[12634\]: Failed password for root from 49.247.206.0 port 36074 ssh2
Apr  5 07:40:12 ns382633 sshd\[15046\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.247.206.0  user=root
Apr  5 07:40:14 ns382633 sshd\[15046\]: Failed password for root from 49.247.206.0 port 45706 ssh2
Apr  5 07:43:57 ns382633 sshd\[15398\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.247.206.0  user=root
2020-04-05 14:17:25
222.186.175.167 attack
Fail2Ban - SSH Bruteforce Attempt
2020-04-05 14:19:43

Recently Reported IPs

143.110.240.48 91.230.168.15 170.39.194.162 110.35.80.116
112.124.56.24 37.191.13.109 36.103.205.240 106.227.8.250
104.236.52.188 111.25.20.227 111.170.156.204 195.178.110.154
85.217.140.40 44.202.33.214 3.84.4.44 34.235.115.207
134.33.66.164 52.90.148.15 20.83.2.253 125.72.113.23