From roots-in@roots-l.rootsweb.com Sat Jun 10 09:13:37 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 k5AFDbjb007223;
	Sat, 10 Jun 2006 09:13:37 -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 k5AFDC4d012347
	for <roots-approved@rootsweb.com>; Sat, 10 Jun 2006 09:13:12 -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 k5ACbRFI020929
	for <roots-approved@rootsweb.com>; Sat, 10 Jun 2006 08:37:27 -0400
Received: (from roots-in@localhost)
	by roots-l.rootsweb.com (8.12.10/8.12.8/Submit) id k5ACbRsG020928
	for roots-approved@rootsweb.com; Sat, 10 Jun 2006 08:37:27 -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 k59NGpFI019095
	for <roots-in@roots-l.rootsweb.com>; Fri, 9 Jun 2006 19:16:51 -0400
Received: (from slist@localhost)
	by lists5.rootsweb.com (8.12.8/8.12.8) id k5A1qNFQ017561
	for roots-in@roots-l.rootsweb.com; Fri, 9 Jun 2006 19:52:23 -0600
X-Envelope-From: dianmah@juno.com Fri Jun  9 19:52:23 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 k5A1qNjb017552
	for <ROOTS-L@lists5.rootsweb.com>; Fri, 9 Jun 2006 19:52:23 -0600
Received: from m23.lax.untd.com (m23.lax.untd.com [64.136.30.86])
	by mail.rootsweb.com (8.13.4/8.13.4) with SMTP id k5A1qKsc007803
	for <ROOTS-L@rootsweb.com>; Fri, 9 Jun 2006 19:52:21 -0600
Received: from m23.lax.untd.com (localhost [127.0.0.1])
	by m23.lax.untd.com with SMTP id AABCJWKP4ABJX7EJ
	for <ROOTS-L@rootsweb.com> (sender <dianmah@juno.com>);
	Fri,  9 Jun 2006 18:51:54 -0700 (PDT)
Received: (from dianmah@juno.com) 
 by m23.lax.untd.com (jqueuemail) id LSGG9ZBF; Fri, 09 Jun 2006 18:51:50 PDT
To: ROOTS-L@rootsweb.com
Date: Fri, 9 Jun 2006 20:50:48 -0500
Message-ID: <20060609.205050.3840.0.dianmah@juno.com>
X-Mailer: Juno 5.0.33
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Juno-Line-Breaks: 0-1,3-4,12-13,17-18
From: Dian Mahaney <dianmah@juno.com>
X-ContentStamp: 6:3:830027804
X-UNTD-OriginStamp: wmVxicAX/NvkiQqWZS0UuE1CVIVqpNNwDczVpBUCrITB7xrF52hdhg==
X-UNTD-Peer-Info: 127.0.0.1|localhost|m23.lax.untd.com|dianmah@juno.com
X-Scanned-By: MIMEDefang 2.52 on 192.168.65.34
X-Scanned-By: MIMEDefang 2.52 on 192.168.65.34
Sender: roots-in@roots-l.rootsweb.com
Subject: [ROOTS-L] Re: ROOTS-L Digest V06 #241 -SSDI

My thoughts on the SSDI -

By publishing the Social Security Death Index - Banks, Credit Card
Companies, and Credit Reporting agencies have that information.

If someone wanted to use my Dad's credit history and information to apply
for a credit card, they would be turned down. His social security number
is listed on the death index. Would it bother my Dad if someone got a
credit card in his name and maxed it with no intention of paying. No, of
course not. But what if collection agencies thought my Mother was
responsible. Or what if someone borrowed money against the house my
mother is still living in using my father's social security number? That
could be very difficult for my mother. 

Any old records that aren't going to be needed that had Dad's Social
Security number on them we shredded. Now since the information is
available to those who do need it, I don't worry about it. (But I still
shred stuff).

I'm not sure how the SSDI could be used for identity theft. If there are
cases of this information being used then the institutions issuing credit
are not doing a complete credit check. 

