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

;; QUESTION SECTION:
;18.119.22.68.			IN	A

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

;; Query time: 46 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 18:45:24 CST 2022
;; MSG SIZE  rcvd: 105
Host info
68.22.119.18.in-addr.arpa domain name pointer ec2-18-119-22-68.us-east-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
68.22.119.18.in-addr.arpa	name = ec2-18-119-22-68.us-east-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
201.162.105.225 attackspam
Aug 29 18:44:16 lcdev sshd\[2691\]: Invalid user es@123 from 201.162.105.225
Aug 29 18:44:16 lcdev sshd\[2691\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.162.105.225
Aug 29 18:44:18 lcdev sshd\[2691\]: Failed password for invalid user es@123 from 201.162.105.225 port 45653 ssh2
Aug 29 18:50:04 lcdev sshd\[3235\]: Invalid user ade from 201.162.105.225
Aug 29 18:50:04 lcdev sshd\[3235\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.162.105.225
2019-08-30 13:06:50
101.109.119.58 attackspam
SMB Server BruteForce Attack
2019-08-30 13:19:50
167.71.64.9 attackspam
Automatic report - Banned IP Access
2019-08-30 13:13:21
121.50.170.124 attackbots
SSH Brute-Force reported by Fail2Ban
2019-08-30 13:18:27
46.105.157.97 attackspambots
Aug 30 06:06:03 icinga sshd[8050]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.105.157.97
Aug 30 06:06:05 icinga sshd[8050]: Failed password for invalid user prashant from 46.105.157.97 port 64995 ssh2
...
2019-08-30 12:47:13
149.129.251.152 attackspambots
Aug 29 20:36:24 vps200512 sshd\[7281\]: Invalid user emo from 149.129.251.152
Aug 29 20:36:24 vps200512 sshd\[7281\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=149.129.251.152
Aug 29 20:36:25 vps200512 sshd\[7281\]: Failed password for invalid user emo from 149.129.251.152 port 57376 ssh2
Aug 29 20:41:11 vps200512 sshd\[7449\]: Invalid user spoj0 from 149.129.251.152
Aug 29 20:41:11 vps200512 sshd\[7449\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=149.129.251.152
2019-08-30 13:14:54
80.211.136.203 attackbotsspam
Automated report - ssh fail2ban:
Aug 30 05:59:41 authentication failure 
Aug 30 05:59:44 wrong password, user=volvo, port=48356, ssh2
Aug 30 06:03:57 authentication failure
2019-08-30 12:39:55
54.36.150.139 attack
Automatic report - Banned IP Access
2019-08-30 13:03:21
152.136.171.14 attackspam
2019-08-30T02:47:13.714003abusebot.cloudsearch.cf sshd\[17871\]: Invalid user london from 152.136.171.14 port 57138
2019-08-30 12:50:58
177.1.214.207 attackspambots
Invalid user cap from 177.1.214.207 port 31713
2019-08-30 13:11:59
163.172.182.255 attack
Aug 30 01:34:18 heissa sshd\[27828\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=163.172.182.255  user=games
Aug 30 01:34:20 heissa sshd\[27828\]: Failed password for games from 163.172.182.255 port 44162 ssh2
Aug 30 01:38:02 heissa sshd\[28186\]: Invalid user java from 163.172.182.255 port 59414
Aug 30 01:38:02 heissa sshd\[28186\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=163.172.182.255
Aug 30 01:38:04 heissa sshd\[28186\]: Failed password for invalid user java from 163.172.182.255 port 59414 ssh2
2019-08-30 12:42:31
54.36.149.62 attack
Automatic report - Banned IP Access
2019-08-30 13:03:47
128.199.240.120 attackbots
Invalid user docker from 128.199.240.120 port 38668
2019-08-30 13:16:57
68.183.83.214 attackbots
Aug 30 04:24:03 bouncer sshd\[28815\]: Invalid user jsclient from 68.183.83.214 port 39240
Aug 30 04:24:03 bouncer sshd\[28815\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.83.214 
Aug 30 04:24:05 bouncer sshd\[28815\]: Failed password for invalid user jsclient from 68.183.83.214 port 39240 ssh2
...
2019-08-30 12:46:33
180.168.198.142 attack
Aug 30 03:30:51 MK-Soft-Root2 sshd\[25687\]: Invalid user teamspeak from 180.168.198.142 port 56088
Aug 30 03:30:51 MK-Soft-Root2 sshd\[25687\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.168.198.142
Aug 30 03:30:53 MK-Soft-Root2 sshd\[25687\]: Failed password for invalid user teamspeak from 180.168.198.142 port 56088 ssh2
...
2019-08-30 13:01:34

Recently Reported IPs

18.119.135.157 18.119.144.224 18.119.27.126 18.119.152.173
18.119.154.66 18.119.50.47 18.119.53.135 18.119.55.187
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