Metropcs-sucks.com Whois Lookup - Who.is
DOMAIN AVAILABILITY FOR METROPCS-SUCKS.COM
Premium domain names are true to their name. These are high value domains that have strong web branding potential, greater type-in traffic, superior relevance, and are typically easier to remember. You can purchase high value, premium domains instantly at Name.com!
In the domain name life cycle, domains are bought, sometimes used (sometimes not), and then they expire. Each and every day there are domain names expiring at Name.com and we give you the opportunity to register these exclusive names before they are deleted and released to other registrars for sale. Check these expiring domains daily for a chance to snatch them up before they are released!
After a domain name expires, it is deleted from the registry, becoming available for registration again. Every day, literally tens of thousands of domains names are deleted from the registry and these deleted domains are now available to register at Name.com!
Name.com's Domain Nabber backorder service allows you to purchase a backorder for any domain name that is currently registered by someone else. Should the domain name ever become available, Domain Nabber will attempt to register that domain on your behalf. Trust your backorders with Name.com!
REGISTRY WHOIS FOR METROPCS-SUCKS.COM
Domain Name: metropcs-sucks.com
Updated: 225 days ago - Refresh
Registrar: MARKMONITOR INC.
Whois Server: whois.markmonitor.com
Referral URL: http://www.markmonitor.com
Expiration Date: 2011-11-15
Creation Date: 2002-11-15
Last Update Date: 2010-05-21
Information Updated: Sun, 3 Jul 2011 02:43:54 UTC
Updated: 225 days ago - Refresh
Registrar: MARKMONITOR INC.
Whois Server: whois.markmonitor.com
Referral URL: http://www.markmonitor.com
Expiration Date: 2011-11-15
Creation Date: 2002-11-15
Last Update Date: 2010-05-21
Information Updated: Sun, 3 Jul 2011 02:43:54 UTC
METROPCS-SUCKS.COM SITE INFORMATION
IP: 64.124.14.63
IP Location: Boise, United States
Website Status: active
Server Type: Apache-Coyote/1.1
IP Location: Boise, United States
Website Status: active
Server Type: Apache-Coyote/1.1
AVAILABLE DOMAINS
PREMIUM DOMAINS
METROPCS-SUCKS.COM WHOIS
Updated: 225 days ago<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title>404 Not Found</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<style type="text/css">
body {
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: 12px;
background-color:#367E8E;
scrollbar-base-color: #005B70;
scrollbar-arrow-color: #F3960B;
scrollbar-DarkShadow-Color: #000000;
color: #FFFFFF;
margin:0;
}
a { color:#021f25; text-decoration:none}
h1 {
font-size: 18px;
color: #FB9802;
padding-bottom: 10px;
background-image: url(sys_cpanel/images/bottombody.jpg);
background-repeat: repeat-x;
padding:5px 0 10px 15px;
margin:0;
}
#body-content p {
padding-left: 25px;
padding-right: 25px;
line-height: 18px;
padding-top: 5px;
padding-bottom: 5px;
}
h2 {
font-size: 14px;
font-weight: bold;
color: #FF9900;
padding-left: 15px;
}
</style>
</head>
<body>
<div id="body-content">
<!-- start content-->
<!--
instead of REQUEST_URI, we could show absolute URL via:
http://HTTP_HOST/REQUEST_URI
but what if its https:// or other protocol?
SERVER_PORT_SECURE doesn't seem to be used
SERVER_PORT logic would break if they use alternate ports
-->
<h1>404 Not Found</h1>
<p>The server can not find the requested page:</p>
<blockquote>
216.55.165.41/request.php?remote_socket=tcp://whois.markmonitor.com:43&request=metropcs-sucks.com%0D%0A (port 80)
</blockquote>
<p>
Please forward this error screen to 216.55.165.41's
<a href="mailto:
@cPanel-1125?subject=Error message [404] 404 Not Found for 216.55.165.41/request.php?remote_socket=tcp://whois.markmonitor.com:43&request=metropcs-sucks.com%0D%0A port 80 on Saturday, 02-Jul-2011 19:43:49 PDT">WebMaster</a>.
</p>
<hr />
<address>Apache/2.0.63 (Unix) mod_ssl/2.0.63 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 Server at 216.55.165.41 Port 80</address>
<!-- end content -->
</div>
</body>
</html>
Information Updated: Sun, 3 Jul 2011 02:43:54 UTC
