WHATWASTHERE.COM WhatWasThere - Put history in its place!

  1. Homepage
  2. whatwasthere.com

whatwasthere.com website information.

whatwasthere.com domain name is registered by .COM top-level domain registry. See the other sites registred in .COM domain zone.

Following name servers are specified for whatwasthere.com domain:

  • ns-1237.awsdns-26.org
  • ns-1582.awsdns-05.co.uk
  • ns-376.awsdns-47.com
  • ns-973.awsdns-57.net

and probably website whatwasthere.com is hosted by FASTLY - Fastly, US web hosting company. Check the complete list of other most popular websites hosted by FASTLY - Fastly, US hosting company.

According to Alexa traffic rank the highest website whatwasthere.com position was 82528 (in the world). The lowest Alexa rank position was 997446. Now website whatwasthere.com ranked in Alexa database as number 318125 (in the world).

Website whatwasthere.com Desktop speed measurement score (60/100) is better than the results of 35.69% of other sites shows that the page desktop performance can be improved.

whatwasthere.com Mobile usability score (59/100) is better than the results of 2.69% of other sites and shows that the page mobile usability is poor and can be improved.

Mobile speed measurement score of whatwasthere.com (59/100) is better than the results of 52.41% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Nov-18-2024 318,1257,187
Nov-17-2024 325,312473
Nov-16-2024 325,7851,616
Nov-15-2024 327,401-2,947
Nov-14-2024 324,454-7,132
Nov-13-2024 317,3220
Nov-12-2024 317,3220

Advertisement

whatwasthere.com Rank History

Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.


whatwasthere.com whois

WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.

Domain Name: WHATWASTHERE.COM
Registry Domain ID: 1604154167_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.PublicDomainRegistry.com
Registrar URL: http://www.publicdomainregistry.com
Updated Date: 2021-03-31T17:42:50Z
Creation Date: 2010-06-28T21:02:33Z
Registry Expiry Date: 2026-06-28T21:02:33Z
Registrar: PDR Ltd. d/b/a PublicDomainRegistry.com
Registrar IANA ID: 303
Registrar Abuse Contact Email: abuse-contact@publicdomainregistry.com
Registrar Abuse Contact Phone: +1.2013775952
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: NS-1237.AWSDNS-26.ORG
Name Server: NS-1582.AWSDNS-05.CO.UK
Name Server: NS-376.AWSDNS-47.COM
Name Server: NS-973.AWSDNS-57.NET
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2024-11-08T15:28:23Z

whatwasthere.com server information

Servers Location

IP Address
23.21.171.184
Country
United States
Region
Virginia
City
Ashburn

whatwasthere.com desktop page speed rank

Last tested: 2015-09-21

Desktop Speed Bad
60/100

whatwasthere.com Desktop Speed Test Quick Summary


priority - 28 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 9 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

https://ajax.googleapis.com/ajax/libs/jquery/1.6.2/jquery.min.js
http://www.whatwasthere.com/js/jquery-ui-1.8.10.custom.min.js
http://maps.googleapis.com/maps/api/js?v=3.7&key=A…nBcSi2NYI&sensor=false
http://maps.gstatic.com/maps-api-v3/api/js/20/16/main.js
http://www.whatwasthere.com/js/utils.min.js?v=2
http://www.whatwasthere.com/js/konami.min.js
http://connect.facebook.net/en_US/all.js
http://www.whatwasthere.com/js/webtrends.min.js
http://sdc.enlighten.com/dcst9uy32x4568537oipzksot_6v4g/wtid.js

Optimize CSS Delivery of the following:

http://www.whatwasthere.com/css/global.min.css?v=1
http://www.whatwasthere.com/css/home.min.css?v=3
http://fonts.googleapis.com/css?family=Roboto:300,400,500,700

priority - 22 Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 216KiB (72% reduction).

Compressing https://static.xx.fbcdn.net/rsrc.php/v2/y8/r/mxj5okZKDDX.js could save 216KiB (72% reduction).

