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

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

;; QUESTION SECTION:
;49.14.85.16.			IN	A

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

;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 22 14:58:22 CST 2025
;; MSG SIZE  rcvd: 104
Host info
Host 16.85.14.49.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 16.85.14.49.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
134.175.170.87 attackspambots
Cowrie Honeypot: 3 unauthorised SSH/Telnet login attempts between 2020-08-16T15:15:58Z and 2020-08-16T15:19:42Z
2020-08-17 04:07:18
142.93.35.169 attack
142.93.35.169 - - [16/Aug/2020:21:34:27 +0100] "POST /wp-login.php HTTP/1.1" 200 1802 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
142.93.35.169 - - [16/Aug/2020:21:34:28 +0100] "POST /wp-login.php HTTP/1.1" 200 1799 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
142.93.35.169 - - [16/Aug/2020:21:34:34 +0100] "POST /wp-login.php HTTP/1.1" 200 1801 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
...
2020-08-17 04:37:52
59.11.35.70 attackbots
Aug 16 12:19:47 garden01 sshd[750920]: Invalid user ubnt from 59.11.35.70 port 55746
Aug 16 12:19:48 garden01 sshd[750922]: Invalid user support from 59.11.35.70 port 56342
Aug 16 12:19:49 garden01 sshd[750928]: Invalid user netscreen from 59.11.35.70 port 57090
Aug 16 12:19:50 garden01 sshd[750932]: Invalid user nexthink from 59.11.35.70 port 57722
Aug 16 12:19:51 garden01 sshd[750934]: Invalid user osbash from 59.11.35.70 port 58478
...
2020-08-17 04:06:04
124.89.2.42 attack
Aug 15 17:40:36 serwer sshd\[17993\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.89.2.42  user=root
Aug 15 17:40:37 serwer sshd\[17993\]: Failed password for root from 124.89.2.42 port 2177 ssh2
Aug 15 17:44:51 serwer sshd\[19512\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.89.2.42  user=root
...
2020-08-17 04:05:15
115.238.36.162 attack
Aug 16 16:35:34 vps639187 sshd\[5006\]: Invalid user jenkins from 115.238.36.162 port 49487
Aug 16 16:35:34 vps639187 sshd\[5006\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.238.36.162
Aug 16 16:35:35 vps639187 sshd\[5006\]: Failed password for invalid user jenkins from 115.238.36.162 port 49487 ssh2
...
2020-08-17 04:33:22
194.26.29.96 attackspam
Port scan
2020-08-17 04:06:51
183.6.107.248 attackspambots
Aug 16 17:23:19 funkybot sshd[25291]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.6.107.248 
Aug 16 17:23:22 funkybot sshd[25291]: Failed password for invalid user rack from 183.6.107.248 port 38660 ssh2
...
2020-08-17 04:13:14
190.210.231.34 attackbotsspam
Aug 16 22:54:53 pkdns2 sshd\[44925\]: Address 190.210.231.34 maps to customer-static-210-231-34.iplannetworks.net, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!Aug 16 22:54:53 pkdns2 sshd\[44925\]: Invalid user user from 190.210.231.34Aug 16 22:54:55 pkdns2 sshd\[44925\]: Failed password for invalid user user from 190.210.231.34 port 59776 ssh2Aug 16 22:59:39 pkdns2 sshd\[45187\]: Address 190.210.231.34 maps to customer-static-210-231-34.iplannetworks.net, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!Aug 16 22:59:39 pkdns2 sshd\[45187\]: Invalid user aga from 190.210.231.34Aug 16 22:59:41 pkdns2 sshd\[45187\]: Failed password for invalid user aga from 190.210.231.34 port 36445 ssh2
...
2020-08-17 04:22:45
218.92.0.215 attackspam
Aug 16 22:35:11 abendstille sshd\[19466\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.215  user=root
Aug 16 22:35:12 abendstille sshd\[19470\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.215  user=root
Aug 16 22:35:14 abendstille sshd\[19466\]: Failed password for root from 218.92.0.215 port 22198 ssh2
Aug 16 22:35:15 abendstille sshd\[19470\]: Failed password for root from 218.92.0.215 port 45251 ssh2
Aug 16 22:35:16 abendstille sshd\[19466\]: Failed password for root from 218.92.0.215 port 22198 ssh2
...
2020-08-17 04:35:58
23.95.224.72 attackspambots
(From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question…

My name’s Eric, I found lacostachiropractic.com after doing a quick search – you showed up near the top of the rankings, so whatever you’re doing for SEO, looks like it’s working well.

So here’s my question – what happens AFTER someone lands on your site?  Anything?

Research tells us at least 70% of the people who find your site, after a quick once-over, they disappear… forever.

That means that all the work and effort you put into getting them to show up, goes down the tubes.

Why would you want all that good work – and the great site you’ve built – go to waste?

Because the odds are they’ll just skip over calling or even grabbing their phone, leaving you high and dry.

But here’s a thought… what if you could make it super-simple for someone to raise their hand, say, “okay, let’s talk” without requiring them to even pull their cell phone from their pocket?
  
You can – thanks to revolutionary new software
2020-08-17 04:25:59
106.12.110.157 attackspam
Aug 16 19:38:41 fhem-rasp sshd[8447]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.110.157  user=root
Aug 16 19:38:43 fhem-rasp sshd[8447]: Failed password for root from 106.12.110.157 port 64776 ssh2
...
2020-08-17 04:22:02
71.246.210.34 attack
Aug 16 14:15:48 ns382633 sshd\[17507\]: Invalid user lyx from 71.246.210.34 port 48334
Aug 16 14:15:48 ns382633 sshd\[17507\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=71.246.210.34
Aug 16 14:15:50 ns382633 sshd\[17507\]: Failed password for invalid user lyx from 71.246.210.34 port 48334 ssh2
Aug 16 14:19:32 ns382633 sshd\[18046\]: Invalid user erp from 71.246.210.34 port 47184
Aug 16 14:19:32 ns382633 sshd\[18046\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=71.246.210.34
2020-08-17 04:19:48
103.238.69.138 attackbots
$f2bV_matches
2020-08-17 04:09:41
87.251.73.235 attack
Port scan on 18 port(s): 2424 2772 9025 9060 9916 10910 12728 13233 13671 21212 21214 26062 26268 31319 42422 50952 52222 63836
2020-08-17 04:25:46
111.161.74.118 attack
SSH Brute-force
2020-08-17 04:16:56

Recently Reported IPs

184.47.104.164 97.253.225.206 15.55.255.109 77.78.189.5
5.131.32.223 27.149.213.182 197.156.224.105 249.58.116.178
40.33.242.77 123.32.221.254 185.175.196.103 213.113.227.20
170.125.118.135 7.82.216.77 194.175.51.71 28.113.175.24
62.110.98.156 59.232.8.10 150.33.46.165 95.240.166.199