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

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

;; QUESTION SECTION:
;107.22.55.140.			IN	A

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

;; Query time: 59 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Apr 07 00:30:46 CST 2022
;; MSG SIZE  rcvd: 106
Host info
140.55.22.107.in-addr.arpa domain name pointer ec2-107-22-55-140.compute-1.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
140.55.22.107.in-addr.arpa	name = ec2-107-22-55-140.compute-1.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
67.20.76.190 attackbots
SSH login attempts.
2020-02-17 20:44:40
203.201.62.36 attack
20/2/17@00:38:46: FAIL: Alarm-Network address from=203.201.62.36
20/2/17@00:38:47: FAIL: Alarm-Network address from=203.201.62.36
...
2020-02-17 21:10:03
5.135.198.62 attackspambots
2020-02-17T06:06:39.6182411240 sshd\[16056\]: Invalid user dvs from 5.135.198.62 port 57823
2020-02-17T06:06:39.6219101240 sshd\[16056\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.135.198.62
2020-02-17T06:06:41.9080551240 sshd\[16056\]: Failed password for invalid user dvs from 5.135.198.62 port 57823 ssh2
...
2020-02-17 21:29:29
103.210.144.207 attack
Automatic report - Port Scan Attack
2020-02-17 21:00:08
196.206.204.139 attackspam
MultiHost/MultiPort Probe, Scan, Hack -
2020-02-17 21:31:00
5.188.86.216 attack
SSH login attempts.
2020-02-17 21:24:04
49.88.112.68 attack
Tried sshing with brute force.
2020-02-17 21:28:58
125.165.10.202 attack
20/2/17@02:29:59: FAIL: Alarm-Network address from=125.165.10.202
20/2/17@02:29:59: FAIL: Alarm-Network address from=125.165.10.202
...
2020-02-17 20:51:07
51.161.8.152 attackspambots
Feb 17 00:27:30 plusreed sshd[18497]: Invalid user ncmdbuser from 51.161.8.152
...
2020-02-17 21:18:28
104.47.17.161 attackspam
SSH login attempts.
2020-02-17 21:22:49
117.1.244.12 attackspam
Automatic report - Port Scan Attack
2020-02-17 21:14:12
104.248.88.100 attackspam
WordPress login Brute force / Web App Attack on client site.
2020-02-17 21:13:05
123.58.5.243 attackbots
$f2bV_matches
2020-02-17 20:53:53
178.128.52.32 attackspambots
Feb 17 08:05:11 ws19vmsma01 sshd[104662]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.52.32
Feb 17 08:05:13 ws19vmsma01 sshd[104662]: Failed password for invalid user spark from 178.128.52.32 port 57630 ssh2
...
2020-02-17 20:42:02
193.169.252.230 attack
SSH login attempts.
2020-02-17 21:13:55

Recently Reported IPs

107.22.52.141 107.22.64.80 107.22.94.45 107.22.99.82
107.23.11.150 107.23.12.249 107.23.148.136 107.23.150.230
107.23.191.89 107.23.217.152 107.23.235.31 107.23.236.27
107.23.25.54 107.23.68.208 107.23.7.247 107.23.70.96
107.23.72.128 107.23.88.170 107.6.184.61 107.6.189.218