USD.EDU University of South Dakota - USD


usd.edu website information.

usd.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 usd.edu domain:

  • ns1-09.azure-dns.com
  • ns2-09.azure-dns.net
  • ns3-09.azure-dns.org
  • ns4-09.azure-dns.info

and probably website usd.edu is hosted by CLOUDFLARENET - Cloudflare, Inc., US web hosting company. Check the complete list of other most popular websites hosted by CLOUDFLARENET - Cloudflare, Inc., US hosting company.

According to Alexa traffic rank the highest website usd.edu position was 12522 (in the world). The lowest Alexa rank position was 14047. Now website usd.edu ranked in Alexa database as number 14002 (in the world).

Website usd.edu Desktop speed measurement score (80/100) is better than the results of 69.89% of other sites and shows that the page is performing great on desktop computers.

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

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

Weekly Rank Report

DateRankChange
Nov-20-2024 N/AN/A
Nov-19-2024 14,002-85
Nov-18-2024 13,917108
Nov-17-2024 14,025-108
Nov-16-2024 13,917-85
Nov-15-2024 13,832153
Nov-14-2024 13,985-58

Advertisement

usd.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.



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

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.

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

Domain Name: USD.EDU

Registrant:
The University of South Dakota
Information Technology Services
414 E. Clark
Vermillion, SD 57069
USA

Administrative Contact:
Cheryl Tiahrt
The University of South Dakota
414 East Clark
Vermillion, SD 57069
USA
+1.6056586025
Cheryl.Tiahrt@usd.edu

Technical Contact:
Kyle Gruhn
The Unviersity of South Dakota
414 East Clark
Vermillion, SD 57069
USA
+1.6056586035
Kyle.Gruhn@usd.edu

Name Servers:
NS3-09.AZURE-DNS.ORG
NS4-09.AZURE-DNS.INFO
NS2-09.AZURE-DNS.NET
NS1-09.AZURE-DNS.COM

Domain record activated: 10-Jul-1986
Domain record last updated: 18-Jun-2024
Domain expires: 31-Jul-2027

usd.edu server information

Servers Location

IP Address
192.236.39.24
Region
South Dakota
City
Vermillion

usd.edu desktop page speed rank

Last tested: 2016-10-14


Desktop Speed Medium
80/100

usd.edu Desktop Speed Test Quick Summary


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

Your page has 3 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:

http://www.usd.edu/Assets/scripts/application.js
http://www.usd.edu/Assets/scripts/moment.min.js
http://www.usd.edu/Assets/scripts/main.js

Optimize CSS Delivery of the following:

http://fonts.googleapis.com/css?family=EB+Garamond…pen+Sans+Condensed:300
http://www.usd.edu/Assets/css/application.css
http://www.usd.edu/Assets/css/font-awesome.css

priority - 4 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 41.1KiB (81% reduction).

Compressing http://www.usd.edu/ could save 41.1KiB (81% reduction).

priority - 3 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://www.usd.edu/Assets/css/application.css (expiration not specified)
http://www.usd.edu/Assets/css/font-awesome.css (expiration not specified)
http://www.usd.edu/Assets/scripts/application.js (expiration not specified)
http://www.usd.edu/Assets/scripts/main.js (expiration not specified)
http://www.usd.edu/Assets/scripts/moment.min.js (expiration not specified)
http://www.googletagmanager.com/gtm.js?id=GTM-TNWDTK (15 minutes)
http://www.google-analytics.com/analytics.js (2 hours)

priority - 3 Reduce server response time

In our test, your server responded in 0.35 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

priority - 2 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 20.4KiB (27% reduction).

Minifying http://www.usd.edu/Assets/scripts/application.js could save 19.5KiB (28% reduction) after compression.
Minifying http://www.usd.edu/Assets/scripts/main.js could save 910B (19% reduction) after compression.

priority - 2 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 15.2KiB (31% reduction).