priority - 16 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://connect.facebook.net/en_US/all.js (20 minutes)
http://maps.googleapis.com/maps/api/js?v=3.7&key=A…nBcSi2NYI&sensor=false (30 minutes)
http://www.google-analytics.com/ga.js (2 hours)
http://www.whatwasthere.com/css/global.min.css?v=1 (24 hours)
http://www.whatwasthere.com/css/home.min.css?v=3 (24 hours)
http://www.whatwasthere.com/images/global/blank.gif (24 hours)
http://www.whatwasthere.com/images/global/facebookNav.png (24 hours)
http://www.whatwasthere.com/images/global/followUsH.gif (24 hours)
http://www.whatwasthere.com/images/global/logo.png (24 hours)
http://www.whatwasthere.com/images/global/nav.png (24 hours)
http://www.whatwasthere.com/images/global/topNavBg.png (24 hours)
http://www.whatwasthere.com/images/global/twitterNav.png (24 hours)
http://www.whatwasthere.com/images/home/browseCopy.png (24 hours)
http://www.whatwasthere.com/images/home/browseTeaserBottomBg.png (24 hours)
http://www.whatwasthere.com/images/home/browseTeaserTopBg.png (24 hours)
http://www.whatwasthere.com/images/home/goBtn.png (24 hours)
http://www.whatwasthere.com/images/home/introText.png (24 hours)
http://www.whatwasthere.com/images/home/iphoneIcon.png (24 hours)
http://www.whatwasthere.com/images/home/makeHistoryH.gif (24 hours)
http://www.whatwasthere.com/images/home/orangeBg.png (24 hours)
http://www.whatwasthere.com/images/home/photoBox.png (24 hours)
http://www.whatwasthere.com/images/home/skyline.png (24 hours)
http://www.whatwasthere.com/images/home/skylineRepeatBg.png (24 hours)
http://www.whatwasthere.com/images/home/teaserBg.png (24 hours)
http://www.whatwasthere.com/images/home/theLatestH.gif (24 hours)
http://www.whatwasthere.com/images/home/uploadBtn.png (24 hours)
http://www.whatwasthere.com/images/uploads/thumb/Photo_78165.jpg (24 hours)
http://www.whatwasthere.com/images/uploads/thumb/Photo_78168.jpg (24 hours)
http://www.whatwasthere.com/images/uploads/thumb/Photo_78171.jpg (24 hours)
http://www.whatwasthere.com/images/uploads/thumb/Photo_78172.jpg (24 hours)
http://www.whatwasthere.com/images/uploads/thumb/Photo_78173.jpg (24 hours)
http://www.whatwasthere.com/images/uploads/thumb/Photo_78174.jpg (24 hours)
http://www.whatwasthere.com/images/uploads/thumb/Photo_78175.jpg (24 hours)
http://www.whatwasthere.com/images/uploads/thumb/Photo_78176.jpg (24 hours)
http://www.whatwasthere.com/js/jquery-ui-1.8.10.custom.min.js (24 hours)
http://www.whatwasthere.com/js/konami.min.js (24 hours)
http://www.whatwasthere.com/js/utils.min.js?v=2 (24 hours)
http://www.whatwasthere.com/js/webtrends.min.js (24 hours)

priority - 2 Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 62% of the final above-the-fold content could be rendered with the full HTML response.

priority - 2 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 9.2KiB (37% reduction).

Losslessly compressing http://www.whatwasthere.com/images/home/uploadBtn.png could save 1.8KiB (27% reduction).
Losslessly compressing http://www.whatwasthere.com/images/home/theLatestH.gif could save 1.2KiB (74% reduction).
Losslessly compressing http://www.whatwasthere.com/images/home/makeHistoryH.gif could save 1.1KiB (62% reduction).
Losslessly compressing http://www.whatwasthere.com/images/global/followUsH.gif could save 1.1KiB (70% reduction).
Losslessly compressing http://www.whatwasthere.com/images/home/browseTeaserBottomBg.png could save 912B (61% reduction).
Losslessly compressing http://www.whatwasthere.com/images/home/browseCopy.png could save 910B (33% reduction).
Losslessly compressing http://www.whatwasthere.com/images/home/orangeBg.png could save 893B (87% reduction).
Losslessly compressing http://www.whatwasthere.com/images/home/teaserBg.png could save 801B (32% reduction).
Losslessly compressing http://www.whatwasthere.com/images/home/introText.png could save 726B (12% reduction).

