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: None

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

;; QUESTION SECTION:
;219.196.50.1.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 20 06:42:16 CST 2025
;; MSG SIZE  rcvd: 105
Host info
1.50.196.219.in-addr.arpa domain name pointer softbank219196050001.bbtec.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
1.50.196.219.in-addr.arpa	name = softbank219196050001.bbtec.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
86.84.88.219 attackbots
Scanning
2020-05-21 17:24:53
2.134.240.168 attackspambots
SSH bruteforce more then 50 syn to 22 port per 10 seconds.
2020-05-21 17:04:41
121.100.17.42 attack
Invalid user bir from 121.100.17.42 port 34930
2020-05-21 17:04:55
161.35.32.43 attack
Invalid user mul from 161.35.32.43 port 32786
2020-05-21 17:05:43
51.91.100.109 attack
Invalid user vrs from 51.91.100.109 port 55986
2020-05-21 17:25:08
106.13.80.186 attackbotsspam
2020-05-21T09:26:13.035156abusebot-6.cloudsearch.cf sshd[11869]: Invalid user wuz from 106.13.80.186 port 46296
2020-05-21T09:26:13.044816abusebot-6.cloudsearch.cf sshd[11869]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.80.186
2020-05-21T09:26:13.035156abusebot-6.cloudsearch.cf sshd[11869]: Invalid user wuz from 106.13.80.186 port 46296
2020-05-21T09:26:15.597532abusebot-6.cloudsearch.cf sshd[11869]: Failed password for invalid user wuz from 106.13.80.186 port 46296 ssh2
2020-05-21T09:30:36.481546abusebot-6.cloudsearch.cf sshd[12172]: Invalid user lql from 106.13.80.186 port 33286
2020-05-21T09:30:36.490699abusebot-6.cloudsearch.cf sshd[12172]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.80.186
2020-05-21T09:30:36.481546abusebot-6.cloudsearch.cf sshd[12172]: Invalid user lql from 106.13.80.186 port 33286
2020-05-21T09:30:38.482153abusebot-6.cloudsearch.cf sshd[12172]: Failed password 
...
2020-05-21 17:43:00
113.160.248.80 attack
May 20 23:25:45 pixelmemory sshd[832822]: Invalid user uaa from 113.160.248.80 port 55083
May 20 23:25:45 pixelmemory sshd[832822]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.160.248.80 
May 20 23:25:45 pixelmemory sshd[832822]: Invalid user uaa from 113.160.248.80 port 55083
May 20 23:25:47 pixelmemory sshd[832822]: Failed password for invalid user uaa from 113.160.248.80 port 55083 ssh2
May 20 23:28:23 pixelmemory sshd[835565]: Invalid user nic from 113.160.248.80 port 36261
...
2020-05-21 17:15:14
142.93.154.174 attack
$f2bV_matches
2020-05-21 17:44:38
62.234.83.138 attack
May 21 11:31:45 dhoomketu sshd[79946]: Invalid user lh from 62.234.83.138 port 41636
May 21 11:31:45 dhoomketu sshd[79946]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.83.138 
May 21 11:31:45 dhoomketu sshd[79946]: Invalid user lh from 62.234.83.138 port 41636
May 21 11:31:47 dhoomketu sshd[79946]: Failed password for invalid user lh from 62.234.83.138 port 41636 ssh2
May 21 11:35:27 dhoomketu sshd[80008]: Invalid user rv from 62.234.83.138 port 56304
...
2020-05-21 17:07:32
61.152.70.126 attack
2020-05-21T04:21:18.048479shield sshd\[21400\]: Invalid user jxz from 61.152.70.126 port 44453
2020-05-21T04:21:18.052321shield sshd\[21400\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.152.70.126
2020-05-21T04:21:20.356634shield sshd\[21400\]: Failed password for invalid user jxz from 61.152.70.126 port 44453 ssh2
2020-05-21T04:24:19.597015shield sshd\[22049\]: Invalid user jaq from 61.152.70.126 port 63550
2020-05-21T04:24:19.599625shield sshd\[22049\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.152.70.126
2020-05-21 17:10:21
162.245.81.36 attackspambots
Unauthorized connection attempt detected from IP address 162.245.81.36 to port 3389
2020-05-21 17:28:31
106.13.190.148 attackbotsspam
k+ssh-bruteforce
2020-05-21 17:18:44
194.61.2.94 attackspam
Wordpress hack xmlrpc or wp-login
2020-05-21 17:31:29
45.82.68.157 attackbots
[portscan] Port scan
2020-05-21 17:21:50
216.126.231.15 attack
2020-05-21T08:21:33.316797struts4.enskede.local sshd\[29930\]: Invalid user mfl from 216.126.231.15 port 36418
2020-05-21T08:21:33.323322struts4.enskede.local sshd\[29930\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=216.126.231.15
2020-05-21T08:21:36.515674struts4.enskede.local sshd\[29930\]: Failed password for invalid user mfl from 216.126.231.15 port 36418 ssh2
2020-05-21T08:30:19.382826struts4.enskede.local sshd\[29982\]: Invalid user vpk from 216.126.231.15 port 56076
2020-05-21T08:30:19.389514struts4.enskede.local sshd\[29982\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=216.126.231.15
...
2020-05-21 17:38:19

Recently Reported IPs

217.90.12.32 245.123.179.77 136.230.202.152 238.32.166.38
42.193.38.52 104.245.68.210 228.157.27.12 193.246.255.67
155.236.106.152 161.166.122.161 85.198.31.155 13.85.98.76
42.126.14.62 166.3.98.206 3.175.133.7 230.190.111.17
242.53.182.52 191.133.198.75 166.108.109.71 139.92.119.144