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 (the)

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

;; QUESTION SECTION:
;50.120.99.22.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 06 22:23:55 CST 2025
;; MSG SIZE  rcvd: 105
Host info
22.99.120.50.in-addr.arpa domain name pointer 50-120-99-22.drr01.athn.oh.frontiernet.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
22.99.120.50.in-addr.arpa	name = 50-120-99-22.drr01.athn.oh.frontiernet.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
123.16.20.132 attack
20/7/9@23:54:03: FAIL: Alarm-Network address from=123.16.20.132
...
2020-07-10 15:11:31
188.166.9.162 attackbots
WordPress wp-login brute force :: 188.166.9.162 0.136 - [10/Jul/2020:06:11:48  0000] [censored_1] "POST /wp-login.php HTTP/1.1" 200 1837 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" "HTTP/1.1"
2020-07-10 15:22:03
222.99.52.216 attackspambots
Jul 10 08:01:54 pkdns2 sshd\[1294\]: Invalid user nilsputnins from 222.99.52.216Jul 10 08:01:56 pkdns2 sshd\[1294\]: Failed password for invalid user nilsputnins from 222.99.52.216 port 61393 ssh2Jul 10 08:05:34 pkdns2 sshd\[1560\]: Invalid user supportpass from 222.99.52.216Jul 10 08:05:36 pkdns2 sshd\[1560\]: Failed password for invalid user supportpass from 222.99.52.216 port 59066 ssh2Jul 10 08:09:07 pkdns2 sshd\[1721\]: Invalid user atanasio from 222.99.52.216Jul 10 08:09:09 pkdns2 sshd\[1721\]: Failed password for invalid user atanasio from 222.99.52.216 port 56755 ssh2
...
2020-07-10 15:16:21
20.52.41.92 attackbots
Did not receive identification string
2020-07-10 15:14:41
172.86.125.116 attackspambots
Too many connections or unauthorized access detected from Arctic banned ip
2020-07-10 15:04:28
188.166.20.141 attack
188.166.20.141 - - [10/Jul/2020:07:48:35 +0200] "POST /xmlrpc.php HTTP/1.1" 403 146 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
188.166.20.141 - - [10/Jul/2020:07:59:45 +0200] "POST /xmlrpc.php HTTP/1.1" 403 146 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
...
2020-07-10 15:03:55
35.234.28.121 attack
WordPress wp-login brute force :: 35.234.28.121 0.096 BYPASS [10/Jul/2020:04:08:37  0000] [censored_2] "POST /wp-login.php HTTP/1.1" 200 2003 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2020-07-10 15:03:21
61.107.72.165 attack
Jul 10 12:00:52 ns1 postfix/smtpd\[17899\]: warning: unknown\[61.107.72.165\]: SASL LOGIN authentication failed: authentication failure
Jul 10 12:00:55 ns1 postfix/smtpd\[17899\]: warning: unknown\[61.107.72.165\]: SASL LOGIN authentication failed: authentication failure
Jul 10 12:27:32 ns1 postfix/smtpd\[18330\]: warning: unknown\[61.107.72.165\]: SASL LOGIN authentication failed: authentication failure
Jul 10 12:27:35 ns1 postfix/smtpd\[18330\]: warning: unknown\[61.107.72.165\]: SASL LOGIN authentication failed: authentication failure
Jul 10 12:54:02 ns1 postfix/smtpd\[18675\]: warning: unknown\[61.107.72.165\]: SASL LOGIN authentication failed: authentication failure
...
2020-07-10 15:12:27
54.37.21.211 attackbotsspam
Automatic report - XMLRPC Attack
2020-07-10 15:01:53
118.25.14.22 attack
Jul 10 08:08:09 journals sshd\[17569\]: Invalid user wata from 118.25.14.22
Jul 10 08:08:09 journals sshd\[17569\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.25.14.22
Jul 10 08:08:11 journals sshd\[17569\]: Failed password for invalid user wata from 118.25.14.22 port 50962 ssh2
Jul 10 08:11:09 journals sshd\[17960\]: Invalid user ngreen from 118.25.14.22
Jul 10 08:11:09 journals sshd\[17960\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.25.14.22
...
2020-07-10 14:58:04
218.92.0.249 attackbotsspam
Jul  9 21:04:48 web9 sshd\[5040\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.249  user=root
Jul  9 21:04:51 web9 sshd\[5040\]: Failed password for root from 218.92.0.249 port 20428 ssh2
Jul  9 21:04:54 web9 sshd\[5040\]: Failed password for root from 218.92.0.249 port 20428 ssh2
Jul  9 21:04:57 web9 sshd\[5040\]: Failed password for root from 218.92.0.249 port 20428 ssh2
Jul  9 21:05:00 web9 sshd\[5040\]: Failed password for root from 218.92.0.249 port 20428 ssh2
2020-07-10 15:09:59
51.83.68.213 attackbotsspam
odoo8
...
2020-07-10 15:10:23
111.26.172.222 attackspambots
(smtpauth) Failed SMTP AUTH login from 111.26.172.222 (CN/China/-): 5 in the last 3600 secs
2020-07-10 14:58:23
35.185.133.141 attackbotsspam
$f2bV_matches
2020-07-10 15:22:43
220.133.250.253 attackspam
Port probing on unauthorized port 85
2020-07-10 15:27:35

Recently Reported IPs

46.198.221.129 59.37.71.107 204.165.70.127 204.197.225.63
169.133.158.2 2.177.220.168 203.162.0.72 235.102.155.192
244.212.213.84 103.153.157.19 84.115.97.164 108.89.155.1
47.67.145.27 54.213.250.219 38.187.158.139 66.161.31.175
147.28.68.235 200.17.227.113 35.30.95.230 181.128.73.208