priority - 0 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 2.5KiB (1% reduction).

Minifying https://static.xx.fbcdn.net/rsrc.php/v2/y8/r/mxj5okZKDDX.js could save 2.5KiB (1% reduction).

whatwasthere.com Desktop Resources

Total Resources120
Number of Hosts18
Static Resources99
JavaScript Resources23
CSS Resources3

whatwasthere.com Desktop Resource Breakdown

whatwasthere.com mobile page speed rank

Last tested: 2019-06-30

Mobile Speed Bad
59/100

whatwasthere.com Mobile Speed Test Quick Summary


priority - 40 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 7 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

https://ajax.googleapis.com/ajax/libs/jquery/1.6.2/jquery.min.js
http://www.whatwasthere.com/js/jquery-ui-1.8.10.custom.min.js
http://maps.googleapis.com/maps/api/js?v=3.7&key=A…Wto92_eMc&sensor=false
http://www.whatwasthere.com/js/utils.min.js?v=2
http://www.whatwasthere.com/js/konami.min.js
http://www.whatwasthere.com/js/webtrends.min.js
http://sdc.enlighten.com/dcst9uy32x4568537oipzksot_6v4g/wtid.js

Optimize CSS Delivery of the following:

http://www.whatwasthere.com/css/global.min.css?v=1
http://www.whatwasthere.com/css/home.min.css?v=3

priority - 25 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://connect.facebook.net/en_US/all.js (20 minutes)
http://maps.googleapis.com/maps/api/js?v=3.7&key=A…Wto92_eMc&sensor=false (30 minutes)
http://www.google-analytics.com/ga.js (2 hours)
http://www.whatwasthere.com/css/global.min.css?v=1 (24 hours)
http://www.whatwasthere.com/css/home.min.css?v=3 (24 hours)
http://www.whatwasthere.com/images/global/blank.gif (24 hours)
http://www.whatwasthere.com/images/global/facebookNav.png (24 hours)
http://www.whatwasthere.com/images/global/followUsH.gif (24 hours)
http://www.whatwasthere.com/images/global/logo.png (24 hours)
http://www.whatwasthere.com/images/global/nav.png (24 hours)
http://www.whatwasthere.com/images/global/topNavBg.png (24 hours)
http://www.whatwasthere.com/images/global/twitterNav.png (24 hours)
http://www.whatwasthere.com/images/home/browseCopy.png (24 hours)
http://www.whatwasthere.com/images/home/browseTeaserBottomBg.png (24 hours)
http://www.whatwasthere.com/images/home/browseTeaserTopBg.png (24 hours)
http://www.whatwasthere.com/images/home/goBtn.png (24 hours)
http://www.whatwasthere.com/images/home/introText.png (24 hours)
http://www.whatwasthere.com/images/home/iphoneIcon.png (24 hours)
http://www.whatwasthere.com/images/home/makeHistoryH.gif (24 hours)
http://www.whatwasthere.com/images/home/orangeBg.png (24 hours)
http://www.whatwasthere.com/images/home/photoBox.png (24 hours)
http://www.whatwasthere.com/images/home/skyline.png (24 hours)
http://www.whatwasthere.com/images/home/skylineRepeatBg.png (24 hours)
http://www.whatwasthere.com/images/home/teaserBg.png (24 hours)
http://www.whatwasthere.com/images/home/theLatestH.gif (24 hours)
http://www.whatwasthere.com/images/home/uploadBtn.png (24 hours)
http://www.whatwasthere.com/images/uploads/thumb/Photo_90048.jpg (24 hours)
http://www.whatwasthere.com/images/uploads/thumb/Photo_90049.jpg (24 hours)
http://www.whatwasthere.com/images/uploads/thumb/Photo_90050.jpg (24 hours)
http://www.whatwasthere.com/images/uploads/thumb/Photo_90051.jpg (24 hours)
http://www.whatwasthere.com/images/uploads/thumb/Photo_90052.jpg (24 hours)
http://www.whatwasthere.com/images/uploads/thumb/Photo_90053.jpg (24 hours)
http://www.whatwasthere.com/images/uploads/thumb/Photo_90054.jpg (24 hours)
http://www.whatwasthere.com/images/uploads/thumb/Photo_90055.jpg (24 hours)
http://www.whatwasthere.com/js/jquery-ui-1.8.10.custom.min.js (24 hours)
http://www.whatwasthere.com/js/konami.min.js (24 hours)
http://www.whatwasthere.com/js/utils.min.js?v=2 (24 hours)
http://www.whatwasthere.com/js/webtrends.min.js (24 hours)

