ICANN Domain Verification Email: Why Your Domain Got Suspended

Your domain isn't expired, your bill is paid, and DNS looks fine in the zone editor — but the site won't load and mail is bouncing. Nine times out of ten when this happens with no warning, it's not a hosting problem at all. It's ICANN's WHOIS verification rule, and your registrar just switched your domain off because of it.

Symptom: what an ICANN suspension actually looks like

This one gets misdiagnosed constantly because it doesn't look like a typical outage:

• The domain resolves to a registrar "account suspended" or "pending verification" page instead of your site — not a parking page, not a 404
• Outbound and inbound email for the domain stops working, even though MX records haven't changed
• Your hosting account, cPanel, and files are all completely untouched — nothing changed on the server side
• A WHOIS lookup shows the domain status as clientHold or similar, not expired

Run a quick check to confirm it's this and not something else:

whois yourdomain.com | grep -i status

If you see clientHold, that's the registrar-applied hold, and it's almost always tied to unverified WHOIS contact info. If you see redemptionPeriod or pendingDelete instead, that's a different problem — an actual expiry — and you'd want our domain expiry recovery guide instead.

Cause: why ICANN forces this on every registrar

This isn't a Getwebup policy or a random registrar quirk. Under ICANN's 2013 Registrar Accreditation Agreement (RAA), every accredited registrar — GoDaddy, Namecheap, BigRock, Google Domains' successor, us, all of them — is contractually required to verify the email address listed as the domain's registrant (or admin) contact.

The rule triggers a fresh verification request whenever any of the following happens:

• You register a brand-new domain
• You transfer a domain in from another registrar
• You edit the WHOIS contact email on an existing domain, even by one character
• The registrar itself does a bulk re-verification sweep (rare, but it happens after data migrations)

The registrar sends an email to that contact address with a confirmation link. Per ICANN's rule, if nobody clicks it within 15 calendar days, the registrar is required to suspend the domain — not just the website, the whole domain, including DNS resolution and mail. This isn't optional on the registrar's end; failing to enforce it puts their own ICANN accreditation at risk, so there's no goodwill exception to ask for.

Why people miss the email

In practice, three things cause almost every case:

• The verification email lands in spam. It's a transactional email from a registrar's automated system, and spam filters are twitchy about those.
• The WHOIS contact email is stale. Common with agency-built sites — the domain is still registered under a freelancer's or a former employee's inbox nobody checks anymore.
• WHOIS privacy is on, but the forwarding address behind it changed. Privacy proxy services forward the verification email to a real inbox — if that forwarding target is outdated, the click-through never happens.

Fix: get the domain reactivated

Step 1 — Log in to the registrar, not your hosting panel

This is a registrar-level hold, so cPanel/WHM won't show anything wrong, and there's nothing to fix there. Log in to wherever the domain is actually registered and look for a banner or notice about "pending verification" or "WHOIS confirmation required." Most registrars surface it prominently on the domain's overview page once you're in.

Step 2 — Confirm and correct the WHOIS contact email

Before resending anything, check what email address is actually on file. If it's wrong, outdated, or belongs to someone who's left, update it to an inbox your team actively monitors first — otherwise you'll just repeat this whole cycle.

Step 3 — Resend the verification email and check spam immediately

Registrars almost always have a "Resend verification email" button once you've fixed the contact address. Send it, then check spam/junk/promotions folders within a few minutes — most of these are near-instant.

Step 4 — Click the link and confirm reactivation

The email contains a confirmation link, usually valid for a limited window again, so don't sit on it. Once clicked, most registrars lift the hold within minutes to a couple of hours. DNS resolution and mail typically come back without you touching anything else — no need to re-save DNS records or restart services.

Step 5 — If you can't get into the registrar account at all

If the account's own login email is the one that's dead (former employee, expired domain used as the account recovery address), you'll need the registrar's account-recovery process, which usually asks for the account holder's ID, the domain's payment history, or WHOIS history as proof of ownership. This takes longer — plan for 24-72 hours depending on the registrar — so open a support ticket the moment you suspect this rather than waiting to confirm it first.

Where to find the resend option, by registrar

Prevention: don't get held again

• Whitelist your registrar's sending domain in your email client so verification and renewal emails never land in spam.
• Keep the WHOIS contact email pointed at a shared inbox your team actually monitors, not a single person's address — especially for agency-managed domains.
• Whenever you edit WHOIS contact info, expect a new verification email and go click it immediately rather than assuming it's routine.
• If you use WHOIS privacy, verify the forwarding address behind it after any change to your contact details — the proxy only forwards correctly if that target is current.
• Add a calendar reminder to audit domain contact emails yearly, particularly if staff or freelancers who originally registered domains have since moved on.

The good news is that unlike an actual expiry, this doesn't cost anything to fix and doesn't put the domain at risk of being grabbed by someone else — it's purely a compliance hold, and it lifts as soon as the email gets confirmed. The annoying part is just how invisible the cause is until you know to check WHOIS status instead of assuming it's a hosting or DNS issue.