mailing list archives
Re: Privacy leak in VeriSign's SiteFinder service #2
From: Marco Ivaldi <raptor () 0xdeadbeef info>
Date: Thu, 25 Sep 2003 13:58:12 +0200 (CEST)
Up to now, e-mails addressed to misspelled mail domains will not be sent
to Verisign's Fake-SMTP-service as MX records are used for mail-domain
resolving. Verisign did not set up wildcard MX records.
That's not entirely correct. Since every host in non-existant domain now
resolves to 184.108.40.206 (DNS record type A), all email traffic with
misspelled recipient domain is actually forwarded to Verisign's
sitefinder, without the need for a specific MX record:
root () voodoo:~# host jasfkjhaf.com
jasfkjhaf.com A 220.127.116.11
E.g., try sending a test email to whatever () non-existant, you'll get
something like that:
<test () jasfkjhaf com>:
18.104.22.168 does not like recipient.
Remote host said: 550 <unknown[X.X.X.X]>: Client host rejected: The
domain you are trying to send mail to does not exist.
Giving up on 22.214.171.124.
Antifork Research, Inc. http://0xdeadbeef.info/
3B05 C9C5 A2DE C3D7 4233 0394 EF85 2008 DBFD B707
- Re: Privacy leak in VeriSign's SiteFinder service #2 Marco Ivaldi (Sep 25)