Website Builder Domain Not Working? Common Fixes to Try

Has Your Site Been Published?

Before diving into DNS records and domain registrars, confirm the most fundamental requirement: your website must be explicitly published to go live on the internet. This step is so foundational that many troubleshooting articles skip it, yet it catches the majority of “domain not working” complaints.

Check the Publish Status in Your Dashboard

Open your website builder account and look for a status indicator, usually labeled “Published,” “Draft,” “Live,” or “Unpublished.” This is typically visible on your dashboard, in your site settings, or near your domain connection area. If the status shows anything other than “Published” or “Live,” your site is not yet public. Locate the Publish button; it’s usually prominently placed at the top of the editor or in a settings menu, and click it. The builder will process your request, which typically takes 30 seconds to a few minutes depending on your site’s size and the platform’s current server load.

After publishing, wait for the confirmation message. Some builders display “Your site is now live” or show a checkmark next to “Published.” Once you see confirmation, your site is accessible to the outside world. Now test it: open a new browser tab or window, go to your domain name, and verify that your website loads correctly. If it does, your domain connection is likely fine. If it doesn’t load within the next minute or two, proceed to the DNS troubleshooting sections below.

Understand the Difference Between Saving and Publishing

Many new website builders streamline the save-and-publish process to reduce confusion, but some keep them separate to give you control over when your site goes live. Understanding this distinction prevents wasted troubleshooting time. Saving preserves your work in the builder’s system, so you can edit, change your mind, and edit again without affecting your live site. Publishing takes whatever you’ve saved and makes it accessible to visitors via your domain.

Some builders combine these into a single “Publish” action; others ask you to save drafts, review a preview, and then publish as a separate step. Regardless of your builder’s design, you always have a final publishing step to complete. Check your builder’s help documentation if you’re unsure where this button is. If you’ve been editing for days and never clicked a final “Publish,” “Make Live,” or “Deploy” button, that’s likely your issue. Click it now, and your site should appear online within minutes.

Website Builder Plans & Pricing

Create a professional website with flexible website builder plans designed for businesses, portfolios, and growing online brands. Choose a plan that matches your needs and build, customize, and manage your website with easy-to-use tools, responsive designs, and essential features for a strong online presence.

Website Builder Personal

$4.99 per month

Share your passion online.

• Responsive mobile design
• Website hosting
• Rapid Page-Load performance
• Create a blog
• Security (SSL)
• 24/7 support

Order Now

Website Builder Business

$7.99 per month

Create an online presence for your business.

• Responsive mobile design
• Website hosting
• Rapid Page-Load performance
• Create a blog
• Security (SSL)
• 24/7 support
• PayPal Buy Now or Donate button
• Search Engine Optimization (SEO)

Order Now

Website Builder Business Plus

$11.99 per month

Attract more customers.

• Responsive mobile design
• Website hosting
• Rapid Page-Load performance
• Create a blog
• Security (SSL)
• 24/7 support
• PayPal Buy Now or Donate button
• Search Engine Optimization (SEO)
• Social Media Integration
• Share content to Facebook
• Online Appointments

Order Now

Website Builder Online Store

$22.99 per month

Sell products and services.

• Responsive mobile design
• Website hosting
• Rapid Page-Load performance
• Create a blog
• Security (SSL)
• 24/7 Support
• PayPal Buy Now or Donate Button
• Search Engine Optimization (SEO)
• Social Media Integration
• Share content to Facebook
• Online Appointments
• Built-in shopping cart
• Sell physical and digital products
• Accept credit and debit cards, PayPal and more
• Flexible shipping options
• Discounts and promotions
• Manage inventory

Order Now

Wait for DNS Propagation (Usually 24–48 Hours)

After you change DNS records at your domain registrar to point your domain to your website builder’s servers, those changes don’t take effect everywhere on the internet at once. The internet is a distributed system with thousands of DNS servers worldwide, each caching domain information for a period of time. When you update a DNS record, the change starts spreading outward from your registrar and gradually reaches DNS servers globally. This spread takes time and is called DNS propagation.

Track Propagation with Free Online Tools

You don’t have to guess whether propagation has completed. Free online DNS lookup tools let you check whether your DNS changes have reached global servers. Tools like dnschecker.org, WhatsMyDNS, and MXToolbox query DNS servers in multiple geographic locations and report whether your domain points to the correct destination from each location. Visit dnschecker.org, enter your domain name, select the record type (A record or CNAME), and run the lookup. The tool will return results from dozens of DNS servers worldwide.

Green checkmarks or consistent results across all locations mean your DNS has propagated globally and is pointing correctly. If you see many red X marks or inconsistent results, propagation is still in progress; wait a few more hours and recheck. This tool removes uncertainty and gives you concrete evidence that your domain is configured correctly. Check every 2–4 hours during the propagation window. Most of the time, you’ll see propagation complete within 6–24 hours, well before the 48-hour maximum.

What If Only One Domain Version Works?

Sometimes www.yoursite.com loads perfectly, but yoursite.com (the “naked” root domain) returns an error, or vice versa. This scenario tells you something important: propagation isn’t the issue; one DNS record is missing or misconfigured. When only one version works, one record is correct, and the other isn’t. Your builder requires both an A record (for the root domain) and a CNAME record (for the www subdomain) to function properly. If only one is set up, only that version will work.

Check your builder’s domain connection screen again and identify the missing or incorrect record. If the A record is pointing to the wrong IP address, update it. If the CNAME record is missing entirely, add it now using the exact values your builder specifies. After updating, wait 2–4 hours for propagation and then recheck with your DNS lookup tool. This targeted approach to partial failures is much faster than waiting a full 48 hours for propagation after a blind change.

Check Your DNS Records Against Builder Requirements

If 48 hours have elapsed since you connected your domain and your site still isn’t loading, the root cause is almost certainly incorrect or missing DNS records. This is where the vast majority of domain failures originate, not with the domain registrar or the builder, but with a mismatch between what the builder requires and what’s actually configured in your DNS.

Remove Conflicting or Old DNS Records

A frequently overlooked cause of domain failure is conflicting DNS records left behind from previous setups. If you’ve used this domain with a different website builder, a different hosting provider, or any other service in the past, old DNS records may still exist in your registrar’s DNS panel. These legacy records compete with your new builder’s records and prevent proper connection. Additionally, some registrars or domain managers automatically create default DNS records when you register a domain. These defaults often conflict with the specific records your builder requires.

Scan your DNS panel for any A, AAAA, or CNAME records that don’t match your builder’s current requirements. AAAA records (which point to IPv6 addresses) can particularly interfere with A records (IPv4). If you see multiple CNAME records for the same subdomain (for example, two CNAME records both for “www”), this is definitely wrong; a single hostname can have only one CNAME. Delete all redundant, old, or conflicting records, leaving only the records your builder specifies. After cleanup, wait 4–6 hours for propagation of these deletions, then verify your domain again.

Special Case: GoDaddy Domains with GoDaddy Website Builder

If both your domain registration and your website builder are with GoDaddy, you have a significant advantage: GoDaddy’s systems integrate automatically, and DNS records update without manual entry. When you connect your domain in GoDaddy Website Builder, GoDaddy’s back-end systems immediately update your DNS records in your domain account. You’ll see this happen in real time or within a few minutes after you confirm the connection. This automated integration is one reason many businesses prefer to consolidate their domain and builder with a single provider.

If your domain is registered elsewhere, with Namecheap, Google Domains, Bluehost, or any other registrar, you must manually add DNS records through that registrar’s DNS panel. Even if you’re using GoDaddy Website Builder, you still need to manually tell the domain registrar the correct DNS values. This is not difficult, but it requires attention to detail when copying and pasting values.

Verify DNS Is Pointing to the Right Place

Before changing any DNS records, verify your current configuration with an external DNS lookup tool. This step is critical because it shows you exactly what the internet currently believes your domain points to. Use MXToolbox, WhatsMyDNS, or a similar free DNS lookup service to query your domain. Enter your domain name, select the record type (A or CNAME), and run the lookup. The results will show you the current values from multiple DNS servers worldwide.

Spot-Check Both Root and WWW Subdomains

Website builders almost always require both a root domain (yoursite.com) and a www subdomain (www.yoursite.com) to be configured correctly. Some DNS lookup tools default to showing only one. To ensure complete coverage, manually enter and check both versions separately. Query yoursite.com to see the A record, then query www.yoursite.com to see the CNAME record. If one query returns the correct builder information and the other returns nothing or an old value, you’ve identified the specific record that needs fixing.

This targeted verification approach saves hours of troubleshooting. Instead of assuming both records might be wrong, you know exactly which one to fix. Update the incorrect record in your registrar’s DNS panel with the exact value your builder specifies, wait 2–4 hours, and recheck with your lookup tool. This methodical approach is far more efficient than making blind changes and hoping they work.

