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

;; QUESTION SECTION:
;159.51.49.80.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 11 02:36:48 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 80.49.51.159.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 80.49.51.159.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
139.217.218.255 attackspam
Unauthorized connection attempt detected from IP address 139.217.218.255 to port 2220 [J]
2020-01-22 21:59:48
139.59.17.118 attackspam
Jan 22 13:51:56 sd-53420 sshd\[17564\]: Invalid user tester from 139.59.17.118
Jan 22 13:51:56 sd-53420 sshd\[17564\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.17.118
Jan 22 13:51:58 sd-53420 sshd\[17564\]: Failed password for invalid user tester from 139.59.17.118 port 47316 ssh2
Jan 22 13:53:23 sd-53420 sshd\[17780\]: User root from 139.59.17.118 not allowed because none of user's groups are listed in AllowGroups
Jan 22 13:53:23 sd-53420 sshd\[17780\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.17.118  user=root
...
2020-01-22 21:27:36
181.164.109.34 attack
Unauthorized connection attempt detected from IP address 181.164.109.34 to port 1433 [J]
2020-01-22 21:55:44
212.1.64.146 attackspam
Unauthorized connection attempt detected from IP address 212.1.64.146 to port 85 [J]
2020-01-22 21:49:34
50.209.11.121 attackbotsspam
Unauthorized connection attempt detected from IP address 50.209.11.121 to port 8080 [J]
2020-01-22 21:43:21
223.26.48.64 attackbotsspam
Unauthorized connection attempt detected from IP address 223.26.48.64 to port 8080 [J]
2020-01-22 21:47:31
219.155.176.2 attack
Unauthorized connection attempt detected from IP address 219.155.176.2 to port 8080 [J]
2020-01-22 21:48:25
87.10.217.225 attack
Unauthorized connection attempt detected from IP address 87.10.217.225 to port 85 [J]
2020-01-22 21:38:05
220.191.208.139 attack
Port 1433 Scan
2020-01-22 21:47:53
212.34.99.44 attackspam
Unauthorized connection attempt detected from IP address 212.34.99.44 to port 23 [J]
2020-01-22 21:49:10
106.12.54.13 attackspambots
Unauthorized connection attempt detected from IP address 106.12.54.13 to port 2220 [J]
2020-01-22 22:07:24
114.7.163.86 attackbots
Unauthorized connection attempt detected from IP address 114.7.163.86 to port 2220 [J]
2020-01-22 22:06:05
122.116.206.25 attack
Unauthorized connection attempt detected from IP address 122.116.206.25 to port 4567 [J]
2020-01-22 21:28:46
143.255.242.181 attackbotsspam
Unauthorized connection attempt detected from IP address 143.255.242.181 to port 8080 [J]
2020-01-22 21:27:20
5.42.76.231 attackbots
Unauthorized connection attempt detected from IP address 5.42.76.231 to port 23 [J]
2020-01-22 21:47:01

Recently Reported IPs

129.6.224.136 104.142.105.102 252.73.250.127 167.117.67.112
133.156.203.69 200.61.198.130 147.155.225.43 239.81.156.238
144.35.168.95 57.255.213.53 14.115.241.53 171.186.249.155
238.206.206.213 127.168.69.133 28.99.178.137 240.195.156.177
1.110.135.126 166.231.221.69 137.167.49.212 164.153.155.30