Infrastructure - https://walkscore.com BeaverCheck Audit

D

Redirect Chain

Action

2 redirect(s), 2654 ms total

FIX

2 redirect(s), 2654 ms total

2 redirects before reaching final URL

Each redirect adds latency. Try to minimize the chain to 1 hop.

HTTP to HTTPS redirect present

WWW normalization redirect

2-hop chain could be reduced to 1 hop

Redirect directly from https://walkscore.com to https://www.walkscore.com/

Redirect overhead: 2654 ms total

Got: 2654 ms

https://walkscore.com

1072 ms · HTTP/1.1

301

http://www.walkscore.com/

511 ms · HTTP/1.1

301

https://www.walkscore.com/

1070 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://walkscore.com	301	1072 ms	HTTP/1.1	Apache/2.4.29 (Ubuntu)
2	http://www.walkscore.com/	301	511 ms	HTTP/1.1	Apache/2.4.29 (Ubuntu)
3	https://www.walkscore.com/	200	1070 ms	HTTP/1.1	Apache/2.4.29 (Ubuntu)

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

Redirect directly from https://walkscore.com to https://www.walkscore.com/

Why this matters

Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.

Source: web.dev

D

URL Variants

Action

www/non-www, trailing slash, HTTP→HTTPS

FIX

www/non-www, trailing slash, HTTP→HTTPS

Both www and non-www versions serve content

Got: Both variants return 200 Expected: One variant 301-redirects to the other

HTTP version does not redirect to HTTPS

Got: HTTP 301 Expected: 301 redirect to HTTPS

www / non-www

200https://www.walkscore.com/

200https://walkscore.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://walkscore.com/ → http://www.walkscore.com/

HTTP version does not redirect to HTTPS

D

CDN & Delivery

Action

No CDN detected

FIX

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

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

HTTP Probe Timing

Total 1059 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

REVIEW

DNS Lookup

100 ms

TCP Connect

239 ms

TLS Handshake

479 ms

Time to First Byte

1.06 s

Total Time

1.06 s

Connection waterfall

DNS Lookup 100 ms TCP Connect 239 ms TLS Handshake 479 ms Server Processing 241 ms Content Transfer 0 ms

B

TLS Certificate Expiry & Recommendations

142 days until leaf cert expires — 4 issues to address

REVIEW

Certificate validity

142

days left

0d 30d 60d 90d+

Recommended actions

Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
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

3 A records, 196 ms lookup

PASS

3 A records, 196 ms lookup

Resolves to 3 IPv4 address(es)

Got: 100.29.228.18, 23.21.15.181, 52.5.207.33

No IPv6 (AAAA) records

4 nameserver(s) configured

Got: ns-1019.awsdns-63.net, ns-1116.awsdns-11.org, ns-1893.awsdns-44.co.uk, ns-236.awsdns-29.com

5 mail exchanger(s) configured

CAA records not checked

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

SPF record present in TXT

DNS resolution time: 196 ms

Got: 196 ms

A	100.29.228.18, 23.21.15.181, 52.5.207.33
AAAA	—
CNAME	—
NS	ns-1019.awsdns-63.net, ns-1116.awsdns-11.org, ns-1893.awsdns-44.co.uk, ns-236.awsdns-29.com
MX	1 aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 aspmx3.googlemail.com 10 aspmx2.googlemail.com
TXT	facebook-domain-verification=ijqqm9vauj4mkfho66art2uzbkwk43 google-site-verification=aAQql7ISkj9Hr6BsPb2Nbk8qzbVMaTsPcH6ycwUgt5Q google-site-verification=suePZ7MGZ0Rm0JjagmtU2t4Dq7nLaVvc6EIr_4dnwDs SPF v=spf1 include:_s94866777.fdmarc.net ~all
CAA	Lookup not available with standard resolver

Resolved in 196 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

Crawlability

robots.txt present, sitemap with 0 URLs

PASS

robots.txt present, sitemap with 0 URLs

robots.txt is present

Got: 719 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml is empty — no URLs found

An empty sitemap provides no value. Add <url> entries for your pages.

robots.txt references sitemap

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more ▾

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

robots.txt 200 OK

Size 719 B Sitemaps referenced 4 User-agents * Blocking No — crawling allowed

User-agent: *
Disallow: /2008/
Disallow: /apartments/search/
Disallow: /auth/
Disallow: /badge/
Disallow: /choice/
Disallow: /commute/
Disallow: /debug
Disallow: /homes/search/
Disallow: /homes-for-sale/search/
Disallow: /list/
Disallow: /nearby/
Disallow: /place-details/
Disallow: /place-category/
Disallow: /report/
Disallow: /settings
Disallow: /serve-walkscore-tile.php
Disallow: /serve-tile.php
Disallow: /tile/
Disallow: /data/

Sitemap: https://s3.amazonaws.com/sitemaps.walkscore/sitemap_uni.txt
Sitemap: https://s3.amazonaws.com/sitemaps.walkscore/sitemap_cities.txt
Sitemap: https://s3.amazonaws.com/sitemaps.walkscore/sitemap_other.txt
Sitemap: https://s3.amazonaws.com/sitemaps.walkscore/sitemap_index.xml

sitemap.xml 200 OK

Type URL Set URLs 0 entries Valid XML Yes

A+

Domain Intelligence

walkscore.com — via GoDaddy Corporate Domains, LLC, 19 years, 1 months old, hosted on AWS

PASS

walkscore.com — via GoDaddy Corporate Domains, LLC, 19 years, 1 months old, hosted on AWS

Domain registered until Jun 21, 2028 (2 years, 2 months remaining)

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.

Registrar: GoDaddy Corporate Domains, LLC

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.

Hosting: AWS

Got: AS14618

Domain expiry

707 days

June 21, 2028

SSL certificate

142 days

Issued by Amazon

Domain age

19 years, 1 months

Registered June 21, 2007

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

23.21.15.181

Registrar

GoDaddy Corporate Domains, LLC

Unlocked 4 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 GoDaddy Corporate Domains, LLC

Created June 21, 2007 (19 years, 1 months ago)

Expires June 21, 2028 (2 years, 2 months)

Last Updated January 20, 2026

Name Servers ns-1019.awsdns-63.net, ns-1116.awsdns-11.org, ns-1893.awsdns-44.co.uk, ns-236.awsdns-29.com

DNSSEC Not enabled

Hosting

IP Address 23.21.15.181

ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)

Provider AWS

Data source: rdap (0.6s)

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