Minifying http://www.usd.edu/ could save 15.2KiB (31% reduction).

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

Minifying http://www.usd.edu/Assets/css/application.css could save 6.2KiB (18% reduction) after compression.

usd.edu Desktop Resources

Total Resources33
Number of Hosts9
Static Resources17
JavaScript Resources5
CSS Resources3

usd.edu Desktop Resource Breakdown

usd.edu mobile page speed rank

Last tested: 2016-10-14


Mobile Speed Medium
68/100

usd.edu Mobile Speed Test Quick Summary


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

Your page has 3 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:

http://www.usd.edu/Assets/scripts/application.js
http://www.usd.edu/Assets/scripts/moment.min.js
http://www.usd.edu/Assets/scripts/main.js

Optimize CSS Delivery of the following:

http://fonts.googleapis.com/css?family=EB+Garamond…pen+Sans+Condensed:300
http://www.usd.edu/Assets/css/application.css
http://www.usd.edu/Assets/css/font-awesome.css

priority - 5 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://www.usd.edu/Assets/css/application.css (expiration not specified)
http://www.usd.edu/Assets/css/font-awesome.css (expiration not specified)
http://www.usd.edu/Assets/scripts/application.js (expiration not specified)
http://www.usd.edu/Assets/scripts/main.js (expiration not specified)
http://www.usd.edu/Assets/scripts/moment.min.js (expiration not specified)
http://www.googletagmanager.com/gtm.js?id=GTM-TNWDTK (15 minutes)
http://www.google-analytics.com/analytics.js (2 hours)

priority - 4 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 41.1KiB (81% reduction).

Compressing http://www.usd.edu/ could save 41.1KiB (81% reduction).

priority - 2 Reduce server response time

In our test, your server responded in 0.35 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

priority - 2 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 20.4KiB (27% reduction).

Minifying http://www.usd.edu/Assets/scripts/application.js could save 19.5KiB (28% reduction) after compression.
Minifying http://www.usd.edu/Assets/scripts/main.js could save 910B (19% reduction) after compression.

priority - 2 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 15.2KiB (31% reduction).

Minifying http://www.usd.edu/ could save 15.2KiB (31% reduction).

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

Minifying http://www.usd.edu/Assets/css/application.css could save 6.2KiB (18% reduction) after compression.

usd.edu Mobile Resources

Total Resources33
Number of Hosts9
Static Resources17
JavaScript Resources5
CSS Resources3

usd.edu Mobile Resource Breakdown

usd.edu mobile page usability

Last tested: 2016-10-14


Mobile Usability Good
100/100

usd.edu similar domains

Similar domains:
www.usd.com
www.usd.net
www.usd.org
www.usd.info
www.usd.biz
www.usd.us
www.usd.mobi
www.sd.edu
www.usd.edu
www.ysd.edu
www.uysd.edu
www.yusd.edu
www.hsd.edu
www.uhsd.edu
www.husd.edu
www.jsd.edu
www.ujsd.edu
www.jusd.edu
www.isd.edu
www.uisd.edu
www.iusd.edu
www.ud.edu
www.uwd.edu
www.uswd.edu
www.uwsd.edu
www.ued.edu
www.used.edu
www.uesd.edu
www.udd.edu
www.usdd.edu
www.udsd.edu
www.uzd.edu
www.uszd.edu
www.uzsd.edu
www.uxd.edu
www.usxd.edu
www.uxsd.edu
www.uad.edu
www.usad.edu
www.uasd.edu
www.us.edu
www.usx.edu
www.usdx.edu
www.uss.edu
www.usds.edu
www.ussd.edu
www.use.edu
www.usde.edu
www.usr.edu
www.usdr.edu
www.usrd.edu
www.usf.edu
www.usdf.edu
www.usfd.edu
www.usc.edu
www.usdc.edu
www.uscd.edu

usd.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.


usd.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.