How to Resend Your Domain Verification Email Print

  • 0

Resend the verification email for your domain — self-service, no ticket required

When you register a new domain through Adaptive Web Hosting, ICANN regulations require you to verify the registrant email address within 15 days. If you missed the email or accidentally deleted it, you can resend the verification email yourself directly from your client area — no support ticket needed.


Quick reference: what the badges mean

On the Domains → My Domains page in your client area, each domain registered through us is tagged with one of two badges:

✓ Verified Your registrant email has been verified. ICANN compliance is met and DNS resolution is unaffected. No action required.
⚠ Verification Required Your registrant email has not been verified yet, or the registry has placed your domain on hold. DNS may not resolve until verification is completed.

Domains registered with a different provider do not get a badge — verification for those is handled by whichever registrar holds the registration.


When to use the resend button

You should resend the verification email if any of the following are true:

  • You see the ⚠ Verification Required badge on a domain in your client area.
  • Your domain is showing as "not resolving" or "unreachable" and you registered it within the past month or two.
  • You never received the original verification email, or it was deleted before you could click the link.
  • The verification link in the original email has expired.

Step-by-step instructions

Step 1 — Sign in to your client area

Go to cp.adaptivewebhosting.com and log in with your Adaptive Web Hosting credentials.

Step 2 — Open the domain that needs verification

From the top menu, click Domains → My Domains. Find the row with the ⚠ Verification Required badge and click anywhere on that row to open the Domain Management page.

Step 3 — Click the Resend button

A yellow alert card appears at the top of the Overview tab with the heading "Domain verification required" and a Resend Verification Email button. Click that button.

Within a few seconds you will see a green confirmation: "We have resent the verification email to the registrant address on file..."

Step 4 — Check your inbox

Open your email inbox — including the spam / junk folder — and look for an email from [email protected]. The subject line usually starts with "Verification Required" or similar.

Click the verification link inside the email and follow the on-screen instructions. The link is usually valid for several days.

Step 5 — Wait for the badge to update

Once the registry confirms your email, the verification hold is released. The badge on your Domains list updates from ⚠ Verification Required to ✓ Verified. DNS resolution typically resumes within a few hours, though it can occasionally take longer depending on DNS propagation.


What if I do not see the button?

The Resend button only appears when your domain actually needs verification. If your domain shows ✓ Verified, the alert and button do not appear because no resend is needed.

  • Already verified: If DNS still does not resolve, the cause is something other than verification — see Troubleshooting Domain and DNS Issues.
  • Domain registered elsewhere: If you registered your domain with another provider (and only host with us), there will be no badge or button on the domain row — you must resend the verification through whichever registrar holds the registration.

How often can I use the button?

To prevent accidentally spamming yourself, the resend button is limited to 3 requests per hour per customer. If you need more than that within an hour, please open a support ticket — there is likely a deeper issue (incorrect registrant address on file, etc.) that we need to resolve manually.

The button is not working — what now?

If you click the button and see an error message, please open a support ticket and include:

  • The exact error message shown on the page.
  • The domain name you are trying to verify.
  • The date and time you tried.

Our team will manually trigger the resend or investigate why the automated one failed.


Related articles


Was this answer helpful?

« Back