Skip to content
https://ualberta.ca

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
76
GRADE
C
FIX
2
REVIEW
2
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 2 REVIEW 2 FIX
F
Redirect Chain
Action
5 redirect(s), 1557 ms total
FIX
5 redirect(s), 1557 ms total
Warning::
5 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
HTTP to HTTPS redirect present
Info::
WWW normalization redirect
Warning::
5-hop chain could be reduced to 1 hop
Redirect directly from https://ualberta.ca to https://www.ualberta.ca/en/index.html
Warning::
Redirect overhead: 1557 ms total
Got: 1557 ms

https://ualberta.ca

704 ms · HTTP/1.1

301

https://www.ualberta.ca/

295 ms · HTTP/1.1

301

http://www.ualberta.ca/en/

62 ms · HTTP/1.1

301

https://www.ualberta.ca/en/

210 ms · HTTP/1.1

301

http://www.ualberta.ca/en/index.html

62 ms · HTTP/1.1

301

https://www.ualberta.ca/en/index.html

224 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ualberta.ca301704 msHTTP/1.1nginx
2https://www.ualberta.ca/301295 msHTTP/1.1Apache/2.4.66 ()
3http://www.ualberta.ca/en/30162 msHTTP/1.1CloudFront
4https://www.ualberta.ca/en/301210 msHTTP/1.1Apache/2.4.66 ()
5http://www.ualberta.ca/en/index.html30162 msHTTP/1.1CloudFront
6https://www.ualberta.ca/en/index.html200224 msHTTP/1.1Apache/2.4.66 ()

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

Redirect directly from https://ualberta.ca to https://www.ualberta.ca/en/index.html

Why this matters

Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.

Source: web.dev

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.

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
TLS Certificate Expiry & Recommendations
45 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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, 164 ms lookup
PASS
1 A records, 164 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 52.32.177.72
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
5 nameserver(s) configured
Got: nom.ualberta.ca, name.ualberta.ca, ns1.d-zone.ca, uans1prd.ualberta.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: 164 ms
Got: 164 ms
A52.32.177.72
AAAA—
CNAME—
NSnom.ualberta.ca, name.ualberta.ca, ns1.d-zone.ca, uans1prd.ualberta.ca, ns2.d-zone.ca
MX
5 mx.ualberta.ca
TXT
QCs4d3JIlwU5ci98HvnZ1EAEoA0pFh84rGC4a6tkVyE=
dtUHhJAUlpOXVhqlO10KcrkrvVRozY6XYZA9QrH73Oo=
_globalsign-domain-verification=pRA-bvZvzngQzWg8d-hG1uRY3kZx3Fekr8fAHxRTjU
cisco-ci-domain-verification=259e63976ca96fa50e49036977d1a9f3d042ab47486b44e3a8f...
b8YRbhSGe0g80hai+8f2Pmie58s46utjYxF2C+Zi24M=
ZOOM_verify_bd-fCm1WTXOvEdhfJl5VIQ
SPF v=spf1 include:_spf.ualberta.ca include:_spf.google.com ?all
MS=ms30097096
atlassian-domain-verification=kQd97sUb-d7qzayyTc6BiaS0QKEaiSpTvz4DyojAXYBhRi7N6O...
7gyOT2z+huN8M7JH84p5TtSjvqAeeY5PSC1zrvGRB3c=
brevo-code:b1414e0a234265a2faa294058248ae06
kSPPWAyqMhE6KcziEVoEHBcHzzpPwQTeKm0bnP63n/M=
google-site-verification=Rx4OrbN7WUyBILkpOzk-GFIjK2xGNpXVV01HRMEAwLs
adobe-idp-site-verification=9931576ad2a690e3d693c72f5170bd4a7f77222355adc478629f...
CAALookup not available with standard resolver
Resolved in 164 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+
Crawlability
robots.txt present, sitemap with 248 URLs
PASS
robots.txt present, sitemap with 248 URLs
Info::
robots.txt is present
Got: 167 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 248 entries
Info::
Sitemap index with 248 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 167 B Sitemaps referenced 0 User-agents *, coveobot Blocking No — crawling allowed
User-Agent: *

Disallow: /homepage-archive/

Disallow: /facilities/

Allow: /facilities/index.html

Disallow: /ProdStage


User-Agent: coveobot

Allow: /facilities/
sitemap.xml 200 OK
Type Sitemap Index URLs 248 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.ualberta.ca/
200https://ualberta.ca/

Preferred variant: non-www

HTTP → HTTPS

301http://ualberta.ca/ → https://www.ualberta.ca/

Consistent

A+
Domain Intelligence
ualberta.ca — via easyDNS Technologies Inc., 25 years, 11 months old, hosted on AWS
PASS
ualberta.ca — via easyDNS Technologies Inc., 25 years, 11 months old, hosted on AWS
Info::
Domain registered until Dec 20, 2032 (6 years, 9 months 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: easyDNS Technologies Inc.
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: AWS
Got: AS16509
Domain expiry

2349 days

December 20, 2032

SSL certificate

45 days

Issued by GlobalSign nv-sa

Domain age

25 years, 11 months

Registered October 4, 2000

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

52.32.177.72

Registrar

easyDNS Technologies Inc.

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 easyDNS Technologies Inc.
Created October 4, 2000 (25 years, 11 months ago)
Expires December 20, 2032 (6 years, 9 months)
Last Updated May 16, 2024
Name Servers name.ualberta.ca, nom.ualberta.ca, ns1.d-zone.ca, ns2.d-zone.ca
DNSSEC Not enabled
Registrant University of Alberta
Hosting
IP Address 52.32.177.72
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.5s)

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 729 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
31 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
175 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
348 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
730 ms
Total Time Total request time from DNS lookup through full response.
730 ms

Connection waterfall

DNS Lookup 31 ms TCP Connect 175 ms TLS Handshake 348 ms Server Processing 176 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