Why my domain or SSL is not working yet

After connecting a domain to your Antihost WordPress site, the domain or SSL may not work immediately.

This does not always mean something is broken. Domain setup includes several separate steps: domain registration, DNS configuration, DNS propagation, and SSL issuance. These steps may complete at different times.

Good to know
A domain can be purchased and configured correctly, but still not open immediately for every user. DNS and SSL changes need time to apply.

Domain and SSL setup stages

Domain purchased

A domain is “purchased” when the registration is completed and the domain is reserved for your use.

At this stage, the domain exists, but it may not yet point to your WordPress site.

What this means
Buying a domain does not automatically mean the website will open on that domain immediately.

DNS records added

DNS records tell the internet where your domain should point.

For example, DNS records can point your domain to the server where your Antihost WordPress instance is hosted.

If your domain was purchased through Antihost, the required DNS setup is handled automatically. If your domain was purchased elsewhere, you may need to update nameservers or DNS records at your registrar.

Simple explanation
The domain is the name.
DNS is the routing system that tells browsers where that name should go.

DNS propagated

DNS propagation means DNS changes have been updated across networks and DNS providers.

This process is not instant. During propagation, the domain may behave differently depending on where it is checked from.

For example:

• one user may already see the new Antihost site;
• another user may still see the old site;
• the domain may work on mobile internet but not on office Wi-Fi;
• the domain may work with www but not without it, or the opposite.

Important
DNS propagation does not finish everywhere at the same time. Temporary inconsistency is normal during this stage.

SSL issued

SSL is the certificate that allows your site to open securely through HTTPS.

SSL can usually be issued only after the domain points to the correct hosting environment. If DNS is still propagating or points to the wrong place, SSL may not be ready yet.

What this means
SSL depends on DNS. If DNS is not correct yet, HTTPS may not work correctly either.

Why the site may open without HTTPS

SSL may still be in progress

Right after domain setup, your site may temporarily open through HTTP instead of HTTPS.

This can happen because SSL issuance or validation is still in progress.

During this time, the site may:

• open without HTTPS;
• show “Not secure” in the browser;
• show a certificate warning;
• redirect incorrectly;
• work on the temporary domain but not on the final domain.

Good to know
A temporary HTTPS issue right after setup is not always a critical problem. It may simply mean SSL is still being issued or applied.

DNS may not point to Antihost yet

SSL cannot be applied correctly if the domain still points to the old hosting provider, old DNS records, or an external service.

This can happen if:

• nameservers were not changed correctly;
• old DNS records are still active;
• the root domain and www version point to different places;
• DNS propagation is still incomplete;
• external DNS or CDN settings override the expected setup.

Browser cache may show an old state

Sometimes DNS and SSL are already updated, but your browser still shows an old cached version.

To check this, try:

• opening the site in incognito/private mode;
• clearing browser cache;
• checking from another device;
• checking from another network;
• trying both https://yourdomain.com and https://www.yourdomain.com.

Tip
If the site works from another network but not from your current one, the issue may be local DNS cache or delayed propagation.

How to check DNS

Check nameservers

If you connected an existing domain to Antihost by changing nameservers, check that the domain uses Antihost nameservers.

Expected result should match the nameservers provided by Antihost.

[ns1.antihost.com]
[ns2.antihost.com]

Important
Replace these placeholders with the real Antihost nameservers before publishing this article.

If old nameservers still appear, the domain may still be managed by the previous provider.

Check A and CNAME records

If you are using external DNS instead of Antihost nameservers, check the A and CNAME records.

You may need to confirm:

• the root domain points to the correct Antihost value;
• the www version points to the correct place;
• old hosting records were removed;
• there are no conflicting records;
• CDN/proxy settings are not routing the domain elsewhere.

Important
If DNS is managed outside Antihost, Antihost cannot fully control your DNS records. The records must match the values provided by Antihost.

Check both domain versions

Check both versions of your domain:

yourdomain.com
www.yourdomain.com

Sometimes one version is configured correctly while the other still points to the wrong place.

Common issue
The root domain may work, but www may not work if the CNAME record is missing or incorrect.

What to do if you see an SSL warning

Do not assume the site is broken immediately

If you see an SSL warning right after domain setup, first check whether DNS is already pointing correctly.

SSL warnings can appear temporarily while:

• DNS is still propagating;
• SSL is still being issued;
• the browser has cached an old certificate state;
• the domain still points to another server;
• only one domain version is configured correctly.

Check the domain without and with www

Try opening:

https://yourdomain.com
https://www.yourdomain.com

If one version works and the other shows an SSL warning, the issue may be related to DNS or SSL coverage for one version of the domain.

Wait and check again

If the domain was just connected, wait and check again later.

During the first setup period, SSL may still be applying.

What this means
SSL warnings during initial setup are often temporary. Persistent SSL warnings after DNS is correct should be checked by support.

When to contact support

Contact support if the issue does not resolve after setup time

Contact Antihost support if:

• the domain still does not open after DNS propagation;
• the domain points to the wrong website;
• the domain works on the temporary domain but not on the final domain;
• SSL still shows an error after DNS is correct;
• only www or only the root domain works;
• the domain was purchased through Antihost but does not connect automatically;
• the domain was added to Antihost but does not appear attached to the WordPress instance;
• you changed nameservers but old nameservers still appear;
• you are using external DNS and are not sure which records to set.

Before contacting support
Check whether the issue is with DNS, SSL, or WordPress access. These are different layers and may need different fixes.

What to include in your support request

Provide enough context

When contacting support, include:

• your domain name;
• whether the domain was purchased through Antihost or another registrar;
• whether you changed nameservers;
• current nameservers;
• whether you use external DNS or CDN;
• whether the issue happens with www, without www, or both;
• screenshot of the browser warning;
• screenshot of DNS settings, if the domain is external;
• whether the temporary domain works.

Why this matters
Domain and SSL issues can happen at different layers: registrar, nameservers, DNS records, propagation, SSL issuance, browser cache, or WordPress instance connection. The more context you provide, the faster support can identify the issue.

Summary

Domain and SSL setup is a sequence

A working domain with HTTPS usually requires all of these steps:

1. The domain is purchased.
2. DNS records are created or updated.
3. DNS changes propagate.
4. The domain points to the correct WordPress instance.
5. SSL is issued and applied.
6. The site opens correctly through HTTPS.

If one step is still in progress, the domain or SSL may not work yet.

In most cases, the right first action is to check DNS, wait for propagation, and then contact support if the issue remains.