priority - 8 Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 69% of the final above-the-fold content could be rendered with the full HTML response.
Click to see the screenshot with only the HTML response:

priority - 1 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 10.1KiB (33% reduction).

Compressing http://www.whatwasthere.com/images/home/uploadBtn.png could save 1.8KiB (27% reduction).
Compressing http://www.whatwasthere.com/images/home/theLatestH.gif could save 1.1KiB (69% reduction).
Compressing http://www.whatwasthere.com/images/global/followUsH.gif could save 951B (61% reduction).
Compressing http://www.whatwasthere.com/images/home/orangeBg.png could save 930B (90% reduction).
Compressing http://www.whatwasthere.com/images/home/makeHistoryH.gif could save 892B (50% reduction).
Compressing http://www.whatwasthere.com/images/home/browseTeaserBottomBg.png could save 798B (53% reduction).
Compressing http://www.whatwasthere.com/images/home/teaserBg.png could save 576B (23% reduction).
Compressing http://www.whatwasthere.com/images/home/skylineRepeatBg.png could save 521B (38% reduction).
Compressing http://www.whatwasthere.com/images/uploads/thumb/Photo_90054.jpg could save 354B (22% reduction).
Compressing http://www.whatwasthere.com/images/uploads/thumb/Photo_90052.jpg could save 330B (20% reduction).
Compressing http://www.whatwasthere.com/images/uploads/thumb/Photo_90055.jpg could save 329B (23% reduction).
Compressing http://www.whatwasthere.com/images/uploads/thumb/Photo_90049.jpg could save 323B (19% reduction).
Compressing http://www.whatwasthere.com/images/uploads/thumb/Photo_90053.jpg could save 321B (20% reduction).
Compressing http://www.whatwasthere.com/images/uploads/thumb/Photo_90048.jpg could save 319B (18% reduction).
Compressing http://www.whatwasthere.com/images/uploads/thumb/Photo_90051.jpg could save 313B (22% reduction).
Compressing http://www.whatwasthere.com/images/uploads/thumb/Photo_90050.jpg could save 312B (22% reduction).
Compressing https://static.xx.fbcdn.net/rsrc.php/v3/y5/r/OqOE21UvWe3.png could save 201B (50% reduction).

priority - 0 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 674B (39% reduction).

Minifying http://connect.facebook.net/en_US/all.js could save 674B (39% reduction) after compression.

priority - 0 Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 237B (34% reduction).

Compressing http://api.ipinfodb.com/v3/ip-city/?key=1dfb4b98ca…427888&_=1561857427893 could save 119B (34% reduction).
Compressing http://api.ipinfodb.com/v3/ip-city/?key=1dfb4b98ca…427887&_=1561857427892 could save 118B (34% reduction).

whatwasthere.com Mobile Resources

Total Resources105
Number of Hosts12
Static Resources94
JavaScript Resources23
CSS Resources3

whatwasthere.com Mobile Resource Breakdown

whatwasthere.com mobile page usability

Last tested: 2019-06-30

Mobile Usability Bad
59/100

whatwasthere.com Mobile Usability Test Quick Summary


priority - 40 Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

LOGIN / REGISTER renders only 4 pixels tall (10 CSS pixels).

FEEDBACK and 2 others render only 4 pixels tall (10 CSS pixels).

Like renders only 4 pixels tall (11 CSS pixels).

120K renders only 4 pixels tall (11 CSS pixels).

iPhone app is…nes App Store. and 1 others render only 5 pixels tall (14 CSS pixels).

WhatWasThere renders only 5 pixels tall (14 CSS pixels).

LEARN MORE renders only 5 pixels tall (12 CSS pixels).

Map data ©2019 Google and 1 others render only 4 pixels tall (10 CSS pixels).

