Skip to content
https://ulaval.ca

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Santa Clara, United States
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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
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
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.ulaval.ca/
200https://ulaval.ca/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://ulaval.ca/ → https://ulaval.ca/

Consistent

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

Certificate validity

321
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, 112 ms lookup
PASS
1 A records, 112 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 132.203.189.82
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.zonerisq.ca, ns2.zonerisq.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: 112 ms
Got: 112 ms
A132.203.189.82
AAAA—
CNAME—
NSns1.zonerisq.ca, ns2.zonerisq.ca
MX
0 ulaval-ca.mail.protection.outlook.com
TXT
apple-domain-verification=eNkUalbnkefoeLm3
ZOOM_verify_Y_UUSbDdS4iVi1SQsjPJag
google-site-verification=gHCV8pw6VG5TA9aoyg7hGEr3p4w7zPjQvodTNCLPFqU
vmware-cloud-verification-a2739a7b-eb48-4ca2-baca-b20e2188f877
7ttapt8ia17k6jdcjfrebr5j4v
google-site-verification=dGLR3hwen8f5eM4yvvD57WcqTNCnGoaJaahMNovgTe8
dipublique.chaire=2032ff26b4db55b8b47b2ae7728095eb
google-site-verification=dLhLsVsJNMUKVOg782M8IJ8MwFaXQiCXagIla5pqdDo
_globalsign-domain-verification=WnsY7VsdaFoAkJwl5AscdcnbvEl_FLnqkwSN6U0ZHu
atlassian-sending-domain-verification=268d8054-35c4-46a2-9012-338f442ff181
atlassian-domain-verification=zBgV1wzyGHcuM3HuoxLBFHBw5axkYTH6L85hsTuH/mFfmgC6ZS...
cisco-ci-domain-verification=1ff8990c2e2d745ced2f68e36f968410a4fad2dcee2d5aa9b14...
mindmanager-verification=94506342061e0af8c0c014114efa757104c31e9bcb553a83787a4d9...
_globalsign-domain-verification=08PkAcai-OPx9VSpk-sNV1kt8RI9Jm9I3eG9qEEoFO
UWgpYOahc2mXCoaniKW0b3GXozHoHi+RETZ0O1yTQno=
SPF v=spf1 MX include:spf.protection.outlook.com include:ofsys.com include:cust-spf....
7Pe1PkwK8xJRnpKfPxVeLGqZCozcEuF33o9EXFcQO4LwfEUsJasZuaj0nTCeupVaoYa/lAraiRdNQlfd...
MdmKB7yZAQkWzdVOWXcRFl9PJi+hOnl7qcYe+JT/40Dbv7Y7xDpMtE9DqvK7OTcdsjEnnDbk+cCDYayr...
CAALookup not available with standard resolver
Resolved in 112 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), 676 ms total
PASS
1 redirect(s), 676 ms total
Info::
Single redirect
Got: https://ulaval.ca → https://www.ulaval.ca/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 676 ms total
Got: 676 ms

https://ulaval.ca

325 ms · HTTP/1.1

301

https://www.ulaval.ca/

351 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ulaval.ca301325 msHTTP/1.1
2https://www.ulaval.ca/200351 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 13 URLs
PASS
robots.txt present, sitemap with 13 URLs
Info::
robots.txt is present
Got: 1706 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 13 entries
Info::
Sitemap index with 13 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 1706 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
#
# 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.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
sitemap.xml 200 OK
Type Sitemap Index URLs 13 entries Valid XML Yes
Child Sitemaps:
A
Domain Intelligence
ulaval.ca — via Tucows.com Co., 25 years, 10 months old, hosted on UNIVERSITE-LAVAL - Universite Laval, CA
PASS
ulaval.ca — via Tucows.com Co., 25 years, 10 months old, hosted on UNIVERSITE-LAVAL - Universite Laval, CA
Warning::
Domain expires in 35 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires May 28, 2026
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: UNIVERSITE-LAVAL - Universite Laval, CA
Got: AS36786
Domain expiry

EXPIRED

May 28, 2026

SSL certificate

321 days

Issued by Sectigo Limited

Domain age

25 years, 10 months

Registered October 15, 2000

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

UNIVERSITE-LAVAL - Universite Laval, CA

ASN AS36786

132.203.189.82

Registrar

Tucows.com Co.

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Tucows.com Co.
Created October 15, 2000 (25 years, 10 months ago)
Expires May 28, 2026 (1 months)
Last Updated April 27, 2025
Name Servers ns1.zonerisq.ca, ns2.zonerisq.ca
DNSSEC Not enabled
Registrant Universite Laval
Hosting
IP Address 132.203.189.82
ASN AS36786 (UNIVERSITE-LAVAL - Universite Laval, CA)
Provider UNIVERSITE-LAVAL - Universite Laval, CA
Data source: rdap (0.3s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

Connection waterfall

DNS Lookup 27 ms TCP Connect 73 ms TLS Handshake 149 ms Server Processing 91 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