Skip to content
https://rsf.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
97
GRADE
A+
FIX
0
REVIEW
1
PASS
8
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
8 PASS 1 REVIEW
B
TLS Certificate Expiry & Recommendations
85 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

85
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
3 A records, 33 ms lookup
PASS
3 A records, 33 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 172.67.66.183, 104.25.94.108, 104.25.93.108
Info::
Has 3 IPv6 (AAAA) record(s)
Got: 2606:4700:20::6819:5d6c, 2606:4700:20::6819:5e6c, 2606:4700:20::ac43:42b7
Info::
2 nameserver(s) configured
Got: elaine.ns.cloudflare.com, jim.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: 33 ms
Got: 33 ms
A172.67.66.183, 104.25.94.108, 104.25.93.108
AAAA2606:4700:20::6819:5d6c, 2606:4700:20::6819:5e6c, 2606:4700:20::ac43:42b7
CNAME
NSelaine.ns.cloudflare.com, jim.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
google-site-verification=G3i1BEMwq2Mytt5INUotswpo5Z6ajAka_MNXza--ZDU
resources=27a807c2f0526170708d0234f12a4b80
google-site-verification=-5t4Zv9k8AeWMWjbyWPFaoBKmMr1uCrNb1qnmW-vjQg
SPF v=spf1 include:spf.mailjet.com include:_spf.google.com include:spf.mandrillapp.c...
amazonses:iJw1cjhgHI0LyeeuC/b/iRh2q16PKNHmsa9Th90ckbo=
gdurgn9u3n137o7eusgms5hvs
google-site-verification=_O8wGDBeCq_7fBk_X9WOxvC3zL3oerFwFu7jDzTAUnc
e132gtn2v4o6m4e18rjatkij
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
1 redirect(s), 259 ms total
PASS
1 redirect(s), 259 ms total
Info::
Single redirect
Got: https://rsf.org → https://rsf.org/fr (301)

https://rsf.org

149 ms · HTTP/1.1

301

https://rsf.org/fr

110 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://rsf.org301149 msHTTP/1.1cloudflare
2https://rsf.org/fr200110 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:20::6819:5d6c, 2606:4700:20::6819:5e6c, 2606:4700:20::ac43:42b7
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:20::6819:5d6c, 2606:4700:20::6819:5e6c, 2606:4700:20::ac43:42b7 Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 27 URLs
PASS
robots.txt present, sitemap with 27 URLs
Info::
robots.txt is present
Got: 3940 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 27 entries
Info::
Sitemap index with 27 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 3940 B Sitemaps referenced 0 User-agents ChatGPT-User, *, Amazonbot, CCBot, CloudflareBrowserRenderingCrawler, Google-Extended, meta-externalagent, Applebot-Extended, Bytespider, ClaudeBot, GPTBot Blocking No — crawling allowed
# As a condition of accessing this website, you agree to abide by the following
# content signals:

# (a)  If a Content-Signal = yes, you may collect content for the corresponding
#      use.
# (b)  If a Content-Signal = no, you may not collect content for the
#      corresponding use.
# (c)  If the website operator does not include a Content-Signal for a
#      corresponding use, the website operator neither grants nor restricts
#      permission via Content-Signal with respect to the corresponding use.

# The content signals and their meanings are:

# search:   building a search index and providing search results (e.g., returning
#           hyperlinks and short excerpts from your website's contents). Search does not
#           include providing AI-generated search summaries.
# ai-input: inputting content into one or more AI models (e.g., retrieval
#           augmented generation, grounding, or other real-time taking of content for
#           generative AI search answers).
# ai-train: training or fine-tuning AI models.

# ANY RESTRICTIONS EXPRESSED VIA CONTENT SIGNALS ARE EXPRESS RESERVATIONS OF
# RIGHTS UNDER ARTICLE 4 OF THE EUROPEAN UNION DIRECTIVE 2019/790 ON COPYRIGHT
# AND RELATED RIGHTS IN THE DIGITAL SINGLE MARKET.

# BEGIN Cloudflare Managed content

