Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BCrawlabilityrobots.txt present, sitemap with 0 URLsREVIEW
Search engines may not be able to parse the sitemap. Fix XML validation errors.
An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.
Learn more ▾ ▴
Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.
Source: sitemaps.org / Google Search Central
An empty sitemap provides no value. Add <url> entries for your pages.
An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.
Learn more ▾ ▴
Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.
Source: Google Search Central / sitemaps.org
Sitemap: https://www.futura-sciences.com/sitemap/index.xml.gz
# ------------------------------------------------------------
# 1. BOTS IA ET BROUILLEURS (INTERDICTIONS TOTALES)
# ------------------------------------------------------------
User-agent: GPTBot
User-agent: ClaudeBot
User-agent: Amazonbot
User-agent: Applebot
User-agent: Applebot-Extended
User-agent: CCbot
User-agent: Bytespider
User-agent: PetalBot
User-agent: FacebookBot
User-agent: MegaIndex.ru
Disallow: /
# ------------------------------------------------------------
# 2. BOTS IA DE RECHERCHE ET ASSISTANCE (AUTORISÉS)
# ------------------------------------------------------------
User-agent: OAI-SearchBot
User-agent: ChatGPT-User
User-agent: Claude-User
User-agent: Claude-SearchBot
User-agent: Amzn-Searchbot
User-agent: Amzn-User
User-agent: PerplexityBot
Allow: /
# ------------------------------------------------------------
# 3. RÈGLE GÉNÉRALE POUR TOUS LES AUTRES ROBOTS (GOOGLE, BING, ETC.)
# ------------------------------------------------------------
User-agent: *
# Signaux de contenu Cloudflare
Content-Signal: ai-train=no, search=yes, ai-input=yes
# Interdictions techniques et SEO
Disallow: /assets/main/scripts/menu/
Disallow: /fr/print/
Disallow: /comparateur_prix/
Disallow: /indexator/
Disallow: /services/guide/
Disallow: /fr/livre/
Disallow: /services/search/
Disallow: /alternative/pdf/
Disallow: *escaped_fragment
Disallow: */download
Disallow: *cHash=
Disallow: /ajax/
Disallow: *.html
Disallow: *id=
Disallow: *photo=
Disallow: *xml=
Disallow: *thumbsonly=
Disallow: */recherche/
Disallow: /alternative/
Disallow: /private/
Disallow: /ajaxlogin/
Disallow: *ts=
Disallow: /sante/medecine/prix-nobel-medecine/?
Disallow: /compte-premium/
Disallow: *//
Disallow: /getpdf/
Disallow: /js/
Disallow: *?amp=
Disallow: /*/undefined/
Disallow: /cdn-cgi/
Disallow: /popup/
Disallow: /site.webmanifest/
Disallow: *?L=en
Disallow: /first-id/
# ------------------------------------------------------------
# 4. RÉSERVE DE DROITS JURIDIQUE (Art. 4 Directive UE 2019/790)
# ------------------------------------------------------------
# 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.
#
# search: building a search index (excludes AI summaries).
# ai-input: real-time content for AI (RAG, grounding).
# 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.
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations40 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 Records2 A records, 18 ms lookupPASS
| A | 104.18.2.163, 104.18.3.163 |
| AAAA | 2606:4700::6812:2a3, 2606:4700::6812:3a3 |
| CNAME | — |
| NS | coraline.ns.cloudflare.com, ray.ns.cloudflare.com |
| MX | 1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com |
| TXT | BSI134559891313 ahrefs-site-verification_cc83602ff69519f3c842ebe61485df58b55d29e01ccaf23c966c419... brave-ledger-verification=bd93cf9d02d0574d7ea51995e266099bf2d71580beeaafb02d3ef9... facebook-domain-verification=stuko3l0te4dothuse2xc77i9kpo4m google-site-verification=fZVxhM37PUUj-qPAfAdYAxLFH0Tda-1lwh-VuAOgi8Q google-site-verification=nhbbfl5_ocz7RsHyXzSoE9Xq-fVD7cIn-jCugKqf-5A grff8dm1qqmyr1xyd8qvxd0ndgzqw1df SPF v=spf1 include:_spf.google.com -all |
| 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), 291 ms totalPASS
https://futura-sciences.com
258 ms · HTTP/1.1
https://www.futura-sciences.com/
33 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://futura-sciences.com | 301 | 258 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.futura-sciences.com/ | 200 | 33 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (2 ms)PASS
A+Domain Intelligencefutura-sciences.com — via OVH sas, 25 years, 8 months oldPASS
2752 days
December 27, 2033
40 days
Issued by Google Trust Services
25 years, 8 months
Registered December 27, 2000
Not enabled
Protects against DNS spoofing
Unknown
2606:4700::6812:2a3
OVH 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