Free network and domain tools
w3dt.net
w3dt.net
Can someone explain to me why they would need that? My instinct tells me that they are trying to circumvent people who delete cookies when the browser is closed and that makes me uneasy...
The site uses html5 to pre-render pages to improve the user experience / site performance... Part of this includes storing the query parameters you make (when running a query) in the new HTML5 web-storage.
This allows the webpage to be rendered before the user actually clicks the "submit" button on any of the tools (Making the site load faster it would normally). The query you specify is then pulled out of the HTML5 web-storage (when the pre-rendered page is made visible) and sent to the backend API servers.
Hope this clears this up for you :)
A few follow up questions:
1. They could have achieved the same using cookies too, right? How is it different from using cookies?
2. Is it better because quicker? Or is it better because local storage allows a site to store/retrieve more data from the user and thus reducing the need to get it all from the server?
3. What about CORS? How doe sthat factor in?
I honestly don't expect you to answer all these questions. you seem knowledgeable about the topic, so posted these questions here. I'd be very glad if you could simply redirect me to a relevant webpage.
Thank you for your time and efforts, I appreciate it very much!
2 - You're correct about #2 - Caching as much data that does not change in the browser (such as images, common requests etc) will often improve the user experience -- especially when on a poor connection such as a 3G mobile phone.
3 - CORS is defined by the w3dt.net servers .. the main w3dt.net site does not allow "cross-origin" sharing to my knowledge but sub domains such as "results.w3dt.net" do allow CORS so that users may embed results into other websites. -- Read here for more info: http://en.wikipedia.org/wiki/Cross-origin_resource_sharing
Have a great day :)
Thanks Guys, much appreciated!
"When we visited this site, we found it exhibited one or more risky behaviors."
Yeah, McAfee SiteAdvisor.
It's simple but it works. I though about making my tool into a business but I don't know what to do about the WHOIS info. If I start making a lot of request I'll probably get banned.
https://w3dt.net/tools/portscan#&query=127.0.0.1
That alone makes me wonder at the sanitization they are carrying out upon the input - there be dragons out there.