TL;DR: lemlist checks your A record in Account Health to confirm your domain resolves and is reachable over HTTPS. If the check fails or shows a warning, the issue is at your DNS provider — verify the A record exists, confirm the IP is correct, and wait up to 48 hours for propagation. Use dnschecker.org to check status.
Symptoms
DNS lookup shows no A record found for your domain
Website or landing page isn't loading after adding an A record
DNS lookup returns an unexpected or outdated IP address
You were told your A record is misconfigured, but lemlist shows no related error
Website resolves in some locations but not others (partial propagation)
What lemlist checks
lemlist's Account Health section includes an A record check. The check verifies that your domain resolves to a valid IP address and is reachable over HTTPS. A passing check confirms your domain is correctly pointed. A warning such as "Your domain is only reachable over HTTP" means the A record resolves, but HTTPS isn't configured, which can reduce trust with mailbox providers. Note: A records are not required for email sending in lemlist — email delivery relies on SPF, DKIM, and DMARC. But lemlist surfaces this check because domain reachability can affect overall deliverability.
What an A record looks like
An A record maps a domain or subdomain to an IPv4 address. Here's the format you'll see in most DNS providers:
Host | Type | Value |
@ | A | 192.0.2.1 |
app | A | 192.0.2.1 |
⚠️ The IP addresses above (192.0.2.1) are examples only — do not copy or use them. Replace the value with the actual IP address provided by your web server or hosting provider.
Step-by-step fix
Go to the DNS provider that manages your nameservers — this is not always where you bought your domain. A common mistake: editing DNS records in GoDaddy when your nameservers actually point to Cloudflare. Changes made in the wrong place won't take effect. To confirm who manages your DNS, run dig yourdomain.com NS in a terminal, or use the NS lookup on dnschecker.org.
Look up your current A record using dnschecker.org or run dig yourdomain.com A in a terminal. Confirm an A record exists and check what IP it's returning.
Compare the IP address in your DNS record against the IP your web server or hosting provider gave you. A single wrong digit breaks the record — correct any mismatch.
Check for a CNAME conflict: if a CNAME record exists on the same hostname as your A record, the A record will be blocked. Remove the CNAME or use a different subdomain.
If you're using Cloudflare, open the A record and check whether it's set to Proxied (orange cloud) or DNS only (grey cloud). Some use cases require DNS only — switch if needed.
Save your changes and wait. DNS changes don't take effect immediately — each record has a TTL (Time to Live) value that controls how long DNS resolvers cache the old value. Changes typically take a few minutes to 48 hours to propagate globally. Recheck with dnschecker.org after waiting.
Confirm it's fixed
✓ dnschecker.org shows the correct IP address propagated globally
✓ Running dig yourdomain.com A in terminal returns the expected IP
✓ Website or landing page loads correctly in a browser
Why it happens
A records are managed entirely by your DNS provider — typos, CNAME conflicts, editing the wrong DNS zone, or propagation delays cause most issues. lemlist has no access to A records and no visibility into A record errors.
Alternatives
If you can't edit DNS yourself, contact your IT team or ask your domain/hosting provider's support to update the A record.
If your DNS provider doesn't support A records on the root domain (apex), use ANAME or ALIAS record types if available — these function similarly.
Still not working?
Contact your DNS provider's support team. Before reaching out, collect:
Your domain name and the subdomain the A record is on (e.g., yourdomain.com or app.yourdomain.com)
The IP address you're trying to point to
A screenshot of your current DNS records
The output from dnschecker.org showing where the record has or hasn't propagated