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

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

;; QUESTION SECTION:
;18.215.104.8.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 18:58:18 CST 2022
;; MSG SIZE  rcvd: 105
Host info
8.104.215.18.in-addr.arpa domain name pointer ec2-18-215-104-8.compute-1.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
8.104.215.18.in-addr.arpa	name = ec2-18-215-104-8.compute-1.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
118.24.38.12 attackbots
Unauthorized connection attempt detected from IP address 118.24.38.12 to port 2220 [J]
2020-02-05 08:37:20
106.12.93.114 attack
Feb  4 22:34:57 srv01 sshd[22009]: Invalid user riehle from 106.12.93.114 port 59646
Feb  4 22:34:57 srv01 sshd[22009]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.93.114
Feb  4 22:34:57 srv01 sshd[22009]: Invalid user riehle from 106.12.93.114 port 59646
Feb  4 22:34:59 srv01 sshd[22009]: Failed password for invalid user riehle from 106.12.93.114 port 59646 ssh2
Feb  4 22:37:25 srv01 sshd[22251]: Invalid user downloads from 106.12.93.114 port 54000
...
2020-02-05 08:56:11
89.40.114.6 attack
Unauthorized connection attempt detected from IP address 89.40.114.6 to port 2220 [J]
2020-02-05 08:57:59
203.197.214.231 attack
Unauthorized connection attempt detected from IP address 203.197.214.231 to port 1433 [J]
2020-02-05 08:47:10
124.156.50.51 attackbots
Unauthorized connection attempt detected from IP address 124.156.50.51 to port 8899 [J]
2020-02-05 08:51:04
92.118.38.57 botsattack
Dictionary attack from 92.118.38.57  SASL LOGIN authentication failed
2020-02-05 08:30:09
122.51.5.69 attack
Unauthorized connection attempt detected from IP address 122.51.5.69 to port 2220 [J]
2020-02-05 08:35:02
150.109.167.32 attackbotsspam
Unauthorized connection attempt detected from IP address 150.109.167.32 to port 8083 [J]
2020-02-05 08:49:53
187.35.189.101 attackbotsspam
Unauthorized connection attempt detected from IP address 187.35.189.101 to port 23 [J]
2020-02-05 08:28:46
1.34.120.227 attackspam
Unauthorized connection attempt detected from IP address 1.34.120.227 to port 4567 [J]
2020-02-05 09:04:28
177.130.252.251 attackspambots
Unauthorized connection attempt detected from IP address 177.130.252.251 to port 23 [J]
2020-02-05 08:31:23
185.173.35.61 attackspambots
Unauthorized connection attempt detected from IP address 185.173.35.61 to port 1026 [J]
2020-02-05 08:29:08
59.152.62.27 attackbots
Unauthorized connection attempt detected from IP address 59.152.62.27 to port 23 [J]
2020-02-05 08:43:30
5.78.20.186 attackspambots
Unauthorized connection attempt detected from IP address 5.78.20.186 to port 23 [J]
2020-02-05 09:03:34
83.110.222.101 attack
Unauthorized connection attempt detected from IP address 83.110.222.101 to port 23 [J]
2020-02-05 08:41:13

Recently Reported IPs

18.215.107.142 18.215.103.147 18.215.102.223 18.215.10.58
18.215.102.8 18.215.109.74 18.215.109.139 18.215.110.144
18.215.112.233 18.215.113.115 18.215.119.85 18.215.138.196
18.215.13.173 18.215.131.103 18.215.111.139 18.215.152.45
18.215.17.40 18.215.120.127 18.215.199.134 18.215.197.85