Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Probed from Madrid, Spain

308 Permanent Redirect

Checks

5 PASS 3 REVIEW 1 FIX

Redirect Chain

Action

4 redirect(s), 932 ms total

FIX

4 redirect(s), 932 ms total

4 redirects before reaching final URL

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

WWW normalization redirect

Uses 302 (temporary) redirect

If permanent, use 301 instead.

Got: https://www.outsideonline.com/

Redirect overhead: 932 ms total

Got: 932 ms

Cross-domain redirect detected

https://outsideonline.com

80 ms · HTTP/1.1

308

https://www.outsideonline.com/

171 ms · HTTP/1.1

302

https://accounts.outsideonline.com/oidc/...

487 ms · HTTP/1.1

302

https://www.outsideonline.com/authorize?...

99 ms · HTTP/1.1

302

https://www.outsideonline.com/featured?s...

95 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://outsideonline.com	308	80 ms	HTTP/1.1	Vercel
2	https://www.outsideonline.com/	302	171 ms	HTTP/1.1	Vercel
3	https://accounts.outsideonline.com/oidc/...	302	487 ms	HTTP/1.1	cloudflare
4	https://www.outsideonline.com/authorize?...	302	99 ms	HTTP/1.1	Vercel
5	https://www.outsideonline.com/featured?s...	200	95 ms	HTTP/1.1	Vercel

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

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

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

TLS Certificate Expiry & Recommendations

36 days until leaf cert expires — 4 issues to address

REVIEW

Certificate validity

days left

0d 30d 60d 90d+

Recommended actions

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

CDN & Delivery

Vercel

REVIEW

Vercel

Site is served via Vercel CDN

Got: x-vercel-id: cdg1::5x9tf-1776811522243-76348915451b

CDN Detected: Vercel

Provider Vercel Evidence x-vercel-id: cdg1::5x9tf-1776811522243-76348915451b

A+

DNS Records

2 A records, 30 ms lookup

PASS

2 A records, 30 ms lookup

Resolves to 2 IPv4 address(es)

Got: 76.76.21.22, 66.33.60.129

No IPv6 (AAAA) records

2 nameserver(s) configured

Got: rosa.ns.cloudflare.com, ram.ns.cloudflare.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: 30 ms

Got: 30 ms

A	76.76.21.22, 66.33.60.129
AAAA	—
CNAME	—
NS	rosa.ns.cloudflare.com, ram.ns.cloudflare.com
MX	1 aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 alt4.aspmx.l.google.com 10 alt3.aspmx.l.google.com
TXT	google-site-verification=fqJnh8fPCAFkyZ03TcpLFUztEfdarKIFzNFR3A4vbcQ google-site-verification=bp6iU0bEEx9UseDEm9DeEHagYCI4WcpEVfcemA9Pkzc SPF v=spf1 include:_spf.google.com include:spf.mandrillapp.com include:4566937.spf07... google-site-verification=rLGXPnJUPV2UPsyV5O2ml9C9KQz2_EGyd4_GI1U8liE google-site-verification=Nn83eEspb-LACxzd3zRlh1njt_H8ynQmW4GS5np2uvM google-site-verification=WPAZcZxLo55th8uPNxN20EZtqiYTQk9pmzH5hKyoVak google-site-verification=_I4n1fJEdiqSVs9rCousoe0NJ8kiKjWac7uXPGtOs2M fastly-domain-delegation-iqrighugvvhtbax4x3qb--2022-12-07 google-site-verification=r202Wirn9-98_pqdYIW9C7hAi2-I2N9udUwJBf6ozM0 google-site-verification=XxG5F7mrWNYLYNpFhAySh81wF-K8RGGZjuICPujVjcw google-site-verification=lv8s5fxunDR5fdZn_fjTzoNa-xnZD-oIt-E6to-IITM google-site-verification=2gPhZXGCUAabPljZJCCysTJjspzM73IqD8x0FoLlzQg
CAA	Lookup not available with standard resolver

Resolved in 30 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 6436 URLs

PASS

robots.txt present, sitemap with 6436 URLs

robots.txt is present

Got: 2482 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 6436 entries

Sitemap index with 6436 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

Size 2482 B Sitemaps referenced 1 User-agents Timpibot, webzio, facebookexternalhit, Googlebot, xAI-Grok, AI2Bot, peer39_crawler/1.0, Googlebot-Video, ChatGPT-User, MistralAI-User, omgili, BingBot, GoogleOther, LinkedInBot, ClaudeBot, DeepseekBot, Applebot, Claude-User, meta-webindexer, bigsur.ai, Bytespider, GrokBot, ImagesiftBot, omgilibot, OAI-SearchBot, AI2Bot-Dolma, Amazonbot, CCBot, iAskBot, meta-externalagent, webzio-extended, Claude-SearchBot, Grok-DeepSearch, PerplexityBot, cohere-training-data-crawler, Petalbot, Googlebot-Image, *, BingPreview, DuckDuckBot, meta-externalfetcher, Perplexity-User, Applebot-Extended, cohere-ai, Diffbot, FacebookBot, Slackbot, Twitterbot, AliyunSecBot, anthropic-ai, GPTBot, peer39_crawler Blocking No — crawling allowed

