|
Originally Posted by golddust
I hope you did get your funds back from Capitalex!!
I agree with HW, I have often used Goldex, and they are very efficient. You can find a link to a list of exchangers on the e-gold home page. You can also do a 'google' search and get good results that way. golddust |
| Must say that Web Life is a rich source of emotions. |
,|
Originally Posted by golddust
Thanks also gnome for offering to help! golddust |
|
Originally Posted by golddust
gnome, you are an emotional guy (?). Don't go getting all va-klemp now. I think this must be a compliment, though it would be our purpose to save HYIPers from themselves
,it does have to include salvation from Capitalex. golddust |
|
canonical name capitalex.com. aliases addresses 202.157.176.93 s Registrant: Capitalex.com Inc. World Trade Center, Piso 1 Area Comercial, Calle 53 Panama City, PA 00000 Panama Registered through: GoDaddy.com Domain Name: CAPITALEX.COM Created on: 26-Sep-03 Expires on: 26-Sep-06 Last Updated on: 16-Sep-05 Administrative Contact: Administrator, Domain Capitalex.com Inc. World Trade Center, Piso 1 Area Comercial, Calle 53 Panama City, PA 00000 Panama 2736276 Fax -- Technical Contact: Administrator, Domain Capitalex.com Inc. World Trade Center, Piso 1 Area Comercial, Calle 53 Panama City, PA 00000 Panama 2736276 Fax -- Domain servers in listed order: NS5.SECURE-WEBHOSTING.COM NS6.SECURE-WEBHOSTING.COM Whois Server Version 1.3 Domain names in the .com and .net domains can now be registered with many different competing registrars. Go to http://www.internic.net for detailed information. Domain Name: CAPITALEX.COM Registrar: GO DADDY SOFTWARE, INC. Whois Server: whois.godaddy.com Referral URL: http://registrar.godaddy.com Name Server: NS5.SECURE-WEBHOSTING.COM Name Server: NS6.SECURE-WEBHOSTING.COM Status: REGISTRAR-LOCK Updated Date: 17-sep-2005 Creation Date: 26-sep-2003 Expiration Date: 26-sep-2006 >>> Last update of whois database: Thu, 23 Mar 2006 18:40:57 EST <<< |
|
DNS Report for Capitalex.com Generated by www.DNSreport.com at 02:22:46 GMT on 24 Mar 2006. Category Status Test Name Information Parent PASS Missing Direct Parent check OK. Your direct parent zone exists, which is good. Some domains (usually third or fourth level domains, such as example.co.us) do not have a direct parent zone ('co.us' in this example), which is legal but can cause confusion. INFO NS records at parent servers Your NS records at the parent servers are: ns5.secure-webhosting.com. [202.186.13.208] [TTL=172800] [MY] ns6.secure-webhosting.com. [202.157.184.113] [TTL=172800] [SG] [These were obtained from m.gtld-servers.net] PASS Parent nameservers have your nameservers listed OK. When someone uses DNS to look up your domain, the first step (if it doesn't already know about your domain) is to go to the parent servers. If you aren't listed there, you can't be found. But you are listed there. PASS Glue at parent nameservers OK. The parent servers have glue for your nameservers. That means they send out the IP address of your nameservers, as well as their host names. PASS DNS servers have A records OK. All your DNS servers either have A records at the zone parent servers, or do not need them (if the DNS servers are on other TLDs). A records are required for your hostnames to ensure that other DNS servers can reach your DNS servers. Note that there will be problems if your DNS servers do not have these same A records. NS INFO NS records at your nameservers Your NS records at your nameservers are: ns6.secure-webhosting.com. ns5.secure-webhosting.com. FAIL Open DNS servers ERROR: One or more of your nameservers reports that it is an open DNS server. This usually means that anyone in the world can query it for domains it is not authoritative for (it is possible that the DNS server advertises that it does recursive lookups when it does not, but that shouldn't happen). This can cause an excessive load on your DNS server. Also, it is strongly discouraged to have a DNS server be both authoritative for your domain and be recursive (even if it is not open), due to the potential for cache poisoning (with no recursion, there is no cache, and it is impossible to poison it). Also, the bad guys could use your DNS server as part of an attack, by forging their IP address. Problem record(s) are: Server 202.186.13.208 reports that it will do recursive lookups. [test] Server 202.157.184.113 reports that it will do recursive lookups. [test] See this page for info on closing open DNS servers. PASS Mismatched glue OK. The DNS report did not detect any discrepancies between the glue provided by the parent servers and that provided by your authoritative DNS servers. PASS No NS A records at nameservers OK. Your nameservers do include corresponding A records when asked for your NS records. This ensures that your DNS servers know the A records corresponding to all your NS records. PASS All nameservers report identical NS records OK. The NS records at all your nameservers are identical. PASS All nameservers respond OK. All of your nameservers listed at the parent nameservers responded. PASS Nameserver name validity OK. All of the NS records that your nameservers report seem valid (no IPs or partial domain names). PASS Number of nameservers OK. You have 2 nameservers. You must have at least 2 nameservers (RFC2182 section 5 recommends at least 3 nameservers), and preferably no more than 7. PASS Lame nameservers OK. All the nameservers listed at the parent servers answer authoritatively for your domain. PASS Missing (stealth) nameservers OK. All 2 of your nameservers (as reported by your nameservers) are also listed at the parent servers. PASS Missing nameservers 2 OK. All of the nameservers listed at the parent nameservers are also listed as NS records at your nameservers. PASS No CNAMEs for domain OK. There are no CNAMEs for Capitalex.com. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present. PASS No NSs with CNAMEs OK. There are no CNAMEs for your NS records. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present. PASS Nameservers on separate class C's OK. You have nameservers on different Class C (technically, /24) IP ranges. You must have nameservers at geographically and topologically dispersed locations. RFC2182 3.1 goes into more detail about secondary nameserver location. PASS All NS IPs public OK. All of your NS records appear to use public IPs. If there were any private IPs, they would not be reachable, causing DNS delays. PASS TCP Allowed OK. All your DNS servers allow TCP connections. Although rarely used, TCP connections are occasionally used instead of UDP connections. When firewalls block the TCP DNS connections, it can cause hard-to-diagnose problems. INFO Nameservers versions Your nameservers have the following versions: 202.186.13.208: "9.2.3" 202.157.184.113: "9.2.3" PASS Stealth NS record leakage Your DNS servers do not leak any stealth NS records (if any) in non-NS requests. SOA INFO SOA record Your SOA record [TTL=3600] is: Primary nameserver: ns6.secure-webhosting.com. Hostmaster E-mail address: admin.secure-webhosting.com. Serial #: 1119496617 Refresh: 7200 Retry: 3600 Expire: 604800 Default TTL: 3600 PASS NS agreement on SOA serial # OK. All your nameservers agree that your SOA serial number is 1119496617. That means that all your nameservers are using the same data (unless you have different sets of data with the same serial number, which would be very bad)! Note that the DNS Report only checks the NS records listed at the parent servers (not any stealth servers). PASS SOA MNAME Check OK. Your SOA (Start of Authority) record states that your master (primary) name server is: ns6.secure-webhosting.com.. That server is listed at the parent servers, which is correct. PASS SOA RNAME Check OK. Your SOA (Start of Authority) record states that your DNS contact E-mail address is: admin@secure-webhosting.com. (techie note: we have changed the initial '.' to an '@' for display purposes). WARN SOA Serial Number WARNING: Your SOA serial number is: 1119496617. That is OK, but the recommended format (per RFC1912 2.2) is YYYYMMDDnn, where 'nn' is the revision. For example, if you are making the 3rd change on 02 May 2000, you would use 2000050203. This number must be incremented every time you make a DNS change. Your SOA serial appears to be the number of seconds since midnight 01 Jan 1970 when the last DNS change was made (tinydns format). That works out to be Wed Jun 22 23:16:57 2005 EST. PASS SOA REFRESH value OK. Your SOA REFRESH interval is : 7200 seconds. This seems normal (about 3600-7200 seconds is good if not using DNS NOTIFY; RFC1912 2.2 recommends a value between 1200 to 43200 seconds (20 minutes to 12 hours)). This value determines how often secondary/slave nameservers check with the master for updates. PASS SOA RETRY value OK. Your SOA RETRY interval is : 3600 seconds. This seems normal (about 120-7200 seconds is good). The retry value is the amount of time your secondary/slave nameservers will wait to contact the master nameserver again if the last attempt failed. PASS SOA EXPIRE value OK. Your SOA EXPIRE time: 604800 seconds. This seems normal (about 1209600 to 2419200 seconds (2-4 weeks) is good). RFC1912 recommends 2-4 weeks. This is how long a secondary/slave nameserver will wait before considering its DNS data stale if it can't reach the primary nameserver. PASS SOA MINIMUM TTL value OK. Your SOA MINIMUM TTL is: 3600 seconds. This seems normal (about 3,600 to 86400 seconds or 1-24 hours is good). RFC2308 suggests a value of 1-3 hours. This value used to determine the default (technically, minimum) TTL (time-to-live) for DNS entries, but now is used for negative caching. MX FAIL MX Category ERROR: I couldn't find any MX records for Capitalex.com. If you want to receive E-mail on this domain, you should have MX record(s). Without any MX records, mailservers should attempt to deliver mail to the A record for Capitalex.com. I can't continue in a case like this, so I'm assuming you don't receive mail on this domain. Mail FAIL Connect to mail servers ERROR: I could not find any mailservers for Capitalex.com. WWW INFO WWW Record Your www.Capitalex.com A record is: www.capitalex.com. A 202.157.176.93 [TTL=3600] [SG] PASS All WWW IPs public OK. All of your WWW IPs appear to be public IPs. If there were any private IPs, they would not be reachable, causing problems reaching your web site. PASS CNAME Lookup OK. Some domains have a CNAME record for their WWW server that requires an extra DNS lookup, which slightly delays the initial access to the website and use extra bandwidth. There are no CNAMEs for www.Capitalex.com, which is good. Legend: Rows with a FAIL indicate a problem that in most cases really should be fixed. Rows with a WARN indicate a possible minor problem, which often is not worth pursuing. Note that all information is accessed in real-time (except where noted), so this is the freshest information about your domain. -------------------------------------------------------------------------------- (C) Copyright 2000-2006 DNSstuff.com |
|
Traceroute Report: Traceroute 1 83.138.166.2 (83.138.166.2) 0.457 ms 0.445 ms 0.417 ms 2 g3-13.core1.lon.rackspace.net (83.138.138.84) 0.249 ms 0.250 ms 0.247 ms 3 g1-2.edge3.lon.rackspace.net (83.138.138.34) 0.945 ms 0.913 ms 0.864 ms 4 peer1.ldn1.flagtel.com (195.66.224.146) 0.948 ms 0.951 ms 1.016 ms 5 so-2-2-0.0.cjr02.ldn001.flagtel.com (62.216.128.197) 1.422 ms 1.400 ms 1.370 ms MPLS Label=129920 CoS=5 TTL=1 S=0 6 so-2-2-0.cjr02.alx001.flagtel.com (62.216.128.5) 76.834 ms 71.239 ms 77.021 ms MPLS Label=190466 CoS=5 TTL=1 S=0 7 ge-1-0-0.0.cjr01.alx001.flagtel.com (62.216.128.161) 71.299 ms 72.190 ms 71.454 ms MPLS Label=147299 CoS=5 TTL=1 S=0 8 so-3-3-0.0.cjr03.hkg003.flagtel.com (62.216.128.222) 210.409 ms 210.035 ms 210.536 ms MPLS Label=390816 CoS=5 TTL=1 S=0 9 so-0-0-0.0.cjr04.hkg003.flagtel.com (62.216.128.106) 210.309 ms 211.214 ms 209.874 ms 10 62.216.146.38 (62.216.146.38) 212.745 ms 62.216.146.242 (62.216.146.242) 211.709 ms 216.917 ms 11 global.hgc.com.hk (218.189.8.217) 214.257 ms 320.430 ms 213.773 ms 12 global.hgc.com.hk (218.189.12.158) 228.900 ms 213.621 ms 218.887 ms 13 p5-1-0.bkj2.jaring.my (161.142.24.57) 252.024 ms 245.768 ms 246.840 ms 14 ge-4-0.bkj93.jaring.my (161.142.173.9) 251.278 ms 246.965 ms 246.259 ms 15 pos0-0-0.mup15.jaring.my (161.142.23.170) 246.494 ms 245.984 ms 246.852 ms 16 161.142.81.46 (161.142.81.46) 247.201 ms 246.304 ms 247.135 ms 17 csw4-my-idc.skali.net (202.186.213.3) 246.444 ms 247.374 ms 247.757 ms 18 ns5.secure-webhosting.com (202.186.13.208) 246.229 ms 247.088 ms 248.104 ms |
|
Many Pipsters are hard up nowadays. Still - help is coming! I am very grateful. Could use 30 times more, though. So I just keep reinvesting in Luke's program - 9.5% daily - our active deposit has grown to $291.10. Goldeneye - $6.00 Help fund, Treasurehunter1 - $100.00 Gift towards needs of members, Stride2win - $5.15 Gift for hope destiny - $5.00 - donation from destiny Pipsqueak - $2.58 - help/relief fund Treasurhunter1 - $50.00 from: Treasurhunter1 Spudkicker - $60.00 Hope this helps Thanks very much. |
|
IP: 202.157.176.93 Country: Singapore City: Colombo, Central Country Code: SG Merchant Note: Country may have high rate of fraud [1] Currency: SGD [Singapore Dollars] Private IP? No Known Proxy? No IP address: 202.157.176.93 Reverse DNS: w1.capitalex.net. Reverse DNS authenticity: [Verified] ASN: 17464 ASN Name: TMIDC-AP (Hosting Services (MYLOCA),) IP range connectivity: 1 Registrar (per ASN): APNIC Country (per IP registrar): SG [Singapore] Country Currency: SGD [Singapore Dollars] Country IP Range: 202.157.128.0 to 202.157.191.255 Country fraud profile: High City (per outside source): Colombo, Central Private (internal) IP? No IP address registrar: BOGUS Known Proxy? No % [whois.apnic.net node-2] % Whois data copyright terms http://www.apnic.net/db/dbcopyright.html inetnum: 202.157.176.0 - 202.157.176.255 netname: ACME-INTERNET-DATA-CENTER-3 country: MY descr: Co-Location & Dedicated Hosting descr: Web hosting & Email Hosting descr: IDC-3 Cyberjaya, Malaysia admin-c: FW90-AP tech-c: FW90-AP status: ASSIGNED NON-PORTABLE changed: *****@webvisions.com 20030620 mnt-by: MAINT-SG-WEBVISIONS source: APNIC person: Wong Fook Seong nic-hdl: FW90-AP e-mail: ****@acmecommerce.com address: Acme Commerce Sdn Bhd address: Cyberjaya phone: +60-3-9281-9329 phone: +60-19-2102-813 fax-no: +60-3-9283-2779 country: MY changed: *****@webvisions.com 20030331 mnt-by: MAINT-SG-WEBVISIONS source: APNIC |
| The fact that the business location is in Panama, however hosted from Mayalsia does raise certain concerns since as reported (and known), the criminal element has more control in many cases then the governing bodies. Perhaps this choice of host, rather than the other programs being hosted there would be the appropriate answer to concerns over hosting associated with "Scam" programs. |
| In addition, there have been other reports of non-payment or payment avoidance by Capitalex apparently unresolved. The problem mentioned here is not an isolated event and should not discharge the other problems Capitalex appears to have in completing exchanges. |
| Furthermore, the association with Global Vantage as recognized by many frustrated investors can not be ignored, but I would love more clarity. Should there be a distinction made in ownership, management, or administration? |
|
Originally Posted by Capitalex.com
Dear golddust,
The Capitalex.com website is hosted by http://www.spirit-international.net (an offshore hosting company). Apparently we are not their only client. They accept e-currencies, therefore it seems that many businesses, individuals, and programs that accept e-currencies make use of their hosting services. If you have any questions about their other clients you should contact them directly. They will be able to confirm that we had nothing to do with these other clients. |
| The fact that the business location is in Panama, however hosted from Mayalsia does raise certain concerns since as reported (and known), the criminal element has more control in many cases then the governing bodies. Perhaps the choice and location of this host, rather than the other programs/clients being hosted, would be appropriate information to answer to concerns over Capitalex's hosting in association with "Scam" programs. |
|
Originally Posted by Spirithosting
Golddust, I am the administrator for Spirit International Hosting. I was contacted by one of your members and asked to respond to this thread on the forum you "moderate". Let me help educate you and your readers about our offshore web hosting services since you are obviously misinformed, as I can see from your responses above.
Welcome to Weblife Spirithosting. Your posts/comments are appreciated! You can expect that members, not just MODs will add comments, questions and facts they feel may be relevant to your attempt to "educate". Spirit Hosting began back in March 1999 as a response to a need for our clients hosting their websites in different countries so not to be governed by the laws of their home country. We abide by International law and do not tolerate scams, copyright infringements, hate crimes, pornography and much of the other filth of the world. We are here to provide a service which I have already alluded to. Spirit International Hosting (aka Spirit Offshore Hosting) has worked closely with The e-Told Reports in many scam cases over the years to close down these theives and help keep people from losing their money. Where were you back in 1992 when the NZ iCafe scammers were hosting a multitude of websites with different offshore hosts and stealing people's gold investment money? I know where we were, we were working with news reporters and NZ police trying to have these people arrested. What about when the owner of OSgold.com was scheming to steal all that money and leave the country? There wasn't much we could do after-the-fact, but we did close down their servers as soon as we became aware of that activity by notices from reputable informers. You can check with Alan alan@e-told.org at e-Told Reports for verication of these actions (unless you think that is a scam too). We host over 1000 shared websites and dedicated servers. It's impossible for us to know the "intentions" of people when they sign up to host a website. However, when we know they are scamming people, we do not tolerate that kind of activity on our servers and will close them down quickly. Your position toward "Scam" operators is commendable. Too bad more hosts don't take such an active position, but there are so many domains and I don't know what else a host can do but as you have indicated. Can you provide specific examples of Scams you've shut down? Yes, it is true that some do not feel "e-told.org" is a reliable source. I remain mute on this point, therefore do not like your insinuation. Spirit International Hosting is also a Panama corporation. We hosted first in Switzerland in 1999, but their customer service and prices were way less than desireable. So we moved our three servers that same year to Panama, but people there seemed to be more interested in lounging on the beach rather than providing technical support. I find this information most interesting since upon research today, I have found information pertaining to 'seemingly' experienced organizations offering offshore protection and hosting services in Panama. Perhaps, at least some of these entities are not as good as they say; I have learned that hosting in Panama is no better than hosting in Maylasia... We moved 5 servers to Malaysia in June 2000 where we currently enjoy excellent technical support services (on our current 12 shared servers) from people who have an excellent work ethic and they are darn good at what they do. The telecommunications infrastructure in Malaysia is newer and near the top in the world. This Data Center is an ultra modern facility which runs state-of-the-art equipment, with transmission speeds of OC-48/STM-16, 2.488 Gbps, on an Optical fiber Internet backbone, which is much faster than what runs in the US and many other areas. So before you go knocking our company or Capitalex, you might check to see what you're talking about. And as for Capitalex - we've never had any complaints about them scamming or not providing less than satisfactory services. I suspect that you would not be the first to hear the Complaints, as it's generally customary for exchange providers and other online vendors or services to first have direct interaction with their clients/customers, yes? In addition, I am not 'knocking' your Company, but have reasons to doubt honest and/or reliable hosting based on my experience with hosting and Scams. IMO, there is a relatedness. Bad hosting can bring a program down, provide a foothold for hackers or ddoser to bring a program down, or be utilized as an excuse by a domain for a programs' failure. In this case, there is a history of known scams hosted from your servers, despite your best efforts. You are vouching for them; do you even know where Capitalex is physically located? The DNS/Whois information reports they are located in the World Trade Center, Piso 1 Calle 53 in Panama City. I did a search of buildings and addresses in Panama City and could not find it. Perhaps that is not relevant to you. Capitalex.com reported that Capitalex has 22% ownership by Global Vantage and its members. (GV: IP - 202.142.1.144 - also hosted in Maylasia. Perhaps you are the host for GV. They are registered through godaddy, same as Capitalex) While this is certainly minority ownership, do you have any idea of the track record of GV and what, if any returns are being paid to members who invested in Capitalex? I can tell you that it isn't pretty. GV is elusive and not forthcoming with 'proprietary' information concerning investment opps to its members and some have called every investment opp it has presented a "SCAM". I am happy to say that I am one of the very few who ever made enough noise to get a refund and get "kicked out of" GV. So, I can relate from where marcphillip is coming. GV is a program that does "monitor off" posts and bans members who post critically. One example would be due to poor or non performing GV investments, such as Capitalex. For this reason, there are some who criticise GV and Capitalex as a non-performing investment. (A SCAM?) So I suggest you put your money where your foot is and use their services to check it out for yourself how good they are. We use them for currency exchange from time to time and they've never been less than what they claim to be. SO, I suggest you become more informed about this particular client, before you come so quickly to their defense and plug "how good they are". I know enough 'history' to know that I will never use or recommend their services, or a host who recommends their services. Perhaps you should file this information where your foot is and chew on it, before you "set the record straight". The same goes for our services. This is the last writing I will make on this subject. However, I want to set the record straight and I hope you don't moderate this off your forum because we challenged you. I'm sure you are also a business person trying to provide good services to your members as Spirit International Hosting is and as Capitalex is too. From Spirit Admin www.spirit-international.net |