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

Region: unknown

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 '42.196.0.0 - 42.197.255.255'

% Abuse contact for '42.196.0.0 - 42.197.255.255' is 'ipas@cnnic.cn'

inetnum:        42.196.0.0 - 42.197.255.255
netname:        HWCSNET
descr:          Huawei Public Cloud Service (Huawei Software Technologies Ltd.Co)
country:        CN
admin-c:        LL3172-AP
tech-c:         LL3172-AP
abuse-c:        AC1601-AP
status:         ALLOCATED PORTABLE
mnt-by:         MAINT-CNNIC-AP
mnt-lower:      MAINT-CNNIC-AP
mnt-routes:     MAINT-CNNIC-AP
mnt-irt:        IRT-CNNIC-CN
last-modified:  2023-10-13T01:14:41Z
source:         APNIC

irt:            IRT-CNNIC-CN
address:        Beijing, China
e-mail:         ipas@cnnic.cn
abuse-mailbox:  ipas@cnnic.cn
admin-c:        IP50-AP
tech-c:         IP50-AP
auth:           # Filtered
remarks:        Please note that CNNIC is not an ISP and is not
remarks:        empowered to investigate complaints of network abuse.
remarks:        Please contact the tech-c or admin-c of the network.
remarks:        ipas@cnnic.cn is invalid
mnt-by:         MAINT-CNNIC-AP
last-modified:  2025-11-17T23:08:37Z
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:         Liu Liqun
address:        HUAWEI CLOUD Data Center, Jiaoxinggong Road, Qianzhong Avenue, Gui'an New District, Guizhou Province
country:        CN
phone:          +86-13360099887
e-mail:         liuliqun2@huawei.com
nic-hdl:        LL3172-AP
mnt-by:         MAINT-CNNIC-AP
last-modified:  2022-04-18T05:33:15Z
source:         APNIC

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

;; QUESTION SECTION:
;42.197.108.45.			IN	A

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

;; Query time: 23 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Nov 21 19:00:23 CST 2026
;; MSG SIZE  rcvd: 106
Host info
Host 45.108.197.42.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 45.108.197.42.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
101.108.240.209 attackspambots
WordPress wp-login brute force :: 101.108.240.209 0.132 BYPASS [04/Oct/2019:13:58:18  1000] [censored_1] "POST /wp-login.php HTTP/1.1" 200 3972 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2019-10-04 12:58:48
39.135.1.160 attack
10/03/2019-23:58:10.054429 39.135.1.160 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2019-10-04 13:04:10
219.94.99.133 attack
Automatic report - Banned IP Access
2019-10-04 12:36:12
110.50.106.255 attackspambots
2019-10-04T04:32:11.949729abusebot-6.cloudsearch.cf sshd\[8156\]: Invalid user Fantasy@2017 from 110.50.106.255 port 4673
2019-10-04 12:57:02
222.186.190.2 attackbotsspam
2019-10-04T04:56:55.646593hub.schaetter.us sshd\[19558\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.190.2  user=root
2019-10-04T04:56:57.159890hub.schaetter.us sshd\[19558\]: Failed password for root from 222.186.190.2 port 50346 ssh2
2019-10-04T04:57:01.803458hub.schaetter.us sshd\[19558\]: Failed password for root from 222.186.190.2 port 50346 ssh2
2019-10-04T04:57:06.131271hub.schaetter.us sshd\[19558\]: Failed password for root from 222.186.190.2 port 50346 ssh2
2019-10-04T04:57:10.339465hub.schaetter.us sshd\[19558\]: Failed password for root from 222.186.190.2 port 50346 ssh2
...
2019-10-04 13:01:16
83.4.201.24 attackspam
Automatic report - Port Scan Attack
2019-10-04 12:44:30
80.211.16.26 attack
Oct  4 00:28:17 ny01 sshd[21741]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.211.16.26
Oct  4 00:28:19 ny01 sshd[21741]: Failed password for invalid user Amigo2017 from 80.211.16.26 port 40766 ssh2
Oct  4 00:32:27 ny01 sshd[22439]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.211.16.26
2019-10-04 12:45:12
153.36.242.143 attackbotsspam
Oct  4 06:25:05 vpn01 sshd[27348]: Failed password for root from 153.36.242.143 port 39537 ssh2
Oct  4 06:25:07 vpn01 sshd[27348]: Failed password for root from 153.36.242.143 port 39537 ssh2
...
2019-10-04 12:26:17
178.128.49.144 attack
WordPress wp-login brute force :: 178.128.49.144 0.128 BYPASS [04/Oct/2019:14:10:00  1000] [censored_1] "POST /wp-login.php HTTP/1.1" 200 3972 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2019-10-04 13:09:25
92.50.249.92 attackbots
Oct  4 04:30:47 web8 sshd\[30863\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.50.249.92  user=root
Oct  4 04:30:49 web8 sshd\[30863\]: Failed password for root from 92.50.249.92 port 50286 ssh2
Oct  4 04:35:05 web8 sshd\[971\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.50.249.92  user=root
Oct  4 04:35:07 web8 sshd\[971\]: Failed password for root from 92.50.249.92 port 33838 ssh2
Oct  4 04:39:07 web8 sshd\[3042\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.50.249.92  user=root
2019-10-04 12:40:37
141.8.143.172 attack
port scan and connect, tcp 80 (http)
2019-10-04 12:59:22
8.208.22.5 attackbotsspam
Oct  4 04:50:26 game-panel sshd[1243]: Failed password for root from 8.208.22.5 port 56328 ssh2
Oct  4 04:54:29 game-panel sshd[1381]: Failed password for root from 8.208.22.5 port 40944 ssh2
2019-10-04 13:05:12
77.223.36.242 attack
Oct  4 05:58:55 host sshd\[22266\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=77.223.36.242  user=root
Oct  4 05:58:57 host sshd\[22266\]: Failed password for root from 77.223.36.242 port 51510 ssh2
...
2019-10-04 12:35:05
222.186.173.238 attack
Oct  4 06:26:14 [host] sshd[6170]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.238  user=root
Oct  4 06:26:16 [host] sshd[6170]: Failed password for root from 222.186.173.238 port 41466 ssh2
Oct  4 06:26:34 [host] sshd[6170]: Failed password for root from 222.186.173.238 port 41466 ssh2
2019-10-04 12:32:15
41.230.23.169 attackspambots
Oct  4 05:52:50 h2177944 sshd\[12427\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.230.23.169  user=root
Oct  4 05:52:52 h2177944 sshd\[12427\]: Failed password for root from 41.230.23.169 port 43227 ssh2
Oct  4 05:58:49 h2177944 sshd\[12718\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.230.23.169  user=root
Oct  4 05:58:51 h2177944 sshd\[12718\]: Failed password for root from 41.230.23.169 port 35506 ssh2
...
2019-10-04 12:32:56

Recently Reported IPs

205.136.5.241 157.230.88.27 192.23.158.120 111.82.35.154
177.225.159.101 172.28.78.127 172.26.59.230 172.16.171.140
169.19.233.91 166.141.173.253 164.125.159.252 159.3.233.251
152.89.141.190 152.155.63.33 147.42.49.201 145.20.192.1
134.199.28.59 18.230.212.164 39.144.149.211 20.55.101.155