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: Puerto Rico

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

;; QUESTION SECTION:
;72.50.106.149.			IN	A

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

;; Query time: 59 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 16 10:13:47 CST 2025
;; MSG SIZE  rcvd: 106
Host info
149.106.50.72.in-addr.arpa domain name pointer adsl-72-50-106-149.prtc.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
149.106.50.72.in-addr.arpa	name = adsl-72-50-106-149.prtc.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
114.219.56.219 attackspambots
Invalid user ursula from 114.219.56.219 port 44350
2020-03-22 02:36:53
63.240.240.74 attackspambots
$f2bV_matches
2020-03-22 02:50:19
212.200.103.6 attack
B: Abusive ssh attack
2020-03-22 02:57:14
118.25.3.29 attackspambots
SSH login attempts @ 2020-03-20 12:18:36
2020-03-22 02:36:24
122.51.68.196 attackspam
SSH login attempts @ 2020-03-17 12:28:42
2020-03-22 02:33:50
190.186.107.59 attackspam
Invalid user ag from 190.186.107.59 port 46826
2020-03-22 03:02:43
187.111.216.193 attackbots
Invalid user admin from 187.111.216.193 port 47912
2020-03-22 03:04:43
198.55.96.147 attack
Invalid user youtube from 198.55.96.147 port 37616
2020-03-22 03:01:02
181.48.28.13 attackbots
$f2bV_matches
2020-03-22 03:06:00
192.99.12.24 attackbots
Invalid user seiji from 192.99.12.24 port 55846
2020-03-22 03:02:07
213.32.19.142 attackspam
Mar 21 19:30:13 ns3042688 sshd\[10239\]: Invalid user teamcity from 213.32.19.142
Mar 21 19:30:15 ns3042688 sshd\[10239\]: Failed password for invalid user teamcity from 213.32.19.142 port 49050 ssh2
Mar 21 19:34:32 ns3042688 sshd\[11883\]: Invalid user ivory from 213.32.19.142
Mar 21 19:34:34 ns3042688 sshd\[11883\]: Failed password for invalid user ivory from 213.32.19.142 port 42326 ssh2
Mar 21 19:38:48 ns3042688 sshd\[12643\]: Invalid user fisnet from 213.32.19.142
...
2020-03-22 02:56:53
82.148.30.16 attack
Invalid user sammy from 82.148.30.16 port 49088
2020-03-22 02:46:22
107.170.129.141 attackbotsspam
Mar 21 13:52:04 lanister sshd[16282]: Invalid user fujiki from 107.170.129.141
Mar 21 13:52:04 lanister sshd[16282]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.170.129.141
Mar 21 13:52:04 lanister sshd[16282]: Invalid user fujiki from 107.170.129.141
Mar 21 13:52:07 lanister sshd[16282]: Failed password for invalid user fujiki from 107.170.129.141 port 59440 ssh2
2020-03-22 02:39:23
82.137.201.69 attackbots
Mar 21 15:41:48 firewall sshd[18532]: Invalid user gq from 82.137.201.69
Mar 21 15:41:51 firewall sshd[18532]: Failed password for invalid user gq from 82.137.201.69 port 50540 ssh2
Mar 21 15:43:44 firewall sshd[18654]: Invalid user decker from 82.137.201.69
...
2020-03-22 02:46:45
89.163.209.26 attack
SSH login attempts @ 2020-03-19 08:24:06
2020-03-22 02:45:37

Recently Reported IPs

148.39.234.33 13.96.42.149 35.145.191.132 225.74.76.195
222.63.20.113 146.133.234.109 39.137.113.69 28.70.173.244
57.170.60.96 37.91.223.112 185.1.3.151 42.107.36.206
208.24.227.31 62.109.242.118 232.181.82.41 158.53.207.8
140.56.184.134 22.128.187.126 199.207.119.154 58.13.83.194