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: United States of America

Internet Service Provider: Amazon Technologies Inc.

Hostname: unknown

Organization: unknown

Usage Type: Search Engine Spider

Comments:
Type Details Datetime
attackspam
Aug  1 19:54:08 debian-2gb-nbg1-2 kernel: \[18562927.607247\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=54.224.140.80 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=225 ID=33222 PROTO=TCP SPT=40553 DPT=2375 WINDOW=1024 RES=0x00 SYN URGP=0
2020-08-02 04:27:35
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 54.224.140.80
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 26840
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

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

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

;; Query time: 24 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Aug 02 04:27:31 CST 2020
;; MSG SIZE  rcvd: 117
Host info
80.140.224.54.in-addr.arpa domain name pointer ec2-54-224-140-80.compute-1.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
80.140.224.54.in-addr.arpa	name = ec2-54-224-140-80.compute-1.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
200.110.174.137 attackbots
Unauthorized connection attempt detected from IP address 200.110.174.137 to port 2220 [J]
2020-01-04 23:36:37
59.173.166.1 attackbots
Unauthorized connection attempt detected from IP address 59.173.166.1 to port 23 [J]
2020-01-04 23:49:50
221.202.17.91 attackbotsspam
Honeypot attack, port: 23, PTR: PTR record not found
2020-01-04 23:24:14
179.186.195.140 attackbots
Automatic report - Port Scan Attack
2020-01-05 00:00:45
123.206.174.21 attackspam
Jan  4 16:13:19 plex sshd[14663]: Invalid user css from 123.206.174.21 port 22101
2020-01-05 00:01:20
69.165.104.14 attackspambots
Constant scan on traceroute ports
2020-01-04 23:18:45
72.48.214.68 attackbots
Jan  4 11:22:31 vps46666688 sshd[28303]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=72.48.214.68
Jan  4 11:22:33 vps46666688 sshd[28303]: Failed password for invalid user testftp from 72.48.214.68 port 57904 ssh2
...
2020-01-04 23:43:52
123.135.127.85 attackspam
firewall-block, port(s): 3389/tcp
2020-01-04 23:25:57
45.136.108.121 attackspam
Jan  4 16:28:03 debian-2gb-nbg1-2 kernel: \[411007.683665\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=45.136.108.121 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=62664 PROTO=TCP SPT=54042 DPT=3717 WINDOW=1024 RES=0x00 SYN URGP=0
2020-01-04 23:45:33
103.55.91.51 attack
Unauthorized connection attempt detected from IP address 103.55.91.51 to port 2220 [J]
2020-01-04 23:52:31
167.99.78.3 attack
Unauthorized connection attempt detected from IP address 167.99.78.3 to port 4333 [J]
2020-01-04 23:27:57
216.218.206.119 attack
3389BruteforceFW23
2020-01-04 23:31:56
5.196.12.2 attackbots
fail2ban honeypot
2020-01-04 23:36:17
222.254.34.118 attackspambots
1578143609 - 01/04/2020 14:13:29 Host: 222.254.34.118/222.254.34.118 Port: 445 TCP Blocked
2020-01-04 23:22:18
179.100.93.106 attackbotsspam
Unauthorized connection attempt detected from IP address 179.100.93.106 to port 1433 [J]
2020-01-04 23:35:12

Recently Reported IPs

153.156.82.176 222.189.100.9 112.197.176.28 245.144.88.242
118.71.149.214 113.88.13.84 94.102.54.250 87.200.157.222
4.15.139.110 212.8.176.88 3.48.251.65 111.233.90.8
23.198.254.144 152.156.251.199 178.199.104.191 167.39.253.84
89.139.59.27 14.219.222.49 52.71.188.110 118.71.222.105