Use DNS Lookup Tools for Detailed Verification

These free verification tools are invaluable for DNS troubleshooting because they show you exactly what’s happening at a technical level. They display each record’s type (A, CNAME, MX, etc.), name (the subdomain or root), value (where it points), and TTL (how long other servers cache the information before checking for updates). Comparing this detailed information side by side with your builder’s requirements eliminates guesswork. Print both your DNS lookup results and your builder’s connection screen requirements, and compare them line by line if needed. Any deviation is a problem to fix.

SSL Certificates Take Time to Activate

After your domain connects and your website begins loading, many site owners encounter a security warning in the browser: “Not Secure” or a padlock with an alert. Before you panic, understand what this means: your site is loading correctly, but your SSL certificate hasn’t activated yet. SSL (Secure Sockets Layer) is the encryption protocol that secures data transmitted between visitors’ browsers and your website. It’s not optional; modern browsers flag sites without SSL as potentially unsafe.

Republish Your Site to Speed Up SSL Certificate Activation

If your domain has been connected for more than 24 hours and the SSL certificate still shows “Pending” or “Activating,” try republishing your site. This tells your builder’s system to restart the SSL certificate issuance process, which often speeds up activation. Open your builder, find the Publish button (you may need to access it through Settings or Site Status), click it to republish, and then wait 30 minutes before checking your site again.

After republishing, test your domain in a different browser if the warning persists in your primary browser. For example, try Firefox or Safari if you’ve been testing in Chrome. Different browsers cache different information, so this cross-browser verification helps isolate whether the issue is your browser cache or an actual SSL delay. Most of the time, republishing resolves SSL activation delays within an hour.

Clear Browser Cache If SSL Seems Stuck

Browsers cache SSL certificate information locally to speed up repeated visits to the same site. If you see a persistent security warning even though your certificate should be active, your browser’s cache may be serving outdated certificate data. Clear your browser’s cache and cookies, then reload your website. If the warning disappears after clearing the cache, the problem was local to your browser, not your site.

An even faster way to test this is to use Incognito or Private Browsing mode. This mode doesn’t use cached data and will fetch fresh certificate information from your site. If the site loads securely (with a padlock, no warning) in Incognito mode but shows a warning in your regular browsing mode, that confirms the problem is your local cache. Clear your cache and the warning should disappear everywhere. If the warning persists even in Incognito mode, the SSL certificate hasn’t activated yet, so wait longer or contact support.

When to Contact Support

You’ve published your site, waited 48+ hours, verified DNS records match your builder’s requirements exactly, confirmed propagation with a DNS lookup tool, removed conflicting old records, waited again, cleared your browser cache, and checked in multiple browsers, yet your domain still isn’t working. At this point, the issue exists outside your direct control, and professional support is the appropriate next step. Don’t feel discouraged; complex domain issues are relatively rare, and your builder’s support team is equipped to diagnose them.

Prepare a Support Ticket with Complete Information

Support teams at Niya Digital and your builder triage issues faster when you provide all relevant details upfront. Include screenshots whenever possible; they’re far more informative than verbal descriptions. Show both what your builder requires (the connection screen) and what your registrar currently has configured (your DNS panel). Include the exact timestamp when you made changes; this helps support correlate their logs to your actions. Note whether you’re using your builder’s automatic setup (if available for your registrar) or manual DNS configuration. These details help pinpoint the exact problem without back-and-forth email exchanges.

What Happens if Your Domain Expires

Your domain registration has an expiration date. If your domain stopped working suddenly after months of working perfectly, the most common cause is domain expiration. Check your registrar account immediately for your domain’s expiration date. If it has expired, renew it right away; most registrars offer simple renewal options in your account dashboard. Renewal is usually quick and takes effect immediately. After renewal, your DNS records are reactivated, and your site will come back online within a few hours as DNS propagates the reactivation. Set a calendar reminder for 60 days before your domain’s next renewal date to avoid this situation in the future.

Domain Registrar vs. Builder Auto-Configuration

Not all domain-and-builder combinations require manual DNS setup. Understanding your specific configuration saves time and frustration. Some builders automatically update DNS when specific conditions are met; others require you to enter DNS records manually. This difference often depends on whether your domain and builder are with the same company.

GoDaddy-to-GoDaddy Auto-Setup