# Outside Online content is for personal, non-commercial use.
# Scraping or data mining with automated tools is not allowed. 
# You cannot use this content to train AI models or create data sets.
# Contact Outside Online for permission to use data.

# (A) ALLOW: SOCIAL PREVIEWS & SEARCH AI (RAG / Citations)
# These bots can see content for user requests and link previews.
User-agent: Applebot
User-agent: BingBot
User-agent: BingPreview
User-agent: ChatGPT-User
User-agent: Claude-SearchBot
User-agent: Claude-User
User-agent: DuckDuckBot
User-agent: facebookexternalhit
User-agent: Grok-DeepSearch
User-agent: Googlebot
User-agent: GoogleOther
User-agent: LinkedInBot
User-agent: meta-externalfetcher
User-agent: meta-webindexer
User-agent: MistralAI-User
User-agent: OAI-SearchBot
User-agent: PerplexityBot
User-agent: Perplexity-User
User-agent: Slackbot
User-agent: Twitterbot
User-agent: xAI-Grok
Allow: /wp-admin/admin-ajax.php
Disallow: /login/
Disallow: /wp-admin/
Disallow: /wp-login.php
Disallow: /*.pantheonsite.io/
Disallow: /accounts.outsideonline.com/
Disallow: /preview/
Allow: /

# (B) BLOCK: AI TRAINING, DATA AGGREGATORS & BRAND SAFETY
# These bots crawl for LLM training or commercial scraping.
User-agent: AI2Bot
User-agent: AI2Bot-Dolma
User-agent: AliyunSecBot
User-agent: Amazonbot
User-agent: anthropic-ai
User-agent: Applebot-Extended
User-agent: bigsur.ai
User-agent: Bytespider
User-agent: CCBot
User-agent: ClaudeBot
User-agent: cohere-ai
User-agent: cohere-training-data-crawler
User-agent: DeepseekBot
User-agent: Diffbot
User-agent: FacebookBot
User-agent: GPTBot
User-agent: GrokBot
User-agent: iAskBot
User-agent: ImagesiftBot
User-agent: meta-externalagent
User-agent: omgili
User-agent: omgilibot
User-agent: peer39_crawler
User-agent: peer39_crawler/1.0
User-agent: Petalbot
User-agent: Timpibot
User-agent: webzio
User-agent: webzio-extended
Disallow: /

# (C) MEDIA CRAWLERS (Images & Video)
User-agent: Googlebot-Image 
User-agent: Googlebot-Video 
Allow: /wp-admin/admin-ajax.php
Disallow: /login/
Disallow: /wp-admin/
Disallow: /wp-login.php
Disallow: /*.pantheonsite.io/
Disallow: /accounts.outsideonline.com/
Disallow: /preview/
Allow: /  

# (D) GENERAL SEARCH ENGINES & SEO TOOLS
User-agent: *
Allow: /wp-admin/admin-ajax.php
Disallow: /login/
Disallow: /wp-admin/
Disallow: /wp-login.php
Disallow: /*.pantheonsite.io/
Disallow: /accounts.outsideonline.com/
Disallow: /preview/
Sitemap: https://www.outsideonline.com/sitemap_index.xml

sitemap.xml 200 OK

Type Sitemap Index URLs 6436 entries Valid XML Yes

Child Sitemaps:

URL Variants

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

PASS

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

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

HTTP→HTTPS redirect uses 302 instead of 301

Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

302https://www.outsideonline.com/

200https://outsideonline.com/

Preferred variant: non-www

HTTP → HTTPS

308http://outsideonline.com/ → https://outsideonline.com/

Use 301 (permanent) instead of 302 (temporary)

A+

Domain Intelligence

outsideonline.com — via Cloudflare, Inc., 27 years, 7 months old, hosted on AWS

PASS

outsideonline.com — via Cloudflare, Inc., 27 years, 7 months old, hosted on AWS

Domain registered until Feb 3, 2027 (9 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: Cloudflare, Inc.

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: AS16509

Domain expiry

234 days

February 3, 2027

SSL certificate

36 days

Issued by Let's Encrypt

Domain age

27 years, 7 months

Registered February 3, 1999

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

76.76.21.22

Registrar

Cloudflare, 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 Cloudflare, Inc.

Created February 3, 1999 (27 years, 7 months ago)

Expires February 3, 2027 (9 months)

Last Updated January 4, 2026

Name Servers ram.ns.cloudflare.com, rosa.ns.cloudflare.com

DNSSEC Not enabled

Hosting

IP Address 76.76.21.22

ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)

Provider AWS

Data source: rdap (0.2s)

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 102 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

PASS

DNS Lookup

30 ms

TCP Connect

1 ms

TLS Handshake

42 ms

Time to First Byte

102 ms

Total Time

103 ms

Connection waterfall

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.