Skip to content
https://gitbook.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Santa Clara, United States
302 Found
Checks
9
5 PASS 3 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: 2a06:98c1:310d::ac40:92a7, 2606:4700:4404::6812:2959
Info::
IPv6 connection error
Got: dial tcp6 [2a06:98c1:310d::ac40:92a7]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2a06:98c1:310d::ac40:92a7, 2606:4700:4404::6812:2959 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
URL Variants
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
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.gitbook.com/
200https://gitbook.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://gitbook.com/ https://gitbook.com/

Consistent

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

Certificate validity

77
days left
0d 30d 60d 90d+

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: SJC)
Got: cf-ray: 9f002384c8dac4f3-SJC
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f002384c8dac4f3-SJC
A+
DNS Records
2 A records, 7 ms lookup
PASS
2 A records, 7 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.41.89, 172.64.146.167
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a06:98c1:310d::ac40:92a7, 2606:4700:4404::6812:2959
Info::
2 nameserver(s) configured
Got: hugh.ns.cloudflare.com, dahlia.ns.cloudflare.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
Info::
DNS resolution time: 7 ms
Got: 7 ms
A104.18.41.89, 172.64.146.167
AAAA2a06:98c1:310d::ac40:92a7, 2606:4700:4404::6812:2959
CNAME
NShugh.ns.cloudflare.com, dahlia.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
TXT
firebase=gitbook-28427
1eimfvl6smqf32ddsbrt935qqq
5c89abfus0pgntcdrib3m156gp
openai-domain-verification=dv-LB8QOARyXE6YrjhX64RDyf8U
google-site-verification=-MPeja1woOvE2Hs6BcUDgkCeYG9ZaAaCPqEyCMyXYLo
google-site-verification=XTowlLW9jzAGRzz5Y7FkWT7IbJhWFjJuHwj0ex0vI38
google-site-verification=YEfVo29t-jyIdELW1-F_B1XQZBsknBgjKdvVXYsBaXc
google-site-verification=ojxGhAwymkbkr39GFI8VBvWzC9THYX6WQABf9Q9-qyY
google-site-verification=vjg2Tbif0nJQ-Kto4AwyZ5VnSSy6tHvD6vnJ0c5uMvk
SPF v=spf1 a mx include:_spf.google.com include:sendgrid.net include:stspg-customer....
CAALookup not available with standard resolver
Resolved in 7 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
1 redirect(s), 123 ms total
PASS
1 redirect(s), 123 ms total
Info::
Single redirect
Got: https://gitbook.com → https://www.gitbook.com/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://gitbook.com

https://gitbook.com

32 ms · HTTP/1.1

302

https://www.gitbook.com/

91 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://gitbook.com30232 msHTTP/1.1cloudflare
2https://www.gitbook.com/20091 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

A+
Crawlability
robots.txt present, sitemap with 258 URLs
PASS
robots.txt present, sitemap with 258 URLs
Info::
robots.txt is present
Got: 68 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 258 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 68 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /

Sitemap: https://www.gitbook.com/sitemap.xml
A+
Domain Intelligence
gitbook.com — via Cloudflare, Inc., 12 years old, hosted on Cloudflare
PASS
gitbook.com — via Cloudflare, Inc., 12 years old, hosted on Cloudflare
Info::
Domain registered until Jun 12, 2030 (4 years, 2 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: Cloudflare, 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.
Info::
Hosting: Cloudflare
Got: AS13335
Domain expiry

1458 days

June 12, 2030

SSL certificate

77 days

Issued by Google Trust Services

Domain age

12 years

Registered June 12, 2014

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.18.41.89

Registrar

Cloudflare, Inc.

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Cloudflare, Inc.
Created June 12, 2014 (12 years ago)
Expires June 12, 2030 (4 years, 2 months)
Last Updated October 19, 2025
Name Servers dahlia.ns.cloudflare.com, hugh.ns.cloudflare.com
DNSSEC Enabled
Hosting
IP Address 104.18.41.89
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: rdap (0.2s)

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 32 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
7 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
4 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.
32 ms
Total Time Total request time from DNS lookup through full response.
32 ms

Connection waterfall

DNS Lookup 7 ms TCP Connect 4 ms TLS Handshake 9 ms Server Processing 12 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.

Send Feedback