नमस्कार दोस्तों जैसा की आप सभी लोग जानते हैं की आधार कार्ड अब एक ऐसा Important डॉक्यूमेंट बन गया है जिसका अगर कोई गलत इस्तेमाल करता है तो वो Victim का बहोत बड़ा नुक्सान कर सकता है और अगर कोई illegal काम करे तो victim फस भी सकता हैं और हमे लगातार ये डर लगता रहता है की कही कोई हमारे आधार कार्ड का गलत इस्तेमाल तो नहीं कर रहा हैं
लकिन अगर मैं आपसे कहू ही आप आसानी से ये पता लगा सकते हैं की पिछले कुछ समय में आपका आधार कार्ड कहाँ कहाँ Use हुआ है तो क्या आप जानना चाहोगे ?
अगर हाँ तो इस पोस्ट को अंत तक पढ़ें और आप जान पाओगे की आपका आधार कार्ड पिछले कुछ समय में कहाँ कहाँ उसे हुआ हैं .
उस से पहले हम आधार कार्ड का इस्तेमाल से सम्बंधित कुछ महत्वपूर्ण सवाल और उनके जवाब पढ़ लेते हैं (Page के Last में विडियो है उसे जरूर देखें ) :-
Aadhaar Authentication History क्या हैं ?
Table of Contents
आधार Aadhaar Authentication History वो History है जो आपके आधार कार्ड के Authentication (इस्तेमाल) का Record रखती हैं और इसे अगर आपको जानना है तो आपको UIDAI की Website में जाना होगा और वहा से आपको पता चलेगा की पिछले कुछ समय में आपका आधार कार्ड कहाँ कहाँ और किस किस चीज़ केलिए इस्तेमाल हुआ हैं .
Aadhar Authentication History कहाँ से पता चलेगी ?
आधार Authentication History जानने के लिए आपको इस लिंक को Visit करना होगा https://resident.uidai.gov.in/aadhaar-auth-history.
What is the procedure for checking Aadhaar Authentication history on UIDAI websites?
Resident can check his/her Aadhaar Authentication history from UIDAI Websites by using his/her Aadhaar Number/VID and following the directions on website.
Note: Registered mobile number is mandatory to avail this service.
What Information resident can get from Aadhaar Authentication history?
Resident can get the following information in Aadhaar Authentication history against every Authentication done by resident.
1. Auth Modality.
2. Date & Time of Authentication.
3. UIDAI Response code.
4. AUA Name
5. AUA Transaction ID (With Code)
6. Authentication Response (Success/Failure)
7. UIDAI Error code
This facility allows me to view maximum 50 authentication records. How can I check more records?
Aadhaar number holder can view details of all authentication records performed by any Authentication User Agency (AUA) or by him/her in the last 6 months. However, maximum of 50 records can be viewed at one point of time.
Some of authentication transactions records are showing as failed, what should I do?
For every failed authentication transaction record, specific error code is assigned. Please check the details of error code number against that failed authentication transaction to know the reason of failure.
If I have not performed some of the transactions listed in the records, what should I do?
If the listed authentication transaction is not performed by the Aadhaar number holder, resident may contact the respective Authentication User Agency (AUA) for further details.
What is UIDAI Response Code in the authentication records?
For every authentication transaction performed by an Aadhaar number holder, UIDAI generates a unique code to identify the transactions and sends the same to Authentication User Agency (AUA) along with the response. This Response Code is helpful to uniquely identify the transaction by AUA as well as UIDAI and may be used for any further enquiry from AUA by the Aadhaar number holder.
What is AUA Transaction ID in the authentication records?
For every authentication transaction performed by an Aadhaar number holder, AUA generates a unique Transaction ID to identify the transaction and sends the same to UIDAI as part of the authentication request. This Transaction ID along with Response Code can be used for any further enquiry from AUA by the Aadhaar number holder.
What is Auth Modality?
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.
What are the UIDAI services?
- Verify Aadhaar Number: This will enable service providers and Aadhaar number holders to verify if the Aadhaar number is valid and is not deactivated
- Verify Email/Mobile Number: This will enable service providers and Aadhaar number holders to verify if the Aadhaar number is valid and is not deactivated
- Lock/Unlock Biometrics: Aadhaar number holders can secure their biometric authentication by locking their biometrics. Once locked, same cannot be used by anyone for authentication. Residents can unlock their biometrics before any biometric authentications transaction.
- Check Aadhaar & Bank Account Linking Status : Aadhaar holders can check if their Aadhaar is linked to their bank account. Aadhaar Linking status is fetched from NPCI Server. Under any circumstance, UIDAI shall not be responsible or liable for the correctness of the displayed status. Further, UIDAI is not storing any information fetched from NPCI server. However, it may be noted that Bank account and Aadhaar linking is not mandatory as per the SC Judgment dated 26.9.2018.
- Aadhaar Authentication History : Aadhaar number holders can view the details of Aadhaar Authentication hey have done.
- Virtual ID Generator: Aadhaar Number holders can generate their 16 Digit Virtual ID (VID).
What are Error Codes? अगर आपको कोई Error मिलता है तो आप जान सकते है की उस Error Code का मतलब क्या हैं
Below are Error Code List –
“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.
What Is the Password to view Aadhaar Authentication Report?
Example 1
Name: SURESH KUMAR
Year of Birth: 1990
Password: SURE1990
Example 2
Name: SAI KUMAR
Year of Birth: 1990
Password: SAIK1990
Example 3
Name: P. KUMAR
Year of Birth: 1990
Password: P.KU1990
Example 4
Name: RIA
Year of Birth: 1990
Password: RIA1990
अगर आपको आधार कार्ड से सम्बंधित और कुछ जानना है तो आप नीचे दिए हुए Posts को पढ़ सकते हैं
Pan card को Aadhar card से link कैसे करें(mobile द्वारा) ,Check Status, आपका PAN Card, Aadhar Card से link है या नही ऐसे पता करें (Mobile से) , PAN Card, Aadhar Card से link है या नही ऐसे Check कैसे करें , How to link PAN Card to Aadhar Card (जानें हिंदी में) , Aadhar Card Online कैसे download करें , Aadhar Card Password-Why Password Required , Aadhar PVC Card- what is aadhar PVC card , Aadhar virtual id-What is aadhar virtual id , Aadhar enrollment id-What is aadhar enrollment id
Thanks
Mohit