STANFORD.EDU Stanford University


stanford.edu website information.

stanford.edu website servers are located in United States and are responding from following IP address 171.67.215.200. Check the full list of most visited websites located in United States.

stanford.edu domain name is registered by .EDU top-level domain registry. See the other sites registred in .EDU domain zone.

Following name servers are specified for stanford.edu domain:

  • Argus.stanford.edu
  • ns6.dnsmadeeasy.com
  • Atalante.stanford.edu
  • Avallone.stanford.edu
  • ns7.dnsmadeeasy.com
  • ns5.dnsmadeeasy.com

and probably website stanford.edu is hosted by stanford.edu web hosting company. Check the complete list of other most popular websites hosted by stanford.edu hosting company.

According to Alexa traffic rank the highest website stanford.edu position was 463 (in the world). The lowest Alexa rank position was 1394. Now website stanford.edu ranked in Alexa database as number 738 (in the world).

Website stanford.edu Desktop speed measurement score (73/100) is better than the results of 58.32% of other sites shows that the page desktop performance can be improved.

stanford.edu Mobile usability score (99/100) is better than the results of 87.11% of other sites and means that the page is mobile-friendly.

Mobile speed measurement score of stanford.edu (56/100) is better than the results of 44.81% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Nov-21-2018 738234
Nov-20-2018 972131
Nov-19-2018 1,103-211
Nov-18-2018 892-107
Nov-17-2018 7851
Nov-16-2018 786-98
Nov-15-2018 688116

Advertisement

stanford.edu 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.


stanford.edu 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.


This Registry database contains ONLY .EDU domains.
The data in the EDUCAUSE Whois database is provided
by EDUCAUSE for information purposes in order to
assist in the process of obtaining information about
or related to .edu domain registration records.

The EDUCAUSE Whois database is authoritative for the
.EDU domain.

A Web interface for the .EDU EDUCAUSE Whois Server is
available at: http://whois.educause.net

By submitting a Whois query, you agree that this information
will not be used to allow, enable, or otherwise support
the transmission of unsolicited commercial advertising or
solicitations via e-mail. The use of electronic processes to
harvest information from this server is generally prohibited
except as reasonably necessary to register or modify .edu
domain names.

You may use "%" as a wildcard in your search. For further
information regarding the use of this WHOIS server, please
type: help

--------------------------

Domain Name: STANFORD.EDU

Registrant:
Stanford University
The Board of Trustees of the Leland Stanford Junior University
241 Panama Street, Pine Hall, Room 115
Stanford, CA 94305-4122
UNITED STATES

Administrative Contact:

Domain Admin
Stanford University
241 Panama Street Pine Hall, Room 115
Stanford, CA 94305-4122
UNITED STATES
(650) 723-4328
sunet-admin@stanford.edu

Technical Contact:

Domain Admin
Stanford University
241 Panama Street Pine Hall, Room 115
Stanford, CA 94305-4122
UNITED STATES
(650) 723-4328
sunet-admin@stanford.edu

Name Servers:
ARGUS.STANFORD.EDU 171.64.7.115, 2607:f6d0:0:9113::ab40:773
AVALLONE.STANFORD.EDU 204.63.227.77
ATALANTE.STANFORD.EDU 171.64.7.61, 2607:f6d0:0:d32::ab40:73d
NS5.DNSMADEEASY.COM
NS6.DNSMADEEASY.COM
NS7.DNSMADEEASY.COM

Domain record activated: 04-Oct-1985
Domain record last updated: 30-Mar-2018
Domain expires: 31-Jul-2018

stanford.edu server information

Servers Location

stanford.edu desktop page speed rank

Last tested: 2016-06-12


Desktop Speed Medium
73/100

stanford.edu Desktop Speed Test Quick Summary


priority - 12 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 120.6KiB (75% reduction).

Compressing http://stanford.edu/assets/css/bootstrap.min.css?v=3.3.2 could save 51.2KiB (82% reduction).
Compressing http://stanford.edu/ could save 23KiB (75% reduction).
Compressing http://stanford.edu/assets/css/base.min.css?v=2.2 could save 10.8KiB (75% reduction).
Compressing http://stanford.edu/assets/css/homepage.min.css?v=2.2 could save 10.6KiB (78% reduction).
Compressing http://stanford.edu/assets/js/bootstrap.min.js could save 5.7KiB (67% reduction).
Compressing http://stanford.edu/assets/js/homepage.js?v=1.3.2 could save 5.5KiB (66% reduction).
Compressing http://stanford.edu/assets/js/modernizr.custom.17475.js could save 5KiB (55% reduction).
Compressing http://stanford.edu/assets/js/jquery-mobile-1.3.2.js could save 3.8KiB (61% reduction).
Compressing http://stanford.edu/assets/js/jquery.timeago.js could save 3.7KiB (64% reduction).
Compressing http://stanford.edu/assets/js/base.js?v=1.3.1 could save 1.3KiB (54% reduction).

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

Your page has 4 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.

Optimize CSS Delivery of the following:

