Skip to content
https://grist.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
92
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
6 PASS 2 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
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

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

Certificate validity

87
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
1 A records, 31 ms lookup
PASS
1 A records, 31 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 192.0.66.120
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: connie.ns.cloudflare.com, quincy.ns.cloudflare.com
Info::
3 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: 31 ms
Got: 31 ms
A192.0.66.120
AAAA
CNAME
NSconnie.ns.cloudflare.com, quincy.ns.cloudflare.com
MX
10 mailstream-central.mxrecord.mx
20 mailstream-east.mxrecord.io
20 mailstream-west.mxrecord.io
TXT
SPF v=spf1 include:_spf.google.com include:_spf.salesforce.com include:aspmx.pardot....
google-site-verification=eSR2uhtZOH8IQNyZLghud676gqyK1ZxL4TpAV6MhLGs
pardot399522=6498f75c2806e552b6763bfdb2c47c1d5013956a144de9620a63878de13688c6
google-site-verification=aquO3PPZgzK6tj0GFwhc7SpSAUxa4SpsvyBmmcOslDU
MS=8D725880A8C0B234701D662888E698D62E7D8E99
MS=ms15648588
google-site-verification=ib-ODvbZqezRzglwuAR0cL2y9DZo3BlFFTeqy-IXq0o
google-site-verification=frAsAyJxWe-yJwCWZjOpwyMfA2j62-oWf6dLHoF8cYY
spf2.0/pra include:_spf.google.com include:_spf.salesforce.com include:aspmx.par...
apple-domain-verification=TyWA5YhXgveBr8MG
CAALookup not available with standard resolver
Resolved in 31 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

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://grist.org

https://grist.org

5 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://grist.org2005 msHTTP/1.1nginx
A+
Crawlability
robots.txt present, sitemap with 80 URLs
PASS
robots.txt present, sitemap with 80 URLs
Info::
robots.txt is present
Got: 360 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 80 entries
Info::
Sitemap index with 80 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 360 B Sitemaps referenced 4 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: */republish/
# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:

Sitemap: https://grist.org/sitemap_index.xml
Sitemap: https://grist.org/grist-50/sitemap_index.xml
Sitemap: https://grist.org/fix/sitemap_index.xml
Sitemap: https://uprootproject.org/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK
sitemap.xml 200 OK
Type Sitemap Index URLs 80 entries Valid XML Yes
Child Sitemaps:
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.grist.org/
200https://grist.org/

Preferred variant: non-www

HTTP → HTTPS

301http://grist.org/ https://grist.org/

Consistent

A+
Domain Intelligence
grist.org — via GoDaddy.com, LLC, 26 years old, hosted on WordPress.com (Automattic)
PASS
grist.org — via GoDaddy.com, LLC, 26 years old, hosted on WordPress.com (Automattic)
Info::
Domain registered until Aug 16, 2026 (3 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: GoDaddy.com, LLC
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: WordPress.com (Automattic)
Got: AS2635
Domain expiry

35 days

August 16, 2026

SSL certificate

87 days

Issued by Let's Encrypt

Domain age

26 years

Registered August 16, 2000

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

WordPress.com (Automattic)

ASN AS2635

192.0.66.120

Registrar

GoDaddy.com, LLC

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar GoDaddy.com, LLC
Created August 16, 2000 (26 years ago)
Expires August 16, 2026 (3 months)
Last Updated December 16, 2024
Name Servers connie.ns.cloudflare.com, quincy.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 192.0.66.120
ASN AS2635 (AUTOMATTIC - Automattic, Inc, US)
Provider WordPress.com (Automattic)
Data source: rdap (0.5s)

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 36 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
30 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
0 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
3 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
35 ms
Total Time Total request time from DNS lookup through full response.
36 ms

Connection waterfall

DNS Lookup 30 ms TCP Connect 0 ms TLS Handshake 3 ms Server Processing 1 ms Content Transfer 1 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback