Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BCrawlabilityrobots.txt present, no sitemapREVIEW
A sitemap helps search engines discover and index your pages more efficiently.
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.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
# Accepter l'indexation
User-agent: *
Crawl-delay: 1
Disallow:
No sitemap found
Adding a sitemap helps search engines discover your pages.
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations35 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
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
ADNS Records1 A records, 214 ms lookupPASS
| A | 132.204.8.144 |
| AAAA | — |
| CNAME | — |
| NS | dnsp2.dit.umontreal.ca, ns2.risq.qc.ca, ns1.risq.qc.ca, dnsp1.dit.umontreal.ca |
| MX | 0 umontreal-ca.mail.protection.outlook.com |
| TXT | ZOOM_verify_JUbGTxRRTg2YzL-q2TqQyg facebook-domain-verification=di3vzdnic7y0ciiwz8ktzu8mdweqa3 apple-domain-verification=mLTV8cNx751rwAOw druide-validation-domaine=87e3a9890a931af8fa24ad802c37e078 _pki-validation.umontreal.ca=DxYe5iwX7EuuGiz7cvrF/Tg==:AFA5-9677-D047-20E1-7D88-... google-site-verification=QHXZGNlmrWVmdBDPvlL5uru5-4U38yeh0-qcpTALgl0 atlassian-domain-verification=GDCjN5qacVk90F32MiO9FuPpRTl7TCdVq0ccb5q4YhW6LbUU1W... ms-domain-verification=51e55ba8-6087-4d11-9fcb-eff118f0914f bcn=E48DC8DC-CF9E-11F0-BFF0-9C8CF66F7529 MS=ms84630678 SPF v=spf1 mx include:spf.protection.outlook.com include:servers.mcsv.net include:sp... MS=ms82235467 4A0p6LSpn7XVS67sNLWJ5S80hqqgn3Q4VpMWvTozpHVcX6tJeLCf1POU67u3cUz6lFlqT2Qq+7xJd6i/... |
| 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), 725 ms totalPASS
https://umontreal.ca
364 ms · HTTP/1.1
https://www.umontreal.ca/
361 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://umontreal.ca | 301 | 364 ms | HTTP/1.1 | |
| 2 | https://www.umontreal.ca/ | 200 | 361 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
A+Domain Intelligenceumontreal.ca — via RIQ, a division of Bell Canada, 25 years, 10 months old, hosted on RISQ-AS - Reseau dInformations Scientifiques du Quebec RISQ Inc., CAPASS
245 days
March 21, 2027
35 days
Issued by SSL Corporation
25 years, 10 months
Registered October 30, 2000
Not enabled
Protects against DNS spoofing
RISQ-AS - Reseau dInformations Scientifiques du Quebec RISQ Inc., CA
ASN AS376
132.204.8.144
RIQ, a division of Bell Canada
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