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

;; QUESTION SECTION:
;18.119.55.187.			IN	A

;; AUTHORITY SECTION:
.			190	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:45:26 CST 2022
;; MSG SIZE  rcvd: 106
Host info
187.55.119.18.in-addr.arpa domain name pointer ec2-18-119-55-187.us-east-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
187.55.119.18.in-addr.arpa	name = ec2-18-119-55-187.us-east-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
223.71.167.165 attack
Unauthorized connection attempt detected from IP address 223.71.167.165 to port 4712 [J]
2020-01-18 06:59:30
79.124.62.34 attack
Jan 17 22:44:50 debian-2gb-nbg1-2 kernel: \[1556782.436363\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=79.124.62.34 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=57146 PROTO=TCP SPT=56468 DPT=3369 WINDOW=1024 RES=0x00 SYN URGP=0
2020-01-18 07:22:07
46.228.199.111 attackbots
1579297725 - 01/17/2020 22:48:45 Host: 46.228.199.111/46.228.199.111 Port: 21 TCP Blocked
2020-01-18 06:39:04
189.236.233.49 attackbotsspam
20/1/17@16:11:38: FAIL: Alarm-Network address from=189.236.233.49
20/1/17@16:11:38: FAIL: Alarm-Network address from=189.236.233.49
...
2020-01-18 06:33:03
128.199.171.89 attackspam
AbusiveCrawling
2020-01-18 06:52:46
36.70.55.193 attackspam
RDP Brute-Force (Grieskirchen RZ2)
2020-01-18 06:49:07
37.17.250.101 attackbots
Unauthorized connection attempt detected from IP address 37.17.250.101 to port 2223 [J]
2020-01-18 07:27:05
173.239.37.163 attackspambots
Fail2Ban Ban Triggered
2020-01-18 07:09:27
94.50.162.191 attackspambots
Honeypot attack, port: 445, PTR: PTR record not found
2020-01-18 06:30:42
89.248.168.63 attackspambots
01/17/2020-18:10:09.431167 89.248.168.63 Protocol: 6 ET DROP Dshield Block Listed Source group 1
2020-01-18 07:18:21
185.209.0.89 attack
Multiport scan : 15 ports scanned 4155 4200 4250 4503 4506 4508 4510 4555 4600 5501 5504 5505 5506 5508 5510
2020-01-18 07:04:45
24.176.206.12 attackspam
Honeypot attack, port: 81, PTR: 24-176-206-12.static.mtpk.ca.charter.com.
2020-01-18 06:51:44
62.12.115.116 attackspam
Unauthorized connection attempt detected from IP address 62.12.115.116 to port 2220 [J]
2020-01-18 06:30:57
78.100.194.80 attackspambots
Unauthorized connection attempt detected from IP address 78.100.194.80 to port 80 [J]
2020-01-18 06:54:16
49.88.112.63 attack
Jan 17 23:52:52 nextcloud sshd\[13769\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.63  user=root
Jan 17 23:52:54 nextcloud sshd\[13769\]: Failed password for root from 49.88.112.63 port 56247 ssh2
Jan 17 23:52:57 nextcloud sshd\[13769\]: Failed password for root from 49.88.112.63 port 56247 ssh2
...
2020-01-18 06:53:14

Recently Reported IPs

18.119.53.135 18.119.55.218 18.119.36.67 18.119.75.177
18.119.60.80 18.119.71.113 18.119.75.25 18.130.115.115
18.119.76.188 18.119.70.142 18.130.120.54 18.130.115.174
18.130.130.251 18.119.94.169 18.130.130.48 18.130.139.188
18.130.134.17 18.130.129.227 18.130.145.51 18.130.168.176