Search
Enter at least two characters without personal information.

    LibraryArticles & FAQ Your projectRequest a quote
    LanguageEN
    Web resources

    Hosting, cloud and domains

    Compare hosting against the site’s real needs: availability, data, backups, support, location and responsibilities. Domain, email and application may belong to different providers.

    Map one real website across domain, DNS, email, files, database and backups. Ask each supplier what it operates and rehearse data recovery before committing.

    AI-generated illustration

    Editorial method

    A directory made to be useful, not merely long.

    Selection prioritises recognition within the field, professional use and reference status. Highly specialised documentation entries are consolidated under their main resource.

    01

    Official foundations

    Standards bodies, official documentation and public authorities are used as primary reference points.

    02

    Professional tools

    Established services are grouped by actual use: building, hosting, measuring, securing, publishing or promoting a website.

    03

    Independent reading

    Inclusion is editorial and unpaid. A listing does not imply a partnership or guarantee.

    Before choosing

    Compare on three practical questions

    Hosting, cloud and domains
    CriterionQuestion to resolve
    ResponsibilitiesWho manages the domain, DNS, certificates, updates and restoration?
    RecoveryCan a backup be restored and data exported in a usable format?
    CommitmentWhich support response times, renewal fees and exit terms are written down?

    Keep a short decision record: requirement, source, observed result and unresolved point. Test the same task with each candidate instead of comparing marketing lists of features.

    Search and filter

    Official starting points for this topic

    Compare their role and documentation before selecting a tool. Inclusion is not a ranking.

    12 resources displayed

    The date applies to the linked document, not to a review of every service feature.

    Hosting, cloud and domains

    Cloudflare

    Network, DNS, content delivery and website protection services. Their role depends on enabled products and the request path to the origin server.

    Cloudflare — Fundamentals · Source consulted

    Use it for : Map DNS, proxy and origin before making changes. Check a public page, a private page and publication of a correction; prepare recovery that preserves the correct destination and distinguishes cache, application and DNS resolution.

    Documented characteristics
    Proxy record types
    A · AAAA · CNAME
    DNS only
    MX · TXT
    Modes
    Proxied / DNS only

    Learning example: adapt files, identifiers and conditions to a test copy before interpreting the result.

    Practical example
    Fictional example: after moving DNS to Cloudflare, a direct query works but a validating resolver fails. The new website address alone does not explain that difference.
    Useful check
    Compare the parent’s published DS with the authoritative provider’s DNSSEC settings. Record answers and time; never copy private keys into the handover notes.
    Interpretation and next step
    A stale DS can break the trust chain. Have the domain owner correct coordination and confirm validated resolution; disabling validation locally does not close the incident.

    Official documentation ·

    Official documentation · Cloudflare — DNSSEC troubleshooting

    InternationalService / platform
    cloudflare.comVisit official website
    Hosting, cloud and domains

    Let’s Encrypt

    Certificate authority supporting automated HTTPS certificate issuance and renewal through compatible clients. Useful for planning validation and operation. Check the certificate actually served for each critical name too: successful issuance does not prove installation on every endpoint.

    Let’s Encrypt · Source consulted

    Use it for : Test automatic renewal and monitor certificate expiry.

    Documented characteristics
    Validation
    HTTP-01 · DNS-01 · TLS-ALPN-01
    Port
    HTTP-01 → TCP 80
    Wildcard certificate
    DNS-01

    Learning example: adapt files, identifiers and conditions to a test copy before interpreting the result.

    Practical example
    Fictional example: a website also needs a wildcard name, but renewal only provides an HTTP token. This Let’s Encrypt method cannot meet the wildcard requirement.
    Useful check
    Assess DNS-01, access to the validation TXT and minimum automation permissions. Having a DNS API does not prove the ACME client and delegation are configured correctly.
    Interpretation and next step
    After validation, check the certificate actually presented for the expected names. A CAA policy authorising issuance replaces neither this check nor private-key protection.

    Official documentation ·

    Official documentation · Let’s Encrypt — Challenge types

    Official documentation · Let’s Encrypt — CAA

    InternationalInstitution / standard
    letsencrypt.orgVisit official website
    Choose a starting point

    What each category helps you decide.

    These examples illustrate uses, not rankings or endorsements. Verify each provider’s current documentation and terms before a decision.

    Hosting, cloud and domains

    Compare hosting against the site’s real needs: availability, data, backups, support, location and responsibilities. Domain, email and application may belong to different providers.

    Questions to check
    • List what the offer includes and what remains your responsibility.
    • Check how data can be exported and a backup restored.
    • Establish what can be restored, by whom, how quickly and from how old a copy.

    A practical use : Map one real website across domain, DNS, email, files, database and backups. Ask each supplier what it operates and rehearse data recovery before committing.

    What this cannot prove : Location, support and restoration depend on the precise plan. Advertised prices may exclude renewal or necessary features.

    Examples : OVHcloud · Cloudflare

    Related guide : Take over or hand over a website with confidence

    Explore troubleshooting situations

    Troubleshooting methods

    A hosting change can affect a chain of services: website, files, domain, email and caches. These symptoms help locate a difficulty before intervention. Run trials on a copy and prepare recovery before changing the public service.

    A corrected page still shows old information

    What you observe
    A change appears on one device but not another, or disappears after changing networks.
    Before drawing a conclusion
    Content may be served by several caches. Clearing one browser’s data does not establish that the public version is updated everywhere.
    Verification step
    Record the exact URL, time, content version and observed response headers. Compare the layers in your architecture, then recheck the change after a targeted action on the relevant cache.

    Restoration works, but images are missing

    What you observe
    The restored database contains the expected pages, but media fails to load or points to an old location.
    Before drawing a conclusion
    A backup file may cover only part of a site. Uploaded files, external dependencies and configuration also need an inventory.
    Verification step
    On the restored copy, open a recent page with media, search for content and check download links. Document missing elements and their planned recovery method before approving the backup.

    The website works after a move, but email does not

    What you observe
    The browser opens the new website, while email exchanges no longer behave as expected.
    Before drawing a conclusion
    The website and email can depend on different suppliers and settings. A working page does not validate every service attached to the domain.
    Verification step
    Compare the pre-change inventory with services currently in use. Ask the email owner to check its settings and test receiving and sending with authorised demonstration messages.
    Another case to examineThe domain and hosting have different renewal contacts
    Situation
    Hosting still works, but a warning concerns the domain name. The provider storing the files is not necessarily responsible for renewing the domain.
    Before drawing a conclusion
    A paid hosting invoice does not prove that the domain has been renewed. The organisation must retain access to the owner account and contact address.
    Practical check
    List the domain, DNS and hosting separately with their owners and renewal dates. Check alert recipients and renewal arrangements in each account without placing credentials in a shared document.

    Further documentation

    Keep useful data when changing tools

    Before making a resource part of website operations, plan for updates and an exit too. These checks concern your trial results without assuming features or prices of a particular plan.

    Recover the site

    Try recovering files, database and media on a copy. An archive containing only the theme cannot reconstruct content.

    Separate services

    Identify domain, DNS, certificates, email and hosting. Moving files does not automatically transfer these other services.

    Check the exit

    Prepare redirects, mail delivery and restoration checks before switching. Record the plan’s renewal and data-recovery conditions.

    Transparency

    Editorial scope and third-party websites

    This non-exhaustive directory had its data consistency and links checked on 2 October 2026. Some websites restrict automated checks. It contains external links to independent websites. Their availability, content, prices, cookies and terms may change. Française du Numérique does not control them and receives no commission for their inclusion.

    Directory questions

    Selection, independence and updates.

    Entries describe resources from their publishers’ pages and provide a source, category, purpose and checking date. The selection covers different Web tasks rather than ranking every available provider. Open the cited source to check current scope, availability and conditions before relying on a service.

    No. Inclusion identifies a resource to examine; it does not certify every feature, price, policy or result. Compare the resource with your actual task, country, language and technical requirements. Confirm current conditions with its publisher before committing time, data or money.

    Yes. Search the displayed catalogue, combine the available filters and clear them to return to the full list. Every entered word must match the indexed text. The visible result count describes this selection, not the entire Web. Individual category pages and direct links remain available without JavaScript.

    It has a known scope, date, recovery procedure and documented restoration test. “Backup included” alone does not establish which files are covered or what assistance is available. Check these details for the specific plan and your site.

    Include renewal costs, remaining administrative tasks and data recovery. Compare equivalent scopes against written supplier terms. A price difference becomes meaningful when you know who handles each responsibility.

    Compare using observable evidence

    Before choosing a resource, run a limited trial using the same data and task. Keep the outcome and its limitations rather than a ranking based on familiarity.

    Prepare a demonstration backup with files, database and attachments. Verify restoration in an isolated environment and record missing elements. Then compare recurring cost, support and exit options; a backup button does not prove successful recovery.

    Use precise terms

    Two distinctions before comparing resources

    An old resource and an access permission require different investigations.

    Read an HTTP response before fixing the page

    Choose a situation to separate the status meaning, the useful check and the pitfall. This reader explains cases; it does not test any address.

    200Available page
    What it means
    The request succeeded. For an HTML page, also examine the returned content.
    What to check
    Check the title, main content and language, then the canonical and indexing directives.
    Watch out for
    A “not found” page returning 200 may become a soft 404. HTTP success does not guarantee indexing.
    301 / 308Permanent move
    What it means
    301 and 308 indicate a permanent new address. 308 explicitly preserves the method and body; with 301, a client may change POST to GET.
    What to check
    Open the old URL and check Location, a relevant destination and the absence of chains or loops.
    Watch out for
    Do not redirect every old page to the home page. For a form, also check the method expected at the destination.
    302 / 307Temporary move
    What it means
    302 and 307 indicate a temporary change. 307 preserves the method and body; with 302, a client may change POST to GET.
    What to check
    Check that the destination is available and that a return to the original address is planned.
    Watch out for
    A temporary redirect does not describe permanent removal. Do not replay a payment or order without checking its state.
    404 / 410Missing or removed resource
    What it means
    404 does not say whether the absence is temporary or permanent. 410 indicates a likely permanent removal.
    What to check
    Look for a broken link, a changed URL or deliberate removal. Offer a replacement only when it meets the same need.
    Watch out for
    A helpful error page must retain the actual 404 or 410 status. An error message with 200 does not fix the absence.
    429Too many requests
    What it means
    429 indicates request rate limiting. A Retry-After header may say when to try again.
    What to check
    Examine the limit’s scope and Retry-After. Slow down requests and bound retries.
    Watch out for
    Avoid immediate retry loops. Without an HTTP response, a network failure is not a 429 status.
    503Temporarily unavailable service
    What it means
    503 fits temporary unavailability, such as maintenance or overload. Retry-After may provide a delay or date.
    What to check
    Check the actual status, affected scope and return to normal service. Remove the notice after recovery.
    Watch out for
    Do not replace all pages with an error indefinitely. Persistent 5xx responses can eventually cause Google to remove URLs from its index.

    Technical references : RFC 9110 §15 · RFC 6585 §4 · Google · HTTP.