Skip to content
https://rhizome.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
96
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Singapore, Singapore
200 OK
Checks
9
7 PASS 2 REVIEW
B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 288 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 288 B Sitemaps referenced 0 User-agents CCBot, Google-Extended, GPTBot, *, anthropic-ai, Claude-Web, ClaudeBot, PerplexityBot Blocking No — crawling allowed
User-agent: anthropic-ai
Disallow: /
User-agent: Claude-Web
Disallow: /
User-agent: ClaudeBot
Disallow: /
User-agent: PerplexityBot
Disallow: /
User-agent: CCBot
Disallow: /
User-agent: Google-Extended
Disallow: /
User-agent: GPTBot
Disallow: /
User-agent: *
Disallow: /profile/Rhizomer/

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

88
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
2 A records, 5 ms lookup
PASS
2 A records, 5 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.66.148.76, 104.20.23.201
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:10::6814:17c9, 2606:4700:10::ac42:944c
Info::
2 nameserver(s) configured
Got: josh.ns.cloudflare.com, rosalie.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: 5 ms
Got: 5 ms
A172.66.148.76, 104.20.23.201
AAAA2606:4700:10::6814:17c9, 2606:4700:10::ac42:944c
CNAME
NSjosh.ns.cloudflare.com, rosalie.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 aspmx2.googlemail.com
10 aspmx3.googlemail.com
TXT
SPF v=spf1 include:_spf.google.com ~all
zoho-verification=zb03190822.zmverify.zoho.com
CAALookup not available with standard resolver
Resolved in 5 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://rhizome.org

https://rhizome.org

712 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://rhizome.org200712 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2606:4700:10::6814:17c9, 2606:4700:10::ac42:944c
Got: 1 ms connect
IPv6 Ready
AAAA Records 2606:4700:10::6814:17c9, 2606:4700:10::ac42:944c Connection Reachable (1 ms)
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.rhizome.org/
200https://rhizome.org/

Preferred variant: non-www

HTTP → HTTPS

301http://rhizome.org/ https://rhizome.org/

Consistent

A+
Domain Intelligence
rhizome.org — via Cloudflare, Inc., 30 years, 4 months old
PASS
rhizome.org — via Cloudflare, Inc., 30 years, 4 months old
Info::
Domain registered until May 10, 2027 (1 years 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: 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.
Domain expiry

301 days

May 10, 2027

SSL certificate

88 days

Issued by Google Trust Services

Domain age

30 years, 4 months

Registered May 9, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:10::ac42:944c

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 May 9, 1996 (30 years, 4 months ago)
Expires May 10, 2027 (1 years)
Last Updated March 24, 2023
Name Servers josh.ns.cloudflare.com, rosalie.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:10::ac42:944c
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 734 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.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
7 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
734 ms
Total Time Total request time from DNS lookup through full response.
735 ms

Connection waterfall

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

Send Feedback