Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations33 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- 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
ADNS Records1 A records, 618 ms lookupPASS
| A | 23.185.0.1 |
| AAAA | 2620:12a:8000::1, 2620:12a:8001::1 |
| CNAME | — |
| NS | ns1.d-zone.ca, ns2.d-zone.ca |
| MX | 0 utoronto-ca.mail.protection.outlook.com |
| TXT | 38bf4df46c158d180f22361f870e4c48 RtZE2VEP2/QzIJjoV+T/snnUrsF+F++iTOv9Eq7NcsxQBCg8Bkn/ThofRktuubkRu1ScUYMLQY63Q8jf... docusign=80847bb1-e887-47d5-b104-cf63f8e3bac3 SPF v=spf1 ip4:128.100.132.0/24 ip4:128.100.46.0/24 include:spf.protection.outlook.c... MS=ms20198435 brevo-code:83ab89a88c5debbb2705c60771f07248 TAILSCALE-AgypQOMvv8oOYeWaommh pf07f8qcrhh6dlh69bns6ug674 docusign=668454a4-fb56-4c8d-93b8-3443c0ff9812 ZOOM_verify_5A4kl6xEpfIcnBO26Ud44w google-gws-recovery-domain-verification=68902687 adobe-idp-site-verification=576a2585f28cfc23afa878030fbddff608ea5aef81ef9909cf2a... 330fji2sj2c4336s0dla5c2ols have-i-been-pwned-verification=dweb_msabv35o7d4qcfmz7z7j7wqf status-page-domain-verification=42dgkgmmw16m bcn=37A2F2BE-C7F4-11ED-B356-8626DE9BF48C google-site-verification=GjMb_hd1-jWiaU0Tm-d0dj_Bc6glya899VRQP3VlTE4 airtable-verification=b6c00b62fad8981071a4a163565d2014 google-site-verification=znm8bRr_x13to8pAj_sCSsyRCC_y5apsz54WKeIlYA8 atlassian-domain-verification=NYUirRcuGTHieqoDDOA1urA3O3ectAEM/8DMMgQ8bLKtUCQxzO... anthropic-domain-verification-r05mrz=4UyBa5Cw6D2RV9Hy6nP1qPbk2 openai-domain-verification=dv-jwyowy4bjM2M4hqLYHLzDVRW |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
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.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
Slow DNS adds latency to every page load. Consider a faster DNS provider.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
ARedirect Chain1 redirect(s), 52 ms totalPASS
https://utoronto.ca
8 ms · HTTP/1.1
https://www.utoronto.ca/
44 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://utoronto.ca | 301 | 8 ms | HTTP/1.1 | Varnish |
| 2 | https://www.utoronto.ca/ | 200 | 44 ms | HTTP/1.1 | nginx |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (0 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 96 URLsPASS
#
# robots.txt
#
# This file is to prevent the crawling and indexing of certain parts
# of your site by web crawlers and spiders run by sites like Yahoo!
# and Google. By telling these "robots" where not to go on your site,
# you save bandwidth and server resources.
#
# This file will be ignored unless it is at the root of your host:
# Used: http://example.com/robots.txt
# Ignored: http://example.com/site/robots.txt
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/robotstxt.html
User-agent: *
# CSS, JS, Images
Allow: /core/*.css$
Allow: /core/*.css?
Allow: /core/*.js$
Allow: /core/*.js?
Allow: /core/*.gif
Allow: /core/*.jpg
Allow: /core/*.jpeg
Allow: /core/*.png
Allow: /core/*.svg
Allow: /profiles/*.css$
Allow: /profiles/*.css?
Allow: /profiles/*.js$
Allow: /profiles/*.js?
Allow: /profiles/*.gif
Allow: /profiles/*.jpg
Allow: /profiles/*.jpeg
Allow: /profiles/*.png
Allow: /profiles/*.svg
# Directories
Disallow: /core/
Disallow: /profiles/
# Files
Disallow: /README.md
Disallow: /composer/Metapackage/README.txt
Disallow: /composer/Plugin/ProjectMessage/README.md
Disallow: /composer/Plugin/Scaffold/README.md
Disallow: /composer/Plugin/VendorHardening/README.txt
Disallow: /composer/Template/README.txt
Disallow: /modules/README.txt
Disallow: /sites/README.txt
Disallow: /themes/README.txt
Disallow: /web.config
# Paths (clean URLs)
Disallow: /admin/
Disallow: /comment/reply/
Disallow: /filter/tips
Disallow: /node/add/
Disallow: /search/
Disallow: /user/register
Disallow: /user/password
Disallow: /user/login
Disallow: /user/logout
Disallow: /media/oembed
Disallow: /*/media/oembed
# Paths (no clean URLs)
Disallow: /index.php/admin/
Disallow: /index.php/comment/reply/
Disallow: /index.php/filter/tips
Disallow: /index.php/node/add/
Disallow: /index.php/search/
Disallow: /index.php/user/password
Disallow: /index.php/user/register
Disallow: /index.php/user/login
Disallow: /index.php/user/logout
Disallow: /index.php/media/oembed
Disallow: /index.php/*/media/oembed
User-agent: *
# Sitemap
sitemap: https://www.utoronto.ca/sitemap.xml
A+Domain Intelligenceutoronto.ca — via Rebel.ca Corp., 25 years, 11 months oldPASS
1691 days
March 2, 2031
33 days
Issued by Let's Encrypt
25 years, 11 months
Registered September 28, 2000
Not enabled
Protects against DNS spoofing
Unknown
2620:12a:8001::1
Rebel.ca Corp.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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