Is QSL.Net gone?

All I get is "The Connection was refused when attempting to contact www.qsl.net."

Looking up www.qsl.net
www.qsl.net
Making HTTP connection to www.qsl.net
Alert!: Unable to connect to remote host.

PING www.qsl.net (63.238.179.50) 56(84) bytes of data.
64 bytes from ftp.qsl.net (63.238.179.50): icmp_seq=1 ttl=239 time=77.9 ms 64 bytes from ftp.qsl.net (63.238.179.50): icmp_seq=2 ttl=239 time=84.8 ms 64 bytes from ftp.qsl.net (63.238.179.50): icmp_seq=3 ttl=239 time=330 ms 64 bytes from ftp.qsl.net (63.238.179.50): icmp_seq=4 ttl=239 time=77.2 ms

--- www.qsl.net ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 77.260/142.759/330.918/108.674 ms

Registration and WHOIS Service Provided By: directNIC.com

Intercosmos Media Group, Inc. provides the data in the directNIC.com
Registrar WHOIS database for informational purposes only. The information may only be used to assist in obtaining information about a domain name's
registration record.

directNIC makes this information available "as is," and does not guarantee
its accuracy.

Registrant:
 QSL.NET, Inc.
 34087 Old Hickory Road
 Laurel, DE 19956
 US
 302-875-7979


Domain Name: QSL.NET

Administrative Contact:
 Waller, Alan [EMAIL PROTECTED]
 34087 Old Hickory Road
 Laurel, DE 19956
 US
 302-875-7979


Technical Contact:
 Waller, Alan [EMAIL PROTECTED]
 34087 Old Hickory Road
 Laurel, DE 19956
 US
 302-875-7979


Record last updated 09-18-2003 06:59:29 PM
Record expires on 01-29-2008
Record created on 01-28-1997

Domain servers in listed order:
        NS1.QSL.NET     63.238.179.1
        NS2.QSL.NET     64.238.2.2
        NS3.QTH.NET     63.238.179.3
        NS4.SWL.NET     63.238.179.188


By submitting a WHOIS query, you agree you will use this data only for lawful purposes. You also agree that, under no circumstances, will you use this data to: a) allow, enable, or otherwise support the transmission by email, telephone, or facsimile of mass, unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or to (b) enable high volume, automated, electronic processes
that send queries or data to the systems of any Registry Operator or
ICANN-Accredited registrar.

So, is it me, or is QSL.Net gone?

73 = Best Regards,
-Geoff/W5OMR

Reply via email to