The idea is to point a DNS entry to 127.0.0.1, so that it's possible to test "inline installation" of browser extensions.
Here's an example service that does this: http://readme.localtest.me/
I'm considering doing this for my own DNS entries.
app.example.com -> production server IP app-stage.example.com -> stage servier IP app-dev.example.com -> 127.0.0.1
Then I can put my app locally to respond to app-dev.example.com and test.
I'm following up on this question from a practical standpoint. The answers generally said there was little security risk for pointing app-dev.example.com to 127.0.0.1.
XSS is a concern in the DNS configs, but that seems different.
Are you aware of a practical issues?
Obviously, each person resolving the DN would need the app installed and working on their machine.
Seems fine, but then ?