Domain Not Working? Find the Cause and Fix It
Hosting & Domains September 15, 2026 Last Updated: October 5, 2026

Domain Not Working? Find the Cause and Fix It

A domain that does not open after setup does not always need more waiting. First confirm the records are correct and were added in the right place, then check propagation and HTTPS.

Start with three simple checks

  1. Open example.com and www.example.com, replacing the example with your domain. Note which one works.
  2. Try mobile data instead of Wi-Fi. Different results may mean one network is still using an older answer.
  3. Save the exact error and the time of your last edit. Avoid changing settings repeatedly before identifying the cause.

Check the record location and values

Open the account where you registered your domain, then its Nameservers settings. These identify the provider that manages your website and email records. If IT PLUS manages those records, open your account → Domains → your domain → DNS management. If another provider manages them, add the records there. If you are unsure, ask support to check your domain before changing anything.

Compare the name, type and value of each record with the current values shown by your website platform. Adding records at a provider that does not manage the domain will not change the website.

Keep existing email records. Do not delete all records or replace nameservers just to connect a website. Copy values from your own project; do not reuse a server address from an article or another customer’s project.

See where to enter the record type, name and value
The actual IT PLUS record form with example data. Use the type, name and value from your platform, not the placeholder shown. Keep the default TTL unless the platform specifies otherwise.
The actual IT PLUS record form with example data. Use the type, name and value from your platform, not the placeholder shown. Keep the default TTL unless the platform specifies otherwise.

When should you wait?

Wait when the required values are correct at the responsible provider and some networks still return old answers. Changes may appear within minutes or hours, sometimes 24–48 hours or longer. Missing or incorrect records need to be fixed first.

If the browser warns the connection is unsafe

This is a separate check from reaching the website server. Review the HTTPS certificate status in the website platform. Make sure it covers the address you are opening, including the main domain or www as needed. Do not bypass the warning or enter credentials on an unsafe page.

What to send support

Share your domain, platform, error screenshot, last edit time, and whether the website, email or both are affected. Support can then determine whether a setting needs correction or a change needs time to appear.

Details for the person helping you set this up

For the administrator: query the authoritative nameservers, then compare public resolvers. Check conflicting A, AAAA and CNAME records and the TTL. Certificate failures may require reviewing verification, CAA or platform settings. Check mail MX and TXT records separately.

Written and reviewed by IT PLUS — September 2026.

Stuck on a step? Share your domain name and a screenshot of the problem so we can help.

Leave a Comment

Comments (0)

No comments yet. Be the first to comment!