Skip to content
https://roll20.net

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Santa Clara, United States
200 OK
Checks
9
6 PASS 2 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: 2606:4700:10::6814:1f8e, 2606:4700:10::ac42:ad12
Info::
IPv6 connection error
Got: dial tcp6 [2606:4700:10::6814:1f8e]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2606:4700:10::6814:1f8e, 2606:4700:10::ac42:ad12 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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 546 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your 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

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 546 B Sitemaps referenced 0 User-agents *, PowerMapper Blocking No — crawling allowed
User-agent: *
Disallow: /gift/forid/
Disallow: /gift/for/
Disallow: /editor/
Disallow: /api/
Disallow: /account/
Disallow: /campaigns/updatedetails/
Disallow: /lfg/search/
Disallow: /image_library/
Disallow: /forum/upload
Disallow: /forum/search
Disallow: /forum/comments_by/
Disallow: /users/profileupdate/
Disallow: /compendium/compendium/getList
Disallow: /compendium/compendium/globalsearch/
Disallow: /payment/
Disallow: /subscribe_newsletter
User-agent: PowerMapper
Disallow: /forum/post/
Disallow: /forum/discussions_by/
Disallow: /search/
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

75
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
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.20.31.142, 172.66.173.18
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:10::6814:1f8e, 2606:4700:10::ac42:ad12
Info::
2 nameserver(s) configured
Got: gabe.ns.cloudflare.com, lara.ns.cloudflare.com
Info::
7 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.20.31.142, 172.66.173.18
AAAA2606:4700:10::6814:1f8e, 2606:4700:10::ac42:ad12
CNAME
NSgabe.ns.cloudflare.com, lara.ns.cloudflare.com
MX
10 aspmx.l.google.com
20 alt2.aspmx.l.google.com
20 alt1.aspmx.l.google.com
30 aspmx2.googlemail.com
30 aspmx4.googlemail.com
30 aspmx5.googlemail.com
30 aspmx3.googlemail.com
TXT
include:9319166.spf51.hubspotemail.net
LNQIB0WLFT00I49K1LMHRFSKZO6BBBF0YBV7D5WD
facebook-domain-verification=lb07chyng6etwkpmjwu29mkje960mx
google-site-verification=006YfoRAhn7L8dUXx1y8yjoH2UFxhDdVEvK0xMsK9OI
google-site-verification=6CVBpYtIAXnXriHcFSG5HavMkPYyRPZ3jGpPFUhbV7k
google-site-verification=WMZoOsqYM6bkCRNNlRhhX9Pl5RvIxbeRCEcPnV5tcJk
google-site-verification=eZKRfjoIih34Q1oIrXhOJBywRtZDS59qC6AtMg5rnMU
google-site-verification=shdPruHCRtS8xu3JBH192PFEp8dx73zwWIR3nzuFeKA
atlassian-domain-verification=qQT1ypPGV3Aad10iSvRGnxiO55VIYEjryuIdO72tc42nJ9pV/M...
SPF v=spf1 a mx include:spf.mandrillapp.com include:mail.zendesk.com include:servers...
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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://roll20.net

https://roll20.net

188 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://roll20.net200188 msHTTP/1.1cloudflare
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)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.roll20.net/
200https://roll20.net/

Preferred variant: non-www

HTTP → HTTPS

301http://roll20.net/ https://roll20.net/

Consistent

A+
Domain Intelligence
roll20.net — via NameCheap, Inc., 14 years, 3 months old, hosted on Cloudflare
PASS
roll20.net — via NameCheap, Inc., 14 years, 3 months old, hosted on Cloudflare
Info::
Domain registered until Mar 20, 2028 (1 years, 11 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: NameCheap, 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

644 days

March 20, 2028

SSL certificate

75 days

Issued by Let's Encrypt

Domain age

14 years, 3 months

Registered March 20, 2012

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

172.66.173.18

Registrar

NameCheap, 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 NameCheap, Inc.
Created March 20, 2012 (14 years, 3 months ago)
Expires March 20, 2028 (1 years, 11 months)
Last Updated April 11, 2023
Name Servers gabe.ns.cloudflare.com, lara.ns.cloudflare.com
DNSSEC Enabled
Hosting
IP Address 172.66.173.18
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: rdap (0.1s)

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

Connection waterfall

DNS Lookup 4 ms TCP Connect 4 ms TLS Handshake 12 ms Server Processing 77 ms Content Transfer 35 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: SJC)
Got: cf-ray: 9f08034708b46897-SJC
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: 9f08034708b46897-SJC
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback