[rickduggan]

This is super cool. I use a similar API to provide a client-side service called IP Request Mapper (https://chrome.google.com/webstore/detail/ip-request-mapper/...). Coming soon to a Show HN near you.

What it does is show where every asset on a web page is loaded from. It allows you to visualize how many different requests go into building just one web page. While it's gotten much better, the Houston Chronicle (https://chron.com) used to make about 500 individual requests to build its home page. It's down to about 125.

It's best to run it across two different monitors, with IP Request Mapper on one monitor and your "normal" browser window on another. Then enter any URL and watch the map start populating based on the geolocating every request made by the page.

But it's projects like ipinfo.io that make these other things possible. Standing on the shoulders of giants and all that...kudos to you, coderholic.

[heipei]

That's the same motivation that started me to build https://urlscan.io. I wanted an easy way for everyone to visualise the amount, size and destinations of the various HTTP requests that a single page-load triggers. Incidentally I also created a tool that is being used by a lot of Security / Phishing researchers. If you ever want some inspiration for additional IP / domain annotation sources, check it out. I should really do a "Show HN" soon ;)

Meanwhile, this is a scan for a particularly noisy German newspaper website (faz.net): https://urlscan.io/result/f23e2e7e-e1eb-4591-9794-92f97957dd...

This website contacted 35 IPs in 7 countries across 24 domains to perform 302 HTTP transactions. Of those, 51 were HTTPS (17 %) and 35% were IPv6. The main IP is 92.123.94.227, located in European Union and belongs to AKAMAI-ASN1. In total, 4 MB of data was transfered, which is 9 MB uncompressed. It took 2.51 seconds to load this page. 16 cookies were set, and 42 messages to the console were logged.

[sumedh]

Any domain I enter, i just get this

invalid csrf token Error code 403

[random_rr]

Very cool tool. Thanks for posting this!

[rickduggan]

Agreed. heipei, love what you did here.

[sAbakumoff]

How is it different from the dev tools network feature that is available in every browser?

[rickduggan]

Not sure if you are asking me or heipei. For my project, it shows the requests on a map, where the requests in dev tools aren't geolocated and mapped. Same basic principle, just a different view.

[sAbakumoff]

Okay, why is it helpful? Or it is just for entertaining?

[rickduggan]

I'd call it more interesting than helpful (not that it's not helpful). It gives insight into how a web page is actually built -- while I'm sure most readers here understand it, that's not true for the general population.

It might make developers think twice about how they build sites if they could see how overly complex they get. As I mentioned, the Houston Chronicle site used to require about 4x the number of requests as it does now so someone did some optimization.

[sAbakumoff]

Reducing number of resources loaded by a web page is the basics of the performance optimization.