If you're interested in the local version or a "how does it work", I wrote this Ruby gem years ago for this functionality, which has been useful in a range of penetration testing engagements where "the Azure tenant" is within scope.
The Gem is virtually unused with the only feedback I had being "eww Ruby", so I made a web interface for an AWS lambda function. Perhaps some non tech people would be interested in seeing what companies work together behind the scenes.
There's no intention of "bragging" here on a page that doesn't name me or any company or include any usage analytics.
That URL field is awful on mobile. I can’t understand why people don’t use the correct attributes to prevent URLs being “helpfully” spell corrected into something else.
This is in the "I'm not a frontend person, I've literally never heard of any correct attributes beyond the ones I copied from the React-hook-form examples" category.
If you can point to a specific change, send it to an issue and I'll do it:
You can just pull dns records and see for yourself. It’s funny. It’s like saying water is wet. You can also see what services are enabled on that domain - and.. maybe rven other things!
6 comments
[ 2.8 ms ] story [ 16.5 ms ] threadhttps://rubygems.org/gems/azure_enum
The Gem is virtually unused with the only feedback I had being "eww Ruby", so I made a web interface for an AWS lambda function. Perhaps some non tech people would be interested in seeing what companies work together behind the scenes.
There's no intention of "bragging" here on a page that doesn't name me or any company or include any usage analytics.
If you can point to a specific change, send it to an issue and I'll do it:
https://github.com/technion/azure-enum-frontend