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: Türkiye

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

;; QUESTION SECTION:
;95.4.50.55.			IN	A

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

;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 01 01:03:05 CST 2025
;; MSG SIZE  rcvd: 103
Host info
55.50.4.95.in-addr.arpa domain name pointer 95.4.50.55.dynamic.ttnet.com.tr.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
55.50.4.95.in-addr.arpa	name = 95.4.50.55.dynamic.ttnet.com.tr.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
107.174.228.140 attackbots
(From eric@talkwithwebvisitor.com) Hey, this is Eric and I ran across advancedchirosolutions.com a few minutes ago.

Looks great… but now what?

By that I mean, when someone like me finds your website – either through Search or just bouncing around – what happens next?  Do you get a lot of leads from your site, or at least enough to make you happy?

Honestly, most business websites fall a bit short when it comes to generating paying customers. Studies show that 70% of a site’s visitors disappear and are gone forever after just a moment.

Here’s an idea…
 
How about making it really EASY for every visitor who shows up to get a personal phone call you as soon as they hit your site…
 
You can –
  
Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number.  It signals you the moment they let you know they’re interested – so that you can talk to that lead while they’re literally looking over your site.

CLICK HERE http:
2020-05-07 00:22:03
117.200.58.93 attack
Unauthorized connection attempt from IP address 117.200.58.93 on Port 445(SMB)
2020-05-06 23:39:58
157.230.133.15 attackbots
firewall-block, port(s): 18777/tcp
2020-05-06 23:44:03
151.80.34.219 attack
May  6 14:52:46 ns3033917 sshd[17607]: Invalid user demo from 151.80.34.219 port 9224
May  6 14:52:48 ns3033917 sshd[17607]: Failed password for invalid user demo from 151.80.34.219 port 9224 ssh2
May  6 15:48:53 ns3033917 sshd[18054]: Invalid user arkserver from 151.80.34.219 port 9224
...
2020-05-06 23:50:11
104.248.43.155 attack
firewall-block, port(s): 17224/tcp
2020-05-06 23:46:18
117.69.47.163 attackbotsspam
Spammer_1
2020-05-07 00:10:45
89.248.168.202 attackspam
firewall-block, port(s): 6318/tcp
2020-05-07 00:22:24
152.32.222.196 attackbotsspam
2020-05-06T13:52:27.199038server.espacesoutien.com sshd[7408]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.32.222.196
2020-05-06T13:52:27.187442server.espacesoutien.com sshd[7408]: Invalid user ubuntu from 152.32.222.196 port 37344
2020-05-06T13:52:29.477752server.espacesoutien.com sshd[7408]: Failed password for invalid user ubuntu from 152.32.222.196 port 37344 ssh2
2020-05-06T13:56:28.460640server.espacesoutien.com sshd[15959]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.32.222.196  user=root
2020-05-06T13:56:30.157398server.espacesoutien.com sshd[15959]: Failed password for root from 152.32.222.196 port 39590 ssh2
...
2020-05-06 23:48:38
180.76.98.239 attack
May  6 14:16:07 sip sshd[23589]: Failed password for root from 180.76.98.239 port 49928 ssh2
May  6 14:19:57 sip sshd[25051]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.98.239
May  6 14:19:58 sip sshd[25051]: Failed password for invalid user team1 from 180.76.98.239 port 57996 ssh2
2020-05-07 00:02:19
57.100.98.105 attackspam
$f2bV_matches
2020-05-06 23:52:00
92.222.26.88 attackbotsspam
[AUTOMATIC REPORT] - 33 tries in total - SSH BRUTE FORCE - IP banned
2020-05-07 00:11:41
49.234.192.24 attackbotsspam
May  6 16:33:11 sxvn sshd[628231]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.192.24
2020-05-06 23:59:45
185.50.149.9 attack
May  6 17:52:26 relay postfix/smtpd\[1606\]: warning: unknown\[185.50.149.9\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
May  6 17:52:46 relay postfix/smtpd\[3804\]: warning: unknown\[185.50.149.9\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
May  6 18:00:36 relay postfix/smtpd\[31974\]: warning: unknown\[185.50.149.9\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
May  6 18:00:58 relay postfix/smtpd\[1606\]: warning: unknown\[185.50.149.9\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
May  6 18:10:56 relay postfix/smtpd\[1606\]: warning: unknown\[185.50.149.9\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-05-07 00:20:45
180.96.63.162 attack
May  6 16:27:02 pve1 sshd[27472]: Failed password for root from 180.96.63.162 port 55325 ssh2
...
2020-05-06 23:52:50
67.205.173.227 attackspambots
" "
2020-05-07 00:16:04

Recently Reported IPs

164.97.197.26 15.23.86.208 28.155.212.200 99.125.60.107
37.179.231.201 45.86.198.203 187.254.82.163 242.86.61.148
237.102.201.121 155.193.20.94 179.114.59.180 59.9.251.247
142.224.76.79 66.32.238.20 62.109.100.115 224.36.157.71
2.87.255.229 58.103.15.190 34.3.74.180 13.66.61.253