If you are trying to activate your Ancestry DNA Account or if you already activated it and want to check your DNA account then, please follow the process below.
In case you have not activated DNA kit then please read our previous blog Ancestry DNA – Buying and Activation.
Login To Ancestry DNA Account?
Open a browser and type in url https://ancestry.com/dna. Click on sign in, sign in option is on the top right corner of this page.
You will get a window as displayed below.
Please type your email address or username and password to login in your account. You will need to make sure to use same email address or username that you have used to sign up for ancestry account. If you have forgotten or username or password, then follow the steps below to reset it.
Reset Password For Ancestry
Please click on forgot password, on next window type your email address. Ancestry will send you a code to your email, which you will need to type in next screen.
Login to your email and find the code. If you do not see email from ancestry to your inbox, then go junk/spam box.
As soon as you type the code sent by ancestry, next screen you can type your new password. Please write it down somewhere your password so you will not lose it.
Now since you have a new password, go to sign in page and login to your account.
Answer – You should contact ancestry as they can help you with retrieving your username or email address.
Answer – Please contact ancestry. They are the only company can change your email address from your ancestry DNA account.
Answer – If you entered wrong information into your ancestry account like wrong username or wrong password then you can’t get into your ancestry account.
Answer – Open your ancestry account setting page, your username will be listed there.
If you are not able to login to your ancestry DNA account, then call our support number +1-888-299-3207 and one of us will help you fix the issue for you.
Please note, we are not ancestry. We are genealogy support company where we help genealogy researcher to get their issue resolved.