http://stanford.edu/assets/css/bootstrap.min.css?v=3.3.2
http://stanford.edu/assets/css/base.min.css?v=2.2
https://fonts.googleapis.com/css?family=Source+Sans+Pro:200,300,400,600,700
http://stanford.edu/assets/css/homepage.min.css?v=2.2

priority - 9 Optimize images

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

Optimize the following images to reduce their size by 90.1KiB (53% reduction).

Compressing and resizing http://stanford.edu/rw_includes/homepage/atstanford/images/stanford125.jpg could save 53.7KiB (84% reduction).
Compressing and resizing http://stanford.edu/assets/su-images/stanforduniversity-125@2x.png could save 11.6KiB (49% reduction).
Losslessly compressing http://stanford.edu/rw_includes/homepage/images/20…_bacc_schori_270px.jpg could save 6.6KiB (15% reduction).
Compressing and resizing http://stanford.edu/assets/su-images/footer-stanford-logo@2x.png could save 4.7KiB (63% reduction).
Losslessly compressing http://stanford.edu/rw_includes/homepage/images/athletics/athletics.png could save 2.3KiB (23% reduction).
Compressing and resizing http://stanford.edu/assets/su-images/social/futurity@2x.png could save 2.2KiB (66% reduction).
Compressing and resizing http://stanford.edu/assets/su-images/social/twitter@2x.png could save 2.1KiB (71% reduction).
Compressing and resizing http://stanford.edu/assets/su-images/social/instagram@2x.png could save 2.1KiB (69% reduction).
Compressing and resizing http://stanford.edu/assets/su-images/social/youtube@2x.png could save 1.8KiB (68% reduction).
Compressing and resizing http://stanford.edu/assets/su-images/social/facebook@2x.png could save 1.6KiB (71% reduction).
Compressing and resizing http://stanford.edu/assets/su-images/social/apple@2x.png could save 1.5KiB (64% reduction).

priority - 4 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://stanford.edu/assets/js/bootstrap.min.js (expiration not specified)
http://stanford.edu/assets/js/jquery-mobile-1.3.2.js (expiration not specified)
http://stanford.edu/assets/js/jquery.timeago.js (expiration not specified)
http://stanford.edu/assets/js/modernizr.custom.17475.js (expiration not specified)
http://use.fontawesome.com/aff1ed173f.js (expiration not specified)
https://use.fontawesome.com/aff1ed173f.css (expiration not specified)
https://use.fontawesome.com/webfontloader/1.6.24/webfontloader.js (expiration not specified)
http://www.google-analytics.com/analytics.js (2 hours)

priority - 1 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 7KiB (43% reduction).

Minifying http://stanford.edu/assets/js/homepage.js?v=1.3.2 could save 3.6KiB (45% reduction).
Minifying http://stanford.edu/assets/js/jquery.timeago.js could save 2.4KiB (42% reduction).
Minifying http://stanford.edu/assets/js/base.js?v=1.3.1 could save 1,008B (43% reduction).

priority - 1 Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 5.5KiB (19% reduction).

Minifying http://stanford.edu/ could save 5.5KiB (19% reduction).

stanford.edu Desktop Resources

Total Resources41
Number of Hosts7
Static Resources31
JavaScript Resources10
CSS Resources6

stanford.edu Desktop Resource Breakdown

stanford.edu mobile page speed rank

Last tested: 2018-02-07


Mobile Speed Bad
56/100

stanford.edu Mobile Speed Test Quick Summary


priority - 68 Optimize images

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

Optimize the following images to reduce their size by 666.6KiB (68% reduction).

Compressing https://www-media.stanford.edu/wp-content/uploads/…3351/health-care-3.jpg could save 228KiB (76% reduction).
Compressing https://events.stanford.edu/events/692/69281/69281-1.jpg could save 134.9KiB (71% reduction).
Compressing https://events.stanford.edu/events/741/74181/74181-2.jpg could save 103.6KiB (68% reduction).
Compressing https://events.stanford.edu/events/267/26721/26721-1.jpg could save 93.2KiB (64% reduction).
Compressing https://events.stanford.edu/events/744/74427/74427-1.jpg could save 92.6KiB (72% reduction).
Compressing https://www-media.stanford.edu/wp-content/uploads/…23180723/dance-8x5.jpg could save 9.4KiB (21% reduction).
Compressing https://www-media.stanford.edu/wp-content/uploads/…548/femto-1023x682.jpg could save 5.1KiB (24% reduction).

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

Your page has 1 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.

Optimize CSS Delivery of the following:

https://www.stanford.edu/wp-content/plugins/awesom…-weather.css?ver=4.9.3

priority - 7 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:

https://events.stanford.edu/events/267/26721/26721-1.jpg (expiration not specified)
https://events.stanford.edu/events/692/69281/69281-1.jpg (expiration not specified)
https://events.stanford.edu/events/741/74181/74181-2.jpg (expiration not specified)
https://events.stanford.edu/events/744/74427/74427-1.jpg (expiration not specified)
https://www-media.stanford.edu/wp-content/uploads/…s_lab-8x5-1023x640.jpg (expiration not specified)
https://www-media.stanford.edu/wp-content/uploads/…class-8x5-1023x640.jpg (expiration not specified)
https://www-media.stanford.edu/wp-content/uploads/…rning-8x5-1023x640.jpg (expiration not specified)
https://www-media.stanford.edu/wp-content/uploads/…_hall-8x5-1023x640.jpg (expiration not specified)
https://www.google-analytics.com/analytics.js (2 hours)

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 506B (38% reduction).

