Free
$0
USD · for 3 months
1 website
1 GB
YourHost is a service provided by CLOUDPAGE LLC.
From your project folder to an HTTPS address. You approve the project in the portal; your AI can publish if it has access to your files and a terminal.
You do not need to read the entire guide. Choose a workflow and follow its steps in order.
Tell your AI which website to change and share this guide. Reading it grants neither account access nor permission to publish.
Choose one workflow; do not run both in sequence. An AI without files and a terminal can guide you, but cannot claim publication. Asking only for a review does not authorize uploading files or changing your website.
https://yourhost.us/en/guia/ia.mdRecommended workflow with CLI 0.3.3 and Node.js 22 or later. A chat without files or a terminal can help prepare a delivery, but cannot execute publication. You can also run the commands yourself.
Create your account, confirm your email and check hosting access in My dashboard. If activation is pending, check its status: do not buy the plan again.
Run publish in the folder. The first time it shows a URL and code. Open the portal, sign in and confirm the code, project and website: create your first website or approve an existing one. Permission is scoped to that project and website; do not copy tokens or passwords into chat.
Approve a project in the portalAfter approval, the CLI transfers the project and follows the result. Share the HTTPS address only after publication is confirmed. To update, repeat publish from the same folder and keep the same website.
npm install --global https://portal.yourhost.us/tools/yourhost-cli-0.3.3.tgzyourhost check .
yourhost publish . --name "My project"
yourhost publish-status . --waitCLI 0.3.3 and the JavaScript portal transfer blocks of up to 1 MiB. Query without publishing using yourhost publish-status .: it only makes GET requests for the submission saved in that folder; add --wait to follow it. It does not automatically query a later repair made by support. While a submission is pending, repeat yourhost publish . in the same folder: it recovers snapshot and UUID even if sources changed. After a confirmed terminal result, identical sources only check status; different sources create an update for the same website using normal publish, including when the previous result was failed. Do not use --retry to incorporate changes. yourhost publish . --retry is reserved for a confirmed transient failure and identical content; it requires confirmed failed, complete transfer and published other than true. It creates a new UUID: it is not a query or a format correction. For PUBLICATION_FAILED without a specific cause, consult support before repeating that content. yourhost publish . --reconnect only renews expired/revoked access with a confirmed terminal result and approval of the same website; it does not publish changes or resolve uncertainty. Combine --reconnect --retry only when both conditions hold. Use yourhost publish . --recover-lock only if the CLI verifies that the recorded process ID (PID) no longer exists. Legacy locks without the new process metadata are not removed automatically. Never delete receipts to start another submission. If the portal closes before transfer completes, return with the same file. Only durable server acceptance lets work continue without the window. --no-wait is an alternative that skips waiting for the build: it waits for approval and upload; do not run it as a second submission. A wait ending confirms neither failure nor publication.
check inspects local files: it does not authenticate, upload or run scripts and does not guarantee server compatibility or admission. CLI 0.3.3 check/publish accepts up to 2048 files in its folder, even though some portal ZIP formats accept 4096. check uses the normal 20 MiB ZIP limit; publish negotiates the normal 20 MiB or up to 128 MiB with Owner permission, without expanding format limits or quotas. HTML accepts local MP4/WebM and up to 10 MiB per file. HTML, Node.js/Next.js, Vite and WordPress backups require compatibility. Generic DB, SMTP, secrets, persistence and egress are not available. Exclude .env files (including examples), keys, wp-config.php and pb_data from the publishable copy; preserve originals.
SOURCE_UNSUPPORTED calls for reviewing the delivery, not blindly converting it. Do not remove package.json, lockfiles, backend code or requirements to force HTML, or replace an application with a mockup. A static export is appropriate only if it actually exists, preserves the agreed functionality and you authorize that change.
Prefer uploading a ZIP? See the portal alternativeAll you need is an email address and a strong password.
Enter your name, email and password.
Open our message and follow the link.
Find your account, subscription and websites here.
To publish a website, manage these plans under View my subscription. This table is not a standalone email catalogue.
$0
USD · for 3 months
1 website
1 GB
$10
USD · per month
5 websites
10 GB
$20
USD · per month
30 websites
50 GB
$100
USD · per month
Unlimited websites
200 GB
Free: three months at no charge. No minimum term or automatic charge at expiry.
My dashboard shows the next step: confirm email, activate hosting or publish. The portal checks your current plan or access grant; registration does not grant hosting. If you already subscribed and activation is pending, check the status or contact support: do not buy the plan again.
First, keep a copy of the project on your own computer.
Under My websites, creating a website requires a name and a ZIP containing your files. You do not choose a technology: YourHost inspects the files to detect HTML, Next.js/Node.js, Vite or a compatible WordPress backup. This is not a universal installer: missing requirements or a format that is not enabled block publication and are explained in the portal.
Enter a name and check the suggested address.
The file is required. This form does not create example pages or empty WordPress sites.
Select Create and publish. Receiving files and reserving an address do not mean your website is online yet.
Wait for Online and open Visit site. If a requirement is missing, fix it from the same website without creating another.
HTML, CSS and images, or an already compiled export.
website.zip
├─ index.html
├─ styles.css
└─ images/Create a website
Automatic detection: Static website (HTML)
Place it at the root alongside the website assets.
Check the address shown in the dashboard.
The portal detects HTML content automatically.
Wait for Online and open Visit site.
How to check that it worked
Your HTTPS address opens the website and its images.
A ZIP containing your files is required; the form does not generate an example page.
Upload your code and its npm configuration.
application.zip
├─ package.json
├─ package-lock.json
├─ app/ or server.js
└─ public/Create a website
Automatic detection: Project (Next.js, Node.js or Vite)
Check the scripts and what your application needs.
Check the suggested subdomain.
Include package.json and package-lock.json; the format is detected automatically.
Use Refresh status, then visit the website.
How to check that it worked
Check the home page and your application routes.
This profile has no DB, persistent disk or outgoing server network.
Deliver Vite source; we publish its dist/ output.
frontend.zip
├─ package.json
├─ package-lock.json
├─ index.html
└─ src/Create a website
Automatic detection: Project (Next.js, Node.js or Vite)
Vite is detected automatically; you do not need to select it.
It must produce the dist/ folder.
Enter a name and attach the code and npm lockfile in a ZIP.
Also open an internal SPA route directly.
How to check that it worked
Your website, images and internal routes respond over HTTPS.
Already have compiled dist/? Upload its contents as HTML.
Upload a ZIP with a compatible database backup and wp-content/.
backup.zip
├─ database.sql
└─ wp-content/
├─ uploads/
├─ plugins/
└─ themes/Create a website
Automatic detection: WordPress
Include database.sql and wp-content/.
The ZIP is required; WordPress is detected from its contents.
Wait for the Online confirmation.
Open WordPress admin under Manage your website.
How to check that it worked
Check pages, images and access to /wp-admin/.
Plugins must be compatible: PHP has no outgoing network or online updates.
Your address stays the same. There is no need to create another website.
Save new files in the same bound publishable folder. Keep the website, permission and receipts. Once the previous submission has a confirmed terminal result, review the changes and authorize a normal publication; a valid permission does not need reconnecting.
publish and ZIP need a complete delivery of the updated project, not only changed files. Omitted source files are removed from the new version. Preserve required assets and functionality; prepare a publishable copy without secrets, without deleting originals. The advanced delta has a different contract.
yourhost check .
yourhost publish .Signing in does not replace hosting or website permission, or remove quotas and validation. For a new rejection, keep its code and UUID and ask support; do not create another website or buy another plan to bypass it. Never send passwords or tokens.
https://my-website.yourhost.usOpen My websites.
Select Upload ZIP file.
Wait without repeating the upload.
Open the same HTTPS address.
Preparing
We are checking your files.
Publishing
We are confirming the new version.
Online
Open your website and check its content.
Needs attention
Read the error and fix it from this same website.
This advanced workflow compares selected files with an already published website and prepares a source delta plan over HTTPS. It does not replace publish for first publication. Check eligibility before preparing a plan.
The advanced example in this guide concerns an active website with the cloudpage-pocketbase-v1 persistent profile, which requires Owner authorization and an available binding. The server determines eligibility for each website: continue only with eligible: true. Do not infer access from using Next.js, Node.js or Vite. Persistent data and configuration have their own procedure. Update my website: CLI or ZIP
Under My websites, find your website and select Domains and publishing tools. Check its address on Manage your website.
Find New key, give it a recognizable name and leave domain management disabled. Save the key when it appears: it is shown only once.
With Node.js 22 or later, install the CLI and set YOURHOST_SITE_TOKEN in your computer's environment. The CLI is YourHost's publishing tool.
npm install --global https://portal.yourhost.us/tools/yourhost-cli-0.3.3.tgzChoose your terminal, run the block, then enter or paste your key when prompted. Input stays hidden and is not added to command history. Keep this terminal open to publish; if you close it, set the variable again.
$key = Read-Host "Website key" -AsSecureString
$env:YOURHOST_SITE_TOKEN = [System.Net.NetworkCredential]::new("", $key).Password
Remove-Variable keyread -rs 'YOURHOST_SITE_TOKEN?Website key: '
export YOURHOST_SITE_TOKEN
printf '\n'read -rs -p "Website key: " YOURHOST_SITE_TOKEN
export YOURHOST_SITE_TOKEN
printf '\n'The key only authorizes publishing to that website, expires after 90 days and can be revoked in the portal. Do not paste it into a shared command, an AI conversation or files you will publish. Administrative keys and management SSH access are not needed.
Open a terminal in your project folder. Check that the local version works and choose the files to update.
The command compares your files with the remote version and saves changes in a plan. It does not publish yet. Replace the example path with one that exists in your project; repeat --files to add more files.
yourhost source plan . --files src/app/page.tsxLook for the id field in the response. This is the code used to publish and check the result. The requestId field identifies the submission; do not use it as the plan code.
idPlan code · use this valuePLAN_IDrequestIdSubmission code · not used with applyREQUEST_IDThe codes shown here are examples. Copy the real id value from your own response, without quotation marks.
Replace PLAN_ID with the real id value. When publication finishes, open the same website address and review the pages you changed.
yourhost source apply PLAN_ID --waitUp to 1 MiB and 128 files per change, under src/, messages/ or public/. The plan and its file snapshot expire after 24 hours. Omitted files are preserved. This channel does not install a new application or change dependencies, private configuration, databases or PocketBase hooks/schema.
An accepted publication can continue after you close the terminal. Check the same plan; if the response asks you to resume, use resume with that same code. Do not create another publication just to find out what happened.
yourhost source status PLAN_IDyourhost source resume PLAN_ID --waitunchanged means the selected files already match the remote version. No extra publication is created. If a plan expired, check its status first, then prepare a new one with your current changes.
Your AI with files and a terminal can submit a request to support@yourhost.us using CLI 0.3.3 and Node.js 22 or later. Creating SMTP-INTEGRATION.md on your computer sends nothing.
npm install --global https://portal.yourhost.us/tools/yourhost-cli-0.3.3.tgzDescribe the issue, expected result and reproduction steps in SMTP-INTEGRATION.md. Do not include passwords, tokens, keys or other secrets. Review the content and explicitly authorize submission.
If YOURHOST_SITE_TOKEN is set, it takes priority over privateStore; --folder does not override that token. Without that variable, the CLI uses the bound folder's private credential (privateStore); use --folder when working elsewhere. Verify that access belongs to the correct website; the server validates the binding. Generate one real UUID and save it with the exact subject and file before submission; replace <UUID>, do not run it literally.
node -e "console.log(crypto.randomUUID())"yourhost support submit SMTP-INTEGRATION.md --subject "Contact form" --request-id <UUID>The response returns the ticket UUID with status: received before sending the SMTP notification. Save that ticket and replace <TICKET_UUID> to check it. support list shows up to your website's 50 most recent requests without resending them. The request UUID is not the ticket UUID.
yourhost support status <TICKET_UUID>
yourhost support listIf YOURHOST_SITE_TOKEN is set, it takes priority over privateStore; --folder does not override that token. Without that variable, the CLI uses the bound folder's private credential (privateStore); use --folder when working elsewhere. Verify that access belongs to the correct website; the server validates the binding. Keep the token private, without displaying it or sharing it in chat; never print its value. To use privateStore you may unset the variable only in your own safe environment, with your authorization; do not delete local credentials. You do not need administrator access and must not add credentials to the support file.
notificationState describes the email notification: queued (waiting), retry (safe retry), sending, sent (accepted by SMTP), failed or uncertain. sent proves neither inbox delivery nor reading. uncertain needs review: do not blindly resend.
If the response is lost, keep the same request UUID, subject and exact file for replay; check support list and the ticket if known. Do not generate a new UUID to resolve uncertainty. Changing content with the same UUID is not a replay. An empty list does not prove the local MD was submitted: check the bound folder or --folder and query the real ticket UUID if already received; do not reconnect or create another ticket to force it to appear.
Maximum: 12,000 message characters, 20 KiB JSON body and 160 subject characters. Up to 20 new requests in the last 24 hours and 200 retained per account; an identical replay does not create another ticket. These limits do not permit secrets.
Website and email permissions are independent. You do not need to create a website to view an email service already authorized and associated with your account.
Publish your websites without creating mailboxes or granting email access.
An authorized email service can exist without a website or a web hosting plan.
Use both services with the same portal account and separate permissions.
Available now: a read-only view of associated domains and mailboxes. Automated purchasing and provisioning of standalone email are still pending; no prices or immediate activation are offered here. Unified webmail sign-in is also pending.
Sign in to the portal and open Your domain email using this guide's link. A current email access grant is required.
Choose a domain associated with your account to view its mailboxes. Other customers' domains are not shown.
Check mailboxes, their status and configured quota. Use Refresh email details whenever you need a recent reading.
Email domainexample.com
Configured quota is the mailbox limit, not storage you have used. This view does not show or change messages, passwords, mailboxes or quotas.
Select Open webmail in the email view. An external site opens: sign in with your email address and mailbox password. Your portal session does not sign you in there automatically.
Check that you are using the right account and that the email service is associated and authorized. A website subscription alone does not activate email. If your session expired, sign in again; if the service is not associated, contact support. Do not change MX records to resolve this message.
With a paid plan: up to five domains per website.
www.example.comTXT + CNAME / AHTTPSOpen Manage your website → Connect your domain.
Use the TXT and CNAME or A shown in the portal.
Allow DNS propagation, then select Verify DNS and HTTPS.
A complete example: connect www.example.com to your website on YourHost.us. Choose the company managing your DNS, even if you bought the domain or hosted your website elsewhere.
At your registrar, open Nameservers and check who manages them. If you bought the domain at GoDaddy but use Cloudflare nameservers, follow Cloudflare. If you do not recognize the servers, ask domain support who manages the active DNS zone. You do not need to transfer your domain or change nameservers to connect www.
Upload your files or import WordPress into YourHost and check your subdomain. Changing DNS does not copy content, databases or email from your previous host. Keep a backup and coordinate the switch if your website receives orders or data.
With an active website and a paid plan, open Manage your website → Connect your domain. Enter www.example.com, without https:// or a path. Add it and keep the records displayed by the portal handy.
Illustration only: replace example.com, mi-web.yourhost.us and the token with your actual portal values. Do not point to yourhost.us or portal.yourhost.us.
You can also open any provider in the list.
For the CNAME, select Proxy status → DNS only (gray cloud) and TTL → Auto. Keep DNS only: the orange proxy hides the destination YourHost checks. If you flatten all CNAME records, turn that off for this name; the TXT still proves ownership. Do not change nameservers for an already active zone.
Sign in to your provider, select example.com and follow this route. Menu names are reference labels; they may vary with your language or account type.
Choose TXT and copy the entire value from your portal. In this example the record belongs to _yourhost-verify.www.example.com, not @ or www itself.
Add recordTXT
Resulting full name
_yourhost-verify.www.example.comCopy your portal value without manually adding quotation marks unless the editor requires them.
To save: Save
Edit the www CNAME if it already exists. If www has A/AAAA records from your previous host, note their values and replace only incompatible records for that name with this CNAME. Do not add a second destination.
Add recordCNAME
Resulting full name
www.example.comTTL: Auto or your provider’s default. If 300 seconds is allowed, you can use it; this does not guarantee instant propagation.
To save: Save
Save both records. Return to YourHost and select Verify DNS and HTTPS. DNS may take minutes or up to 24–48 hours depending on previous caching; the new TTL does not clear the old cache. If ownership is verified but HTTPS is pending, wait a few minutes and verify again.
www.example.com
Verify DNS and HTTPSWhen the portal shows HTTPS ready, visit https://www.example.com and check pages, images and forms before retiring your previous hosting.
Bought it through Google Domains? Those domains migrated to Squarespace. Sign in at account.squarespace.com/domains and follow this route if it manages your DNS. Google Workspace, Gmail, Google Sites and Search Console alone do not tell you where to edit DNS. If your nameservers belong to another provider, use its guide. For Cloud DNS, open the alternative below.
Sign in to your provider, select example.com and follow this route. Menu names are reference labels; they may vary with your language or account type.
Choose TXT and copy the entire value from your portal. In this example the record belongs to _yourhost-verify.www.example.com, not @ or www itself.
Add recordTXT
Resulting full name
_yourhost-verify.www.example.comCopy your portal value without manually adding quotation marks unless the editor requires them.
To save: Save
Edit the www CNAME if it already exists. If www has A/AAAA records from your previous host, note their values and replace only incompatible records for that name with this CNAME. Do not add a second destination.
Add recordCNAME
Resulting full name
www.example.comTTL: Auto or your provider’s default. If 300 seconds is allowed, you can use it; this does not guarantee instant propagation.
To save: Save
Save both records. Return to YourHost and select Verify DNS and HTTPS. DNS may take minutes or up to 24–48 hours depending on previous caching; the new TTL does not clear the old cache. If ownership is verified but HTTPS is pending, wait a few minutes and verify again.
www.example.com
Verify DNS and HTTPSWhen the portal shows HTTPS ready, visit https://www.example.com and check pages, images and forms before retiring your previous hosting.
Only if a public Cloud DNS zone already manages your DNS. Select the correct project and zone. Enter the prefix in DNS name and check the full name appended by the console. Use a 300-second (5-minute) TTL if allowed; do not create a private zone or switch nameservers to follow this example.
Sign in to your provider, select example.com and follow this route. Menu names are reference labels; they may vary with your language or account type.
Choose TXT and copy the entire value from your portal. In this example the record belongs to _yourhost-verify.www.example.com, not @ or www itself.
Add standardTXT
Resulting full name
_yourhost-verify.www.example.comCopy your portal value without manually adding quotation marks unless the editor requires them.
To save: Create
Edit the www CNAME if it already exists. If www has A/AAAA records from your previous host, note their values and replace only incompatible records for that name with this CNAME. Do not add a second destination.
Add standardCNAME
Resulting full name
www.example.comTTL: Auto or your provider’s default. If 300 seconds is allowed, you can use it; this does not guarantee instant propagation.
To save: Create
Save both records. Return to YourHost and select Verify DNS and HTTPS. DNS may take minutes or up to 24–48 hours depending on previous caching; the new TTL does not clear the old cache. If ownership is verified but HTTPS is pending, wait a few minutes and verify again.
www.example.com
Verify DNS and HTTPSWhen the portal shows HTTPS ready, visit https://www.example.com and check pages, images and forms before retiring your previous hosting.
Edit the existing www CNAME if it points to @ or an old website. Enter the portal destination in Value, not @ or a URL. If Domain Protection requests identity verification, complete it to save. If GoDaddy only registers the domain and DNS is external, make these changes at that other provider.
Sign in to your provider, select example.com and follow this route. Menu names are reference labels; they may vary with your language or account type.
Choose TXT and copy the entire value from your portal. In this example the record belongs to _yourhost-verify.www.example.com, not @ or www itself.
Add New RecordTXT
Resulting full name
_yourhost-verify.www.example.comCopy your portal value without manually adding quotation marks unless the editor requires them.
To save: Save / Save All Records
Edit the www CNAME if it already exists. If www has A/AAAA records from your previous host, note their values and replace only incompatible records for that name with this CNAME. Do not add a second destination.
Add New RecordCNAME
Resulting full name
www.example.comTTL: Auto or your provider’s default. If 300 seconds is allowed, you can use it; this does not guarantee instant propagation.
To save: Save / Save All Records
Save both records. Return to YourHost and select Verify DNS and HTTPS. DNS may take minutes or up to 24–48 hours depending on previous caching; the new TTL does not clear the old cache. If ownership is verified but HTTPS is pending, wait a few minutes and verify again.
www.example.com
Verify DNS and HTTPSWhen the portal shows HTTPS ready, visit https://www.example.com and check pages, images and forms before retiring your previous hosting.
Use hPanel’s DNS zone editor; some accounts also expose it through Websites → Dashboard. If Hostinger CDN controls www, disable that connection for the name you are moving before replacing it. Do not use a wizard to point to Hostinger hosting: the destination is your website’s YourHost subdomain.
Sign in to your provider, select example.com and follow this route. Menu names are reference labels; they may vary with your language or account type.
Choose TXT and copy the entire value from your portal. In this example the record belongs to _yourhost-verify.www.example.com, not @ or www itself.
Add recordTXT
Resulting full name
_yourhost-verify.www.example.comCopy your portal value without manually adding quotation marks unless the editor requires them.
To save: Add Record / Update
Edit the www CNAME if it already exists. If www has A/AAAA records from your previous host, note their values and replace only incompatible records for that name with this CNAME. Do not add a second destination.
Add recordCNAME
Resulting full name
www.example.comTTL: Auto or your provider’s default. If 300 seconds is allowed, you can use it; this does not guarantee instant propagation.
To save: Add Record / Update
Save both records. Return to YourHost and select Verify DNS and HTTPS. DNS may take minutes or up to 24–48 hours depending on previous caching; the new TTL does not clear the old cache. If ownership is verified but HTTPS is pending, wait a few minutes and verify again.
www.example.com
Verify DNS and HTTPSWhen the portal shows HTTPS ready, visit https://www.example.com and check pages, images and forms before retiring your previous hosting.
For TXT, choose Other Host and enter _yourhost-verify.www; for CNAME, choose www. Alias to must point to the external hostname shown by YourHost. In classic view: Advanced Tools → Advanced DNS Records → Manage; edit Host Aliases (CNAME) and Text (TXT), then confirm Save Changes. Do not switch nameservers just to enable this editor.
Sign in to your provider, select example.com and follow this route. Menu names are reference labels; they may vary with your language or account type.
Choose TXT and copy the entire value from your portal. In this example the record belongs to _yourhost-verify.www.example.com, not @ or www itself.
+ Add RecordTXT
Resulting full name
_yourhost-verify.www.example.comCopy your portal value without manually adding quotation marks unless the editor requires them.
To save: Add / Edit
Edit the www CNAME if it already exists. If www has A/AAAA records from your previous host, note their values and replace only incompatible records for that name with this CNAME. Do not add a second destination.
+ Add RecordCNAME
Resulting full name
www.example.comTTL: Auto or your provider’s default. If 300 seconds is allowed, you can use it; this does not guarantee instant propagation.
To save: Add / Edit
Save both records. Return to YourHost and select Verify DNS and HTTPS. DNS may take minutes or up to 24–48 hours depending on previous caching; the new TTL does not clear the old cache. If ownership is verified but HTTPS is pending, wait a few minutes and verify again.
www.example.com
Verify DNS and HTTPSWhen the portal shows HTTPS ready, visit https://www.example.com and check pages, images and forms before retiring your previous hosting.
If the menu opens Manage Subdomains, select www → DNS. Add the TXT from the example.com zone with the relative name shown. IONOS may ask you to disconnect another product using www before accepting a CNAME; review the affected service. This connects www, not the root domain automatically.
Sign in to your provider, select example.com and follow this route. Menu names are reference labels; they may vary with your language or account type.
Choose TXT and copy the entire value from your portal. In this example the record belongs to _yourhost-verify.www.example.com, not @ or www itself.
Add recordTXT
Resulting full name
_yourhost-verify.www.example.comCopy your portal value without manually adding quotation marks unless the editor requires them.
To save: Save
Edit the www CNAME if it already exists. If www has A/AAAA records from your previous host, note their values and replace only incompatible records for that name with this CNAME. Do not add a second destination.
Add recordCNAME
Resulting full name
www.example.comTTL: Auto or your provider’s default. If 300 seconds is allowed, you can use it; this does not guarantee instant propagation.
To save: Save
Save both records. Return to YourHost and select Verify DNS and HTTPS. DNS may take minutes or up to 24–48 hours depending on previous caching; the new TTL does not clear the old cache. If ownership is verified but HTTPS is pending, wait a few minutes and verify again.
www.example.com
Verify DNS and HTTPSWhen the portal shows HTTPS ready, visit https://www.example.com and check pages, images and forms before retiring your previous hosting.
The primary route is Domains → DNS in the current portal. If your account manages that zone in cPanel, use Domains → Zone Editor → Manage and full names www.example.com. and _yourhost-verify.www.example.com.; check the suffix before saving. Do not use a DNS template that replaces the entire zone.
Sign in to your provider, select example.com and follow this route. Menu names are reference labels; they may vary with your language or account type.
Choose TXT and copy the entire value from your portal. In this example the record belongs to _yourhost-verify.www.example.com, not @ or www itself.
+ Add recordTXT
Resulting full name
_yourhost-verify.www.example.comCopy your portal value without manually adding quotation marks unless the editor requires them.
To save: Add / Save
Edit the www CNAME if it already exists. If www has A/AAAA records from your previous host, note their values and replace only incompatible records for that name with this CNAME. Do not add a second destination.
+ Add recordCNAME
Resulting full name
www.example.comTTL: Auto or your provider’s default. If 300 seconds is allowed, you can use it; this does not guarantee instant propagation.
To save: Add / Save
Save both records. Return to YourHost and select Verify DNS and HTTPS. DNS may take minutes or up to 24–48 hours depending on previous caching; the new TTL does not clear the old cache. If ownership is verified but HTTPS is pending, wait a few minutes and verify again.
www.example.com
Verify DNS and HTTPSWhen the portal shows HTTPS ready, visit https://www.example.com and check pages, images and forms before retiring your previous hosting.
Choose the TXT and CNAME tabs under Create New Record. If your interface shows Site Tools → Domain → DNS Zone Editor, open the same editor there. To update www, use the pencil under Manage DNS Records. Changes only take effect if the active nameservers belong to SiteGround.
Sign in to your provider, select example.com and follow this route. Menu names are reference labels; they may vary with your language or account type.
Choose TXT and copy the entire value from your portal. In this example the record belongs to _yourhost-verify.www.example.com, not @ or www itself.
Create New RecordTXT
Resulting full name
_yourhost-verify.www.example.comCopy your portal value without manually adding quotation marks unless the editor requires them.
To save: Create / Confirm
Edit the www CNAME if it already exists. If www has A/AAAA records from your previous host, note their values and replace only incompatible records for that name with this CNAME. Do not add a second destination.
Create New RecordCNAME
Resulting full name
www.example.comTTL: Auto or your provider’s default. If 300 seconds is allowed, you can use it; this does not guarantee instant propagation.
To save: Create / Confirm
Save both records. Return to YourHost and select Verify DNS and HTTPS. DNS may take minutes or up to 24–48 hours depending on previous caching; the new TTL does not clear the old cache. If ownership is verified but HTTPS is pending, wait a few minutes and verify again.
www.example.com
Verify DNS and HTTPSWhen the portal shows HTTPS ready, visit https://www.example.com and check pages, images and forms before retiring your previous hosting.
In Zone Editor, enter full names and check the trailing dot. If you bought the domain at HostGator, your Customer Portal may also offer Domains → domain → DNS. Use the editor for the zone actually serving your DNS, not both. The CNAME Record field takes a hostname, never an IP address.
Sign in to your provider, select example.com and follow this route. Menu names are reference labels; they may vary with your language or account type.
Choose TXT and copy the entire value from your portal. In this example the record belongs to _yourhost-verify.www.example.com, not @ or www itself.
+ Add RecordTXT
Resulting full name
_yourhost-verify.www.example.comCopy your portal value without manually adding quotation marks unless the editor requires them.
To save: Save Record
Edit the www CNAME if it already exists. If www has A/AAAA records from your previous host, note their values and replace only incompatible records for that name with this CNAME. Do not add a second destination.
+ Add RecordCNAME
Resulting full name
www.example.comTTL: Auto or your provider’s default. If 300 seconds is allowed, you can use it; this does not guarantee instant propagation.
To save: Save Record
Save both records. Return to YourHost and select Verify DNS and HTTPS. DNS may take minutes or up to 24–48 hours depending on previous caching; the new TTL does not clear the old cache. If ownership is verified but HTTPS is pending, wait a few minutes and verify again.
www.example.com
Verify DNS and HTTPSWhen the portal shows HTTPS ready, visit https://www.example.com and check pages, images and forms before retiring your previous hosting.
This route applies to BasicDNS, PremiumDNS or FreeDNS. Select TXT Record and CNAME Record, not URL Redirect Record. If you use Namecheap Web Hosting DNS, manage the zone in cPanel → Zone Editor. Do not switch to BasicDNS just to follow this guide without first migrating the records for your other services.
Sign in to your provider, select example.com and follow this route. Menu names are reference labels; they may vary with your language or account type.
Choose TXT and copy the entire value from your portal. In this example the record belongs to _yourhost-verify.www.example.com, not @ or www itself.
Add New RecordTXT
Resulting full name
_yourhost-verify.www.example.comCopy your portal value without manually adding quotation marks unless the editor requires them.
To save: Save All Changes / ✓
Edit the www CNAME if it already exists. If www has A/AAAA records from your previous host, note their values and replace only incompatible records for that name with this CNAME. Do not add a second destination.
Add New RecordCNAME
Resulting full name
www.example.comTTL: Auto or your provider’s default. If 300 seconds is allowed, you can use it; this does not guarantee instant propagation.
To save: Save All Changes / ✓
Save both records. Return to YourHost and select Verify DNS and HTTPS. DNS may take minutes or up to 24–48 hours depending on previous caching; the new TTL does not clear the old cache. If ownership is verified but HTTPS is pending, wait a few minutes and verify again.
www.example.com
Verify DNS and HTTPSWhen the portal shows HTTPS ready, visit https://www.example.com and check pages, images and forms before retiring your previous hosting.
If www is Fully Hosted and DreamHost will not let you replace its automatic records, review its DNS Only option before creating the CNAME. That change removes hosting configuration for the affected name: back up/import first and review the impact on example.com and email with support. If you want to keep root-domain hosting, confirm how to release only www; do not remove the entire domain blindly.
Sign in to your provider, select example.com and follow this route. Menu names are reference labels; they may vary with your language or account type.
Choose TXT and copy the entire value from your portal. In this example the record belongs to _yourhost-verify.www.example.com, not @ or www itself.
Add RecordTXT
Resulting full name
_yourhost-verify.www.example.comCopy your portal value without manually adding quotation marks unless the editor requires them.
To save: Add Record
Edit the www CNAME if it already exists. If www has A/AAAA records from your previous host, note their values and replace only incompatible records for that name with this CNAME. Do not add a second destination.
Add RecordCNAME
Resulting full name
www.example.comTTL: Auto or your provider’s default. If 300 seconds is allowed, you can use it; this does not guarantee instant propagation.
To save: Add Record
Save both records. Return to YourHost and select Verify DNS and HTTPS. DNS may take minutes or up to 24–48 hours depending on previous caching; the new TTL does not clear the old cache. If ownership is verified but HTTPS is pending, wait a few minutes and verify again.
www.example.com
Verify DNS and HTTPSWhen the portal shows HTTPS ready, visit https://www.example.com and check pages, images and forms before retiring your previous hosting.
Depending on your view, the zone may also appear under Domain names → example.com → DNS zone. The wizard appends .example.com to the subdomain; do not repeat it. For CNAME, enter the full destination with a trailing dot if required and review the summary before Confirm. Do not select Reset DNS zone or web forwarding.
Sign in to your provider, select example.com and follow this route. Menu names are reference labels; they may vary with your language or account type.
Choose TXT and copy the entire value from your portal. In this example the record belongs to _yourhost-verify.www.example.com, not @ or www itself.
Add an entryTXT
Resulting full name
_yourhost-verify.www.example.comCopy your portal value without manually adding quotation marks unless the editor requires them.
To save: Add / Confirm
Edit the www CNAME if it already exists. If www has A/AAAA records from your previous host, note their values and replace only incompatible records for that name with this CNAME. Do not add a second destination.
Add an entryCNAME
Resulting full name
www.example.comTTL: Auto or your provider’s default. If 300 seconds is allowed, you can use it; this does not guarantee instant propagation.
To save: Add / Confirm
Save both records. Return to YourHost and select Verify DNS and HTTPS. DNS may take minutes or up to 24–48 hours depending on previous caching; the new TTL does not clear the old cache. If ownership is verified but HTTPS is pending, wait a few minutes and verify again.
www.example.com
Verify DNS and HTTPSWhen the portal shows HTTPS ready, visit https://www.example.com and check pages, images and forms before retiring your previous hosting.
Use console.hetzner.com → your project → DNS; select the primary zone managing example.com. Check names and destination in the final list. Having a server or registering a domain at Hetzner does not mean its DNS zone is there: confirm the active nameservers first.
Sign in to your provider, select example.com and follow this route. Menu names are reference labels; they may vary with your language or account type.
Choose TXT and copy the entire value from your portal. In this example the record belongs to _yourhost-verify.www.example.com, not @ or www itself.
Type → TXT / CNAMETXT
Resulting full name
_yourhost-verify.www.example.comCopy your portal value without manually adding quotation marks unless the editor requires them.
To save: Add
Edit the www CNAME if it already exists. If www has A/AAAA records from your previous host, note their values and replace only incompatible records for that name with this CNAME. Do not add a second destination.
Type → TXT / CNAMECNAME
Resulting full name
www.example.comTTL: Auto or your provider’s default. If 300 seconds is allowed, you can use it; this does not guarantee instant propagation.
To save: Add
Save both records. Return to YourHost and select Verify DNS and HTTPS. DNS may take minutes or up to 24–48 hours depending on previous caching; the new TTL does not clear the old cache. If ownership is verified but HTTPS is pending, wait a few minutes and verify again.
www.example.com
Verify DNS and HTTPSWhen the portal shows HTTPS ready, visit https://www.example.com and check pages, images and forms before retiring your previous hosting.
It is a separate name: add it separately in YourHost and use A + TXT with the current portal values. Its TXT name is _yourhost-verify.example.com (usually Host: _yourhost-verify). Do not create a standard CNAME at @. Configuring www does not automatically connect or redirect example.com.
publish is the recommended workflow from your project with a terminal; ZIP in the dashboard is the alternative. These other tools are optional and have their own permissions and requirements per website.
Publish by pushing to main.
git clone <URL from your dashboard>
git push origin mainUpload with FileZilla or WinSCP.
portal.yourhost.us · SFTP · 7387
/upload/public/ → HTML
/upload/source/ → Project / WordPresspublish connects your project; support sends reviewed requests; deploy and source keep their advanced contracts.
npm install --global https://portal.yourhost.us/tools/yourhost-cli-0.3.3.tgz
yourhost check .
yourhost publish .
yourhost publish-status .
yourhost deploy ./public
yourhost source plan . --files src/app/page.tsx
yourhost source apply <UUID> --wait
yourhost source status <UUID>
yourhost source resume <UUID> --waitAutomate a ZIP with a website key.
POST https://portal.yourhost.us/api/v1/site/deploy
Content-Type: application/zip
Authorization: Bearer <website-key>
Idempotency-Key: <UUID>Open your workflow, copy the instruction and review the delivery before uploading.
No. Your AI with a terminal must review the file with you and run support submit with explicit authorization. Keep UUID, subject and file if the response is uncertain. See the three steps under Send a support request; received confirms a ticket, not resolution or a read email.
Check your authorized hosting access and any pending operation in the portal. Contact support if you need help. Buying another plan does not replace pending activation.
Identify the submission and read its code. A historical failure is not a website block. If pending or uncertain, query the same UUID. For different sources after a confirmed terminal result, use normal publish in the same folder or upload the corrected ZIP to the same website; not --retry or --reconnect. Repeating identical content requires a confirmed transient failure; PUBLICATION_FAILED without a specific cause needs support review. Do not create a duplicate website.
There is no automatic charge. To continue, explicitly subscribe to a paid plan. Check your dashboard's expiry date and keep a local copy.
Open View my subscription. Use Manage subscription for payments/cancellation and the portal's plan-change options. Downgrading requires your websites and storage to fit the new quota.
Website and email permissions are independent. If your email service is already authorized and associated, you can view its domains and mailboxes in the portal without creating a website. Automated standalone email purchasing and provisioning are still pending. Webmail requires its own sign-in. Keep your MX records until a migration is coordinated.
WordPress has its own database. The Node profile has no DB, persistence, configurable secrets or outgoing server network. General Python/PHP profiles and MCP are not available; ask about compatibility before uploading.
Check spam and request another confirmation if the link expired. For password recovery, use Forgot your password? and open the latest message. Resetting a password does not confirm the email.
That is the company providing YourHost. Stripe processes payments for CLOUDPAGE LLC; also check the amount and date. Contact support if you do not recognize a charge.
Share the error message with support, never passwords, keys or full card details.
Tell us your website type and the message you see.
Get helpYourHost is a service provided by CLOUDPAGE LLC.