City: Nanjing
Region: Jiangsu
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: 146.56.0.0 - 146.56.255.255
CIDR: 146.56.0.0/16
NetName: APNIC-ERX-146-56-0-0
NetHandle: NET-146-56-0-0-1
Parent: NET146 (NET-146-0-0-0-0)
NetType: Early Registrations, Transferred to APNIC
OriginAS:
Organization: Asia Pacific Network Information Centre (APNIC)
RegDate: 2004-02-04
Updated: 2009-10-08
Comment: This IP address range is not registered in the ARIN database.
Comment: This range was transferred to the APNIC Whois Database as
Comment: part of the ERX (Early Registration Transfer) project.
Comment: For details, refer to the APNIC Whois Database via
Comment: WHOIS.APNIC.NET or http://wq.apnic.net/apnic-bin/whois.pl
Comment:
Comment: ** IMPORTANT NOTE: APNIC is the Regional Internet Registry
Comment: for the Asia Pacific region. APNIC does not operate networks
Comment: using this IP address range and is not able to investigate
Comment: spam or abuse reports relating to these addresses. For more
Comment: help, refer to http://www.apnic.net/apnic-info/whois_search2/abuse-and-spamming
Ref: https://rdap.arin.net/registry/ip/146.56.0.0
ResourceLink: https://apps.db.ripe.net/db-web-ui/query
ResourceLink: 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
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-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 '146.56.192.0 - 146.56.255.255'
% Abuse contact for '146.56.192.0 - 146.56.255.255' is 'abuse@tencent.com'
inetnum: 146.56.192.0 - 146.56.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:58Z
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 '146.56.192.0/18AS45090'
route: 146.56.192.0/18
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:20:14Z
source: APNIC
% This query was served by the APNIC Whois Service version 1.88.48 (WHOIS-AU5); <<>> DiG 9.10.3-P4-Ubuntu <<>> 146.56.197.194
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 6904
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;146.56.197.194. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026111001 1800 900 604800 86400
;; Query time: 6 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Nov 11 04:00:24 CST 2026
;; MSG SIZE rcvd: 107Host 194.197.56.146.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 194.197.56.146.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 222.186.175.140 | attackbotsspam | 2020-02-21T05:52:30.046043abusebot-4.cloudsearch.cf sshd[28606]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.140 user=root 2020-02-21T05:52:32.525124abusebot-4.cloudsearch.cf sshd[28606]: Failed password for root from 222.186.175.140 port 49846 ssh2 2020-02-21T05:52:35.337261abusebot-4.cloudsearch.cf sshd[28606]: Failed password for root from 222.186.175.140 port 49846 ssh2 2020-02-21T05:52:30.046043abusebot-4.cloudsearch.cf sshd[28606]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.140 user=root 2020-02-21T05:52:32.525124abusebot-4.cloudsearch.cf sshd[28606]: Failed password for root from 222.186.175.140 port 49846 ssh2 2020-02-21T05:52:35.337261abusebot-4.cloudsearch.cf sshd[28606]: Failed password for root from 222.186.175.140 port 49846 ssh2 2020-02-21T05:52:30.046043abusebot-4.cloudsearch.cf sshd[28606]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 ... |
2020-02-21 13:55:08 |
| 92.63.196.3 | attack | Feb 21 06:35:22 debian-2gb-nbg1-2 kernel: \[4522531.461559\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=92.63.196.3 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=57518 PROTO=TCP SPT=40661 DPT=9689 WINDOW=1024 RES=0x00 SYN URGP=0 |
2020-02-21 13:45:50 |
| 112.11.112.147 | attackbots | xmlrpc attack |
2020-02-21 14:11:33 |
| 185.86.167.4 | attack | Wordpress attack |
2020-02-21 14:18:41 |
| 181.80.185.166 | attackspam | Automatic report - Port Scan Attack |
2020-02-21 13:55:41 |
| 120.131.3.119 | attack | Feb 21 01:57:57 vps46666688 sshd[1882]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.131.3.119 Feb 21 01:57:58 vps46666688 sshd[1882]: Failed password for invalid user jira from 120.131.3.119 port 63084 ssh2 ... |
2020-02-21 14:13:52 |
| 49.233.46.219 | attackspambots | Feb 21 11:52:59 itv-usvr-01 sshd[25295]: Invalid user hanshow from 49.233.46.219 Feb 21 11:52:59 itv-usvr-01 sshd[25295]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.233.46.219 Feb 21 11:52:59 itv-usvr-01 sshd[25295]: Invalid user hanshow from 49.233.46.219 Feb 21 11:53:01 itv-usvr-01 sshd[25295]: Failed password for invalid user hanshow from 49.233.46.219 port 34682 ssh2 Feb 21 11:57:59 itv-usvr-01 sshd[25484]: Invalid user cpanelphppgadmin from 49.233.46.219 |
2020-02-21 14:13:39 |
| 52.170.145.235 | attackspam | Feb 21 06:13:17 srv-ubuntu-dev3 sshd[19848]: Invalid user msagent from 52.170.145.235 Feb 21 06:13:17 srv-ubuntu-dev3 sshd[19848]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.170.145.235 Feb 21 06:13:17 srv-ubuntu-dev3 sshd[19848]: Invalid user msagent from 52.170.145.235 Feb 21 06:13:19 srv-ubuntu-dev3 sshd[19848]: Failed password for invalid user msagent from 52.170.145.235 port 35080 ssh2 Feb 21 06:18:11 srv-ubuntu-dev3 sshd[20239]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.170.145.235 user=nginx Feb 21 06:18:13 srv-ubuntu-dev3 sshd[20239]: Failed password for nginx from 52.170.145.235 port 35424 ssh2 Feb 21 06:23:12 srv-ubuntu-dev3 sshd[20729]: Invalid user testuser from 52.170.145.235 Feb 21 06:23:12 srv-ubuntu-dev3 sshd[20729]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.170.145.235 Feb 21 06:23:12 srv-ubuntu-dev3 sshd[20729]: Invalid use ... |
2020-02-21 13:46:47 |
| 209.17.97.34 | attack | Automatic report - Banned IP Access |
2020-02-21 14:07:08 |
| 123.20.52.28 | attackspam | 20/2/20@23:57:36: FAIL: Alarm-Network address from=123.20.52.28 20/2/20@23:57:36: FAIL: Alarm-Network address from=123.20.52.28 ... |
2020-02-21 14:27:27 |
| 43.226.149.146 | attack | Feb 20 19:43:56 web9 sshd\[6065\]: Invalid user rstudio-server from 43.226.149.146 Feb 20 19:43:56 web9 sshd\[6065\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.226.149.146 Feb 20 19:43:58 web9 sshd\[6065\]: Failed password for invalid user rstudio-server from 43.226.149.146 port 48598 ssh2 Feb 20 19:48:08 web9 sshd\[6603\]: Invalid user couchdb from 43.226.149.146 Feb 20 19:48:08 web9 sshd\[6603\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.226.149.146 |
2020-02-21 14:00:52 |
| 201.238.232.69 | attack | 20/2/21@00:54:11: FAIL: Alarm-Network address from=201.238.232.69 20/2/21@00:54:11: FAIL: Alarm-Network address from=201.238.232.69 ... |
2020-02-21 14:17:51 |
| 93.43.76.70 | attackspambots | Feb 21 06:08:46 ns3042688 sshd\[19906\]: Invalid user debian from 93.43.76.70 Feb 21 06:08:48 ns3042688 sshd\[19906\]: Failed password for invalid user debian from 93.43.76.70 port 58620 ssh2 Feb 21 06:12:33 ns3042688 sshd\[20606\]: Invalid user zbl from 93.43.76.70 Feb 21 06:12:34 ns3042688 sshd\[20606\]: Failed password for invalid user zbl from 93.43.76.70 port 35292 ssh2 Feb 21 06:16:17 ns3042688 sshd\[21334\]: Invalid user tomcat from 93.43.76.70 ... |
2020-02-21 14:08:40 |
| 27.2.175.40 | attackspambots | firewall-block, port(s): 23/tcp |
2020-02-21 14:14:19 |
| 51.89.21.206 | attackspam | 51.89.21.206 was recorded 5 times by 5 hosts attempting to connect to the following ports: 5060. Incident counter (4h, 24h, all-time): 5, 18, 121 |
2020-02-21 13:46:05 |