Skip to content
https://usask.ca

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
75
GRADE
C
FIX
2
REVIEW
4
PASS
3
INFO
0
Probed from Singapore, Singapore
302 Found
Checks
9
3 PASS 4 REVIEW 2 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 302 Expected: 301 redirect to HTTPS

www / non-www

200https://www.usask.ca/
200https://usask.ca/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://usask.ca/ http://www.usask.ca/

HTTP version does not redirect to HTTPS

D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
Redirect Chain
1 redirect(s), 1323 ms total
REVIEW
1 redirect(s), 1323 ms total
Info::
Single redirect
Got: https://usask.ca → https://www.usask.ca/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://usask.ca
Warning::
Redirect overhead: 1323 ms total
Got: 1323 ms

https://usask.ca

706 ms · HTTP/1.0

302

https://www.usask.ca/

617 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://usask.ca302706 msHTTP/1.0BigIP
2https://www.usask.ca/200617 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 420 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 420 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
#

# This file lists local URLs that well-behaved robots should ignore

#

User-agent: *

Disallow: /cgi-bin/		# includes some large virtual spaces

Disallow: /test/

Disallow: /test.php


#

# Sandboxes and code bases - WCS-1562

#

Disallow: /_uofs-codebase/

Disallow: /_uofs-site-basic/

Disallow: /_usask/

Disallow: /arts-sandbox/

Disallow: /wcs-sandbox/

Disallow: /wcms-sandbox/

Disallow: /usaskcdn-sandbox/


sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
TLS Certificate Expiry & Recommendations
100 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

100
days left
0d 30d 60d 90d+

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
1 A records, 184 ms lookup
PASS
1 A records, 184 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 128.233.195.103
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns1.usask.ca, ns1.d-zone.ca, ns2.usask.ca, ns2.d-zone.ca
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 184 ms
Got: 184 ms
A128.233.195.103
AAAA
CNAME
NSns1.usask.ca, ns1.d-zone.ca, ns2.usask.ca, ns2.d-zone.ca
MX
10 usask-ca.mail.protection.outlook.com
TXT
google-site-verification=aBPFCGnTyB6NX0tejdGkeL6PaAuMUIbtV4Ehd7uggW0
adobe-idp-site-verification=6d59d085a7ad6bf50227e2db9e91e29fd1c7dfdc3f0547b4f4ea...
workplace-domain-verification=8lrmPJL4HARldnYhl8oo16Hn9JJ5f2
cdQryRfnHw394VVEMNNpR+UVDdIOnDchjb14fmJk8Dog675Nz1M4i/PG7gHooC8pDUF8DXNXN4sP9/72...
bcn=913CF5D6-F0AE-11EC-9178-8F43EDC9BA70
MS=ms78208264
google-site-verification=SXX9kuQggzW_DF7-pR_dMAkdhQNUeXzTfbdLtdStKOM
8ET90NBDX38M5XNL9E7FU03G8X8S2VAQ38AEHQY6A
SPF v=spf1 a ip4:168.245.64.247 ip4:128.233.215.0/24 ip4:128.233.238.106 ip4:128.233...
cisco-ci-domain-verification=2951e46c42154ea8ee5e6c9127b74273bc63ea75312fdb2f197...
CAALookup not available with standard resolver
Resolved in 184 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A+
Domain Intelligence
usask.ca — via Tucows.com Co., 25 years, 10 months old, hosted on USASK - University of Saskatchewan, CA
PASS
usask.ca — via Tucows.com Co., 25 years, 10 months old, hosted on USASK - University of Saskatchewan, CA
Info::
Domain registered until Apr 28, 2027 (1 years remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Tucows.com Co.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: USASK - University of Saskatchewan, CA
Got: AS22950
Domain expiry

290 days

April 28, 2027

SSL certificate

100 days

Issued by DigiCert Inc

Domain age

25 years, 10 months

Registered October 13, 2000

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

USASK - University of Saskatchewan, CA

ASN AS22950

128.233.195.103

Registrar

Tucows.com Co.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Tucows.com Co.
Created October 13, 2000 (25 years, 10 months ago)
Expires April 28, 2027 (1 years)
Last Updated March 5, 2026
Name Servers ns1.d-zone.ca, ns1.usask.ca, ns2.d-zone.ca, ns2.usask.ca
DNSSEC Not enabled
Registrant Dave Scarfe
Hosting
IP Address 128.233.195.103
ASN AS22950 (USASK - University of Saskatchewan, CA)
Provider USASK - University of Saskatchewan, CA
Data source: rdap (1.3s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A
HTTP Probe Timing
Total 703 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
4 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
174 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
350 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
704 ms
Total Time Total request time from DNS lookup through full response.
704 ms

Connection waterfall

DNS Lookup 4 ms TCP Connect 174 ms TLS Handshake 350 ms Server Processing 175 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback