Skip to content
https://dal.ca

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Singapore, Singapore
301 Moved Permanently
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
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.dal.ca/
200https://dal.ca/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://dal.ca/ https://www.dal.ca/

Consistent

B
HTTP Probe Timing
Total 900 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
4 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
223 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
450 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
901 ms
Total Time Total request time from DNS lookup through full response.
901 ms

Connection waterfall

DNS Lookup 4 ms TCP Connect 223 ms TLS Handshake 450 ms Server Processing 224 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
235 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

235
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, 4 ms lookup
PASS
1 A records, 4 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 129.173.31.187
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::
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: 4 ms
Got: 4 ms
A129.173.31.187
AAAA
CNAME
NSns1.d-zone.ca, ns2.d-zone.ca
MX
0 dal-ca.mail.protection.outlook.com
TXT
asv=da02ef79740e6388f96d94a3b017ee8e
apple-domain-verification=wUDBRU7icoRXwyRY
atlassian-sending-domain-verification=b8939af5-becc-45a7-b7e8-5c66269add21
SPF v=spf1 mx ip4:64.50.144.0/20 ip4:192.254.116.40/32 ip4:204.63.190.0/23 ip4:64.26...
atlassian-domain-verification=ydOKYvf0dIO7QBaCQzN5zmUB5zeZ35xRqE3ujmNr855mSuqGhM...
CAALookup not available with standard resolver
Resolved in 4 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), 909 ms total
PASS
1 redirect(s), 909 ms total
Info::
Single redirect
Got: https://dal.ca → https://www.dal.ca/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 909 ms total
Got: 909 ms

https://dal.ca

899 ms · HTTP/1.1

301

https://www.dal.ca/

10 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://dal.ca301899 msHTTP/1.1Apache/2.4.62 (Red Hat Enterprise Linux) OpenSSL/3.5.1 mod_fcgid/2.3.9
2https://www.dal.ca/20010 msHTTP/1.1nginx/1.14.1

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 119 URLs
PASS
robots.txt present, sitemap with 119 URLs
Info::
robots.txt is present
Got: 44 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 119 entries
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 44 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: */search.html?*q=*$

A+
Domain Intelligence
dal.ca — via Webnames.ca Inc., 25 years, 10 months old, hosted on DALUNIV - Dalhousie University, CA
PASS
dal.ca — via Webnames.ca Inc., 25 years, 10 months old, hosted on DALUNIV - Dalhousie University, CA
Info::
Domain registered until Jun 18, 2030 (4 years, 2 months remaining)
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: Webnames.ca 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: DALUNIV - Dalhousie University, CA
Got: AS8111
Domain expiry

1463 days

June 18, 2030

SSL certificate

235 days

Issued by DigiCert Inc

Domain age

25 years, 10 months

Registered October 25, 2000

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

DALUNIV - Dalhousie University, CA

ASN AS8111

129.173.31.187

Registrar

Webnames.ca Inc.

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Webnames.ca Inc.
Created October 25, 2000 (25 years, 10 months ago)
Expires June 18, 2030 (4 years, 2 months)
Last Updated April 13, 2026
Name Servers ns1.d-zone.ca, ns2.d-zone.ca
DNSSEC Not enabled
Registrant Jay Pasemko
Hosting
IP Address 129.173.31.187
ASN AS8111 (DALUNIV - Dalhousie University, CA)
Provider DALUNIV - Dalhousie University, CA
Data source: rdap (1.2s)

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback