Daily-Capital-www.daily-capital.com

blocparty как и я любит играть по крупному....


Почти отбил...
В среду вложения окупаются и приносят доход - ну а дальше чистейшая прибыль ( на сколько проекта хватит)

Нужно вкладывать по крупному в 5-10 разных проектов и не более чем на 2х недельный срок - и тогда станешь сам относиться ко всем проектам оптимистично.

Да, наши 70 сегодня пришли Надеюсь еще 11 раз они нас так же порадуют!

По поводу прогнозов... да, после руссо, в который с моей подачи несколько человек закинуло прилично (дня них) денег, а он мило накрылся тазиком, я прогнозы делать опосаюсь. Мы вложились вчера, сумма для нас не маленькая, но на что идем мы знали. Получим свое - замечательно, нет - сами выноваты. Если господа вкладывают такие деньги, значит они могут это себе позволить и я буду искренне за них рада, если они получат прибыль! Это ведь хорошо, когда твои соотечественники не прогарают на буржуях, а зарабатывают
Так что всем нам удачи! А новички пусть свои головы на плечах тоже имеют!

Вчера получил 3/12 надеюсь доживет))

и сного сайт не пашет.
кстате если дело так и дальше пойдёт - Им придётся прикрыть лавочку ( медным тазом )

Это веть пирамида и зависит всё в ней от вложений людей - за счёт которых они делают ежедневные выплаты... Но вот уже 2 дня туда не чего не кто не ложит и думаю уже не положит... У них сейчас стабильная потеря денег на выплатах идёт...
Если проблема с сайтом будет продолжаться ещё 1-2 дня - они могут закрыть сайт ( а мы будем думать реконструируют - будем говорить давайте 2 дня подождём - а они пока все деньги выведут )
Если проблема продлится 1-2 дня с сайтом и если за нормально работающие дни этой недели ( четверг и пятница ) в сайт не поступят крупные инвистиции - то очень большая вероятность что сайт прикроют до понедельника!!!
( Ночное соотношение прихода и выплат уже не нравится в статистике)

Это лишь моё мнение - возможно я лишь всех пугаю!

Удачи нам всем !!!

Сайт действительно не открыватся, и выплаты за сегодня не получены.

Приношу свои извинения..... Загрузился из кеша спутникового инета. Поэтому и напутал.... Сайт вообще ни с какого доступа не грузится...

при загрузке страницы выдаёт - 502 Bed Gateway

выплаты не пришли.
накрылся проект.

Сайт не грузится... могу сделать предположение, что выплат нет по причине сбоев в работе сайте. Администрации действительно не выгодно производить выплаты при том, что поступления не идут. Пока еще есть надежда на то, что выплаты начнут производится, когда сайт восстановится полностью... а может ничего и не получится...

вчера не работал сайт - но выплаты делали.
думаю это конец.

Вчера, они ещё не осознали 1 из 2, или всё, или пока не платят, потому что им не платят.

А у кого-нибудь есть адрес саппорта? Написать им чтоли...

Полностью соглашусь, ждем когда заработает проект. А мыло саппорта 7support#daily-capital.com да что толку, если полный даун.

интересно а остольные сайты на серваке так же лежат или только этот?

если другие сайты не лежат - значит они уже отмывают еголд ( им нужно на это 1 день)

вообще я как и все очень хочу чудо!
надеюсь проект заработает и заплатит.

Остальные сайты живут и посвистывают. Все там в порядке, хостинг-сервер работает, сайты крутятся, даже некоторые смог открыть

DNSreport for daily-capital.com
Generated by www.DNSreport.com at 15:46:08 GMT on 24 Jul 2007.
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:

