Timeline for Godaddy Server location?
Current License: CC BY-SA 3.0
12 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jan 24, 2017 at 16:46 | vote | accept | macc | ||
Dec 14, 2016 at 17:29 | answer | added | midhunams | timeline score: -1 | |
Jun 16, 2016 at 4:42 | comment | added | Douglas Thomas | Yeah, I'm fully agree with @closetnoc. IP is just allocation, it can't describe location. If they hide their IP, you cant even ping it or know the location. | |
Jun 6, 2016 at 11:13 | comment | added | user | 160.153.0.0/16 is indeed registered to GoDaddy through ARIN, but since it's a direct allocation that doesn't have to mean much. Whois only tells you part of the story; they could, in principle, be publishing routes causing a portion of that netblock to end up in non-ARIN space. | |
S Jun 6, 2016 at 11:03 | history | suggested | user | CC BY-SA 3.0 |
Incorporate from comments to answer
|
Jun 6, 2016 at 11:01 | review | Suggested edits | |||
S Jun 6, 2016 at 11:03 | |||||
Jun 6, 2016 at 9:52 | history | tweeted | twitter.com/StackWebmasters/status/739756833980723201 | ||
Jun 5, 2016 at 22:57 | answer | added | Chris Rutherfurd | timeline score: 10 | |
Jun 5, 2016 at 22:31 | comment | added | closetnoc | That is just the IP allocation. It is not the location. | |
Jun 5, 2016 at 21:49 | comment | added | Tim Malone | If you do a traceroute of the IP, where is it based then? It might just be that GoDaddy are listed as the owners - depending on where you looked it up. | |
Jun 5, 2016 at 21:19 | review | First posts | |||
Jun 5, 2016 at 21:49 | |||||
Jun 5, 2016 at 21:14 | history | asked | macc | CC BY-SA 3.0 |