Hacker News Reader

Full thread

thefilmore

I can think of at least four reasons and security concerns not to use a service like this:

- Exposing a potentially private IP to an external service

- If testing local IPs, adds a requirement for an internet connection

- Must trust that it will always resolve to the actual IP not another one

- Requires your service to accept a hostname that it likely shouldn't

View on HN

> Exposing a potentially private IP to an external service

I have to ask why knowing an IP address would be an issue.

Surely it's not the key point in any reasonably possible exploit.

If you're using this for testing, it's likely that you haven't fully locked down your server yet. It's not an exploit in itself but it potentially makes the server a target. No reason to do that until and unless it's required.

But this day want make the IP accessible, just "known".

It's still a private IP.

Reply on news.ycombinator.com