Traceroute Mapper – Show Your Traceroute on a Map
31–36 of 36 posts
Re: Traceroute Mapper – Show Your Traceroute on a Map
#32Earlier quoted context omitted.
How does that work?
Someone has set up the routing to 162.252.205.157 so that it passes through many other address which they control (162.252.205.130 through to .157) the reverse DNS for, and customised them in the appropriate order: $ dig -x 162.252.205.142 +short a.murder.would.be.nice.of.course.
Re: Traceroute Mapper – Show Your Traceroute on a Map
#33Mandatory comment: Be sure to Traceroute bad.horse
Re: Traceroute Mapper – Show Your Traceroute on a Map
#34Mandatory comment: Be sure to Traceroute bad.horse
Re: Traceroute Mapper – Show Your Traceroute on a Map
#35Earlier quoted context omitted.
> we have geolocation API which uses latency triangulation and does not suffer from those issues Who is "we"? I'd like to test drive a service like that.
You can send me email to janusz@speedchecker.xyz or through contact us page on www.speedchecker.xyz We operate large scale testing platform which can ping from many locations so we can triangulate better, demo here - http://www.maplatency.com
Re: Traceroute Mapper – Show Your Traceroute on a Map
#36Also, if you want to self-host the website (and thus get your own ipinfo ratelimit quota), it seems like the Google Maps API now requires you to get an API key (it didn't before). Get one here: https://developers.google.com/maps/documentation/javascript/...