Your config in WP is generally correct, but you have "forwarding" enabled at Namecheap, where they just redirect to your IP. Set it up as a real DNS A entry pointing to the IP.
Then set up your IIS to listen at port 80.
For reference, here's how I debugged it (I'll replace your actual IP with the example you used):
curl -v "http://autocoaching.life/"
* Hostname was NOT found in DNS cache
* Trying 192.64.119.185...
* Connected to autocoaching.life (192.64.119.185) port 80 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.35.0
> Host: autocoaching.life
> Accept: */*
>
< HTTP/1.1 302 Found
* Server nginx is not blacklisted
< Server: nginx
< Date: Fri, 26 Jan 2018 21:53:51 GMT
< Content-Type: text/html; charset=utf-8
< Content-Length: 49
< Connection: keep-alive
< Location: http://112.123.123.123:8085/
< X-Served-By: Namecheap URL Forward
<
<a href='http://112.123.123.123:8085/'>Found</a>.
http://112.123.123.123:8085/ redirects to http://112.123.123.123/, and that lead to the dreaded IIS page.
However, curl -v -H "Host: autocoaching.life" "http://167.114.6.216:8085" looks much better and gets us the correct WP response, therefore your IIS is set up correctly as far as the host name goes, but it's listening on the non-standard port and because of the namecheap redirect, it doesn't get the request with the correct Host header (which I've added with curl).
Once you fix your DNS entries from HTTP forwarding to a normal A entry and make IIS use Port 80 for that host, you should be fine.
If for some reason, you don't want to use port 80, that's fine too, but you'd have to set up WP to reflect that in the URL, e.g. use http://autocoaching.life:8085 and type that into the URL as well.
