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
User-agent: *
Disallow: /_ADMIN/
Disallow: /_internal/
Disallow: /DEVL/
Disallow: /okanagan/facultystaff/bba
Disallow: /okanagan/itservices/service-catalogue/accounts/novell/imanager.html
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 & Recommendations176 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
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
ADNS Records1 A records, 203 ms lookupPASS
| A | 52.223.56.149 |
| AAAA | — |
| CNAME | — |
| NS | dns3.ubc.ca, nightbird.eis.utoronto.ca, hub.ubc.ca |
| MX | 6 esva.mail-relay.ubc.ca |
| TXT | google-site-verification=R9cO7rkuHJbNgGfmWNU6QoT-M_McG2CAYT8UrnVblyA 1 17446cc0-b680-11d0-9c89-89524766aa77 Master /.../ubc.ca/css3_ch 1ada77aa-adc0-... _t3b6l0ypgbtowyxhx29r5lat51e7rkb SPF v=spf1 redirect=_spf.ubc.ca MS=ms18503103 00D6A000002iFfi=1TBON00000004lE status-page-domain-verification=0fvty1h81vdc _86fe10bcf2a9b7bff5236413c6491499.hsmgrxbjqd.acm-validations.aws. 1 17446cc0-b680-11d0-9c89-89524766aa77 Readonly /.../ubc.ca/css4_ch b69281c0-adc... dg8sdmeh2qb8jok5ntgu9uhrvk google-site-verification=FvAn1UCFiztLsNwhPDp0Zu_R6obmeBI9EKIBUWH66m4 google-site-verification=UMUrsb6ODL9E9jIpiUYlpHGgr6QuBbs3RJo3CAonLsM vmware-cloud-verification-76214695-a291-4fe0-86aa-10a320c21194 MS=ms10900305 00D5o0000008aLS=1TBJR00000007MU yahoo-verification-key=TS+lfUKc/Ury3j4sW2vZ1muLWY1vjvASZAkLEOngMpg= 00DKj000001Cj5z=1TBOG00000006mz google-site-verification=w7lDcYrH76wXY8ygnTdalcL0Qne_kLWyfXcwyBaGtj0 1 17446cc0-b680-11d0-9c89-89524766aa77 Master /.../ubc.ca/css3_ch 1ada77aa-adc0... |
| 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), 358 ms totalPASS
https://ubc.ca
280 ms · HTTP/1.1
https://www.ubc.ca:443/
77 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://ubc.ca | 301 | 280 ms | HTTP/1.1 | awselb/2.0 |
| 2 | https://www.ubc.ca:443/ | 200 | 77 ms | HTTP/1.1 | Apache/2.4.59 () |
See the visual redirect chain in the HTTP Probe tab →
A+Domain Intelligenceubc.ca — via Webnames.ca Inc., 25 years, 10 months old, hosted on AWSPASS
944 days
January 13, 2029
176 days
Issued by Amazon
25 years, 10 months
Registered October 5, 2000
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
52.223.56.149
Webnames.ca Inc.
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