Skip to content
https://concordia.ca

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
81
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Santa Clara, United States
307 Temporary Redirect
Checks
9
4 PASS 4 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
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 1023 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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

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 1023 B Sitemaps referenced 0 User-agents Googlebot-news, * Blocking No — crawling allowed
user-agent: *

#

#control parameterization on scientific monitoring pages

Disallow: *scientific-monitoring.html?*

Disallow: *veille-scientifique.html?*

#

#control calendar indexation

Disallow: *calendar-deseve.html?*

Disallow: *calendar-va114.html?*

#

#control search spam

Disallow: /search.html?search-mode=*

#

#disallow crawling of old events pages - 2021 & 2022 still produce traffic

disallow: /cuevents/*/200*

disallow: /cuevents/*/201*

disallow: /cuevents/*/2020/*

Disallow: /ucactualites/*/200*

Disallow: /ucactualites/*/201*

Disallow: /ucactualites/*/2020/*

#

#Control crawling of errant social media site URLs being appended to all-groups.html 

Disallow: */all-groups.html*.com

#

#Block empty root faculty page from crawling so primary faculty page ranks

Disallow: /faculty.html$


Disallow: /news/newsletters/*

Disallow: /services/profile/attachment*

Disallow: /etc/designs/concordia/resources*


User-Agent: Googlebot-news

Disallow: /profiles/

Disallow: /content/shared/en/profiles/*
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

C
URL Variants
Action
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
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.concordia.ca/
200https://concordia.ca/

Inconsistent — duplicate content risk

HTTP → HTTPS

307http://concordia.ca/ https://www.concordia.ca/

Use 301 (permanent) instead of 302 (temporary)

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

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
1 A records, 72 ms lookup
PASS
1 A records, 72 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 132.205.244.185
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: ns1.cc.umanitoba.ca, ns1.zonerisq.ca, ns2.zonerisq.ca, ns-a.concordia.ca, ns-b.concordia.ca, ns1-1.cc.umanitoba.ca
Info::
2 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: 72 ms
Got: 72 ms
A132.205.244.185
AAAA
CNAME
NSns1.cc.umanitoba.ca, ns1.zonerisq.ca, ns2.zonerisq.ca, ns-a.concordia.ca, ns-b.concordia.ca, ns1-1.cc.umanitoba.ca
MX
10 ums-sgw-gw.concordia.ca
10 ums-loy-gw.concordia.ca
TXT
1vqcgpqbl12w1l7xhv5ltbkrj9q74s5r
_66o43uia4qoilex7nyia1tdr5ax80vp
_j345icl9xsq5mn0cackupsdxmkky4dq
_tfncmckq74rua5gju5jo1vef8s7t676
apple-domain-verification=iUVRRs3hJFYY2CAC
MS=181601A53DE8C2F3254D8E00A1198DA937922397
docusign=9e457a72-4f2a-4114-831d-d56cd30c15b2
jamf-site-verification=qg1gAqCuxYrBYGpkQh3l1g
amazonses:JJEgc2X8caKvveKF0PnGDM7lVON1QBt/fDCo18QC6Mg=
knowbe4-site-verification=3d5afed8e3b444af895e4f9828c0b4e2
facebook-domain-verification=jw4n94mv6pja2qr6tjy25iwm8e0t6p
google-site-verification=uOIZvTwus80VB_IdnC9t4akqt-tmMiAUREUcvDo8hMg
_globalsign-domain-verification=-C2dT9yzatXeqjjxdiza_spaIeYnHB9ajTpycaC6pG
_globalsign-domain-verification=1r7-4B_s4TuugHTDktmXVWuMs_IbbUt-MQ04moheXk
_globalsign-domain-verification=GkGfTl8rAs9S59Xaoa41cGQYwwCw7K-ss4BzeKCUAe
_globalsign-domain-verification=Idtfy9h0ljEyPFDlzDsyYtWTtaAH_HaGu2VJz7PiBS
_globalsign-domain-verification=VLbEe4AAqYazWz4TZT8aeHk467u58EVHD2Hu5m1ruC
_globalsign-domain-verification=kY1gyzMmC6sM8NrC3LA3SMrFtbYG4dBKAi5M06TYtE
_globalsign-domain-verification=qLKA0thmOEtbbRtz2UBwDtRRfnnH6r-srYz2xJwRns
b4ePjd4+yFILE7PxBKWsQhZJj32C5CYTRoWOko3gs6+1sscmYSepshKhpUHtA1Fd8u8jGpOnPqvypaAa...
adobe-idp-site-verification=23c0a80f2ab63e221e3706dbed37e5c3c556ca4bd7065d819fe0...
cisco-ci-domain-verification=28a4ea26fa8c540ab097d802f51b8221fe0ba282bf79b7fc91f...
SPF v=spf1 ip4:132.205.153.10 ip4:132.205.157.10 ip4:132.205.123.180 ip4:132.205.123...
CAALookup not available with standard resolver
Resolved in 72 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), 480 ms total
PASS
1 redirect(s), 480 ms total
Info::
Single redirect
Got: https://concordia.ca → https://www.concordia.ca/ (307)
Info::
WWW normalization redirect

https://concordia.ca

229 ms · HTTP/1.1

307

https://www.concordia.ca/

251 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://concordia.ca307229 msHTTP/1.1
2https://www.concordia.ca/200251 msHTTP/1.1Microsoft-IIS/10.0

See the visual redirect chain in the HTTP Probe tab →

A+
Domain Intelligence
concordia.ca — via A.R.C. Informatique Inc., 25 years, 11 months old, hosted on RISQ-AS - Reseau dInformations Scientifiques du Quebec RISQ Inc., CA
PASS
concordia.ca — via A.R.C. Informatique Inc., 25 years, 11 months old, hosted on RISQ-AS - Reseau dInformations Scientifiques du Quebec RISQ Inc., CA
Info::
Domain registered until Apr 7, 2030 (4 years remaining)
Info::
DNSSEC is enabled
Info::
Registrar: A.R.C. Informatique 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: RISQ-AS - Reseau dInformations Scientifiques du Quebec RISQ Inc., CA
Got: AS376
Domain expiry

1361 days

April 7, 2030

SSL certificate

44 days

Issued by GlobalSign nv-sa

Domain age

25 years, 11 months

Registered September 25, 2000

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

RISQ-AS - Reseau dInformations Scientifiques du Quebec RISQ Inc., CA

ASN AS376

132.205.244.185

Registrar

A.R.C. Informatique Inc.

Unlocked 5 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar A.R.C. Informatique Inc.
Created September 25, 2000 (25 years, 11 months ago)
Expires April 7, 2030 (4 years)
Last Updated January 22, 2026
Name Servers ns-a.concordia.ca, ns-b.concordia.ca, ns1.cc.umanitoba.ca, ns1.zonerisq.ca, ns2.zonerisq.ca
DNSSEC Enabled
Registrant Concordia University
Hosting
IP Address 132.205.244.185
ASN AS376 (RISQ-AS - Reseau dInformations Scientifiques du Quebec RISQ Inc., CA)
Provider RISQ-AS - Reseau dInformations Scientifiques du Quebec RISQ Inc., CA
Data source: rdap (0.3s)

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

Connection waterfall

DNS Lookup 14 ms TCP Connect 68 ms TLS Handshake 77 ms Server Processing 72 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