How Oingo.com Domain
Parking Works (April 28, 2006)
Example #1: Washingtonpsot.com uses
HTTP 301 Redirection to let oingo.com
directly host the page content.
HTTP/1.1
301 Moved Permanently
Proxy-Connection:
Keep-Alive
Connection:
Keep-Alive
Content-length:
122
Via: 1.1 RED-PRXY-09
Date: Fri,
28 Apr 2006 16:17:27 GMT
Location: http://apps5.oingo.com/apps/domainpark/domainpark.cgi?client=netw8744&s=WASHINGTONPSOT.COM
Content-type:
text/html
Server:
Sun-ONE-Web-Server/6.1
<HTML><HEAD><TITLE>Moved
Permanently</TITLE></HEAD>
<BODY><H1>Moved
Permanently</H1>
An error
has occurred.
</BODY></HTML>
Example #2: Comcsast.net
domain page includes an HTML frame that loads an ads-listing page from oingo.com.
<HTML><HEAD></HEAD><TITLE>comcsast.net</TITLE>
<FRAMESET rows='*,40,0' BORDER='0' bordercolor=FFFFFF>
<FRAME Name='central' SRC='http://apps5.oingo.com/apps/domainpark/domainpark.cgi?s=comcsast.net&dp_lp=24&hl=en&dp_lp=7&cid=DTRG4295&dp_p4pid=oingo_inclusion_xml_06&dp_format=1.3'
Scrolling='Auto' marginheight=2>
<FRAME Name='header' SRC='/footer3.php?dom=comcsast.net&adm=info%40domaincar.com&sta=1&txt=&url=&ref=&prm=0&str=comcsast.net&c=&gid=DTRG4295'
Scrolling='auto'>
<FRAME Name='adv' SRC='/adv.php?dom=comcsast.net&adm=info%40domaincar.com&sta=1&txt=&url=&ref=&prm=0&str=comcsast.net&c=1'
Scrolling='auto'>
</FRAMESET></HTML>
The following WhoIs lookup
shows that the IP address of Comcsast.net is
64.20.33.131 and there are 129,908 other sites hosted on this server.
Apparently all of them are parked with oingo.com:
see the funny result screenshot below when you visit http://64.20.33.131, which seems to imply that
any HTTP request sent to that server will generate ads-fetching traffic to
oingo.com with the last two hostname-components (e.g., “33.131” in this case)
extracted as the “domain name”.
