From roots-in@roots-l.rootsweb.com Tue Apr 11 14:35:08 2006
Received: from mail.rootsweb.com (mail.rootsweb.com [192.168.65.34])
	by admin.rootsweb.com (8.12.8/8.12.8) with ESMTP id k3BKZ8jb029071;
	Tue, 11 Apr 2006 14:35:08 -0600
Received: from roots-l.rootsweb.com (roots-l.rootsweb.com [66.43.16.22])
	by mail.rootsweb.com (8.13.4/8.13.4) with ESMTP id k3BKZ79x028198
	for <roots-approved@rootsweb.com>; Tue, 11 Apr 2006 14:35:07 -0600
Received: from roots-l.rootsweb.com (roots-l [127.0.0.1])
	by roots-l.rootsweb.com (8.12.10/8.12.10) with ESMTP id k3BI2vFI020897
	for <roots-approved@rootsweb.com>; Tue, 11 Apr 2006 14:02:57 -0400
Received: (from roots-in@localhost)
	by roots-l.rootsweb.com (8.12.10/8.12.8/Submit) id k3BI2v3e020896
	for roots-approved@rootsweb.com; Tue, 11 Apr 2006 14:02:57 -0400
Received: from lists5.rootsweb.com (lists5.rootsweb.com [66.43.27.41])
	by roots-l.rootsweb.com (8.12.10/8.12.10) with SMTP id k3BGTFFI020594
	for <roots-in@roots-l.rootsweb.com>; Tue, 11 Apr 2006 12:29:15 -0400
Received: (from slist@localhost)
	by lists5.rootsweb.com (8.12.8/8.12.8) id k3BJ1F1s004620
	for roots-in@roots-l.rootsweb.com; Tue, 11 Apr 2006 13:01:15 -0600
X-Envelope-From: baldwinman@yahoo.com Tue Apr 11 13:01:15 2006
Received: from mail.rootsweb.com (mail.rootsweb.com [192.168.65.34])
	by admin.rootsweb.com (8.12.8/8.12.8) with ESMTP id k3BJ1Fjb004609
	for <ROOTS-L@lists5.rootsweb.com>; Tue, 11 Apr 2006 13:01:15 -0600
Received: from web30306.mail.mud.yahoo.com (web30306.mail.mud.yahoo.com [68.142.200.99])
	by mail.rootsweb.com (8.13.4/8.13.4) with SMTP id k3BJ1CiB015310
	for <ROOTS-L@rootsweb.com>; Tue, 11 Apr 2006 13:01:12 -0600
Received: (qmail 52179 invoked by uid 60001); 11 Apr 2006 19:01:07 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=1If7v2hDT0TbD9SoVv7GclbDpX/B1wgI9JpsoupQJ+h9kkhzvINYQS3vC6UBcWU+yYiHyy9uaKH74Zw5R75pcEDbUP5WXLhYflipMmNcuc45LCNctpXe13ntrHUyR1CaJ/CZosud02Ksya1k1GaJUkJ0Qpipi4iKeLISlkJ4BIU=  ;
Message-ID: <20060411190107.52177.qmail@web30306.mail.mud.yahoo.com>
Received: from [67.8.252.28] by web30306.mail.mud.yahoo.com via HTTP; Tue, 11 Apr 2006 12:01:07 PDT
Date: Tue, 11 Apr 2006 12:01:07 -0700 (PDT)
From: Baldwin <baldwinman@yahoo.com>
To: ROOTS-L@rootsweb.com
In-Reply-To: <200604111448.k3BEmI45013343@lists5.rootsweb.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
X-Spam-Score: 2.71 (**) BAYES_00,FORGED_YAHOO_RCVD
X-Scanned-By: MIMEDefang 2.52 on 192.168.65.34
X-Scanned-By: MIMEDefang 2.52 on 192.168.65.34
X-MIME-Autoconverted: from 8bit to quoted-printable by lists5.rootsweb.com id k3BJ1F1s004620
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by roots-l.rootsweb.com id k3BGTFFI020594
Sender: roots-in@roots-l.rootsweb.com
Subject: [ROOTS-L] Social Security # and geographical data

The first three digits of a Social Security # indicate which state the office the card was applied at.  Each state has its own unique groupings of this code.
   
  You then know that the person lived or had a connection to that particular state when the applied for the #.
   
  I have found a LARGE amount of information from the Social Secuirty Death Index by having a SS#. It provided birth and death dates, dates of last residence, and location last check was sent to. 
   
  I have never applied for a SS-5 report but understand it can contain a large amount of data as well including parents name, employer information amongst other.
   
  - best wishes
  stephen