How to Find a Half Sibling From a Name and a Date of Birth
Of everything a person can arrive with on a sibling search, this is the strongest pair. A full name narrows a country to a few hundred people; a date of birth narrows those few hundred to one. Which means you are in a different position from almost everyone else reading about this subject. You are not trying to work out who your sibling is. You are trying to confirm that a particular living human being is the person your two fields describe — and then find out where they are now. That is a verification problem, not a discovery problem, and it has exactly one serious failure mode.
The Short Version
A date of birth locates nobody. It appears on no mailbox and in no phone listing, and it will never tell you which town anyone lives in. What it does is tell two people apart. Paired with a name it becomes close to a unique key, which is why it is the field that confirms an identification rather than the field that produces one — and why the whole search turns on the date being right. It very often is not. Dates that reach people through a relative’s memory, an old form, an agency summary or a line of adoption paperwork are routinely off by a day, by two transposed digits, or by a year. And a wrong date does not announce itself: an exact-match query returns a clean, confident, empty result that is visually identical to proof that no such person was ever born. So the method is to stop querying a date and start searching a range, which is how a records office searches anyway. Bring the name, the date as you have it, a state if you have one, and a subject inside the United States. We verify the identity, close the distance to a current address, and come back usually within 24 hours — and what the person on the other end wants is theirs to decide, not ours and not yours.
Watch: Verifying a Person From a Name and a Date
A Date of Birth Finds Nobody. It Tells Two People Apart.
Understanding what the field is for decides every move that follows.
Names are ambiguous and dates are not, and that asymmetry is the whole reason this pair works. A surname puts you inside a family; a given name and a surname put you inside a crowd; a date of birth reaches into that crowd and picks out one person, because two people who share a name only rarely share the day as well. The date does no finding whatever. It does all of the distinguishing.
So the order of work reverses. You do not search for a date; you search for a name, produce candidates, and apply the date to them one at a time. Typing a date into a search box and hoping a person falls out asks a question no index is built to answer, and the searcher concludes the records are useless when what failed was the direction of travel.
It also explains why the pair is treated as sensitive: together these two fields are what a stranger needs to pass for you at a counter. That is a separate subject with its own page — what someone can actually do with your name and birthday is written for the person guarding these fields, not the person using them. Nothing here defeats an identity check; it matches one documentary record to another.
What Makes This Servable, and What Does Not
A full name with a date of birth is a real identifier, and a state makes it faster because vital records are filed locally with no national index above them. The subject has to be inside the United States. Not yet a case: a first name with a birthday, an age with no name, a date attached to a nickname from a story. Better to read that here than wait on a reply that says it.
Four companion pages start from different clues and carry methods this one does not — our marriage-record page reads parentage fields on a licence application, our maiden-name page runs a mother’s birth name downward, our relative’s-name page works sideways from an aunt or a cousin, and our common-name page handles a name thousands of people carry. If a test result brought you here, the shared-DNA side belongs to reading a match in the half-sibling range and no genetic figure is printed on this page.
How Wrong Is the Date, and What Does That Cost You
A graded taxonomy rather than a record list. Read the third column – the damage a discrepancy does is not proportional to its size, and the smallest error on this table is the most expensive.
| The discrepancy | Commonest innocent cause | What it does to an exact-match search | The move that recovers it |
|---|---|---|---|
| Day and month exchanged | A date copied across a form whose fields ran in the other order, or written by somebody using a different convention. | Returns nothing — while the correct record sits under a date whose digits you have already typed. | Run the mirror date as a second query before anything wider. One extra search, and it clears a whole class of error. |
| Out by a day or two | The paperwork was completed the next morning, or the birth fell either side of midnight and two documents disagree. | Returns nothing, and the near neighbour is never surfaced or suggested. | A same-week band. Cheap, fast, and it resolves a surprising share of apparently missing people. |
| Out by one year | An age was converted to a birth year against the wrong month, or a school year was mistaken for a birth year. | The dangerous one. It can return nothing, or return a real person with the right name born in the year you guessed. | Search the year, the year before and the year after as three separate queries, and keep any candidate from each rather than picking. |
| Right day and month, wrong decade | A single mistyped or misread digit, most often in a handwritten source transcribed decades later. | Frequently returns a plausible stranger, which is worse than returning nothing because it terminates the search. | Hold the month and day fixed and sweep the decade. Then confirm on a second field that has nothing to do with the date. |
| A placeholder date | A system demanded a full date when only a month or a year was known, so the first of the month or the first of January was entered. | Matches an enormous number of people and looks like a strong hit. | Treat a first-of-January date as a year, never as a date, and never as corroboration of anything. |
| No error at all, and still nothing | The index does not cover those years, does not expose a date column, or the birth was registered in a state nobody mentioned. | Identical on screen to every row above it, which is why the date gets blamed and re-searched for weeks. | Stop changing the date and change the jurisdiction. Establish what the index actually contains before you widen it again. |
The pattern in the third column is the thing to take away: a large error usually returns nothing and a small one sometimes returns somebody. Nothing is recoverable, because you keep working. A plausible stranger is not, because you stop. So the discipline is to distrust a comfortable single hit at least as much as an empty result — and to confirm every date match on a field that was not derived from the date.
The Date You Were Given Is Probably a Little Bit Wrong
How far you should widen is set by who handed you the date, not by how sure they sounded.
Almost nobody reading this got their date from a certificate, and the provenance of a date predicts its drift far better than the confidence of the person who said it. There is a ladder. At the top is the registered record itself, made at the event by somebody whose job it was. Below that, a document made near the event for another purpose — a baptism entry, a school enrolment, an old insurance form. Below that, a form somebody filled in from a document, which is where transcription enters. Below that, an agency summary written from a file the writer was deliberately paraphrasing; if that is your source, what an adoptee’s file typically contains is worth reading for what those documents fix and what they do not. And at the bottom, a person’s memory, which is usually right about the season and the story and unreliable about the digits.
Write down which rung your date came off, because that is the number that should set the width of your first search — not your patience, and not how certain the source sounded. A date two rungs down does not become firmer because you have been carrying it for thirty years.
The reason any of this matters is that a nearly-right date is the worst possible input to an exact-match query. The system does not hesitate, flag anything or offer a near neighbour. It returns nothing, instantly, and nothing looks identical whether the person was never born, was born in another state, or was born on the Wednesday rather than the Tuesday. A negative result is not a negative finding. Treat every empty return as unproven until the date has been widened, and you avoid the commonest way this search is abandoned one day short of the answer.
Four Ways a Verification Goes Wrong Without the Date Being Wrong
Everything above assumes the date is the problem. These four are what happens when it is not.
The date came from the file you are testing
Reading a birth date off an aggregator and then using it to filter that same aggregator is one measurement counted twice. It feels like corroboration and adds nothing. Note where each fact came from and refuse to let a source confirm itself.
The middle name went missing
The name half of your key is weaker than it looks. Indexes keyed on first and last name silently discard the middle name, the suffix and the initial — which is exactly the field that would have separated a father from his son on the same street.
One matching pair, checked once
A single name-and-date agreement is a hypothesis. It becomes an identification when a second, independent field agrees: a place of birth, a parent, a document that existed before any of the files you searched. One key, checked twice, in two places.
You asked for a date instead of a search
Hand a clerk an exact date and you get one exact lookup. Say the date is approximate, give the range and explain why, and you get the search their office is actually set up to perform. The wording of the request decides the result more often than the record does.
Search a Range, Because the Records Office Already Does
The unit of a real records search is a span of years, not a date – and it is written into the statute.
You think in dates. A vital-records office thinks in searches, and a search has a width. Closing that mismatch is most of the practical advice on this page.
Illinois writes the width into its fee provision, which makes it a clean illustration of the shape even though it is one state’s rule and yours will differ. Under 410 ILCS 535/25, the State Registrar “shall search the files of birth, death, and fetal death records, upon receipt of a written request and a fee of … from any applicant entitled to such search” — a search, note, as a service distinct from a copy. The same section then prices index work by span: a request to a custodian “for a search of the death record indexes for genealogical research shall require a fee of … per name for a 5-year search,” with “[a]n additional fee of … for each additional year searched.” That sentence is about the death indexes specifically and should not be carried across to births as though it were a rule. What travels is the idea it exposes: the native unit is a name plus a band of years, and widening the band is a normal, priced request rather than an admission of ignorance.
So say it when you write. “On or about the fourteenth of March 1968, possibly 1967 or 1969” gets a range search; a bare date gets one lookup and a form letter. Widen in steps rather than all at once, and write down each attempt with its result, because on a search this shape the value accumulates in what you have ruled out.
Establish one thing before you spend anything: whether the index is open to you. It is not automatic. Under 410 ILCS 535/24(1), access to Illinois vital records “and indexes thereof” is limited to the custodian and their employees for administrative purposes, “except that the indexes of those records … originating prior to January 1, 1916, shall be made available to persons for the purpose of genealogical research.” An open index and a closed one look identical from outside, and what you may order when you are not immediate family is the question to settle first.
Why the Record Shows a Year and Not a Date
A cross-check that comes back with only a birth year has not contradicted you.
Sooner or later your candidate turns up in a court file and the birth information there is four digits. That is not carelessness and it is not a different person. Under Fed. R. Civ. P. 5.2(a), unless the court orders otherwise, a federal filing containing “an individual’s social-security number, taxpayer-identification number, or birth date” may include “only … the year of the individual’s birth.” The date is not withheld because it is secret; it is redacted by rule, at the point of filing, on every federal docket in the country. A year-only entry is consistent with your date and cannot confirm it — and reading it as a contradiction is a mistake people make in both directions.
The useful half is the carve-out. That same rule exempts “the official record of a state-court proceeding,” which is where most of ordinary life is litigated: probate, family matters, collections, small claims. So the document class most likely to carry a full date of birth is a state court file and the class guaranteed not to is a federal one, which is worth knowing before you spend a week on the wrong docket. It also answers the question people ask about their own date. It is not confidential the way a Social Security number is, nor open the way a name is; its exposure is decided one record class at a time.
Absence From a Death Index Is Not Proof of Life
The one gap a name-and-date check cannot see into, and it is the most recent three years.
A verification pass includes a death check, because everything downstream changes if the answer is yes, and this is where the two fields are at their most powerful: a death index matched on both is about as close to conclusive as record-matching gets.
But a clean result has a blind spot with a statutory edge to it. 42 U.S.C. § 1306c(a) provides that the Secretary of Commerce “shall not disclose to any person information contained on the Death Master File with respect to any deceased individual at any time during the 3-calendar-year period beginning on the date of the individual’s death, unless such person is certified under the program established under subsection (b).” The certification programme in (b) turns on a certified “legitimate fraud prevention interest” or a “legitimate business purpose pursuant to a law” — a fraud-control gate rather than a research one.
The consequence is precise and easy to miss. A recent death is invisible in that source by design, so an absence there is evidence of life for older deaths and almost none for the last three years. The answer is not to press that file harder but to go around it, to what a death generates locally — a county certificate, a published notice, a probate opening — and the ways a death actually surfaces in the record sets those out. It is a grim paragraph on a page about finding family, and leaving it out would be worse: people have spent years searching for someone who died in the interval, never told the gap existed.
A Matching Date Proves Identity. It Never Proves Kinship.
What we do with a confirmed person, what we refuse, and who has the last word.
Hold the two claims apart, because collapsing them is the quiet error at the end of a successful search. Confirming that the living Margaret Ellis in Toledo is the Margaret Ellis born on your date establishes who she is, and nothing at all about whether she is your sister. Identity comes from the name-and-date match; relationship comes from parentage on a document, or from biology, and neither of those is a birthday. Where the date arrived with the relationship attached — someone said “your brother, born then” — the relationship rests on that person’s say-so, and it should be labelled that way in your notes until a record or a test says otherwise.
The rest is distance. A confirmed identity is not a mailing address, and what separates them is ordinary public-records work: the name run forward across the paper an adult life deposits, every candidate address dated, and each one tested against the others until a single current one holds and the rest are accounted for. That is what our skip tracing work does. It is also precisely where a family-history subscription stops.
Two refusals, stated here rather than buried. A name and an exact date of birth is the most efficient pair anyone can use to find a person who moved in order not to be found, and that is precisely why this page will not help with it. Where the purpose of a request looks like reaching someone shielded by a protective order, or someone who relocated after abuse or stalking, we decline it, and a family relationship does not change the answer — it is frequently the reason for it. If you are the person being looked for: nearly every state runs an address confidentiality programme, Safe at Home being the best known, under which a substitute address stands in for yours on public filings, and the court that issued your order commands records access and sanctions no private party has. Those doors are the right ones and they work.
The second refusal is gentler and applies far more often. We make no approach on your behalf, we do not turn up, and the person located learns nothing about you from us. Somebody found this way may not know you exist, may not know they were adopted, and may be learning both facts in the same minute. Finding a person creates no entitlement to their attention, and a refusal is a right being exercised, not an obstacle. We stop at the address; the first move toward the person is yours and it should be a letter. Where it is that letter and not the paperwork keeping you awake, the guide to a sibling you never knew existed was written for exactly that.
How the Search Runs
From two fields to a verified living person.
Send the Pair and Its Provenance
The name in every spelling you have heard, the date exactly as you hold it, and where the date came from — a document, a relative, an agency summary. Provenance sets the width of the first search and we will tell you what it implies.
We Build Candidates From the Name
Same-name individuals assembled from records rather than from one index, before the date is applied to anybody. Running it in this order is what stops a near-miss date deleting the answer at step one.
We Apply the Date as a Range
The exact date first, then the mirror, then the widening bands, each attempt and each result recorded. Candidates are eliminated against documents and every surviving one is carried forward rather than chosen between.
You Receive a Person and a Choice
A current verified name and address, the records the identification rests on, and a plain note on anything the paperwork left unsettled. What you do next is yours. What they do next is theirs.
Who Arrives Holding a Name and a Date
Different rooms, the same two fields.
Adoptees
A non-identifying summary or an amended record gave a name and a birth date, and the date on agency paperwork is the one most likely to have drifted.
Late Discoverers
A parent died and a letter, a photograph or a solicitor’s file named a person and a birthday nobody had ever mentioned.
People Told by a Relative
Somebody finally said it out loud, with a date attached. The name and the date are both real and both come from one person’s memory.
Donor-Conceived Adults
A clinic file or a registry entry produced a name and a date of birth and nothing else that identifies anybody.
Older Siblings Looking Down
You remember the year and the season, and a family paper turned up with an exact date on it decades later.
Administrators and Heirs
An estate needs a half sibling identified rather than assumed, and a name with a date of birth is the pair a court expects to see matched.
Our Commitment
We treat a date of birth as something to be tested rather than trusted: the name builds the candidates, the date divides them, and a range is searched wherever the provenance says the date may have drifted. What comes back is either a living person who survives checking or a candid account of which step the records could not support and why. Families have brought us this kind of research since 2004, we take United States subjects only, and a first read usually lands within 24 hours. We never approach the person on your behalf, nothing identifying you is passed to them, and we turn down any request that reads as an attempt to reach somebody who moved for their own protection.
Frequently Asked Questions
Everything I try comes back empty. How do I tell a wrong date from a missing record?
Run a positive control, which is the single most useful habit on a search of this shape and almost nobody does it. Pick somebody you already know is in that index in those years — yourself, a parent, a relative whose certificate you hold — and search for them the same way, through the same interface, with the same fields filled in. If the control comes back and your subject does not, the tool works and the problem is your date or your jurisdiction. If the control comes back empty too, you have been testing the index rather than the person, and no amount of widening the date will fix it. Never accept a negative until you can name the index, the years it actually covers, and a control that returned.
Is a date of birth confidential information?
It is neither a secret nor a public fact; its exposure is decided one record class at a time, which is why the same date can be redacted in one file and printed in another. In federal court, Fed. R. Civ. P. 5.2(a) permits a filing that contains a birth date to include only the year of the individual’s birth unless the court orders otherwise — but the same rule exempts the official record of a state-court proceeding, where full dates commonly appear. Vital records go their own way again: as an example of one state’s approach, 410 ILCS 535/24(1) limits access to Illinois vital records and their indexes to the custodian, opening only pre-1916 indexes for genealogical research. Other states differ, sometimes sharply.
The name is spelled two different ways and the date is identical. Is that one person?
Probably, and the date is why you can say so. Spelling is the unstable half of your key — it changes with a clerk’s ear, an anglicisation, a marriage, a transcription from handwriting — while a date of birth is the same string on every document a person ever generates. Two records with a full date in common and a surname one letter apart are far likelier to be one person than two. Test it the same way you would test anything else: find a third document that carries both the variant spelling and something the first two also assert, such as a place of birth or a parent’s name.
I have the name and the date but no idea which state. Can you still run it?
Yes, and it is worth saying so because people hold back for months over exactly this. A name and a full date of birth is enough to start; a state makes it faster and cheaper, and its absence changes the sequence rather than the outcome. Without a state the work begins with national-scope records that carry a date — the paper an adult life leaves across many jurisdictions — and narrows to a state before it touches a vital record, because that is the point at which a jurisdiction has to be chosen. Anything you can add helps: a city somebody once mentioned, a school, a military connection, an employer.
My candidate matches the date exactly but was born in a county nobody in my family has ever mentioned. Which do I trust?
Trust neither yet, and stop treating them as competing claims. A birth county your family never mentioned is unremarkable — people cross a state line for a hospital, a pregnancy is spent with relatives, a birth happens away from home. What it does mean is that your date match is now the only thing holding the identification up, and a single field is not enough to carry one. Get a second, independent point of agreement before you accept it, and note that the county itself is testable: whoever was living there at the time is a question the records can answer.
Could two different people genuinely share my sibling's name and date of birth?
Yes. It is uncommon and it is not rare enough to design a search around ignoring, and the risk climbs steeply with a common surname, a popular given name of that generation, and a large metropolitan county. The practical consequence is not to abandon the method but to refuse to stop at one confirmation: two people can share a name and a date, and they will not also share a place of birth, a parent, an address history and a middle name. When two live candidates both survive the date test, that is a finding in itself and the next step is a field that predates every file you have searched.
My sibling was adopted. Is the date on my paperwork the date on their current records?
Usually yes for the date itself, which is the reassuring part — an adoption generally changes the name and the parents on the operative record rather than the day the person was born. The unreliability comes from somewhere else: the date reached you through an agency summary or a file note rather than from a certificate, and those are exactly the documents where a month becomes a month-and-a-day and a year gets transcribed twice. So carry the date forward with confidence in what it represents and scepticism about how it was written down, and search a band rather than a day.
What do you need from me, will you contact them, and how long does it take?
Send the name in every spelling anyone has used, the date exactly as you hold it, and the origin of the date — a certificate, an agency letter and an aunt’s memory are weighted very differently and we will tell you how. A state or a city helps and is not required. Subjects must be inside the United States. A first read usually comes back within 24 hours, and where the records cannot settle it you get a dated account of what was searched instead of a maybe. We make no approach on your behalf, nothing identifying you is passed to the person located, and any request that reads as an attempt to reach somebody who moved for their own protection is turned down.
Have a Name and a Birthday?
Send the pair, and tell us where the date came from. We build the candidates from the name, apply the date as a range, and come back with a verified living person — usually inside 24 hours. Contact us to get started.
Start Your Request →