two snapshots…of the world. and 1 others render only 5 pixels tall (12 CSS pixels).

© Enlighten Ventures, LLC 2012 renders only 4 pixels tall (11 CSS pixels).

priority - 20 Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a id="ctl00_ContentP…1_loginOutLink" href="login.aspx" class="loginLink">Login / Register</a> is close to 1 other tap targets.

The tap target <a id="ctl00_ContentP…er1_HyperLink6" href="Privacy.aspx">Privacy</a> and 2 others are close to other tap targets.

The tap target <a id="facebookNav" href="http://www.fac…m/whatwasthere">Facebook</a> is close to 3 other tap targets.

The tap target <a id="twitterNav" href="http://twitter…m/whatwasthere">Twitter</a> is close to 5 other tap targets.

The tap target <div id="u_0_1">Like120K</div> is close to 1 other tap targets.

The tap target <button type="submit" class="inlineBlock _2tga _49ve">Like120K</button> is close to 1 other tap targets.

The tap target <a id="ctl00_ContentP…er1_HyperLink7" href="default.aspx" class="logo">What Was There</a> is close to 2 other tap targets.

The tap target <a id="ctl00_ContentP…er1_HyperLink1" href="browse.aspx">Explore Photos</a> is close to 1 other tap targets.

The tap target <a id="ctl00_ContentP…er1_HyperLink2" href="uploadAllSteps.aspx">Upload Photos</a> is close to 1 other tap targets.

The tap target <a id="ctl00_ContentP…er1_HyperLink3" href="myPhotos.aspx">My Photos</a> is close to 3 other tap targets.

The tap target <a id="ctl00_ContentP…er1_HyperLink4" href="about.aspx">About</a> is close to 3 other tap targets.

The tap target <a id="ctl00_ContentP…er1_HyperLink5" href="iphone/default.aspx" class="learnMore">Learn More</a> is close to 1 other tap targets.

The tap target <a id="ctl00_ContentP…r1_HyperLink23" href="iphone/default.aspx" class="wholeBarLink"> is close to 1 other tap targets.

The tap target <a href="https://www.go…erms_maps.html">Terms of Use</a> is close to 1 other tap targets.

The tap target <button type="button" class="gm-control-act…screen-control"></button> is close to 2 other tap targets.

The tap target <button type="button" class="gm-control-active"></button> and 1 others are close to other tap targets.

The tap target <a id="goBtn" href="#" class="browseGoBtn">Go</a> is close to 1 other tap targets.

The tap target <a id="ctl00_ContentP…rl0_Hyperlink1" href="browse.aspx#!/…fo/sv/zoom/14/"></a> and 7 others are close to other tap targets.

priority - 10 Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

Configure a viewport for this page.

priority - 3 Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 1,016 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

The element <div id="navWrapper">Login / Regist…Feedback</div> falls outside the viewport.
The element <a id="ctl00_ContentP…er1_HyperLink7" href="default.aspx" class="logo">What Was There</a> falls outside the viewport.
The element <a id="ctl00_ContentP…r1_HyperLink23" href="iphone/default.aspx" class="wholeBarLink"> falls outside the viewport.
The element <div class="clear"> falls outside the viewport.

whatwasthere.com similar domains