ns1.hostsilo.com. [72.52.150.179] [TTL=172800] [US]
ns2.hostsilo.com. [72.52.150.180] [TTL=172800] [US]
[These were obtained from c.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: ns2.hostsilo.com. [72.52.150.180] [TTL=86400]
ns1.hostsilo.com. [72.52.150.179] [TTL=86400]
PASS Open DNS servers OK. Your DNS servers do not announce that they are open DNS servers. Although there is a slight chance that they really are open DNS servers, this is very unlikely. Open DNS servers increase the chances that of cache poisoning, can degrade performance of your DNS, and can cause your DNS servers to be used in an attack (so it is good that your DNS servers do not appear to be 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 daily-capital.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.
WARN Nameservers on separate class C's WARNING: All of your nameservers (listed at the parent nameservers) are in the same Class C (technically, /24) address space, which means that they are probably at the same physical location. Your nameservers should be at geographically dispersed locations. You should not have all of your nameservers at the same location. 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.
FAIL Single Point of Failure ERROR: Although you have at least 2 NS records, they both point to the same server, resulting in a single point of failure. You are required to have at least 2 nameservers per RFC 1035 section 2.2.
INFO Nameservers versions [For security reasons, this test is limited to members]
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=86400] is:

Primary nameserver: ns1.hostsilo.com.
Hostmaster E-mail address: chidienyi.hotmail.com.
Serial #: 2007061001
Refresh: 86400
Retry: 7200
Expire: 3600000
Default TTL: 86400
PASS NS agreement on SOA serial # OK. All your nameservers agree that your SOA serial number is 2007061001. 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 DNSreport 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: ns1.hostsilo.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: [email protected]. (techie note: we have changed the initial '.' to an '@' for display purposes).
PASS SOA Serial Number OK. Your SOA serial number is: 2007061001. This appears to be in the recommended format of YYYYMMDDnn, where 'nn' is the revision. So this indicates that your DNS was last updated on 10 Jun 2007 (and was revision #1). This number must be incremented every time you make a DNS change.
WARN SOA REFRESH value WARNING: Your SOA REFRESH interval is : 86400 seconds. This seems high. You should consider decreasing this value to about 3600-7200 seconds (or higher, if using DNS NOTIFY). RFC1912 2.2 recommends a value between 1200 to 43200 seconds (20 minutes to 12 hours, with the longer time periods used for very slow Internet connections), and if you are using DNS NOTIFY the refresh value is not as important (RIPE recommend 86400 seconds if using DNS NOTIFY). This value determines how often secondary/slave nameservers check with the master for updates. A value that is too high will cause DNS changes to be in limbo for a long time.
PASS SOA RETRY value OK. Your SOA RETRY interval is : 7200 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.
WARN SOA EXPIRE value WARNING: Your SOA EXPIRE time is : 3600000 seconds. This seems a bit high. You should consider decreasing this value to about 1209600 to 2419200 seconds (2 to 4 weeks). RFC1912 suggests 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: 86400 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 INFO MX Record Your 1 MX record is:

0 daily-capital.com. [TTL=14400] IP=72.52.150.179 [TTL=14400] [US]
PASS Low port test OK. Our local DNS server that uses a low port number can get your MX record. Some DNS servers are behind firewalls that block low port numbers. This does not guarantee that your DNS server does not block low ports (this specific lookup must be cached), but is a good indication that it does not.
PASS Invalid characters OK. All of your MX records appear to use valid hostnames, without any invalid characters.
PASS All MX IPs public OK. All of your MX records appear to use public IPs. If there were any private IPs, they would not be reachable, causing slight mail delays, extra resource usage, and possibly bounced mail.
PASS MX records are not CNAMEs OK. Looking up your MX record did not just return a CNAME. If an MX record query returns a CNAME, extra processing is required, and some mail servers may not be able to handle it.
PASS MX A lookups have no CNAMEs OK. There appear to be no CNAMEs returned for A records lookups from your MX records (CNAMEs are prohibited in MX records, according to RFC974, RFC1034 3.6.2, RFC1912 2.4, and RFC2181 10.3).
PASS MX is host name, not IP OK. All of your MX records are host names (as opposed to IP addresses, which are not allowed in MX records).
INFO Multiple MX records NOTE: You only have 1 MX record. If your primary mail server is down or unreachable, there is a chance that mail may have troubles reaching you. In the past, mailservers would usually re-try E-mail for up to 48 hours. But many now only re-try for a couple of hours. If your primary mailserver is very reliable (or can be fixed quickly if it goes down), having just one mailserver may be acceptable.
PASS Differing MX-A records OK. I did not detect differing IPs for your MX records (this would happen if your DNS servers return different IPs than the DNS servers that are authoritative for the hostname in your MX records).
PASS Duplicate MX records OK. You do not have any duplicate MX records (pointing to the same IP). Although technically valid, duplicate MX records can cause a lot of confusion, and waste resources.
FAIL Reverse DNS entries for MX records ERROR: The IP of one or more of your mail server(s) have no reverse DNS (PTR) entries/* (if you see "Timeout" below, it may mean that your DNS servers did not respond fast enough)*/. RFC1912 2.1 says you should have a reverse DNS for all your mail servers. It is strongly urged that you have them, as many mailservers will not accept mail from mailservers with no reverse DNS entry. You can double-check using the 'Reverse DNS Lookup' tool at the DNSstuff site if you recently changed your reverse DNS entry (it contacts your servers in real time; the reverse DNS lookups in the DNS report use our local caching DNS server). The problem MX records are:
179.150.52.72.in-addr.arpa [No reverse DNS entry (rcode: 3 ancount: 0) (check it)]
Mail PASS Connect to mail servers OK: I was able to connect to all of your mailservers.
PASS Mail server host name in greeting OK: All of your mailservers have their host name in the greeting:

daily-capital.com:
220-host.hostsilo.com ESMTP Exim 4.63 #1 Tue, 24 Jul 2007 09:46:12 -0600 220-We do not authorize the use of this system to transport unsolicited, 220 and/or bulk e-mail.
PASS Acceptance of NULL <> sender OK: All of your mailservers accept mail from "<>". You are required (RFC1123 5.2.9) to receive this type of mail (which includes reject/bounce messages and return receipts).
PASS Acceptance of postmaster address OK: All of your mailservers accept mail to [email protected] (as required by RFC822 6.3, RFC1123 5.2.7, and RFC2821 4.5.1).
PASS Acceptance of abuse address OK: All of your mailservers accept mail to [email protected].
INFO Acceptance of domain literals WARNING: One or more of your mailservers does not accept mail in the domain literal format (user@[0.0.0.0]). Mailservers are technically required RFC1123 5.2.17 to accept mail to domain literals for any of its IP addresses. Not accepting domain literals can make it more difficult to test your mailserver, and can prevent you from receiving E-mail from people reporting problems with your mailserver. However, it is unlikely that any problems will occur if the domain literals are not accepted (mailservers at many common large domains have this problem).

daily-capital.com's postmaster@[72.52.150.179] response:
>>> RCPT TO:<postmaster@[72.52.150.179]>
<<< 501 <postmaster@[72.52.150.179]>: domain literals not allowed
PASS Open relay test OK: All of your mailservers appear to be closed to relaying. This is not a thorough check, you can get a thorough one here.

daily-capital.com OK: 550-85.3b.354a.static.theplanet.com (test.DNSreport.com) [74.53.59.133]:1447 is 550-currently not permitted to relay through this server. Perhaps you have not 550-logged into the pop/imap server in the last 30 minutes or do not have SMTP 550 Authentication turned on in your email client.
WARN SPF record Your domain does not have an SPF record. This means that spammers can easily send out E-mail that looks like it came from your domain, which can make your domain look bad (if the recipient thinks you really sent it), and can cost you money (when people complain to you, rather than the spammer). You may want to add an SPF record ASAP, as 01 Oct 2004 was the target date for domains to have SPF records in place (Hotmail, for example, started checking SPF records on 01 Oct 2004).
WWW
INFO WWW Record Your www.daily-capital.com A record is:

www.daily-capital.com. CNAME daily-capital.com. [TTL=14400]
daily-capital.com. A 72.52.150.179 [TTL=14400] [US]
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. You do have a CNAME record for www.daily-capital.com, which can cause some confusion. However, this is legal. Your CNAME entry also returns the A record for the CNAME entry, which is good -- otherwise, it would require an extra DNS lookup, which slightly delays the initial access to the website and use extra bandwidth. Note that if the CNAME points to another CNAME, it will likely cause problems.
INFO Domain A Lookup Your daily-capital.com A record is:

daily-capital.com. A 72.52.150.179 [TTL=14400]


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.
* Note that automated usage is not tolerated; please only view the DNS report directly with your web browser

Ну ждем до завтра и прощаемся с деньгами

я не успел получить последние две выплаты ... итого оказался в точке безубыточности

ждать бесполезно - не выплатят.
По идеи нам сайт не нужен для выплат - они их и без него могли бы сделать!
Как сделали это вчера.
Мне не хватило 2х выплат - сам виноват... ( в предь буду осторожнее)

Возможно конечно их досят ! ( но это очень мало вероятно)


вообщем тазом накрылся сайт.

Kastel, ты как-то чрезмерно категоричен... чуть что - тазом, чуть что - все в порядке... мы все еще ждем. Точно можно будет сказать к завтрашнему дню. Я бы на месте админов тоже не делала выплат, если с сайтом проблемы. Им надо привлекать капитал, а у них одни растраты, вложиться то никто не может! Если завтра не заработает, тогда понятно, что каюк. Сегодня еще ждем...