If you registered your domain with GoDaddy and you’re using GoDaddy Website Builder (also called Airo AI Builder), domain connection is largely automatic. You add the domain in the builder and confirm the connection; GoDaddy’s back-end systems update your DNS records automatically within minutes. You’ll see the connection status change from “Connecting” to “Connected” as the system configures DNS. This integrated approach is one advantage of keeping your domain and builder with the same provider: less technical work and fewer potential points of failure.

Third-Party Registrars Require Manual DNS

If your domain is registered with Namecheap, Google Domains, Bluehost, or any registrar other than your builder’s provider, you must manually configure DNS records. Your builder provides the specific DNS values your domain needs (typically shown on a domain connection screen). You copy these values, log into your registrar’s DNS panel, and add the records manually. This process is straightforward: copy and paste, but pay close attention to ensure every character is correct. The benefit: you maintain flexibility and aren’t locked into a single provider for all services.

Interpreting Common Domain Connection Error Messages

Error messages are clues that point toward specific solutions. Website builders and registrars display error codes to guide your troubleshooting. Understanding what these messages mean speeds up problem-solving and prevents unnecessary changes. Here are the most common domain connection errors and what they actually indicate.

Error 1001: DNS Resolution Failed

This error indicates that DNS records are either completely missing or pointing to the wrong location. The system tried to resolve your domain using the DNS records currently configured but couldn’t find information pointing to your builder’s servers. This error appears when you’ve connected your domain but haven’t yet (or incorrectly) configured DNS records in your registrar. To fix it, verify that the A record and CNAME record in your registrar’s DNS panel match exactly what your builder requires. Check for typos, missing characters, or trailing periods. Recheck with a DNS lookup tool after updating.

Connection Refused & Timeout Errors

“Connection refused” or “request timed out” errors often occur during the first 48 hours after DNS changes, when propagation is still in progress. Your builder’s systems are running; they’re just not accessible globally yet because some DNS servers haven’t received the update. These errors are usually temporary and resolve as propagation completes. If these errors persist beyond 48 hours, your DNS records are likely still configured incorrectly. Use a DNS lookup tool to verify the records match your builder’s requirements exactly.

Security & SSL Troubleshooting Beyond 48 Hours

When SSL certificates refuse to activate despite correct DNS records and extended waiting periods, specific DNS record conflicts are usually responsible. SSL certificate issuance depends on successful domain verification, which relies on DNS being completely and correctly configured. If DNS is incomplete or conflicting, the certificate authority cannot verify domain ownership, and the certificate remains stuck in a pending state indefinitely.

CAA Records & SSL Conflicts

CAA (Certification Authority Authorization) records tell certificate authorities which providers are authorized to issue SSL certificates for your domain. If a CAA record exists in your DNS but doesn’t list your builder’s certificate provider, SSL activation fails. Your builder’s certificate authority (typically Let’s Encrypt or another service) tries to issue a certificate, but the CAA record says “you’re not authorized,” so it isn’t issued. To fix this, check your registrar’s DNS panel for any CAA records. If you do, remove them or update them to include your builder’s certificate authority. Incorrect CNAME or CAA records can also conflict with SSL.

Forcing SSL Certificate Reissuance

If your domain’s DNS is now correct but the certificate is still stuck in “Pending” status, request a manual reissuance. Republishing your site instructs the system to restart the entire SSL issuance process. Most builders offer a “Renew SSL,” “Reissue Certificate,” or similar option in domain settings. After reissuing, wait 30 minutes and check for activation. If the certificate is still pending after an hour, contact your builder’s support team with your DNS records and the timestamp of your reissuance request. They can manually force certificate issuance or investigate server-side blockers preventing activation.

Launching on Your Connected Domain: What’s Next

Once your domain connects, your SSL certificate activates, and your site loads correctly, you’ve crossed the critical threshold from setup to launch. Your website is now live on the internet. However, a working domain is the start, not the finish. Post-launch steps ensure your site remains healthy, secure, and performing well.

Post-Launch Maintenance Checklist

After your domain goes live, perform comprehensive testing to ensure everything works correctly. Test your site from multiple browsers (Chrome, Firefox, Safari, Edge) and multiple devices (desktop, tablet, mobile phone) to verify that it displays correctly everywhere and that all interactive elements function. Test all forms, contact forms, newsletter signups, appointment booking, shopping carts, or any other interactive features. Click every link to confirm they work. Load all images to ensure they appear correctly. Test any third-party integrations (payment processing, email marketing, analytics) to confirm they’re connected.