User-agent: *
Content-Signal: search=yes,ai-train=no
Allow: /

User-agent: Amazonbot
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: CloudflareBrowserRenderingCrawler
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: meta-externalagent
Disallow: /

# END Cloudflare Managed Content

#
# robots.txt
#
# This file is to prevent the crawling and indexing of certain parts
# of your site by web crawlers and spiders run by sites like Yahoo!
# and Google. By telling these "robots" where not to go on your site,
# you save bandwidth and server resources.
#
# This file will be ignored unless it is at the root of your host:
# Used:    http://example.com/robots.txt
# Ignored: http://example.com/site/robots.txt
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/robotstxt.html

User-agent: *
# CSS, JS, Images
Allow: /core/*.css$
Allow: /core/*.css?
Allow: /core/*.js$
Allow: /core/*.js?
Allow: /core/*.gif
Allow: /core/*.jpg
Allow: /core/*.jpeg
Allow: /core/*.png
Allow: /core/*.svg
Allow: /profiles/*.css$
Allow: /profiles/*.css?
Allow: /profiles/*.js$
Allow: /profiles/*.js?
Allow: /profiles/*.gif
Allow: /profiles/*.jpg
Allow: /profiles/*.jpeg
Allow: /profiles/*.png
Allow: /profiles/*.svg
# Directories
Disallow: /core/
Disallow: /profiles/
# Files
Disallow: /README.txt
# Paths (clean URLs)
Disallow: /admin/
Disallow: /comment/reply/
Disallow: /filter/tips
Disallow: /node/add/
Disallow: /search/
Disallow: /user/register/
Disallow: /user/password/
Disallow: /user/login/
Disallow: /user/logout/
# Paths (no clean URLs)
Disallow: /index.php/*
# Custom RSF
Disallow: /fr/recherche
Disallow: /fr/recherche?*
Disallow: /fr/admin
Disallow: /fr/admin/*
Disallow: /en/recherche
Disallow: /en/recherche?*
Disallow: /en/admin
Disallow: /en/admin/*
Disallow: /es/recherche
Disallow: /es/recherche?*
Disallow: /es/admin
Disallow: /es/admin/*
Disallow: /pt-br/recherche
Disallow: /pt-br/recherche?*
Disallow: /pt-br/admin
Disallow: /pt-br/admin/*
Disallow: /ar/recherche
Disallow: /ar/recherche?*
Disallow: /ar/admin
Disallow: /ar/admin/*
Disallow: /fa/recherche
Disallow: /fa/recherche?*
Disallow: /fa/admin
Disallow: /fa/admin/*
Disallow: /zh-hans/recherche
Disallow: /zh-hans/recherche?*
Disallow: /zh-hans/admin
Disallow: /zh-hans/admin/*
Disallow: /zh-hant/recherche
Disallow: /zh-hant/recherche?*
Disallow: /zh-hant/admin
Disallow: /zh-hant/admin/*
User-agent: GPTBot
Disallow: /
User-agent: ChatGPT-User
Disallow: /
User-agent: Bytespider
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)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.rsf.org/
200https://rsf.org/

Preferred variant: non-www

HTTP → HTTPS

301http://rsf.org/ https://rsf.org/

Consistent

A+
Domain Intelligence
rsf.org — via Gandi SAS, 26 years, 5 months old
PASS
rsf.org — via Gandi SAS, 26 years, 5 months old
Info::
Domain registered until Mar 29, 2027 (11 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: Gandi SAS
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

253 days

March 29, 2027

SSL certificate

85 days

Issued by Google Trust Services

Domain age

26 years, 5 months

Registered March 29, 2000

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:20::6819:5e6c

Registrar

Gandi SAS

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 Gandi SAS
Created March 29, 2000 (26 years, 5 months ago)
Expires March 29, 2027 (11 months)
Last Updated February 2, 2026
Name Servers elaine.ns.cloudflare.com, jim.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:20::6819:5e6c
Data source: rdap (0.4s)

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

Connection waterfall

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

Send Feedback