From owner-freebsd-security Thu Jan 24 10:55:25 2002 Delivered-To: freebsd-security@freebsd.org Received: from energyhq.homeip.net (213-97-200-73.uc.nombres.ttd.es [213.97.200.73]) by hub.freebsd.org (Postfix) with ESMTP id 4ECE337B422 for ; Thu, 24 Jan 2002 10:55:08 -0800 (PST) Received: from there (kajsa.energyhq.org [192.168.0.1]) by energyhq.homeip.net (Postfix) with SMTP id 55A6B3FC05; Thu, 24 Jan 2002 19:55:10 +0100 (CET) Content-Type: text/plain; charset="iso-8859-1" From: Miguel Mendez Organization: Energy HQ To: "Robert Herrold" , Subject: Re: whois records hacked? Date: Thu, 24 Jan 2002 19:54:43 +0100 X-Mailer: KMail [version 1.3.2] References: <052501c1a475$1105b480$6c01a8c0@mpcsecurity.com> In-Reply-To: <052501c1a475$1105b480$6c01a8c0@mpcsecurity.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020124185510.55A6B3FC05@energyhq.homeip.net> Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thursday 24 January 2002 02:18, Robert Herrold wrote: > Did a whois on microsoft.com and not sure if it's something corrupted in my > whois, or if Microsoft.com's whois record had been compromised. Any > thoughts? Yes, man whois :) flynn@kajsa# whois -h whois.geektools.com microsoft.com Query: microsoft.com Registry: whois.networksolutions.com Results: Registrant: Microsoft Corporation (MICROSOFT-DOM) 1 microsoft way redmond, WA 98052 US Domain Name: MICROSOFT.COM Administrative Contact: Microsoft Hostmaster (MH37-ORG) msnhst@MICROSOFT.COM Microsoft Corp One Microsoft Way Redmond, WA 98052 US 425 882 8080 Fax- - - .: 206 703 2641 Technical Contact: MSN NOC (MN5-ORG) msnnoc@MICROSOFT.COM Microsoft Corp One Microsoft Way Redmond, WA 98052 US 425 882 8080 Fax- PATH [....] Cheers, -- Miguel Mendez - flynn@energyhq.homeip.net EnergyHQ :: http://energyhq.homeip.net FreeBSD - The power to serve! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message