Set up Google Search Console and Google Analytics to monitor traffic, identify the search terms bringing people to your site, and track user behavior. Use free tools like Google PageSpeed Insights to measure your site’s speed and identify performance improvements. Set reminders for regular content updates; even small refreshes signal to search engines and visitors that your site is active and maintained.

Monitoring Site Performance & Uptime

Ongoing monitoring prevents the crisis of a site going down without your immediate knowledge. Set up uptime monitoring (many free services alert you immediately if your site becomes inaccessible) so you know about problems before your customers do. Check your domain’s expiration date monthly, and set calendar reminders weeks before renewal dates. Monitor your SSL certificate’s expiration date too; most builders renew certificates automatically, but verification is worthwhile. Periodically refresh DNS lookup checks to ensure nothing has changed unexpectedly. These small, regular checks prevent the emergency of waking up to discover your site is offline.

Frequently Asked Questions

Why does my domain show the old website even though I changed the DNS?

DNS changes propagate gradually across thousands of internet servers worldwide, typically taking 24–48 hours. During propagation, different geographic regions possess different information about your domain. A visitor in one location may see your new website while another visitor sees the old content. This isn’t a problem; it’s normal DNS behavior. Wait for full propagation to complete before assuming an error occurred. You can confirm faster by using a DNS lookup tool like dnschecker.org, which queries servers globally and shows propagation status. If the tool shows your records are correct across all locations, propagation is complete.

Can I use a domain from any registrar with a website builder?

Yes, absolutely. Website builders support domains from virtually any registrar, GoDaddy, Namecheap, Squarespace, Bluehost, Google Domains, and hundreds of others. You’ll need to log into your registrar’s account and manually add the DNS records your builder provides. The process involves copying the A record and CNAME values from your builder and pasting them into your registrar’s DNS panel. If your domain is registered with the same company as your builder (both GoDaddy, for example), DNS updates often happen automatically without manual entry, which many business owners appreciate.

What’s the difference between an A record and a CNAME record?

An A record points a domain name directly to an IP address (a numeric address like 192.0.2.1). A CNAME record points a domain name to another domain name or hostname alias instead. Website builders typically use an A record for your root domain (yoursite.com) and a CNAME record for the www subdomain (www.yoursite.com), but specific requirements vary by builder platform. Both record types are necessary for a complete domain setup; if only one is configured, only that specific domain version will work.

My domain works but says “Not Secure”; is my site hacked?

No, your site is not hacked. The “Not Secure” warning means your SSL certificate hasn’t activated yet, which is normal for newly connected domains. SSL certificates take 24–30 hours to issue and activate after you connect your domain. During this activation window, browsers display security warnings because the certificate doesn’t exist yet. The warning disappears automatically once the certificate activates. If the warning persists beyond 48 hours, try republishing your site or clearing your browser cache; both often resolve the issue. Contact support if the warning continues past 48 hours.

How do I check if my DNS records are pointing correctly?

Use a free DNS lookup tool like dnschecker.org, MXToolbox, or WhatsMyDNS. Enter your domain name, select the record type (A or CNAME), and run the lookup. The tool queries DNS servers worldwide and reports whether your domain points to the correct location. Green checkmarks or consistent correct values across all locations mean your DNS is configured correctly. Red marks or inconsistent values indicate DNS problems or incomplete propagation. This tool eliminates guesswork about whether your DNS is set up correctly.

Can I connect multiple subdomains (like blog.yoursite.com) to my builder?

Most website builders support only the root domain (yoursite.com) and the www subdomain (www.yoursite.com) for the main site. Additional subdomains like blog.yoursite.com or shop.yoursite.com typically require separate setup, usually managed through additional DNS records or routing to other platforms. Check your builder’s documentation specifically for subdomain support, as policies vary by platform. Some builders offer subdomain support; others don’t. Plan your domain structure before finalizing your setup.

What if my registrar doesn’t allow me to edit DNS records?

Some older registrar accounts or certain reseller accounts restrict DNS editing for security reasons. Contact your registrar’s support team and ask them to either enable DNS zone editing on your account or to update your DNS records for you manually. Provide them with the exact DNS record values your builder requires, and they’ll configure them on your behalf. This adds a step, but still enables domain connection. Alternatively, you can transfer your domain to a registrar that offers full DNS control, though this adds complexity.