Similar domains:
www.whatwasthere.com
www.whatwasthere.net
www.whatwasthere.org
www.whatwasthere.info
www.whatwasthere.biz
www.whatwasthere.us
www.whatwasthere.mobi
www.hatwasthere.com
www.whatwasthere.com
www.qhatwasthere.com
www.wqhatwasthere.com
www.qwhatwasthere.com
www.ahatwasthere.com
www.wahatwasthere.com
www.awhatwasthere.com
www.shatwasthere.com
www.wshatwasthere.com
www.swhatwasthere.com
www.ehatwasthere.com
www.wehatwasthere.com
www.ewhatwasthere.com
www.watwasthere.com
www.wbatwasthere.com
www.whbatwasthere.com
www.wbhatwasthere.com
www.wgatwasthere.com
www.whgatwasthere.com
www.wghatwasthere.com
www.wyatwasthere.com
www.whyatwasthere.com
www.wyhatwasthere.com
www.wuatwasthere.com
www.whuatwasthere.com
www.wuhatwasthere.com
www.wjatwasthere.com
www.whjatwasthere.com
www.wjhatwasthere.com
www.wnatwasthere.com
www.whnatwasthere.com
www.wnhatwasthere.com
www.whtwasthere.com
www.whqtwasthere.com
www.whaqtwasthere.com
www.whqatwasthere.com
www.whwtwasthere.com
www.whawtwasthere.com
www.whwatwasthere.com
www.whstwasthere.com
www.whastwasthere.com
www.whsatwasthere.com
www.whztwasthere.com
www.whaztwasthere.com
www.whzatwasthere.com
www.whawasthere.com
www.wharwasthere.com
www.whatrwasthere.com
www.whartwasthere.com
www.whafwasthere.com
www.whatfwasthere.com
www.whaftwasthere.com
www.whagwasthere.com
www.whatgwasthere.com
www.whagtwasthere.com
www.whaywasthere.com
www.whatywasthere.com
www.whaytwasthere.com
www.whatasthere.com
www.whatqasthere.com
www.whatwqasthere.com
www.whatqwasthere.com
www.whataasthere.com
www.whatwaasthere.com
www.whatawasthere.com
www.whatsasthere.com
www.whatwsasthere.com
www.whatswasthere.com
www.whateasthere.com
www.whatweasthere.com
www.whatewasthere.com
www.whatwsthere.com
www.whatwqsthere.com
www.whatwaqsthere.com
www.whatwwsthere.com
www.whatwawsthere.com
www.whatwwasthere.com
www.whatwssthere.com
www.whatwassthere.com
www.whatwzsthere.com
www.whatwazsthere.com
www.whatwzasthere.com
www.whatwathere.com
www.whatwawthere.com
www.whatwaswthere.com
www.whatwaethere.com
www.whatwasethere.com
www.whatwaesthere.com
www.whatwadthere.com
www.whatwasdthere.com
www.whatwadsthere.com
www.whatwazthere.com
www.whatwaszthere.com
www.whatwaxthere.com
www.whatwasxthere.com
www.whatwaxsthere.com
www.whatwaathere.com
www.whatwasathere.com
www.whatwashere.com
www.whatwasrhere.com
www.whatwastrhere.com
www.whatwasrthere.com
www.whatwasfhere.com
www.whatwastfhere.com
www.whatwasfthere.com
www.whatwasghere.com
www.whatwastghere.com
www.whatwasgthere.com
www.whatwasyhere.com
www.whatwastyhere.com
www.whatwasythere.com
www.whatwastere.com
www.whatwastbere.com
www.whatwasthbere.com
www.whatwastbhere.com
www.whatwastgere.com
www.whatwasthgere.com
www.whatwastyere.com
www.whatwasthyere.com
www.whatwastuere.com
www.whatwasthuere.com
www.whatwastuhere.com
www.whatwastjere.com
www.whatwasthjere.com
www.whatwastjhere.com
www.whatwastnere.com
www.whatwasthnere.com
www.whatwastnhere.com
www.whatwasthre.com
www.whatwasthwre.com
www.whatwasthewre.com
www.whatwasthwere.com
www.whatwasthsre.com
www.whatwasthesre.com
www.whatwasthsere.com
www.whatwasthdre.com
www.whatwasthedre.com
www.whatwasthdere.com
www.whatwasthrre.com
www.whatwastherre.com
www.whatwasthrere.com
www.whatwasthee.com
www.whatwastheee.com
www.whatwastheree.com
www.whatwastheere.com
www.whatwasthede.com
www.whatwastherde.com
www.whatwasthefe.com
www.whatwastherfe.com
www.whatwasthefre.com
www.whatwasthete.com
www.whatwastherte.com
www.whatwasthetre.com
www.whatwasther.com
www.whatwastherw.com
www.whatwastherew.com
www.whatwastherwe.com
www.whatwasthers.com
www.whatwastheres.com
www.whatwastherse.com
www.whatwastherd.com
www.whatwasthered.com
www.whatwastherr.com
www.whatwastherer.com
www.whatwasthere.con

whatwasthere.com Ping

Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.

whatwasthere.com TRACEROUTE

Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.