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.49.69.42
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 34007
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;163.49.69.42.			IN	A

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

;; Query time: 60 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun May 28 14:20:06 CST 2023
;; MSG SIZE  rcvd: 105
Host info
Host 42.69.49.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 42.69.49.163.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
202.29.230.21 attackspambots
$f2bV_matches
2020-02-11 03:10:25
80.67.223.41 attackspambots
MultiHost/MultiPort Probe, Scan, Hack -
2020-02-11 02:57:32
216.117.55.0 attack
ICMP MH Probe, Scan /Distributed -
2020-02-11 02:59:23
178.157.251.180 attackbotsspam
firewall-block, port(s): 57623/udp
2020-02-11 03:09:21
202.29.236.42 attackbots
$f2bV_matches
2020-02-11 03:08:10
202.29.98.39 attack
$f2bV_matches
2020-02-11 03:02:07
104.129.204.80 attackproxy
appears to ipv6 to ipv4 redirect ssl with dns cache poisoning
2020-02-11 02:35:32
202.29.33.74 attack
$f2bV_matches
2020-02-11 03:06:48
176.9.190.40 attackspambots
Hits on port : 22
2020-02-11 03:06:03
178.32.221.142 attackspam
Feb 10 18:00:08 vpn01 sshd[9021]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.32.221.142
Feb 10 18:00:09 vpn01 sshd[9021]: Failed password for invalid user hhc from 178.32.221.142 port 43965 ssh2
...
2020-02-11 02:49:48
200.86.33.140 attackspambots
Feb 10 14:56:39 dedicated sshd[23053]: Failed password for invalid user qfa from 200.86.33.140 port 10939 ssh2
Feb 10 14:56:37 dedicated sshd[23053]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.86.33.140 
Feb 10 14:56:37 dedicated sshd[23053]: Invalid user qfa from 200.86.33.140 port 10939
Feb 10 14:56:39 dedicated sshd[23053]: Failed password for invalid user qfa from 200.86.33.140 port 10939 ssh2
Feb 10 14:59:27 dedicated sshd[23589]: Invalid user snw from 200.86.33.140 port 10428
2020-02-11 03:08:27
202.29.70.46 attack
$f2bV_matches
2020-02-11 03:03:09
162.243.128.11 attackspam
Port probing on unauthorized port 520
2020-02-11 02:48:37
178.69.128.30 attack
20/2/10@08:38:20: FAIL: Alarm-Network address from=178.69.128.30
...
2020-02-11 03:04:39
202.45.147.125 attack
$f2bV_matches
2020-02-11 02:56:31

Recently Reported IPs

233.89.17.53 69.128.204.106 100.65.141.113 178.135.48.237
209.232.225.83 132.125.201.236 240.34.14.216 152.5.61.147
194.86.101.218 54.9.161.124 75.219.94.217 23.64.157.199
91.129.41.172 36.76.191.162 191.252.132.0 13.111.103.81
142.112.24.18 149.20.186.29 170.233.186.223 179.64.40.12