Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN (document or assets)FIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
BReverse DNS0/1 IPs match cert SANREVIEW
BRedirect Chain2 redirect(s), 309 ms totalREVIEW
https://SOLIDARITES.ORG
131 ms · HTTP/1.1
https://www.solidarites.org/
147 ms · HTTP/1.1
https://www.solidarites.org/fr/?noredire...
31 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://SOLIDARITES.ORG | 302 | 131 ms | HTTP/1.1 | nginx |
| 2 | https://www.solidarites.org/ | 302 | 147 ms | HTTP/1.1 | nginx |
| 3 | https://www.solidarites.org/fr/?noredire... | 200 | 31 ms | HTTP/1.1 | nginx |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
If permanent, use 301 instead.
302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.
Learn more ▾ ▴
Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).
Source: Google Search Central
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BTLS Certificate Expiry & Recommendations66 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
BOperational Status PageNo status page link detectedREVIEW
A+DNS Records1 A records, 43 ms lookupPASS
| A | 46.101.121.232 |
| AAAA | — |
| CNAME | — |
| NS | ns-18-c.gandi.net, ns-23-a.gandi.net, ns-148-b.gandi.net |
| MX | 10 solidarites-org.mail.protection.outlook.com |
| TXT | apple-domain-verification=E3TnCzdOQ7n1i5Uy sophos-domain-verification=88e783ad19ea9535408af779e93d023c1997c60460cfdac6ef866... facebook-domain-verification=thvrfwq8etf695a1ohx1ggf1nrgsqw nocodb-verification-3a3d6aa4305ac6ccb47158689c40ee53 atlassian-sending-domain-verification=e99beab2-c4f4-4eae-833b-df5ea52d8d33 brevo-code:13e9cb51e5e607144b936ee44a738a1b brevo-code:348ee6856ceddf0d72974f164e88f6d6 google-site-verification=AymwWMR7dwuQyubLWcIaBUbrya6dYo3XonSx_JPU7l8 SPF v=spf1 include:spf.mailjet.com include:amazonses.com include:spf.protection.outl... MS=ms87904877 protonmail-verification=0c369f1a2507efd8e543d9421a981ddf69ebe114 google-site-verification=ZdG9pPXUm6s4nwlNEDPstk6RG7lm--D1PGSzbzew4mc amazonses:ng68S5MoDuz1Imrt6EMXt0ZXwNwpY/xdl8QEd3/ZysI= |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
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
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
A+Multi-Resolver DNS SpeedMean 28ms across 3 resolvers (spread 21ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 14 URLsPASS
#Regles pour les bots
# Fermeture totale certains bots
User-agent: Baiduspider-favo
User-agent: Baiduspider-cpro
User-agent: Baiduspider-ads
User-agent: Baidu
User-agent: Baiduspider-news
User-agent: Baiduspider-video
User-agent: Baiduspider-image
User-agent: Baiduspider
User-agent: 008
User-agent: Alexibot
User-agent: AlvinetSpider
User-agent: Antenne Hatena
User-agent: ApocalXExplorerBot
User-agent: asterias
User-agent: BackDoorBot/1.0
User-agent: BizInformation
User-agent: Black Hole
User-agent: BlowFish/1.0
User-agent: BotALot
User-agent: BuiltBotTough
User-agent: Bullseye/1.0
User-agent: BunnySlippers
User-agent: Cegbfeieh
User-agent: CheeseBot
User-agent: CherryPicker
User-agent: CherryPickerElite/1.0
User-agent: CherryPickerSE/1.0
User-agent: CopyRightCheck
User-agent: cosmos
User-agent: Crescent
User-agent: Crescent Internet ToolPak HTTP OLE Control v.1.0
User-agent: DISCo Pump 3.1
User-agent: DittoSpyder
User-agent: dotbot
User-agent: EmailCollector
User-agent: EmailSiphon
User-agent: EmailWolf
User-agent: EroCrawler
User-agent: Exabot
User-agent: ExtractorPro
User-agent: Flamingo_SearchEngine
User-agent: Foobot
User-agent: Harvest/1.5
User-agent: hloader
User-agent: httplib
User-agent: HTTrack
User-agent: HTTrack 3.0
User-agent: humanlinks
User-agent: Igentia
User-agent: InfoNaviRobot
User-agent: JennyBot
User-agent: JikeSpider
User-agent: Kenjin Spider
User-agent: LexiBot
User-agent: libWeb/clsHTTP
User-agent: LinkextractorPro
User-agent: LinkScan/8.1a Unix
User-agent: LinkWalker
User-agent: lwp-trivial
User-agent: lwp-trivial/1.34
User-agent: Mata Hari
User-agent: Microsoft URL Control - 5.01.4511
User-agent: Microsoft URL Control - 6.00.8169
User-agent: MIIxpc
User-agent: MIIxpc/4.2
User-agent: Mister PiX
User-agent: MLBot
User-agent: moget
User-agent: moget/2.1
User-agent: MS Search 4.0 Robot
User-agent: MS Search 5.0 Robot
User-agent: Naverbot
User-agent: NetAnts
User-agent: NetAttache
User-agent: NetMechanic
User-agent: NICErsPRO
User-agent: Offline Explorer
User-agent: Openfind
User-agent: OpenindexSpider
User-agent: ProPowerBot/2.14
User-agent: ProWebWalker
User-agent: psbot
User-agent: QuepasaCreep
User-agent: QueryN Metasearch
User-agent: RepoMonkey
User-agent: RMA
User-agent: SightupBot
User-agent: SiteBot
User-agent: SiteSnagger
User-agent: SiteSucker
User-agent: Sogou web spider
User-agent: sosospider
User-agent: SpankBot
User-agent: spanner
User-agent: Speedy
User-agent: suggybot
User-agent: SuperBot
User-agent: SuperBot/2.6
User-agent: suzuran
User-agent: Szukacz/1.4
User-agent: Teleport
User-agent: Telesoft
User-agent: The Intraformant
User-agent: TheNomad
User-agent: TightTwatBot
User-agent: Titan
User-agent: toCrawl/UrlDispatcher
User-agent: TosCrawler
User-agent: trendictionbot
User-agent: True_Robot
User-agent: True_Robot/1.0
User-agent: turingos
User-agent: TurnitinBot
User-agent: UrlPouls
User-agent: URLy Warning
User-agent: VCI
User-agent: Web Image Collector
User-agent: WebAuto
User-agent: WebBandit
User-agent: WebBandit/3.50
User-agent: WebCopier
User-agent: webcopy
User-agent: WebEnhancer
User-agent: WebmasterWorldForumBot
User-agent: webmirror
User-agent: WebReaper
User-agent: WebSauger
User-agent: website extractor
User-agent: Website Quester
User-agent: Webster Pro
User-agent: WebStripper
User-agent: WebStripper/2.02
User-agent: WebZip
User-agent: wget
User-agent: WikioFeedBot
User-agent: WinHTTrack
User-agent: WWW-Collector-E
User-agent: Xenu Link Sleuth/1.3.8
User-agent: yacy
User-agent: yandex
User-agent: YRSPider
User-agent: Zeus
User-agent: Zookabot
User-agent: Qwantify
Disallow: /
User-agent: *
Disallow: /wp-admin/
Disallow: /wp-includes/
Disallow: /wp-content/
Allow: /wp-content/uploads/
User-agent: Googlebot
Allow: .js
Allow: .css
Sitemap: https://www.solidarites.org/fr/sitemap_index.xml
- https://www.solidarites.org/fr/post-site...
- https://www.solidarites.org/fr/post-site...
- https://www.solidarites.org/fr/page-site...
- https://www.solidarites.org/fr/mission_f...
- https://www.solidarites.org/fr/partenair...
- https://www.solidarites.org/fr/publicati...
- https://www.solidarites.org/fr/communiqu...
- https://www.solidarites.org/fr/category-...
- https://www.solidarites.org/fr/post_tag-...
- https://www.solidarites.org/fr/publicati...
- https://www.solidarites.org/fr/publicati...
- https://www.solidarites.org/fr/presse_ca...
- https://www.solidarites.org/fr/presse_ta...
- https://www.solidarites.org/fr/partenair...
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain IntelligenceSOLIDARITES.ORG — via Gandi SAS, 27 years, 11 months old, hosted on DigitalOceanPASS
2716 days
March 31, 2034
66 days
Issued by Let's Encrypt
27 years, 11 months
Registered March 31, 1999
Not enabled
Protects against DNS spoofing
DigitalOcean
ASN AS14061
46.101.121.232
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