Supported document type
Detect tampered and deepfake Israeli ID (Teudat Zehut)
The Teudat Zehut is Israel's compulsory national identity card, issued by the Population and Immigration Authority, and it anchors banking and fintech onboarding and doubles as the personal tax number. Its nine-digit identity number carries a Luhn-style check digit, so invented numbers fail arithmetic, and its dual Gregorian and Hebrew birth dates give a second built-in cross-check.
API slug: israel_id
Last updated:
What a genuine Israeli ID contains
The number runs nine digits, often zero-padded on the left, and the whole number must pass a Luhn-style computation in which digits are weighted alternately by one and two. It encodes no personal data, so the date of birth must be read from the card. The card carries full name, date of birth in both Gregorian and Hebrew calendars, sex, and photograph, with margins in Hebrew and Arabic and fields filled in Hebrew.
Two generations circulate: the legacy booklet-style card, and the biometric smart card mandatory for new issues from June 2017. Biometric cards last ten years, or five for holders who decline fingerprints, and old non-biometric cards expired by July 2022. An old-format card presented as current is therefore an expiry concern, and leading zeros or a Hebrew date beside the Gregorian one are normal.
How Israeli ID forgeries are made
Luhn-style check
The nine digits must satisfy the alternating one-and-two weighting with a total divisible by ten. A failing number was typed rather than issued.
Calendar agreement
The card shows date of birth in Gregorian and Hebrew form. A pair that disagrees means one date was edited.
Edition and expiry logic
The legacy booklet and the biometric card differ in layout, and old non-biometric cards expired by July 2022. An old-style card presented as current is flagged as an expiry concern.
Script and layout conformance
Margins run in Hebrew and Arabic while fields are filled in Hebrew. Fields in the wrong script or misaligned lines point to a rebuilt template.
Photo and name patching
Portrait swaps and edited name or date lines leave cut-line edges, font passes, and resolution steps that localise the substituted region.
What TamperCheck checks on an Israeli ID
TamperCheck runs 200+ forensic checks across three layers and returns a risk score from 0 to 100 with plain-English findings tied to specific regions of the document. These three carry the most weight on this document class.
Portrait substitution and face-swap analysis
The document is isolated from whatever it was photographed on, then the portrait region is assessed against the card surface around it. A pasted or generated face rarely matches the substrate it was placed onto.
Date and validity consistency
Issue, expiry, and period dates are checked against one another and against the file's own creation metadata, which catches backdating and validity extension.
Reference and document number checks
Document, account, and reference numbers are checked for issuer format conformance and against every other place the same value appears on the page.
And many more checks
The three above are the layers that carry the most weight on an Israeli ID. Every upload runs the full suite of 200+ checks regardless of document class, spanning file structure and metadata, pixel-level forensics, font and text rendering, optical and print characteristics, provenance signals, AI-generation signatures, and many more checks.
Who verifies an Israeli ID, and why
Israeli banks, fintechs, and eKYC platforms. In each case the document is being used to unlock money, access, or a legal status, which is exactly what makes it worth forging.
How to verify an Israeli ID in 4 steps
Photograph both sides
Capture the card flat at full resolution so the nine digits and both date lines survive close analysis.
Validate the number
Pad to nine digits if needed, then apply the alternating-weight computation and confirm the total is divisible by ten.
Compare the dates
Check that the Gregorian and Hebrew dates of birth agree, and that the card edition fits the date it is presented.
Run a forensic check on the file
The number carries the structural story, and the print carries the edit history. TamperCheck runs 200+ forensic checks including identity-number check-digit validation and patch detection, returning a risk score from 0 to 100 with findings tied to specific regions of the image.
Frequently asked questions
How is an Israeli ID number validated?
It has nine digits and must pass a Luhn-style computation, with digits weighted alternately by one and two and the total divisible by ten. A number that fails was not issued, whatever the print quality.
Does the number encode birth date or sex?
No. The identity number encodes no personal data, so those fields must be checked against the printed card, including the two calendar dates.
Are old Israeli ID cards still valid?
Old non-biometric cards expired by July 2022, so an old-format card shown as current is an expiry concern rather than proof of forgery. The biometric card replaced it for new issues from 2017.
How does TamperCheck verify an Israeli ID?
TamperCheck recomputes the check digit, compares the Gregorian and Hebrew dates, and inspects the name, date, and portrait regions for patching. Uploads run through a single REST endpoint, are processed ephemerally and not stored, and findings tie to specific regions.
TamperCheck analyses israeli id (teudat zehut) uploads with a hybrid forensic and AI pipeline tuned for this document class. Upload endpoints accept PDF and common image formats; class is inferred automatically. See the API documentation for authentication, async jobs, and webhooks.