Koncile detects tampering in PDF and image files, and documents generated or edited by AI, then returns a fraud score from 0 to 100: catch a fake birth certificate before it becomes a real ID.
Create a free account to run the analysis.
Create a free accountFor document volumes or an API, talk to an expert.
The document checker used by insurers, banks and large companies
4.8 / 5
A certified copy comes from a state, county or city vital records office. It carries the registrar's signature, the seal of the issuing authority, a filing date and the parents' names. Check those first, then the dates, then the file itself: editing traces, text laid over a scan, a PDF that never came out of a vital records system.
A birth certificate usually arrives as a scan or a photo, and a template site or an AI produces one in minutes. The fake birth certificate detector reads the file and the image first, then the required fields and the dates.
A certified copy comes out of a vital records system. A certificate filled in a word processor or a generator leaves another signature in the file: producer software, fonts, the way the PDF was written.
On a scan or a photo, K-Detect, our image analysis model, isolates the areas where the background was erased and a name or date laid on top. It also flags certificates generated in whole or in part by AI.
Registrar, seal, parents' names, birth, filing and issue dates: each certificate is read against the rules of a certified copy and matched with the ID in the same file.
Creation and modification dates, saved versions, dormant objects: a certificate edited after issue often keeps its original version inside the PDF. Koncile recovers it and shows the before and after.
Search for birth certificate verification and the first page is vital records offices. They issue certified copies. They do not look at the file a person sent you.
Each state, and in some places the county or city, keeps birth records and issues certified copies to eligible requesters, usually the person, their parents or a legal representative. Ordering a copy at the source is the safest check, when you are entitled to it and can wait for it. Most businesses are neither.
Government agencies can verify birth record data electronically with the issuing jurisdiction, through the EVVE system run by NAPHSIS, the association of state vital records offices. This is how agencies check a certificate presented for a passport or a benefit. It is not open to lenders, insurers or employers.
A business receives a PDF or a photo, sent by the person themselves. That file is what a fraudster edits, and that file is what needs checking: image editing, PDF structure, the consistency of the dates and fields. The checker on this page does that part, not the records lookup.
A birth certificate is a breeder document: it is used to obtain other documents. A fake at this step turns into real IDs later, which no document check will flag.
Birth certificates prove age and identity for a passport, a REAL ID driver's license or a state ID. A fake accepted at that step produces an authentic card in a false identity, and every check after that sees a real document.
A certified birth certificate is an acceptable List C document for Form I-9, and it is used to add a child as a dependent on health or insurance coverage. A fake one opens employment eligibility or benefits that the person does not have.
A date of birth moved by a few years changes eligibility for youth sports, school placement, age restricted services or retirement benefits. These are small edits on a real certificate, the hardest to see by eye.
The first page of Google for fake birth certificate is full of templates and makers. This page is about catching their output. Four cases come up, and each leaves different traces.
Template sites, novelty generators and PDF form fillers produce something that looks like a certificate. It never went through a vital records system: office or design software in the metadata, a seal pasted in as an image, fields typed in a generic font, no filing date or a registrar who does not exist.
The most common case: a real certified copy scanned, then a name, a date or a parent changed. The field is erased and the new value laid on top. What breaks: the security background under the new text, a font that is close but not exact, an alignment that drifts from the line.
A generative assistant produces a complete image of a certificate in minutes, from a sample or a photo of a real one. K-Detect, our image analysis model, flags images generated in whole or in part.
A genuine certificate belonging to someone else, often a deceased person or a relative, is the base of many synthetic identities. No file check can see it, since nothing was modified. Only the match with the ID and the rest of the file brings the inconsistency out.
Koncile's checker is for businesses verifying the documents they receive, never for producing one.
Without a tool, these three checks stop clumsy fakes in a few minutes. A tip: when you can, ask for a photo of the certified copy itself, not a photocopy, so the seal and the paper show.
Full name, date and place of birth, parents' full names, registrar's signature, filing date, seal of the issuing authority. A hospital record or a short abstract missing several of these is not a full certified copy.
Date of birth, filing date, issue date of the copy: they must follow each other. The date of birth must match the ID and every other document in the file, and the parents' names must match any other record you hold.
Use our free PDF metadata viewer and look at Creator, Producer and the timestamps. A certificate made in Word, Canva or an online form filler, or a file modified after its issue date, is a red flag.
Each check reads in two steps: what you can look at yourself, then what the software measures on the file. The grid is the same as for an ID document, with a fraud score from 0 to 100 justified test by test.
By eye, compare the certificate with another one from the same state and period. The software reads how the PDF was written: producer software, object order, compression. A certificate made in a word processor or a generator looks like no copy issued by a vital records system, however neat the layout.
By eye, look for a field sharper, darker or straighter than the rest. Image analysis finds the areas where the security background was erased and text laid on top, and the parts generated by AI, even after a compression that makes them invisible on screen.
A filing date before the birth, an issue date before the filing date, a date of birth that differs from the ID, a missing registrar or parent field: these inconsistencies can be checked by hand, and the software flags them on every certificate. They catch template fakes, filled in without knowing the rules.
A PDF keeps a record of its saves. A strong signal, not proof: in a test with a forensics partner, an authentic certificate came out high risk because a scanning app had resaved the file. Thresholds are now calibrated by document type and channel, and every alert comes with its justification.
No access to vital records or EVVE: the checker judges the document sent, not whether the record exists.
Koncile's fraud detection API gives you a score from 0 to 100 and detailed explanations of manipulation risks, right inside your own tools.
Names, date and place of birth, parents, registrar and dates, field by field.
High, medium or low level, with a one sentence explanation.
High risk from 80.
A one line summary ready for your information system.
curl -X POST https://api.koncile.ai/v1/upload_file \ -H "Authorization: Bearer $API_KEY" \ -F "files=@birth-certificate.pdf"requests.post("https://api.koncile.ai/v1/upload_file/", headers={"Authorization": f"Bearer {API_KEY}"}, files=[("files", open("birth-certificate.pdf", "rb"))]){ "status": "DONE", "General_fields": { "Document_type": { "value": "Certified copy of birth record", "confidence_score": 0.99 }, "Issue_date": {"value": "2026-09-14", "confidence_score": 0.96} }, "Fraud_detection": { "risk_score": 78, "summary": "Text laid over a scanned certificate, seal pasted as an image", "signals": [ {"name": "Image retouching", "severity": "high"}, {"name": "Content consistency", "severity": "medium"} ] }}Wherever a birth certificate backs up an identity, an age or a family link, a fake opens the door to a synthetic identity or a dependent who does not exist. Here is where the checker fits in.
The certificate backs up an ID, or stands in for one for a minor. It is checked with the rest of the file, and the detail of every test is kept for audit.
A certified birth certificate is a List C document for employment eligibility. The checker flags the copies that deserve a closer look before onboarding.
Beneficiaries, dependents and age based policies rely on the certificate. The check runs before a policy is issued or a claim is paid.
Adding a child as a dependent usually takes a birth certificate. The document is checked before coverage starts.
A name or a date laid on a real scan often leaves no visible error. The fake birth certificate detector relies on signals invisible to the naked eye, in the pixels of the image and in the file itself.
| Element of the certificate | What Koncile checks | What gives a fake away |
|---|---|---|
| PDF software | Creator and Producer, compared with what issuing offices produce | Word, a PDF editor or an online form filler |
| File dates | Creation and modification dates, compared with the issue date | A file modified after issue, rewritten dates |
| File structure | Saved versions, dormant objects, serialisation fingerprint | The old name or old date recovered inside the file |
| File nature | Native PDF, scan, photo or hybrid file | A certificate image pasted into a PDF to hide the original scan |
| Image and laid text | Background under each field, fonts, alignment, AI generated parts | A name laid on an erased background, a seal pasted as an image |
| Required fields | Registrar, seal, filing date, parents' names | A missing registrar or filing date, a hospital souvenir passed off as a record |
| Dates | Birth, filing and issue dates, compared with each other and with the ID | An issue date before filing, a date of birth that differs from the ID |
| External sources | Certified copy ordered from the issuing office; EVVE for government users | A record the issuing office cannot find |
A birth certificate brings together a name, a date and place of birth and the parents' names, often a mother's maiden name: the answers to many security questions. Founded by a former lawyer, Koncile was built with data protection at the core of its architecture: third party SOC 2 audit, GDPR compliance, secure hosting. Certificates are encrypted, deleted after analysis and never used to train a third party model.
Not by a business, through an official channel. Government agencies verify records electronically with the issuing jurisdiction through EVVE, and anyone eligible can order a certified copy from the vital records office. What you can do online is check the file you received: the checker at the top of this page analyses editing, template origin, fields and dates in about ten seconds.
It is issued by a state, county or city vital records office and carries the registrar's signature and the seal of the issuing authority, raised, embossed, impressed or multicolored. It shows the full name, date and place of birth, the parents' full names and the date the birth was filed with the registrar.
No. The decorative certificate many hospitals give parents, sometimes with footprints, is a souvenir. It is not a vital record and is not accepted as proof of birth. Ask for a certified copy from the vital records office.
You never know for certain: you measure a risk. It becomes high when one test goes over its threshold, or when several point the same way: text laid over the scan, a seal pasted as an image, office software in the metadata, dates that do not follow each other. That body of evidence is what should raise the alarm.
Yes, in most cases. AI produces convincing images but gets details wrong: fields in a generic font, dates that do not fit together, a seal without the texture of a real impression. Image analysis spots generated areas, and the file structure shows that the certificate never came from a vital records system.
It can help, mainly to spot inconsistent dates or missing fields. It lacks three things: models specialised in images edited or generated by AI, knowledge of the traces each editing tool leaves, and a base of what issuing offices actually produce. A language model is only one part of the machine.
Yes. Forging or using a forged birth certificate is a crime under state law, and federal charges can follow when it is used for a passport or other federal document or benefit. If you receive a fake, keep the original file, the analysis report and the date of receipt.
It depends on your volume. The price combines a base subscription and a cost per page or per document processed. The plans are detailed on the pricing page.
Yes. Koncile complies with SOC 2 and GDPR, and an independent firm certifies our security and data protection. Your documents are hosted securely with a provider that itself holds SOC 2 and ISO 27001 certifications.
Each document gets its own method: a proprietary ML model for photos, known metadata and forensics for native PDFs, and contextual cross checks.
Inflated balances, deleted lines, a PDF rewritten with software other than the bank's.
See the detection
Net pay changed, contributions that do not match gross pay, a layout that does not match the payroll software.
See the detection
Photo replaced, date of birth or number changed, an MRZ that no longer matches the fields.
See the detection
Edited amounts, wrong VAT, duplicates and made up suppliers.
See the detectionUpload your bank statements, pay stubs or IDs: Koncile extracts the data and flags fakes in seconds.
Talk to an expert
