Skip to content
https://toronto.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 3 REVIEW 1 FIX
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
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more ▾

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

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

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

32
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, 51 ms lookup
PASS
1 A records, 51 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 128.100.5.23
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns1.d-zone.ca, ns2.d-zone.ca
Info::
10 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: 51 ms
Got: 51 ms
A128.100.5.23
AAAA—
CNAME—
NSns1.d-zone.ca, ns2.d-zone.ca
MX
10 s.mx.toronto.edu
10 r.mx.toronto.edu
10 u.mx.toronto.edu
10 o.mx.toronto.edu
10 t.mx.toronto.edu
10 p.mx.toronto.edu
10 v.mx.toronto.edu
10 q.mx.toronto.edu
10 n.mx.toronto.edu
10 m.mx.toronto.edu
TXT
google-site-verification=GjMb_hd1-jWiaU0Tm-d0dj_Bc6glya899VRQP3VlTE4
330fji2sj2c4336s0dla5c2ols
pf07f8qcrhh6dlh69bns6ug674
status-page-domain-verification=42dgkgmmw16m
SPF v=spf1 ip4:128.100.132.0/24 ip4:128.100.46.0/24 include:spf.protection.outlook.c...
have-i-been-pwned-verification=c7e6d10166e0cf4922677bebbca47844
MS=ms20198435
MS=ms98651681
RtZE2VEP2/QzIJjoV+T/snnUrsF+F++iTOv9Eq7NcsxQBCg8Bkn/ThofRktuubkRu1ScUYMLQY63Q8jf...
CAALookup not available with standard resolver
Resolved in 51 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
Redirect Chain
1 redirect(s), 385 ms total
PASS
1 redirect(s), 385 ms total
Info::
Single redirect
Got: https://toronto.edu → https://www.utoronto.ca/ (301)
Info::
WWW normalization redirect
Info::
Cross-domain redirect detected

https://toronto.edu

331 ms · HTTP/1.1

301

https://www.utoronto.ca/

54 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://toronto.edu301331 msHTTP/1.1Apache/2.4.52 (Ubuntu)
2https://www.utoronto.ca/20054 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

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.toronto.edu/
200https://toronto.edu/

Preferred variant: non-www

HTTP → HTTPS

301http://toronto.edu/ → https://www.utoronto.ca/

Consistent

A+
Domain Intelligence
toronto.edu — 40 years, 6 months old, hosted on UTORONTO-AS - University of Toronto, CA
PASS
toronto.edu — 40 years, 6 months old, hosted on UTORONTO-AS - University of Toronto, CA
Info::
Domain registered until Jul 31, 2027 (1 years, 3 months remaining)
Info::
Hosting: UTORONTO-AS - University of Toronto, CA
Got: AS239
Domain expiry

348 days

July 31, 2027

SSL certificate

32 days

Issued by Let's Encrypt

Domain age

40 years, 6 months

Registered May 8, 1986

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

UTORONTO-AS - University of Toronto, CA

ASN AS239

128.100.5.23

Registrar

Registrar unknown

Lock status unknown 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar
Created May 8, 1986 (40 years, 6 months ago)
Expires July 31, 2027 (1 years, 3 months)
Last Updated June 3, 2024
Name Servers ns2.d-zone.ca, ns1.d-zone.ca
Registrant University of Toronto
Hosting
IP Address 128.100.5.23
ASN AS239 (UTORONTO-AS - University of Toronto, CA)
Provider UTORONTO-AS - University of Toronto, CA
Data source: whois (0.9s)
A+
HTTP Probe Timing
Total 371 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
46 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
108 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
110 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
371 ms
Total Time Total request time from DNS lookup through full response.
372 ms

Connection waterfall

DNS Lookup 46 ms TCP Connect 108 ms TLS Handshake 110 ms Server Processing 108 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