Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.FIPv6 ReadinessActionIPv6 records exist but unreachableFIX
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.
Learn more ▾ ▴
Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.
Source: RFC 8305 (Happy Eyeballs)
CTLS Certificate Expiry & RecommendationsAction23 days until leaf cert expires — 5 issues to addressREVIEW
Certificate validity
Recommended actions
- Renew certificate — 23 days remaining
- Add includeSubDomains to the HSTS directive
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- 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 Records4 A records, 79 ms lookupPASS
| A | 151.101.194.132, 151.101.2.132, 151.101.66.132, 151.101.130.132 |
| AAAA | 2a04:4e42::645, 2a04:4e42:400::645, 2a04:4e42:200::645, 2a04:4e42:600::645 |
| CNAME | — |
| NS | ext-dns-azure-a.uwaterloo.ca, cn-dns-ec2-new.uwaterloo.ca, cn-dns-mc-new.uwaterloo.ca |
| MX | 10 mx2.hc503-62.ca.iphmx.com 10 mx1.hc503-62.ca.iphmx.com |
| TXT | e2ma-verification=nkdcb adobe-idp-site-verification=4dec50d4c90dac093d5e1824a81021691629e2f94fd22b4f2f23... tCDWAp4EmLpfAmyq5fdhO5GwZAI0t7b2RWEuaProESY= globalsign-domain-verification=Q8Dh3hR2uXY5UdIukr4rHDZhsq3SOGVSfcZCmhdgfp atlassian-domain-verification=KTsA2pVA/ItP1xFPT8GLOUb1jgkXmZjaxEYOrv6Z/IuYAxEyMY... ZOOM_verify_7z1v7rXUSOOS-ShYcymx0A b8PB06RrjXJHHTuGGaWkgBpUQl+HYzLLeNzDIlu3Gv/im99YYnCPZQJjzPrB9yLks3ra2mp/C/OM7fnS... google-site-verification=eSSi6Zp_XdwpO8Z-T-lpb3V6tY6X3BvlqJXPeoXs5GQ apple-domain-verification=xc5D2Lp8oXM8J4E2 google-site-verification=tlHpRcZ9EQvp1JMSvMB0NHq4rUgQbaz-hO96RDjguEs 84cc41ef767947fe85ff32fb16bdaf41 MS=78E4ABCABB8A53406B8B16D50FAA6015ACEA3A87 k5sc36lcc2rbjv7h3sl2c2gn0e SPF v=spf1 exists:%{i}.spf.hc503-62.ca.iphmx.com ip4:129.97.0.0/16 include:ca05._spf... |
| CAA | Lookup not available with standard resolver |
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.
A+Redirect ChainNo redirects — direct accessPASS
https://uwaterloo.ca
84 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://uwaterloo.ca | 200 | 84 ms | HTTP/1.1 | nginx |
ACrawlabilityno robots.txt, sitemap with 12 URLsPASS
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.
Learn more ▾ ▴
A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.
Source: robotstxt.org
No robots.txt found
This is fine for most sites — a missing robots.txt allows all crawling by default.
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligenceuwaterloo.ca — via Webnames.ca Inc., 25 years, 11 months old, hosted on FastlyPASS
1323 days
January 29, 2030
23 days
Issued by Certainly
25 years, 11 months
Registered September 20, 2000
Not enabled
Protects against DNS spoofing
Fastly
ASN AS54113
151.101.2.132
Webnames.ca Inc.
Expiry timeline
Recommended actions
- Renew the TLS certificate or verify auto-renewal is working
- 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