Skip to content
https://Lakemount.ca

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
1
REVIEW
1
PASS
7
INFO
0
Probed from Santa Clara, United Stated
200 OK
Checks
9
7 PASS 1 REVIEW 1 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2606:4700:3033::ac43:da51, 2606:4700:3031::6815:1868
Info::
IPv6 connection error
Got: dial tcp6 [2606:4700:3033::ac43:da51]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2606:4700:3033::ac43:da51, 2606:4700:3031::6815:1868 Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

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)

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

Certificate validity

39
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
2 A records, 27 ms lookup
PASS
2 A records, 27 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.21.24.104, 172.67.218.81
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3033::ac43:da51, 2606:4700:3031::6815:1868
Info::
2 nameserver(s) configured
Got: desi.ns.cloudflare.com, seamus.ns.cloudflare.com
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: 27 ms
Got: 27 ms
A104.21.24.104, 172.67.218.81
AAAA2606:4700:3033::ac43:da51, 2606:4700:3031::6815:1868
CNAME
NSdesi.ns.cloudflare.com, seamus.ns.cloudflare.com
MX
0 lakemount-ca.mail.protection.outlook.com
TXT
SPF v=spf1 include:spf.protection.outlook.com include:spf.skystreamhosting.com a inc...
CAALookup not available with standard resolver
Resolved in 27 ms

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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://Lakemount.ca

https://Lakemount.ca

353 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://Lakemount.ca200353 msHTTP/1.1cloudflare
A+
Crawlability
robots.txt present, sitemap with 5 URLs
PASS
robots.txt present, sitemap with 5 URLs
Info::
robots.txt is present
Got: 170 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 5 entries
Info::
Sitemap index with 5 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 170 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:

Sitemap: https://lakemount.ca/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.Lakemount.ca/
200https://Lakemount.ca/

Preferred variant: non-www

HTTP → HTTPS

301http://Lakemount.ca/ https://Lakemount.ca/

Consistent

A+
Domain Intelligence
Lakemount.ca — via Rebel.ca Corp., 25 years, 7 months old, hosted on Cloudflare
PASS
Lakemount.ca — via Rebel.ca Corp., 25 years, 7 months old, hosted on Cloudflare
Info::
Domain registered until Dec 26, 2026 (8 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: Rebel.ca Corp.
Info::
Hosting: Cloudflare
Got: AS13335
Domain expiry

193 days

December 26, 2026

SSL certificate

39 days

Issued by Google Trust Services

Domain age

25 years, 7 months

Registered December 26, 2000

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.21.24.104

Registrar

Rebel.ca Corp.

Lock status unknown 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
Registrar Rebel.ca Corp.
Created December 26, 2000 (25 years, 7 months ago)
Expires December 26, 2026 (8 months)
Last Updated February 9, 2026
Name Servers desi.ns.cloudflare.com, seamus.ns.cloudflare.com
DNSSEC Not enabled
Registrant Lakemount Worship Centre
Hosting
IP Address 104.21.24.104
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: rdap (0.3s)

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

A+
HTTP Probe Timing
Total 343 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
11 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
2 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
8 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
335 ms
Total Time Total request time from DNS lookup through full response.
344 ms

Connection waterfall

DNS Lookup 11 ms TCP Connect 2 ms TLS Handshake 8 ms Server Processing 313 ms Content Transfer 9 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: SJC)
Got: cf-ray: 9e889858e9bfebe5-SJC
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: 9e889858e9bfebe5-SJC
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback