Know Where Your Aadhar Card Used Till Now : Aadhar Card Authentication History Check

How to know Aadhaar Authentication History?

In this article, you will find the history of your aadhaar card usage. You will find time and place where and when your eaadhaar or hard copy of aadhaar has been used.

You will also get solution of error codes which appears during aadhaar authentication history checking.

 

What is Aadhaar card?

Aadhaar card is a very essential document for Indian citizen. Nowadays aadhaar card compulsory for service like New Pan card registration, Passport, SIM card service aadhaar card also mandatory for different government shame.

Aadhaar card is 12-digit unique identification number for all the residents of India. Aadhaar number is provided by Unique Identification Authority of India (UIDAI) which is a statutory authority established on 12 July 2016 by the Government of India under the jurisdiction of the Ministry of Electronics and Information Technology. 12- digit unique number link with ten fingerprints and two iris scans, basic information like address, date of Birth, Photograph. All data kept safe in the centralised database.

A number of features make aadhaar digital identification like QR Code and Document of the card itself is electronic in PDF format.

know when aadhaar was used authentication

How to know EAadhaar Authentication History & Error Codes?

For Indian citizen nowadays aadhaar number is a very important document for PAN card, Passport Seva, driving license, Insurance policy, Bank account. All Personal information contains the Aadhaar card and aadhaar card linked with different service Insurance, Bank, mobile sim card and many other. We all use a number of time aadhaar authentication in a different service. it is very difficult to track all authentication through made by us. So, UIDAI provides authentication facility with different modes such as demographic, biometric (fingerprint or iris) or One Time Password (OTP). Auth Modality shows the mode of authentication used to perform that specific authentication transaction.

Below are the UIDAI services which are used by Aadhaar number holder to perform Aadhaar Authentication:

 

How to Check Aadhaar Authentication History? / How to know where your aadhar card has been used?

  • Step 1: open official website of https://www.uidai.gov.in/
  • Step 2: Click on Aadhaar Authentication History. After click on aadhaar Authentication history, you can find below screen

aadhaar authentication history

 

  • Step 3: Enter Aadhaar number and security code and click on send OTP,  you can receive OTP on the register mobile number of your aadhaar number. after enter OTP find an option as below.

where my aadhaar card has been used

 

  • Step 4: you have to select an option like authentication type, Date range, Number of Records and enter your OTP received on your mobile which is valid for 30 min. you can find the Authentication &  UNA: Aadhaar History on your screen.
  • If the listed authentication transaction is not performed by the E Aadhaar number holder, the resident may contact the respective Authentication User Agency (AUA) for further details.

If you find any error code in history you can see the error history

 

List Of Error Codes And Their Meaning In Aadhaar Card Authentication History

  • “100” – Personal information demographic data did not match.
  • “200” – Personal address demographic data did not match.
  • “300” – Biometric data did not match.
  • “310” – Duplicate fingers used.
  • “311” – Duplicate Irises used.
  • “312” – FMR and FIR cannot be used in same transaction.
  • “313” – Single FIR record contains more than one finger.
  • “314” – Number of FMR/FIR should not exceed 10.
  • “315” – Number of IIR should not exceed 2.
  • “316” – Number of FID should not exceed 1.
  • “330” – Biometrics locked by Aadhaar holder.
  • “400” – Invalid OTP value.
  • “402” – “txn” value did not match with “txn” value used in Request OTP API.
  • “500” – Invalid encryption of session key.
  • “501” – Invalid certificate identifier in “ci” attribute of “Skey”.
  • “502” – Invalid encryption of PID.
  • “503” – Invalid encryption of Hmac.
  • “504” – Session key re-initiation required due to expiry or key out of sync.
  • “505” – Synchronized Key usage not allowed for the AUA.
  • “510” – Invalid Auth XML format.
  • “511” – Invalid PID XML format.
  • “512” – Invalid Aadhaar holder consent in “rc” attribute of “Auth”.
  • “520” – Invalid “tid” value.
  • “521” – Invalid “dc” code under Meta tag.
  • “524” – Invalid “mi” code under Meta tag.
  • “527” – Invalid “mc” code under Meta tag.
  • “530” – Invalid authenticator code.
  • “540” – Invalid Auth XML version.
  • “541” – Invalid PID XML version.
  • “542” – AUA not authorized for ASA. This error will be returned if AUA and ASA do not have linking in the portal.
  • “543” – Sub-AUA not associated with “AUA”. This error will be returned if Sub-AUA specified in “sa” attribute is not added as “Sub-AUA” in portal.
  • “550” – Invalid “Uses” element attributes.
  • “551” – Invalid “tid” value.
  • “553” – Registered devices currently not supported. This feature is being implemented in a phased manner.
  • “554” – Public devices are not allowed to be used.
  • “555” – rdsId is invalid and not part of certification registry.
  • “556” – rdsVer is invalid and not part of certification registry.
  • “557” – dpId is invalid and not part of certification registry.
  • “558” – Invalid dih.
  • “559” – Device Certificate has expired.
  • “560” – DP Master Certificate has expired.
  • “561” – Request expired (“Pid->ts” value is older than N hours where N is a configured threshold in authentication server).
  • “562” – Timestamp value is future time (value specified “Pid->ts” is ahead of authentication server time beyond acceptable threshold).
  • “563” – Duplicate request (this error occurs when exactly same authentication request was re-sent by AUA).
  • “564” – HMAC Validation failed.
  • “565” – AUA license has expired.
  • “566” – Invalid non-decryptable license key.
  • “567” – Invalid input (this error occurs when unsupported characters were found in Indian language values, “lname” or “lav”).
  • “568” – Unsupported Language.
  • “569” – Digital signature verification failed (means that authentication request XML was modified after it was signed).
  • “570” – Invalid key info in digital signature (this means that certificate used for signing the authentication request is not valid – it is either expired, or does not belong to the AUA or is not created by a well-known Certification Authority).
  • “571” – PIN requires reset.
  • “572” – Invalid biometric position.
  • “573” – Pi usage not allowed as per license.
  • “574”– Pa usage not allowed as per license.
  • “575”– Pfa usage not allowed as per license.
  • “576” – FMR usage not allowed as per license.
  • “577” – FIR usage not allowed as per license.
  • “578” – IIR usage not allowed as per license.
  • “579” – OTP usage not allowed as per license.
  • “580” – PIN usage not allowed as per license.
  • “581” – Fuzzy matching usage not allowed as per license.
  • “582” – Local language usage not allowed as per license.
  • “586” – FID usage not allowed as per license. This feature is being implemented in a phased manner.
  • “587” – Name space not allowed.
  • “588” – Registered device not allowed as per license.
  • “590” – Public device not allowed as per license.
  • “710” – Missing “Pi” data as specified in “Uses”.
  • “720” – Missing “Pa” data as specified in “Uses”.
  • “721” – Missing “Pfa” data as specified in “Uses”.
  • “730” – Missing PIN data as specified in “Uses”.
  • “740” – Missing OTP data as specified in “Uses”.
  • “800” – Invalid biometric data.
  • “810” – Missing biometric data as specified in “Uses”.
  • “811” – Missing biometric data in CIDR for the given Aadhaar number.
  • “812” – Aadhaar holder has not done “Best Finger Detection”. Application should initiate BFD to help Aadhaar holder identify their best fingers.
  • “820” – Missing or empty value for “bt” attribute in “Uses” element.
  • “821” – Invalid value in the “bt” attribute of “Uses” element.
  • “822” – Invalid value in the “bs” attribute of “Bio” element within “Pid”.
  • “901” – No authentication data found in the request (this corresponds to a scenario wherein none of the auth data – Demo, Pv, or Bios – is present).
  • “902” – Invalid “dob” value in the “Pi” element (this corresponds to a scenarios wherein “dob” attribute is not of the format “YYYY” or “YYYYMM-DD”, or the age is not in valid range).
  • “910” – Invalid “mv” value in the “Pi” element.
  • “911” – Invalid “mv” value in the “Pfa” element.
  • “912” – Invalid “ms” value.
  • “913” – Both “Pa” and “Pfa” are present in the authentication request (Pa and Pfa are mutually exclusive).
  • “930 to 939” – Technical error that are internal to authentication server.
  • “940” – Unauthorized ASA channel.
  • “941” – Unspecified ASA channel.
  • “950” – OTP store related technical error.
  • “951” – Biometric lock related technical error.
  • “980” – Unsupported option.
  • “995” – Aadhaar suspended by competent authority.
  • “996” – Aadhaar cancelled (Aadhaar is no in authenticable status).
  • “997” – Aadhaar suspended (Aadhaar is not in authenticatable status).
  • “998” – Invalid Aadhaar Number.
  • “999” – Unknown error.
Updated: May 7, 2019 — 12:35 pm

Leave a Reply

Your email address will not be published. Required fields are marked *