Infrastructure - https://forrester.com BeaverCheck Audit

F

Redirect Chain

Action

4 redirect(s), 555 ms total

FIX

4 redirect(s), 555 ms total

4 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

4-hop chain could be reduced to 1 hop

Redirect directly from https://forrester.com to https://www.forrester.com/bold/

Uses 302 (temporary) redirect

If permanent, use 301 instead.

Got: https://www.forrester.com/

Redirect overhead: 555 ms total

Got: 555 ms

https://forrester.com

5 ms · HTTP/1.1

301

https://www.forrester.com/

188 ms · HTTP/1.1

302

https://www.forrester.com/bold

153 ms · HTTP/1.1

301

http://www.forrester.com/bold/

2 ms · HTTP/1.1

301

https://www.forrester.com/bold/

206 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://forrester.com	301	5 ms	HTTP/1.1	Varnish
2	https://www.forrester.com/	302	188 ms	HTTP/1.1	Apache
3	https://www.forrester.com/bold	301	153 ms	HTTP/1.1	nginx
4	http://www.forrester.com/bold/	301	2 ms	HTTP/1.1	Varnish
5	https://www.forrester.com/bold/	200	206 ms	HTTP/1.1	nginx

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://forrester.com to https://www.forrester.com/bold/

Why this matters

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

Source: web.dev

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

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

URL Variants

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

REVIEW

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

www/non-www redirect configured correctly (preferred: non-www)

HTTP version does not redirect to HTTPS

Got: HTTP 301 Expected: 301 redirect to HTTPS

www / non-www

302https://www.forrester.com/

200https://forrester.com/

Preferred variant: non-www

HTTP → HTTPS

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

HTTP version does not redirect to HTTPS

B

TLS Certificate Expiry & Recommendations

79 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

79

days left

0d 30d 60d 90d+

Recommended actions

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 Records

4 A records, 39 ms lookup

PASS

4 A records, 39 ms lookup

Resolves to 4 IPv4 address(es)

Got: 151.101.131.52, 151.101.195.52, 151.101.3.52, 151.101.67.52

No IPv6 (AAAA) records

6 nameserver(s) configured

Got: pdns99.ultradns.net, pdns99.ultradns.biz, pdns99.ultradns.com, ns14.ultradns2.com, ns14.ultradns2.org, pdns99.ultradns.org

1 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: 39 ms

Got: 39 ms

A	151.101.131.52, 151.101.195.52, 151.101.3.52, 151.101.67.52
AAAA	—
CNAME	—
NS	pdns99.ultradns.net, pdns99.ultradns.biz, pdns99.ultradns.com, ns14.ultradns2.com, ns14.ultradns2.org, pdns99.ultradns.org
MX	0 forrester-com.mail.protection.outlook.com
TXT	google-site-verification=i1LlQVlwRUTBrK1bKh02eEDyCqcTuXDdk3MKc7XfMkU pexip-ms-tenant-domain-verification=ca0149bd-f11c-42f0-bee8-58901e4c0798 pendo-domain-verification=ade47a0b-2e2a-41a8-961d-712af6319b9e SPF v=spf1 include:1j7kk7v3n.spf.checkpoint-spf.com include:spf.protection.outlook.c... atlassian-domain-verification=ygvObghOLO0UdkhvS8BCG6KIIqPAsMg3zrcS3YkCFtD/m0Gh9n... figma-domain-verification=d897df10f7c614090b5368f2886de2e06c17952d9864900c901e40...
CAA	Lookup not available with standard resolver

Resolved in 39 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 39 URLs

PASS

robots.txt present, sitemap with 39 URLs

robots.txt is present

Got: 1294 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 39 entries

Sitemap index with 39 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

Size 1294 B Sitemaps referenced 1 User-agents GPTBot, ClaudeBot, Claude-User, Google-Extended, CCBot, FacebookBot, Omgilibot, *, Claude-SearchBot Blocking No — crawling allowed

# Duplicate entries with a * prefix are to handle SWFaddress urls (e.g., "/home#/help")
User-agent: *
Disallow: /help
Disallow: /staticassets/fn-maint/
Disallow: /marketing/help
Disallow: /ecomm/
Disallow: /reg/
Disallow: /myaccount/
Disallow: /dl/
Disallow: /api/
Disallow: /v1/api/
Disallow: /forr/companyadmin/
Disallow: /messages 
Disallow: /clipping
Disallow: /calendar
Disallow: /products
Disallow: /contacts
Disallow: /MyAccount
Disallow: /feedback
Disallow: /cart.srv
Disallow: /reg/regmsg.xhtml
Disallow: /pimages/
Disallow: */help
Disallow: */marketing/help
Disallow: */ecomm/
Disallow: */reg/
Disallow: */myaccount/
Disallow: */dl/
Disallow: */forr/companyadmin/
Disallow: */messages 
Disallow: */clipping
Disallow: */calendar
Disallow: */products
Disallow: */contacts
Disallow: */MyAccount
Disallow: */feedback
Disallow: */reg/regmsg.xhtml
Disallow: */Home/0,3257,1,FF.html

User-agent: GPTBot
Disallow: /report/*

User-agent: ClaudeBot
Disallow: /report/*

User-agent: Claude-User
Disallow: /report/*

User-agent: Claude-SearchBot
Disallow: /report/*

User-agent: Google-Extended
Disallow: /report/*

User-agent: CCBot
Disallow: /report/*

User-agent: FacebookBot
Disallow: /report/*

User-agent: Omgilibot
Disallow: /report/*

Sitemap: https://www.forrester.com/sitemap_index.xml

sitemap.xml 200 OK

Type Sitemap Index URLs 39 entries Valid XML Yes

Child Sitemaps:

A+

Domain Intelligence

forrester.com — via GoDaddy Corporate Domains, LLC, 32 years, 4 months old, hosted on Fastly

PASS

forrester.com — via GoDaddy Corporate Domains, LLC, 32 years, 4 months old, hosted on Fastly

Domain registered until May 13, 2031 (5 years, 1 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: Fastly

Got: AS54113

Domain expiry

1792 days

May 13, 2031

SSL certificate

79 days

Issued by Let's Encrypt

Domain age

32 years, 4 months

Registered May 12, 1994

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Fastly

ASN AS54113

151.101.3.52

Registrar

GoDaddy Corporate Domains, LLC

Unlocked 6 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 May 12, 1994 (32 years, 4 months ago)

Expires May 13, 2031 (5 years, 1 months)

Last Updated May 17, 2024

Name Servers ns14.ultradns2.com, ns14.ultradns2.org, pdns99.ultradns.biz, pdns99.ultradns.com, pdns99.ultradns.net, pdns99.ultradns.org

DNSSEC Not enabled

Hosting

IP Address 151.101.3.52

ASN AS54113 (FASTLY - Fastly, Inc., US)

Provider Fastly

Data source: rdap (0.1s)

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

A+

HTTP Probe Timing

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

PASS

DNS Lookup

42 ms

TCP Connect

0 ms

TLS Handshake

3 ms

Time to First Byte

47 ms

Total Time

47 ms

Connection waterfall

DNS Lookup 42 ms TCP Connect 0 ms TLS Handshake 3 ms Server Processing 1 ms Content Transfer 0 ms

A+

CDN & Delivery

Fastly (HIT)

PASS

Fastly (HIT)

Site is served via Fastly CDN

Got: x-served-by: cache-toj-leto2350063-TOJ

CDN cache status: HIT

CDN Detected: Fastly

Provider Fastly Cache Status HIT Evidence x-served-by: cache-toj-leto2350063-TOJ