Minifying https://www.stanford.edu/wp-content/plugins/awesom…et-frontend.js?ver=1.1 could save 506B (38% reduction) after compression.

priority - 0 Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 248B (92% reduction).

Minifying https://www.stanford.edu/wp-content/themes/homesite17/style.css?ver=4.9.3 could save 248B (92% reduction) after compression.

stanford.edu Mobile Resources

Total Resources58
Number of Hosts8
Static Resources34
JavaScript Resources8
CSS Resources7

stanford.edu Mobile Resource Breakdown

stanford.edu mobile page usability

Last tested: 2018-02-07


Mobile Usability Good
99/100

stanford.edu Mobile Usability Test Quick Summary


priority - 0 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 href="#main-content">Explore Stanford</a> is close to 1 other tap targets.

The tap target <a href="https://law.st…s-and-drought/">Running out of…., and drought</a> is close to 1 other tap targets.

The tap target <a href="http://visit.s…plan/maps.html">Maps &amp; Directions</a> is close to 2 other tap targets.
The tap target <a href="http://www.fac…k.com/stanford" class="xsu-link">Facebook</a> and 3 others are close to other tap targets.
The tap target <a href="http://instagram.com/stanford" class="xsu-link">Instagram</a> and 1 others are close to other tap targets.

stanford.edu Mobile Resources

Total Resources58
Number of Hosts8
Static Resources34
JavaScript Resources8
CSS Resources7

stanford.edu Mobile Resource Breakdown

stanford.edu similar domains

Similar domains:
www.stanford.com
www.stanford.net
www.stanford.org
www.stanford.info
www.stanford.biz
www.stanford.us
www.stanford.mobi
www.tanford.edu
www.stanford.edu
www.wtanford.edu
www.swtanford.edu
www.wstanford.edu
www.etanford.edu
www.setanford.edu
www.estanford.edu
www.dtanford.edu
www.sdtanford.edu
www.dstanford.edu
www.ztanford.edu
www.sztanford.edu
www.zstanford.edu
www.xtanford.edu
www.sxtanford.edu
www.xstanford.edu
www.atanford.edu
www.satanford.edu
www.astanford.edu
www.sanford.edu
www.sranford.edu
www.stranford.edu
www.srtanford.edu
www.sfanford.edu
www.stfanford.edu
www.sftanford.edu
www.sganford.edu
www.stganford.edu
www.sgtanford.edu
www.syanford.edu
www.styanford.edu
www.sytanford.edu
www.stnford.edu
www.stqnford.edu
www.staqnford.edu
www.stqanford.edu
www.stwnford.edu
www.stawnford.edu
www.stwanford.edu
www.stsnford.edu
www.stasnford.edu
www.stsanford.edu
www.stznford.edu
www.staznford.edu
www.stzanford.edu
www.staford.edu
www.stabford.edu
www.stanbford.edu
www.stabnford.edu
www.stahford.edu
www.stanhford.edu
www.stahnford.edu
www.stajford.edu
www.stanjford.edu
www.stajnford.edu
www.stamford.edu
www.stanmford.edu
www.stamnford.edu
www.stanord.edu
www.stancord.edu
www.stanfcord.edu
www.stancford.edu
www.standord.edu
www.stanfdord.edu
www.standford.edu
www.stanrord.edu
www.stanfrord.edu
www.stanrford.edu
www.stantord.edu
www.stanftord.edu
www.stantford.edu
www.stangord.edu
www.stanfgord.edu
www.stangford.edu
www.stanvord.edu
www.stanfvord.edu
www.stanvford.edu
www.stanfrd.edu
www.stanfird.edu
www.stanfoird.edu
www.stanfiord.edu
www.stanfkrd.edu
www.stanfokrd.edu
www.stanfkord.edu
www.stanflrd.edu
www.stanfolrd.edu
www.stanflord.edu
www.stanfprd.edu
www.stanfoprd.edu
www.stanfpord.edu
www.stanfod.edu
www.stanfoed.edu
www.stanfored.edu
www.stanfoerd.edu
www.stanfodd.edu
www.stanfordd.edu
www.stanfodrd.edu
www.stanfofd.edu
www.stanforfd.edu
www.stanfofrd.edu
www.stanfotd.edu
www.stanfortd.edu
www.stanfotrd.edu
www.stanfor.edu
www.stanforx.edu
www.stanfordx.edu
www.stanforxd.edu
www.stanfors.edu
www.stanfords.edu
www.stanforsd.edu
www.stanfore.edu
www.stanforde.edu
www.stanforr.edu
www.stanfordr.edu
www.stanforrd.edu
www.stanforf.edu
www.stanfordf.edu
www.stanforc.edu
www.stanfordc.edu
www.stanforcd.edu

stanford.edu 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.


stanford.edu 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.