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

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:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 163.42.222.173
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 2105
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;163.42.222.173.			IN	A

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

;; Query time: 58 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Dec 28 14:40:57 CST 2021
;; MSG SIZE  rcvd: 107
Host info
Host 173.222.42.163.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 173.222.42.163.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
110.138.2.84 attack
1589880952 - 05/19/2020 11:35:52 Host: 110.138.2.84/110.138.2.84 Port: 445 TCP Blocked
2020-05-20 03:51:01
188.35.187.50 attack
Invalid user qjb from 188.35.187.50 port 59112
2020-05-20 03:59:13
106.124.132.105 attackbots
May 19 06:55:34 auw2 sshd\[26280\]: Invalid user ayt from 106.124.132.105
May 19 06:55:34 auw2 sshd\[26280\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.124.132.105
May 19 06:55:36 auw2 sshd\[26280\]: Failed password for invalid user ayt from 106.124.132.105 port 54738 ssh2
May 19 07:00:44 auw2 sshd\[26728\]: Invalid user bfq from 106.124.132.105
May 19 07:00:44 auw2 sshd\[26728\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.124.132.105
2020-05-20 03:58:02
137.74.246.160 attack
spam 19 May 2020 10:01 Received: from pablo.finkarts.com ([137.74.246.160]) Return-Path: 
2020-05-20 04:10:38
139.162.75.112 attackbotsspam
May 19 19:21:49 *** sshd[15536]: Did not receive identification string from 139.162.75.112
2020-05-20 03:51:52
118.25.18.30 attackbotsspam
May 19 11:35:45 host sshd[12257]: Invalid user wlw from 118.25.18.30 port 38472
...
2020-05-20 03:52:18
142.93.204.221 attackbotsspam
wp-login.php
2020-05-20 03:58:29
167.114.98.234 attackspam
detected by Fail2Ban
2020-05-20 04:09:51
157.230.125.122 attack
60/tcp 19947/tcp 24982/tcp...
[2020-04-12/05-18]76pkt,28pt.(tcp)
2020-05-20 04:25:16
49.145.233.141 attackspambots
1589880890 - 05/19/2020 11:34:50 Host: 49.145.233.141/49.145.233.141 Port: 445 TCP Blocked
2020-05-20 04:10:16
49.235.149.108 attack
May 19 11:35:09 lnxded64 sshd[23602]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.149.108
2020-05-20 04:05:30
89.151.178.48 attackbots
Invalid user agd from 89.151.178.48 port 5924
2020-05-20 04:18:37
185.220.101.20 attack
xmlrpc attack
2020-05-20 04:01:48
203.160.57.250 attackbots
Portscan - Unauthorized connection attempt
2020-05-20 03:52:34
156.193.15.38 attackbotsspam
1589880976 - 05/19/2020 11:36:16 Host: 156.193.15.38/156.193.15.38 Port: 22 TCP Blocked
2020-05-20 03:47:56

Recently Reported IPs

67.50.105.171 199.9.170.9 253.6.75.227 85.51.8.188
245.34.151.49 47.148.191.8 250.166.148.99 37.1.222.240
158.131.245.152 45.182.60.94 69.51.247.157 45.247.57.240
80.45.9.164 30.191.40.217 244.85.144.207 49.65.39.162
47.215.190.199 98.183.128.106 219.76.79.145 114.9.226.186