Skip to content
https://docs.rs

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
1
REVIEW
1
PASS
7
INFO
0
Probed from Santa Clara, United States
200 OK
Checks
9
7 PASS 1 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: 2a04:4e42:200::347, 2a04:4e42::347, 2a04:4e42:600::347, 2a04:4e42:400::347
Info::
IPv6 connection error
Got: dial tcp6 [2a04:4e42:200::347]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2a04:4e42:200::347, 2a04:4e42::347, 2a04:4e42:600::347, 2a04:4e42:400::347 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
TLS Certificate Expiry & Recommendations
249 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

249
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
A+
DNS Records
4 A records, 33 ms lookup
PASS
4 A records, 33 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 151.101.1.91, 151.101.129.91, 151.101.65.91, 151.101.193.91
Info::
Has 4 IPv6 (AAAA) record(s)
Got: 2a04:4e42:200::347, 2a04:4e42::347, 2a04:4e42:600::347, 2a04:4e42:400::347
Info::
4 nameserver(s) configured
Got: ns-1397.awsdns-46.org, ns-1937.awsdns-50.co.uk, ns-314.awsdns-39.com, ns-779.awsdns-33.net
Info::
2 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: 33 ms
Got: 33 ms
A151.101.1.91, 151.101.129.91, 151.101.65.91, 151.101.193.91
AAAA2a04:4e42:200::347, 2a04:4e42::347, 2a04:4e42:600::347, 2a04:4e42:400::347
CNAME
NSns-1397.awsdns-46.org, ns-1937.awsdns-50.co.uk, ns-314.awsdns-39.com, ns-779.awsdns-33.net
MX
10 mxa.mailgun.org
10 mxb.mailgun.org
TXT
google-site-verification=nQmKb5oHlB3NddbejV8Akpd9YFcKRL4Eqc9ENoIsWtY
SPF v=spf1 include:mailgun.org ~all
CAALookup not available with standard resolver
Resolved in 33 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://docs.rs

https://docs.rs

25 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://docs.rs20025 msHTTP/1.1nginx/1.14.0 (Ubuntu)
A+
Crawlability
robots.txt present, sitemap with 33 URLs
PASS
robots.txt present, sitemap with 33 URLs
Info::
robots.txt is present
Got: 375 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 33 entries
Info::
Sitemap index with 33 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 375 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
Sitemap: https://docs.rs/sitemap.xml
# Semver-based URL are always redirects, and sometimes
# confuse Google's duplicate detection, so we block crawling them.
# https://docs.rs/about/redirections
User-Agent: *
Disallow: */^
# %5E is '^', URL-encoded. Based on the Search Console, Google
# may be encoding '^' before checking against robots.txt.
Disallow: */%5E
Disallow: */~

A
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

301https://www.docs.rs/
200https://docs.rs/

Preferred variant: non-www

HTTP → HTTPS

308http://docs.rs/ https://docs.rs/

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
docs.rs — via Webglobe d.o.o., hosted on Fastly
PASS
docs.rs — via Webglobe d.o.o., hosted on Fastly
Info::
Registrar: Webglobe d.o.o.
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: Fastly
Got: AS54113
Domain expiry

Unknown

SSL certificate

249 days

Issued by GlobalSign nv-sa

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Fastly

ASN AS54113

151.101.65.91

Registrar

Webglobe d.o.o.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Webglobe d.o.o.
Name Servers ns-1937.awsdns-50.co.uk, ns-314.awsdns-39.com, ns-779.awsdns-33.net, ns-1397.awsdns-46.org
Registrant Individual
Hosting
IP Address 151.101.65.91
ASN AS54113 (FASTLY - Fastly, Inc., US)
Provider Fastly
Data source: whois (0.9s)

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 29 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
5 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.
5 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
29 ms
Total Time Total request time from DNS lookup through full response.
29 ms

Connection waterfall

DNS Lookup 5 ms TCP Connect 2 ms TLS Handshake 5 ms Server Processing 17 ms Content Transfer 0 ms
A
CDN & Delivery
Fastly (MISS)
PASS
Fastly (MISS)
Info::
Site is served via Fastly CDN
Got: x-served-by: cache-sjc10027-SJC
Info::
CDN cache status: MISS
CDN Detected: Fastly
Provider Fastly Cache Status MISS Evidence x-served-by: cache-sjc10027-SJC
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback