Skip to content
https://raspberrypi.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Sao Paulo, Brazil
302 Found
Checks
9
5 PASS 4 REVIEW
B
Redirect Chain
1 redirect(s), 2039 ms total
REVIEW
1 redirect(s), 2039 ms total
Info::
Single redirect
Got: https://raspberrypi.com → https://www.raspberrypi.com/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://raspberrypi.com
Warning::
Redirect overhead: 2039 ms total
Got: 2039 ms

https://raspberrypi.com

1043 ms · HTTP/1.1

302

https://www.raspberrypi.com/

996 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://raspberrypi.com3021043 msHTTP/1.1cloudflare
2https://www.raspberrypi.com/200996 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

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
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.raspberrypi.com/
200https://raspberrypi.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://raspberrypi.com/ https://www.raspberrypi.com/

Use 301 (permanent) instead of 302 (temporary)

B
HTTP Probe Timing
Total 1043 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
157 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.
9 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.04 s
Total Time Total request time from DNS lookup through full response.
1.04 s

Connection waterfall

DNS Lookup 157 ms TCP Connect 2 ms TLS Handshake 9 ms Server Processing 875 ms Content Transfer 1 ms
B
TLS Certificate Expiry & Recommendations
42 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

42
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, 202 ms lookup
PASS
2 A records, 202 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.21.88.234, 172.67.154.53
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3037::ac43:9a35, 2606:4700:3034::6815:58ea
Info::
2 nameserver(s) configured
Got: ns1.mythic-beasts.com, ns2.mythic-beasts.com
Info::
5 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
Warning::
DNS resolution is slow (202 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 202 ms
A104.21.88.234, 172.67.154.53
AAAA2606:4700:3037::ac43:9a35, 2606:4700:3034::6815:58ea
CNAME
NSns1.mythic-beasts.com, ns2.mythic-beasts.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
apple-domain-verification=G7NolqwJTxv5WxQj
docusign=91cb7347-7fab-4483-80fb-3d7326442b20
MS=97C42B5E419A7AD928DAE17310BF7867C08D90E2
pinterest-site-verification=4fb4cc62b233cb88b49e2aad52fdd084
stripe-verification=ee7ecbe1c0c0c6d7443e13f7c4c6372ecfb72793ded6416c6c067d83fada...
SPF v=spf1 include:_spf.google.com include:spf.mandrillapp.com include:shops.shopify...
dell-technologies-domain-verification=raspberrypi.com_20704c72-49f3-4e7c-a60b-91...
MS=ms56169171
AHZ9PD4BGV
cursor-domain-verification-9e1cyz=Hxtzte6NDZUbuj7fnq9t9MDvY
anthropic-domain-verification-z4m9km=1OseFNip1MLLUhKI2K12aZzY7
google-site-verification=wWXB4My_qeRukIY61lCWME7pUnjcnYjczybFknxv8Fg
linkedin-site-verification=a5e7d055-3e4e-4aaa-a81d-377f2f276f38
CAALookup not available with standard resolver
Resolved in 202 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.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
IPv6 Readiness
IPv6 reachable (2 ms)
PASS
IPv6 reachable (2 ms)
Info::
IPv6 is configured and reachable at 2606:4700:3037::ac43:9a35, 2606:4700:3034::6815:58ea
Got: 2 ms connect
IPv6 Ready
AAAA Records 2606:4700:3037::ac43:9a35, 2606:4700:3034::6815:58ea Connection Reachable (2 ms)
A
Crawlability
robots.txt present, no sitemap
PASS
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 355 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt references sitemap

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

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

robots.txt 200 OK
Size 355 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /wp/wp-admin/
Allow: /wp/wp-admin/admin-ajax.php
Disallow: /news/archive/
Disallow: /success-stories/*?*solution
Disallow: /success-stories/*?*industry

# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:

Sitemap: https://www.raspberrypi.com/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

A+
Domain Intelligence
raspberrypi.com — via Tucows Domains Inc., 17 years, 10 months old
PASS
raspberrypi.com — via Tucows Domains Inc., 17 years, 10 months old
Info::
Domain registered until Sep 15, 2027 (1 years, 5 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: Tucows Domains Inc.
Warning::
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.
Domain expiry

424 days

September 15, 2027

SSL certificate

42 days

Issued by Google Trust Services

Domain age

17 years, 10 months

Registered September 15, 2008

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:3037::ac43:9a35

Registrar

Tucows Domains Inc.

Unlocked 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
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Tucows Domains Inc.
Created September 15, 2008 (17 years, 10 months ago)
Expires September 15, 2027 (1 years, 5 months)
Last Updated August 4, 2022
Name Servers ns1.mythic-beasts.com, ns2.mythic-beasts.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:3037::ac43:9a35
Data source: rdap (0.4s)

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
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: GRU)
Got: cf-ray: 9f0003b8bbf44979-GRU
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: 9f0003b8bbf44979-GRU
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback