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: Porto Alegre

Region: Rio Grande do Sul

Country: Brazil

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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;201.72.14.85.			IN	A

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

;; Query time: 112 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 02 02:29:02 CST 2020
;; MSG SIZE  rcvd: 116
Host info
Host 85.14.72.201.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 85.14.72.201.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
182.61.54.14 attackbotsspam
$f2bV_matches
2019-11-10 19:32:23
217.182.252.63 attack
Automatic report - Banned IP Access
2019-11-10 19:40:16
47.17.177.110 attackbots
Nov 10 12:16:34 legacy sshd[22568]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=47.17.177.110
Nov 10 12:16:37 legacy sshd[22568]: Failed password for invalid user brgs from 47.17.177.110 port 51958 ssh2
Nov 10 12:22:12 legacy sshd[22719]: Failed password for root from 47.17.177.110 port 60922 ssh2
...
2019-11-10 19:37:19
82.243.236.16 attackspambots
Nov 10 10:32:14 **** sshd[31336]: User root from 82.243.236.16 not allowed because not listed in AllowUsers
2019-11-10 19:36:40
31.214.157.4 attackbots
*Port Scan* detected from 31.214.157.4 (NL/Netherlands/-). 4 hits in the last 271 seconds
2019-11-10 19:54:30
39.135.1.156 attackbotsspam
39.135.1.156 was recorded 5 times by 1 hosts attempting to connect to the following ports: 80,6380,8080,1433,6379. Incident counter (4h, 24h, all-time): 5, 11, 50
2019-11-10 19:59:05
73.189.112.132 attack
2019-11-10T10:07:18.307117abusebot-4.cloudsearch.cf sshd\[14766\]: Invalid user welcome from 73.189.112.132 port 59560
2019-11-10 19:37:58
96.251.179.115 attackspambots
Nov 10 13:59:46 server sshd\[378\]: Invalid user gm_prop from 96.251.179.115
Nov 10 13:59:46 server sshd\[378\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=96.251.179.115 
Nov 10 13:59:48 server sshd\[378\]: Failed password for invalid user gm_prop from 96.251.179.115 port 38944 ssh2
Nov 10 14:16:19 server sshd\[5020\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=96.251.179.115  user=root
Nov 10 14:16:21 server sshd\[5020\]: Failed password for root from 96.251.179.115 port 59856 ssh2
...
2019-11-10 19:43:46
164.132.27.202 attackbots
detected by Fail2Ban
2019-11-10 19:46:11
47.247.60.226 attackspam
RDP Bruteforce
2019-11-10 20:00:11
198.46.213.221 attackspambots
(From eric@talkwithcustomer.com) Hey,

You have a website familychiropractorsofridgewood.com, right?

Of course you do. I am looking at your website now.

It gets traffic every day – that you’re probably spending $2 / $4 / $10 or more a click to get.  Not including all of the work you put into creating social media, videos, blog posts, emails, and so on.

So you’re investing seriously in getting people to that site.

But how’s it working?  Great? Okay?  Not so much?

If that answer could be better, then it’s likely you’re putting a lot of time, effort, and money into an approach that’s not paying off like it should.

Now… imagine doubling your lead conversion in just minutes… In fact, I’ll go even better.
 
You could actually get up to 100X more conversions!

I’m not making this up.  As Chris Smith, best-selling author of The Conversion Code says: Speed is essential - there is a 100x decrease in Leads when a Lead is contacted within 14 minutes vs being contacted within 5 minutes.

He’s bac
2019-11-10 19:28:43
139.59.91.176 attackbots
detected by Fail2Ban
2019-11-10 19:30:54
139.59.128.97 attackspambots
2019-11-10 08:10:44,870 fail2ban.actions        \[14488\]: NOTICE  \[sshd\] Ban 139.59.128.97
2019-11-10 08:49:02,637 fail2ban.actions        \[14488\]: NOTICE  \[sshd\] Ban 139.59.128.97
2019-11-10 09:24:24,886 fail2ban.actions        \[14488\]: NOTICE  \[sshd\] Ban 139.59.128.97
2019-11-10 09:56:40,310 fail2ban.actions        \[14488\]: NOTICE  \[sshd\] Ban 139.59.128.97
2019-11-10 10:28:57,612 fail2ban.actions        \[14488\]: NOTICE  \[sshd\] Ban 139.59.128.97
...
2019-11-10 19:47:18
1.207.250.78 attack
Nov 10 09:09:01 ns381471 sshd[10989]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.207.250.78
Nov 10 09:09:03 ns381471 sshd[10989]: Failed password for invalid user mntner from 1.207.250.78 port 20069 ssh2
2019-11-10 19:35:02
93.39.79.144 attack
93.39.79.144 was recorded 17 times by 1 hosts attempting to connect to the following ports: 23. Incident counter (4h, 24h, all-time): 17, 166, 166
2019-11-10 19:41:15

Recently Reported IPs

136.71.113.167 155.198.181.171 222.79.13.49 214.158.141.104
125.191.135.202 64.46.118.145 112.120.166.11 125.222.108.70
197.111.10.122 150.173.3.234 159.241.48.34 72.4.229.25
126.245.199.153 96.173.190.68 148.9.81.181 199.113.241.31
185.241.185.90 39.63.142.211 55.189.254.222 178.79.145.60