Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BTLS Certificate Expiry & Recommendations85 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
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 Records3 A records, 33 ms lookupPASS
| A | 172.67.66.183, 104.25.94.108, 104.25.93.108 |
| AAAA | 2606:4700:20::6819:5d6c, 2606:4700:20::6819:5e6c, 2606:4700:20::ac43:42b7 |
| CNAME | — |
| NS | elaine.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 |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
ARedirect Chain1 redirect(s), 259 ms totalPASS
https://rsf.org
149 ms · HTTP/1.1
https://rsf.org/fr
110 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://rsf.org | 301 | 149 ms | HTTP/1.1 | cloudflare |
| 2 | https://rsf.org/fr | 200 | 110 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (17 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 27 URLsPASS
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
# 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: /
- https://rsf.org/sitemap.xml?page=1
- https://rsf.org/sitemap.xml?page=2
- https://rsf.org/sitemap.xml?page=3
- https://rsf.org/sitemap.xml?page=4
- https://rsf.org/sitemap.xml?page=5
- https://rsf.org/sitemap.xml?page=6
- https://rsf.org/sitemap.xml?page=7
- https://rsf.org/sitemap.xml?page=8
- https://rsf.org/sitemap.xml?page=9
- https://rsf.org/sitemap.xml?page=10
- https://rsf.org/sitemap.xml?page=11
- https://rsf.org/sitemap.xml?page=12
- https://rsf.org/sitemap.xml?page=13
- https://rsf.org/sitemap.xml?page=14
- https://rsf.org/sitemap.xml?page=15
- https://rsf.org/sitemap.xml?page=16
- https://rsf.org/sitemap.xml?page=17
- https://rsf.org/sitemap.xml?page=18
- https://rsf.org/sitemap.xml?page=19
- https://rsf.org/sitemap.xml?page=20
- https://rsf.org/sitemap.xml?page=21
- https://rsf.org/sitemap.xml?page=22
- https://rsf.org/sitemap.xml?page=23
- https://rsf.org/sitemap.xml?page=24
- https://rsf.org/sitemap.xml?page=25
- https://rsf.org/sitemap.xml?page=26
- https://rsf.org/sitemap.xml?page=27
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencersf.org — via Gandi SAS, 26 years, 5 months oldPASS
253 days
March 29, 2027
85 days
Issued by Google Trust Services
26 years, 5 months
Registered March 29, 2000
Not enabled
Protects against DNS spoofing
Unknown
2606:4700:20::6819:5e6c
Gandi SAS
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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