Do I need to move my domain to a new registrar to use a website builder?

No, moving your domain is completely optional. You can keep your domain registered at any registrar and connect it to your builder through DNS records. Moving only makes sense if you want to consolidate all your services (domain, hosting, site builder) with a single provider for simpler management. But this is a convenience choice, not a technical requirement. Your current registrar will continue managing your domain while your builder hosts your website.

Why does my SSL certificate keep showing as “Pending”?

SSL certificates can take 24–48 hours to issue and activate. The delay typically happens because the certificate authority must verify domain ownership before issuing the certificate, a process that relies on correct DNS configuration. If any DNS records are missing or incorrect, verification fails and the certificate never issues. Ensure all your DNS records match your builder’s requirements exactly. Try republishing your site, which often restarts the certification process. If the certificate remains pending beyond 48 hours, contact support with a screenshot of your DNS records.

My domain worked fine for months, then suddenly stopped. What happened?

The most common cause is domain expiration. Check your registrar account for your domain’s expiration date immediately. If it’s expired, renew it right away; most registrars offer one-click renewal. Your site will come back online within hours as DNS propagates. If the domain isn’t expired, you may have accidentally changed or overwritten your DNS settings. Use a DNS lookup tool to verify your current settings match what your builder requires. Contact support if you can’t identify what changed.

How do I know if I should use nameservers or DNS records?

Your builder’s documentation specifies which method to use; some platforms support both, while others require one method specifically. Nameserver changes point your entire domain to your builder’s system, while DNS record changes (A and CNAME) point only specific records. DNS record changes propagate faster (typically 2–24 hours) than nameserver changes (24–72 hours). If your builder provides specific DNS record values, use those records instead of changing nameservers; it’s the faster approach.

Can I have more than one website on the same domain?

Website builders typically allow one website per domain. If you want to run multiple distinct websites, you’ll need multiple domains, one per site. Some builders support subdomains (like blog.yoursite.com being a separate site), but this requires separate configuration and may not be supported by all platforms. If you need multiple sites, plan your domain structure and clarify with your builder what’s possible within your platform.

Why does dnschecker show different results in different locations?

This is completely normal during DNS propagation. Different DNS servers worldwide update at different times based on their cache settings and update frequencies. A server in one country might have the new information while a server in another country still has the old data. All locations should show the same result within 48 hours maximum. If many locations still show old data after 48 hours, your DNS records are likely still configured incorrectly; recheck them for typos or missing values.

What should I do if I accidentally deleted a DNS record?

Log back into your registrar, recreate the exact record using the values your builder specifies, save it, and wait for propagation. DNS changes are fully reversible, so this is easy to fix. You can check propagation progress with a DNS lookup tool. Check every 2 hours until your lookup tool shows the record is correct and propagated globally.

Does my builder help troubleshoot domain issues?

Yes, reputable builders, including Niya Digital, provide support for domain setup and troubleshooting. Niya Digital’s team specifically handles domain connection issues through onboarding support, template customization guidance, and account management services. Contact your builder’s support team with your DNS details and error messages for faster resolution. They can often diagnose and resolve issues that remain invisible to standard troubleshooting.

Glossary

• DNS (Domain Name System): The foundational technology underlying the internet that translates human-readable domain names (like yoursite.com) into numeric IP addresses so browsers can locate and load the correct website servers.
• Domain: A website’s unique internet address and identifier, such as yoursite.com or www.yoursite.com. Domains are registered through registrars for an annual fee and must connect to a website builder or hosting provider to work.
• A Record: A DNS record that points a root domain (yoursite.com, without “www”) directly to an IP address managed by your website builder or hosting provider, enabling browser access to your site.
• CNAME Record: A DNS record that points a subdomain, typically the www version (www.yoursite.com), to a domain name or hostname alias controlled by your website builder, enabling browser access via the www address.
• DNS Propagation: The gradual worldwide distribution of DNS changes across internet servers, typically taking 24–48 hours for complete global propagation, during which some servers have updated information while others retain cached older data.
• SSL Certificate: A digital security certificate that encrypts data transmitted between visitors’ browsers and your website, enabling the https:// protocol and the padlock security icon. Website builders provide SSL certificates automatically.
• Registrar: A company authorized by ICANN to register and manage domain names, such as GoDaddy, Namecheap, or Bluehost. Registrars maintain your domain’s DNS records and handle renewals.