Trust and information

Methodology

The data model, letter mappings, date formulas, chart calculations, compatibility weights, correction rules, and uncertainty limits behind NameByStars.

Last reviewed: 17 September 2026

Canonical name data and aliases

Each canonical record can store a URL slug, native script, transliteration, pronunciation, gender usage, languages, regions, cultural or locale context, origin, meaning, etymology, variants, related names, styles, starting character, syllable count, source provenance, research tier, and computed number values.

The curated tier is reviewed record by record. The reference tier is compiled into this file from locale-specific first-name provider lists under their included MIT notice; runtime deployment does not require that source package. Reference-tier pages treat spelling, locale, and provider gender grouping as source data, while meaning, etymology, and pronunciation remain visibly unverified. Search indexes normalized canonical spellings, native scripts, variants, and transliterations once at startup. Unique aliases resolve to the canonical record, and deterministic slug suffixes prevent collisions.

Numerology mappings

Pythagorean numerology maps A through Z cyclically to 1 through 9. It separately calculates the full Expression total, vowels for Soul Urge, and consonants for Personality. Chaldean mapping uses the common groups 1: A I J Q Y; 2: B K R; 3: C G L S; 4: D M T; 5: E H N X; 6: U V W; 7: O Z; and 8: F P.

The full total is retained as a compound number before reduction. Master numbers 11, 22, and 33 are preserved where the selected formula calls for them. Compound interpretations are labeled as interpretive traditions, not facts about a person.

Hebrew characters may use a Gematria value table and Arabic characters may use an Abjad table. These script-specific values are not treated as interchangeable with Latin mappings. Other scripts are not blindly transliterated unless a canonical, visible transliteration is available and the result says that it was used.

Date-based numbers and Lo Shu grid

Life Path reduces all digits in the ISO birth date while preserving recognized master numbers. Birth Number reduces the day of month; Birthday Number can preserve a master day. Personal Year combines the birth month, birth day, and current year; Personal Month adds the calendar month.

The Lo Shu display counts non-zero digits in DDMMYYYY, then reports missing and repeated digits. The display is an interpretive date-grid convention and never describes a missing digit as a medical, intellectual, or moral defect.

Astronomical and astrology calculations

The application loads packaged JPL DE421 ephemeris data through Skyfield when available. It derives geocentric ecliptic longitudes for major bodies within supported coverage. Tropical signs use 30-degree zodiac segments. The Vedic-style view subtracts a documented Lahiri-style ayanamsha approximation and labels boundary sensitivity.

An exact birth time and resolved timezone are required for the Ascendant and house-based emphasis. Local time is converted with IANA timezone rules, including historical daylight-saving changes where the timezone database supports them. With an unknown time, midday is used only for date-level context and time-sensitive factors are withheld or warned.

Nakshatra divides the sidereal zodiac into 27 equal segments, each with four padas. Naming sounds come from the standard sound group stored for the calculated nakshatra and the primary sound follows the pada. Near a boundary, a specialist ephemeris check is sensible.

Planet strength, yogas, doshas, and dashas

The planet influence score combines selected sign dignity, angular or house emphasis when calculable, and limited chart relationships. It is a transparent NameByStars score from 0 to 100; it is not classical Shadbala and not an astronomical measurement.

Only a small rule set of commonly recognized chart patterns is reported, and only when the required positions are available. Absence from the result does not mean that no other traditional yoga or dosha exists. Vimshottari major-period dates use the Moon's nakshatra balance and are withheld when unknown time could make a boundary unreliable.

Baby-name compatibility score

Available factors can include gender usage, language, culture, first letter, excluded letters, ending, length, syllables, style, preferred meaning, nakshatra sound, Life Path relationship, Birth Number relationship, and the full-name relationship with a surname.

Each applicable factor has a fixed weight. Unavailable factors are omitted rather than assigned a random value. The weighted result is normalized to 0 through 100, and the largest positive and negative contributors become the plain-language reasons shown on the card. Identical normalized inputs produce identical scores.

Name correction and match bands

Correction candidates come from established canonical records, recorded variants, aliases, recognized transliterations, and close spellings. The model rewards pronunciation retention, small edit distance, cultural and language fit, protected letters, recognizable style, birth-number fit, and optional naming-sound fit.

Natural spelling and identity preservation take priority over reaching an artificial 100 percent. The display groups useful options into Good, Strong, Best Model Match, and Related Alternative bands. If no plausible spelling reaches the top of the model, the result says so.

Supportive life periods

For upcoming years, the model compares each Personal Year with the Life Path. When a reliable Vedic dasha timeline is available, the current major-period lord and its chart influence can adjust the score. High relative years are grouped into short ranges and accompanied by the factors that raised them.

The wording is deliberately comparative: a period may feel easier or could favor growth according to the model. It never guarantees wealth, marriage, pregnancy, recovery, investment return, or another event.

Important limitations

Astrology and numerology are not scientifically validated prediction systems. Name meanings can remain disputed. Transliteration can lose sound distinctions. Geocoding can resolve the wrong city when a place name is ambiguous. Timezone and ephemeris boundaries need extra care for historical dates or values close to a sign, house, nakshatra, or dasha boundary.

The ordinary result page therefore favors understandable explanations and visible caveats over false precision. An interested reader can use this methodology to understand exactly which kind of claim is being made.

0 names selected
Compare