I set an A record pointing at Imweb's IP like an old guide said, and it won't connect. Why?

Because that method no longer exists. Imweb stopped accepting new domain connections by A record on May 4, 2021, and began retiring existing A-record connections after that. Any tutorial that tells you to paste an IP address into an A record is out of date — the IP it gives you either doesn't answer for your site or won't stay valid. There are only two supported ways to connect a custom domain now: change your domain's nameservers to the ones Imweb assigns you (the recommended path), or set a CNAME alias for a subdomain. Delete the stale A record and pick one of those.

My site loads on the custom domain but the browser says 'not secure' — where's the HTTPS?

You almost certainly connected the domain by *forwarding* rather than by pointing its nameservers at Imweb. Forwarding just bounces visitors to your Imweb address; the certificate authority can't prove you control the domain that way, so no SSL certificate is issued and the padlock never appears. The fix is not a setting inside Imweb — it's changing the domain's nameservers at your registrar to Imweb's assigned nameservers. Once the domain is actually delegated to Imweb, the SSL certificate can be issued and HTTPS works. Forwarding and real delegation look similar in a browser until you check for the padlock.

I connected www with a CNAME but the root domain (no www) doesn't work, and SSL won't issue. What happened?

Two things collided. First, a CNAME can only sit on a subdomain like www — the root/apex of a domain can't hold a CNAME alongside its other required records, which is why the bare domain fails. Second, if you attach the CNAME to www without first completing the root-domain step, Imweb registers the site as www-only, and an SSL certificate for the bare domain then can't be issued. The clean fix is the nameserver method, which lets Imweb manage both the root and www and issue SSL for both. If you must stay on CNAME, ask your registrar's support to add the root-domain record before requesting SSL.

Imweb Custom Domain Not Connecting? Fix DNS

Problem

You pointed a custom domain at your Imweb site and it isn’t working — it times out, shows “server not found,” loads someone else’s parking page, or loads your site but with no HTTPS padlock. The domain clearly exists and you own it; what’s broken is the connection method. Imweb supports more than one way to attach a domain, each method fails in its own specific way, and the single most common cause of a stuck Imweb domain is following an old tutorial for a method Imweb has since removed.

Symptoms

The domain resolves to nothing (NXDOMAIN / “server not found”) or times out.
It loads a parking page, the registrar’s default page, or an old site instead of your Imweb content.
The site loads on the custom domain but the browser shows “Not secure” — no HTTPS, no padlock.
Only www.yourdomain.com works and the bare yourdomain.com doesn’t (or the reverse).
You set an A record to an IP an old guide gave you and nothing connects.

The Four Ways to Connect — and How Each Breaks

An Imweb “domain not connecting” problem is almost always a mismatch between the method you think you used and what your DNS actually says. There are four methods, and only two of them are supported today.

Nameserver change (recommended, and the only path to SSL). You change your domain’s nameserver (NS) records at your registrar to the 1st–4th nameservers Imweb assigns in your admin console. This hands Imweb full authority over the domain, so it can manage both the root and www and — critically — issue an SSL certificate. This is the method that gives you working HTTPS.

CNAME alias (subdomains only). You leave the domain’s nameservers where they are and add a CNAME record for a subdomain (typically www) pointing at your Imweb address. This works for the subdomain but has two traps: a CNAME can’t sit on the root/apex of a domain, and connecting www by CNAME without completing the root-domain step registers the site as www-only, after which SSL for the bare domain can’t be issued.

Forwarding (loads, but never gets HTTPS). You set up domain forwarding at the registrar so visitors get bounced to your Imweb address. The site appears to work, but because the certificate authority can’t verify domain control through a forward, no SSL certificate is issued — the padlock never shows. This is the number-one cause of “my Imweb site has no HTTPS.”

A record (removed — will not connect). Pointing an A record at an Imweb IP was retired: Imweb stopped accepting new A-record connections on May 4, 2021, and phased out existing ones afterward. Old blog tutorials still recommend it, which is why people paste an IP into an A record and nothing happens.

Top 3 Causes

Following an outdated A-record tutorial. The most common single cause. The A-record method is gone since May 2021, so any IP you set won’t reliably answer for your Imweb site. The tell: you have an A record pointing at an IP address, and the domain either doesn’t resolve to your content or connects intermittently.
Connected by forwarding, so SSL never issues. The site loads over HTTP but the browser flags it “not secure.” Forwarding can’t prove domain control to a certificate authority, so no cert is issued. The tell: the site works but has no padlock, and your registrar shows a forwarding/redirect rule rather than Imweb nameservers.
CNAME on the wrong scope, or nameservers not fully switched. You put a CNAME on the root (which can’t hold one), connected www only, or changed the nameservers but didn’t register all of the ones Imweb assigned — or the delegation simply hasn’t propagated yet. The tell: one of root/www works and the other doesn’t, or the registrar still shows the old nameservers.

Diagnose with DechoNet

DNS Lookup shows your domain’s current NS records and its A/CNAME answers in one view — so you can see immediately whether the domain is delegated to Imweb’s nameservers (the SSL-capable path), still pointing at your old provider, carrying a stale A record, or set up as a www-only CNAME. This is the fastest way to tell which of the four methods your DNS is actually on.
DNS Propagation Check queries resolvers around the world at once. If they disagree after a nameserver change, you’re still inside the delegation window and should wait rather than change anything; if they agree on a wrong answer, propagation is done and the record itself is the problem.

Resolution Checklist

Run DNS Lookup and read the NS records first. If they’re not Imweb’s, the domain isn’t delegated to Imweb — decide between switching nameservers (for SSL) or the CNAME method (subdomain only).
Delete any leftover A record pointing at an Imweb IP. That method was removed in May 2021 and only causes confusion.
If you want HTTPS, use the nameserver method: at your registrar, register all of the 1st–4th nameservers Imweb lists in your admin console — not just the first one — then expect the delegation to take up to 24–48 hours.
If the site loads but has no padlock, check for a forwarding rule at your registrar and remove it; forwarding cannot get an SSL certificate. Switch to the nameserver method instead.
If you’re on CNAME, remember it only works for a subdomain like www; the root domain needs a separate record added through your registrar’s support before SSL can issue for the bare name.
Use DNS Propagation Check across resolvers; if they disagree, wait out the TTL rather than making more changes.
Once DNS resolves correctly everywhere, confirm the page actually serves with an HTTP check.

When to Escalate

If DNS resolves to the correct target everywhere but SSL still won’t issue after the domain is delegated to Imweb’s nameservers, that’s an issuance step on Imweb’s side — contact Imweb support with the domain and the timestamp you completed delegation.
If the domain resolves correctly but is unreachable only from inside Korea, rule out an administrative access block before assuming a DNS fault — that’s a separate process handled through the registrar or host, not a records change.

Check your own domain now

Free, no sign-up. Runs the exact check this guide describes and shows what to fix.