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

Region: Tokyo

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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;121.114.69.109.			IN	A

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

;; Query time: 177 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jan 09 05:56:03 CST 2020
;; MSG SIZE  rcvd: 118
Host info
109.69.114.121.in-addr.arpa domain name pointer i121-114-69-109.s42.a013.ap.plala.or.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
109.69.114.121.in-addr.arpa	name = i121-114-69-109.s42.a013.ap.plala.or.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
14.47.110.94 attack
Triggered by Fail2Ban at Vostok web server
2020-01-14 22:01:09
201.49.72.130 attackbotsspam
20/1/14@08:49:58: FAIL: Alarm-Network address from=201.49.72.130
20/1/14@08:49:59: FAIL: Alarm-Network address from=201.49.72.130
...
2020-01-14 21:52:57
165.22.69.88 attack
Unauthorized connection attempt detected from IP address 165.22.69.88 to port 443 [J]
2020-01-14 22:09:06
107.170.192.131 attack
Unauthorized connection attempt detected from IP address 107.170.192.131 to port 2220 [J]
2020-01-14 22:14:19
120.221.130.112 attack
" "
2020-01-14 22:02:51
54.37.159.12 attack
Unauthorized connection attempt detected from IP address 54.37.159.12 to port 2220 [J]
2020-01-14 22:23:29
188.166.68.8 attackbots
2020-01-14T13:33:56.701445shield sshd\[11806\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.166.68.8  user=root
2020-01-14T13:33:59.138029shield sshd\[11806\]: Failed password for root from 188.166.68.8 port 42154 ssh2
2020-01-14T13:37:21.485725shield sshd\[13048\]: Invalid user kelvin from 188.166.68.8 port 44974
2020-01-14T13:37:21.491851shield sshd\[13048\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.166.68.8
2020-01-14T13:37:23.075458shield sshd\[13048\]: Failed password for invalid user kelvin from 188.166.68.8 port 44974 ssh2
2020-01-14 21:52:29
104.218.48.106 attackbotsspam
this ip attack my router.
2020-01-14 21:51:47
117.6.222.107 attack
MultiHost/MultiPort Probe, Scan, Hack -
2020-01-14 21:47:56
167.114.226.137 attackspambots
Unauthorized connection attempt detected from IP address 167.114.226.137 to port 2220 [J]
2020-01-14 22:29:19
37.187.44.143 attackbots
Jan 14 10:01:54 firewall sshd[3017]: Invalid user bull from 37.187.44.143
Jan 14 10:01:56 firewall sshd[3017]: Failed password for invalid user bull from 37.187.44.143 port 34044 ssh2
Jan 14 10:04:39 firewall sshd[3074]: Invalid user alex from 37.187.44.143
...
2020-01-14 21:49:49
177.221.57.10 attack
Automatic report - Banned IP Access
2020-01-14 22:22:06
81.241.207.133 attack
Automatic report - Port Scan Attack
2020-01-14 22:28:32
121.139.225.144 attack
Unauthorized connection attempt detected from IP address 121.139.225.144 to port 22 [J]
2020-01-14 21:49:05
41.65.138.3 attack
20/1/14@08:04:14: FAIL: Alarm-Network address from=41.65.138.3
20/1/14@08:04:14: FAIL: Alarm-Network address from=41.65.138.3
...
2020-01-14 22:14:00

Recently Reported IPs

160.39.191.63 114.232.30.94 39.98.239.189 180.109.55.89
176.141.50.132 18.223.169.126 107.189.137.108 103.51.17.6
154.89.174.42 171.112.227.208 113.127.203.18 196.232.62.209
221.233.169.101 112.187.57.236 73.68.207.10 175.140.119.26
119.225.223.120 229.113.107.130 182.61.134.64 54.204.131.248