Google 網路論壇不再支援新的 Usenet 貼文或訂閱項目,但過往內容仍可供查看。

SPEWS: S2547 Removal request

瀏覽次數:33 次
跳到第一則未讀訊息

Alex Polyakov

未讀,
2004年1月23日 下午4:12:052004/1/23
收件者:
Hello,

My name is Alex Polyakov, I'm the owner of Pilot Holding, LLC
(hosting bbahost.com
(the Russian site) / bbasafehosting.com (the English site) is also known as
sysvhost.com).
First of all I'd like to tell that mybizhosting.com
(ebizhostingsolutions.com, myservlethosting.com)
which are owned by E-Biz Hosting Solutions, LLC is not related to Pilot
Holding, LLC.
I worked at E-Biz Hosting Solutions, LLC as a main specialist of Java
Hosting department.It wasn't my hosting,
my sites or my projects. All projects are owned by CEO of E-Biz Hosting
Solutions, LLC - Adam Kling.
As I've said before, I was main specialist of Java branch, but there were
lots of other projects, on the
person who worked at on of them is Alex Mosh. Afterwards he started his
owned business. You know that living
standart in Ukraine is too low and people don't lose any chance to make some
money. So I can't judge Alex for
dealing with spammers, although I roundly denounce spam. Alex Mosh owned
hosting company bbahost.com/bbasafehosting.com
/pilotholding.com, but due to his spam related deals his hosting company
suffered from a sequence of failures and
was nearly dead.
After negotiating with Alex on the end of July he described me the situation
roughly, and hosting company was sold
to me for a not so big of money.
I left my work at E-Biz Hosting Solutions and started development and
recreation of hosting. All remote administrators
which have been working for Alex were fired and a new team of local
administrators was created. Unfortunately I
had no opportunity to prove not-participation of
bbahost.com/bbasafehosting.com in spam stuff. I was forced to
transfer all the hosting including dedicated servers to sysvhost.com domain,
it nearly was a last straw for a hosting.
After a half of year have passed, with a help of promoters and friends I
managed to elevate hosting company in search engines and
forums to a certain level which allowed to start wiping all detractive
things and opinions about my hosting. So I write to you.
My hosting has Zero Tolerance against spam, that is specified on
http://bbasafehosting.com/services/policy.html page
(bbasafehosting.com -> services -> helpful documentation -> policy), and I
personally is enemy to spam as an intervention into human's
private life. I fight against spam and both of my DataCenters
(ev1servers.net (formerly rackshack.net) and theplanet.com)
can confirm that all the domains and accounts that were related to spam or
TOS/AUP violations were removed after the first notice.
As I have read FAQ on spews.org site and found information in
groups.google.com concerning bbahost.com/bbasafehosting.com/sysvhost.com I'd
like to say that
all the domains, registered by Pilot Holding, LLC and involved in spam were
removed not only from hosting servers (actually they were removed
during moving servers from calpop.com/datacolo.com datacenters, before I
became the owner of the company) but I also correspond with opensrs.net
domain registrar ,
(we are reseller of its service) concerning complete removal these domain
from the registry of root DNS servers.
I have only permitted myself to leave bba*.com domains, because of its
positions in the search and rate systems and as a trade mark of a hosting,
and beacuse of earlier date of registration
than sysvhost.com, you should understand.
As it's written in a certain post in the news group
news.admin.net-abuse.blocklisting, "Capo" Borman (Vladislav Melnyk in real
life) is actually has relation to
bbahost.com/bbasafehosting.com/sysvhost.com and is working for me now. He is
NOT an owner of the hosting, he is just a promoter from the sales
department. He was working in the hosting before
I have bought it, he was promoting the company in the russian and english
parts of internet.
What concerns carderplanet.com I understend your abhorrence but let me
justify myself once more - carderplanet.com
is highly visited forum which is visited not only by
frauders/carders/scummers/spammers, etc but also by honest people like
analysts, workers of the antifraud departments, software developers,
webmasters and other people who would like to
be aware of the current ways of fraud in the internet, and protect
themselves from it. Forum is opened for all who wants to use it,
and is widely known. Status of the "Capo" member is explained at
http://www.carderplanet.com/capo.html - "..people who are included in this
part, don't take part
in the active life of our forum, but they deserve respect for to their
honesty and decency.. ".
We pay monthly for advertizing on that forum and have no other relations
with it.
Anyway if you will tell us to remove our advertizing from that forum - we
will do it immediately.
What is related to proxydialup.com and ist owner AlekseyB and Alex Blood:
Blood is a nickname of Alexander Mosh, domains were registered with the
technical contacts to Alex Blood and are not related to proxydialup.com.
I have already changed contact inforamtion to my own and I am takting all
responsibility to my name for these domains to be clean of any abusive
things.
Domain proxydialup.com was completely removed from the hosting.

If I personally tolerate spam? - absolutely NOT! As for an ordinary user of
internet and for an ordinary businessman, for me spam is annoying
sort of advertizing which intervents into the private life and causes
inconvenience to the ordinary users of
internet on the on the one hand, and is very unstable and short term
business which delivers little amount of money and
large amount of problems from the other hand as I can see due to my almost
personal experience, on the example of
Alex Mosh and already mine BBA Safe Hosting. I assume hosting business as a
stable profitable business and don't want to
have any relation to the spam, I would like to clear my name (which was
erroneously connected with spam) and and my
hosting's name as well to the internet community. I apologise for all the
misdeeds commited by BBA Safe Hosting (to be exact Pilot
Holding LLC)
and I'm ready to provide any necessary help for fighting against spam and
become the active participant of your
community. Please give me a chance to prove the innocence of BBA Safe
Hosting. Please show that you're not the
tyrants who block ASP/ISP whithout any investigation and destroying the
business, but the real fighters against
internet abuse.
I'm ready to answer any questions, and to made any changes in the hosting
you say.
Plese tell me what can I do to redress a guilt of Pilot Holding LLC, remove
us from blocklisting and develop my business with a clear name?

Sorry for my poor english and please understand that if I could say better
and more eloquent - I would certainly do that.

With best regards,
Alex Polyakov

--
Comments posted to news.admin.net-abuse.blocklisting
are solely the responsibility of their author. Please
read the news.admin.net-abuse.blocklisting FAQ at
http://www.blocklisting.com/faq.html before posting.

Alex Polyakov

未讀,
2004年1月27日 上午11:28:502004/1/27
收件者:
Hello,

I ask you to stop yourself, and not to destroy honest hosting company. We
put lot of money and power in it, pinned our hopes on it. Being anonymous
you take risk of nothing, but God is seing - you're doing wrong. You can
re-add us to blocklisting any moment, after first spam event.

What is my fault? My efforts to clean my hosting's and my personal name and
reputation? My apologies for the former sins of the company?
Is couple of letters worth destroying of buisness and leaving employee's
families without piece of bread?
For the last half of year when I'm ahead of the company there has been no
problem cases, every spam related domain has been terminated at the first
spam event.
Is that not enough to prove you that our hosting has stopped all spam
relations, and I as a owner of the company worth at least one chance.
We'll agree with any condition of cooperation.

Dear newsgroup readers,
can anyone advise us how to remove our domains from SPEWS blocklist ?

Thanks in advance,
Alex Polyakov


"Alex Polyakov" <apol...@sysvhost.com> wrote in message
news:bus8rf$229v$1...@Oxy.TM.Odessa.UA...


> Hello,
>
> My name is Alex Polyakov, I'm the owner of Pilot Holding, LLC
> (hosting bbahost.com
> (the Russian site) / bbasafehosting.com (the English site) is also known


[skipped]

ru.ig...@usask.ca

未讀,
2004年1月27日 中午12:35:552004/1/27
收件者:
Alex Polyakov <apol...@sysvhost.com> wrote:
>Hello,

>I ask you to stop yourself, and not to destroy honest hosting company. We
>put lot of money and power in it, pinned our hopes on it. Being anonymous
>you take risk of nothing, but God is seing - you're doing wrong. You can
>re-add us to blocklisting any moment, after first spam event.

>What is my fault? My efforts to clean my hosting's and my personal name and
>reputation? My apologies for the former sins of the company?
>Is couple of letters worth destroying of buisness and leaving employee's
>families without piece of bread?

The cold hard truth is that this is your problem, not anyone else's.
SPEWS is only a list. It is used by mail administrators around the
world who don't like ISPs that seem to support spamming. My point is
that it is the mail administrators' choice to use SPEWS, and they are
doing it because they don't want mail from ISPs that are suspicious.
You have the right to send e-mail, but you have no right to getting
those e-mail delivered. So, you will have to work hard at reversing
their opinion of your company.

>For the last half of year when I'm ahead of the company there has been no
>problem cases, every spam related domain has been terminated at the first
>spam event.
>Is that not enough to prove you that our hosting has stopped all spam
>relations, and I as a owner of the company worth at least one chance.

It isn't enough. You can prove that your company has stopped spamming
by proving ALL of the entries in SPEWS S2547 are now no longer on your
network. Check each entry, see if you or your clients are providing
connectivity to them (e-mail, web, dns,...), show they are no longer
on your network, or terminate their account (or tell your client to
terminate their account upon punishment of terminating your client).
You can give us progress report on your work (i.e. you don't have to
show us one big document), but I suspect only after you have finished
cleaning out that file will you be unlisted. Nothing else will work,
as far as we can tell.

>We'll agree with any condition of cooperation.

Ok, show us.

ru

--
I am not SPEWS.

adam brower

未讀,
2004年1月27日 下午1:59:202004/1/27
收件者:
Alex Polyakov wrote:
>
> Hello,
>
[snip]

> Is couple of letters worth destroying of buisness and leaving employee's
> families without piece of bread?

there are generous programs to support the indigent here
in the u.s. you are located in nevada, i believe. or is
it new hampshire?

anyway, we are in the midst of a roaring economic recovery.
(however, this recovery will screech to a halt after the
november elections, so get those resumés out right away.)

[snip]


>
> Dear newsgroup readers,
> can anyone advise us how to remove our domains from SPEWS blocklist ?
>

yes. stop providing spam support services, and return to
your victims the money you have made hosting the most
vile of thieves. blaming your misfortunes on others
will avail you naught.


adam

--

Anri Erinin

未讀,
2004年1月27日 晚上8:10:372004/1/27
收件者:
Alex Polyakov wrote:
>
> I ask you to stop yourself, and not to destroy honest hosting company. We
> put lot of money and power in it, pinned our hopes on it.

Money earned from spamming/scaming/carding.

> What is my fault? My efforts to clean my hosting's and my personal name and
> reputation? My apologies for the former sins of the company?

Your fault is engaging in spam business.

> Is couple of letters worth destroying of buisness and leaving employee's
> families without piece of bread?

Yes, couple of zillions of spams are worth destroying a spam operation.

> For the last half of year when I'm ahead of the company there has been no
> problem cases, every spam related domain has been terminated at the first
> spam event.

nanas shows that at least till 21 Sep 2003 carderportal used
ns1.bbasafehost.com. This is one third of a year ago:
http://www.google.com/groups?selm=ZkqdnerWEI2kcfCiXTWJhg%40comcast.com

You terminated spamplanet.net only after I posted this:
http://www.google.com/groups?selm=buu2ht%24lm226%241%40ID-115151.news.uni-berlin.de
this is 1/120 of an year ago.

When it was carderplanet moved from your hosting?

> Is that not enough to prove you that our hosting has stopped all spam
> relations, and I as a owner of the company worth at least one chance.

Every spam complaint sent to your abuse addy had given you a chance. You
missed them all.

> We'll agree with any condition of cooperation.

Change your name and start a new company.

--
Yes, I do have a spellchequer

SomeOne... or Other!

未讀,
2004年1月28日 清晨7:01:532004/1/28
收件者:
To news.admin.net-abuse.blocklisting subscribers,

> From: Alex Polyakov <apol...@sysvhost.com>,

> Is that not enough to prove you that our hosting has stopped all spam
> relations, and I as a owner of the company worth at least one chance.
> We'll agree with any condition of cooperation.

I'll answer your question more kindly.

This is a bad place to ask about 'second chances' as nanab (a.k.a
news.admin.net-abuse.blocklisting) is frequented by hardliners. Some
said hardliners feel no penalty is too great if less spam results, and
are very ready to say so.

Eradicating spammers from your network isn't just to please the
hardliners; it's to please everyone. Spam is consistently in the Top 5
'Internet Woes' when users are surveyed. This is an opportunity to be
part of the solution.

Once the spammers are gone (_all_ services terminated), come here and
say so (detailing the SPEWS record number(s)) and give an indication of
how you will help stop them returning to your network. Refuse service
to known spammers? Measures to enforce anti-abuse provisions of your
Terms of Service/Acceptable Use Policy? Active monitoring and
investigation of _all_ abuse reports? All of these make a good start.

You can't change the past, but present and future are under your
control. Ignore the rhetoric on sins of the past, focus on the problem
at hand, and stop the spammers. The rhetoric will disappear of its own
accord. As will - based on past experience only - the SPEWS listing(s).

SomeOne... or Other!

Alex Polyakov

未讀,
2004年1月28日 下午3:20:592004/1/28
收件者:
Hello Adam,

unfortunately, all the hosting staff lives and works in Ukraine, not in USA.
Life standarts in Ukraine is too low, average salary makes 45$/month. Pilot
Holding, LLC is really registered in USA, Nevada as an offshore company but
none of us lives there.

The company has stopped all relations with spam and spammers from the moment
I've purchased it (~ 6 months ago). I apologise once more for the former
activities of the company, they're not compatible with my understanding of
internet business basics.
Please understand that your proposition of returning money is not possible
in our condition. Though I'd do it if I had such a possibility. I ask to
forgive us, once more.

With best regards,
Alex Polyakov


"adam brower" <ad...@hermes-grp.com> wrote in message
news:4016C903...@hermes-grp.com...

Alex Polyakov

未讀,
2004年1月28日 下午5:44:352004/1/28
收件者:
Hello Anri,


"Anri Erinin" <spamme...@rambler.ru> wrote in message
news:bv6ftm$njbrd$1...@ID-115151.news.uni-berlin.de...


> Alex Polyakov wrote:
> >
> > I ask you to stop yourself, and not to destroy honest hosting company.
We
> > put lot of money and power in it, pinned our hopes on it.
>
> Money earned from spamming/scaming/carding.


I invested my own money, I have made by honest, legal work. I've never dealt
with "spamming/scaming/carding", please stop blackening my name. I've just
bought this company, which hosted spam-related sites before I bought it. I
knew what I was doing and what dificulties I might meet. And all of us spent
this half of year to make it possible to prove that our company is not
dealing with spam/spammers anymore.


>
> > What is my fault? My efforts to clean my hosting's and my personal name
and
> > reputation? My apologies for the former sins of the company?
>
> Your fault is engaging in spam business.
>
> > Is couple of letters worth destroying of buisness and leaving employee's
> > families without piece of bread?
>
> Yes, couple of zillions of spams are worth destroying a spam operation.

Once more I ask you personally and all internet community to forgive my
company for helping spammers in past. I've found no traces of mailings from
Pilot Holding, LLC (BBA Safe Hosting) name, as well as traces of spam
advertizing of sites of my company. The man who led the company before me,
Alex Mosh assured me that there were just failed efforts of hosting
direct-marketing sites, now I see that it was not complete information, and
apologise for it. I'd like to make a stress on the fact that my company is
not dealing with spam/spammers already for a half of year. Look when was the
last record of spam events connected with my company name ?


>
> > For the last half of year when I'm ahead of the company there has been
no
> > problem cases, every spam related domain has been terminated at the
first
> > spam event.
>
> nanas shows that at least till 21 Sep 2003 carderportal used
> ns1.bbasafehost.com. This is one third of a year ago:
> http://www.google.com/groups?selm=ZkqdnerWEI2kcfCiXTWJhg%40comcast.com
>
> You terminated spamplanet.net only after I posted this:
>
http://www.google.com/groups?selm=buu2ht%24lm226%241%40ID-115151.news.uni-be
rlin.de
> this is 1/120 of an year ago.
>
> When it was carderplanet moved from your hosting?
>

Please understand that we have automated control system (H-SPHERE Control
Panel), using which users can regiter, re-regiter, transfer, park (add dns
zones for domaint located at another hosting, server, network, etc., that
have no relations with our hosting) and delete domains in their accounts.
Actually number of domains is so great that neither I nor my colleagues
can't watch them all. I can provide anyone who would like it with a test
account, so you can check it yourself. At the first abuse for any domain on
aour hostng, account containing that domain is beeing deleted without
warning. I don't want to have any relations with spam or any kind of fraud.
Spamplanet was hosted at our company but unfortunately I learned about it
only after your post and terminated this account immediately before it was
blocklisted anywhere.

Now we have checked all domains and wrote scripts, notifying administrators
about creating domains containing words "spam/carding/fraud/scum" and
watching attentively not to let hosting such domains.


> > Is that not enough to prove you that our hosting has stopped all spam
> > relations, and I as a owner of the company worth at least one chance.
>
> Every spam complaint sent to your abuse addy had given you a chance. You
> missed them all.
>

I can assure you that every complain that our hosting or datacenter have
received during my ownership of the company was satisfied and domains and
accounts causing abuses were immediately terminated.

> > We'll agree with any condition of cooperation.
>
> Change your name and start a new company.
>

It's not the thing I'm talking about. I'm trying to clear my name from false
connections and prove you that BBA Safe Hosting is worth beeing removed from
blocklists.


> --
> Yes, I do have a spellchequer
>
>
>
> --
> Comments posted to news.admin.net-abuse.blocklisting
> are solely the responsibility of their author. Please
> read the news.admin.net-abuse.blocklisting FAQ at
> http://www.blocklisting.com/faq.html before posting.
>

With best regards,
Alex Polyakov


Anri Erinin

未讀,
2004年1月28日 下午6:03:432004/1/28
收件者:
Alex Polyakov wrote:

>
> The company has stopped all relations with spam and spammers from the moment
> I've purchased it (~ 6 months ago).

This is a blatant lie. Dare to say something more about c4 team? Dare to
say when you terminated spamplanet.net?

easyandquickloans.com has address 66.98.142.14
nslookup 66.98.142.14
Canonical name: webbear.sysvhost.com
Addresses: 66.98.142.14

The page with fresh, continuously updated list of trojaned proxies on
nonstandard ports http://onyx1.sysvhost.com/socks.php was up on 14 Jan 2004.

http://board.gulli.com/thread/277780
Posted on 23. 12. 2003 12:20

Hier ein Weihnachtsgeschenk fu"r alle
100% anonyme Socks5 server
100% keine Logdaten
keine standart-ports
werden jede Sekunde u"berpru"ft und automatisch ersetzt!

http://onyx1.sysvhost.com/socks.php
http://onyx1.sysvhost.com/socks1.php - befindet sich noch im beta-test

And is still live at:

69.56.247.190/proj/stat-live.cgi/live.txt

NetRange: 69.56.128.0 - 69.56.255.255
CIDR: 69.56.128.0/17
NetName: NETBLK-THEPLANET-BLK-6
NetHandle: NET-69-56-128-0-1
Parent: NET-69-0-0-0-0
NetType: Direct Allocation
NameServer: NS1.THEPLANET.COM
NameServer: NS2.THEPLANET.COM
Comment:
RegDate: 2003-06-10
Updated: 2003-09-29


--
Yes, I do have a spellchequer

Alex Polyakov

未讀,
2004年1月29日 清晨6:57:222004/1/29
收件者:
Hello ru,

thanks for your answer. I completle understand the both the purpose of
SPEWS and its authority. It's not just a list, it's one of the most widely
used lists, and if you're listed in it not many datacenters will agree to
host your servers. We would use it by ourserves if it wouldn't block our own
mail. Now we're using spam assasin to filter spam. And yes, my colleagues
and I are ready to work hard to reverse opinion about our company.

Here's the first part of the result of checking S2547 entries:

---------------------------------------------

1, 216.65.107.39, auragirls.com /* Dead */ hostonfly.net


auragirls.com. 66111 IN NS ns1.hostonfly.net.
auragirls.com. 66111 IN NS ns2.hostonfly.net.
auragirls.com. 66111 IN NS ns1.hostonfly.net.
auragirls.com. 66111 IN NS ns2.hostonfly.net.
ns1.hostonfly.net. 132749 IN A 65.19.167.135 /* Not in our
hosting's network */
ns2.hostonfly.net. 132749 IN A 65.19.167.118 /* Not in our
hosting's network */
auragirls.com. 86400 IN MX 20 mail2.hostonfly.net.
auragirls.com. 86400 IN MX 10 mail1.hostonfly.net.


hostonfly.net. 82406 IN NS ns1.hostonfly.net.
hostonfly.net. 82406 IN NS ns2.hostonfly.net.
hostonfly.net. 82515 IN MX 10 mail2.hostonfly.net.
hostonfly.net. 82515 IN MX 20 mail1.hostonfly.net.
hostonfly.net. 82406 IN NS ns1.hostonfly.net.
hostonfly.net. 82406 IN NS ns2.hostonfly.net.
ns1.hostonfly.net. 132749 IN A 65.19.167.135 /* Not in our
hosting's network */
ns2.hostonfly.net. 132749 IN A 65.19.167.118 /* Not in our
hosting's network */
mail2.hostonfly.net. 82515 IN A 65.19.167.116 /* Not in our
hosting's network */
mail1.hostonfly.net. 82515 IN A 65.19.167.115 /* Not in our
hosting's network */

---------------------------------------------

1, 216.65.107.31, awmpartner.com hostonfly.net x-shop-x.com


awmpartner.com. 172594 IN NS invalid-address.joker.com.
awmpartner.com. 172594 IN NS invalid-address.joker.com.
invalid-address.joker.com. 3682 IN A 194.176.0.5 /* Not in our
hosting's network */
awmpartner.com. IN MX


hostonfly.net. 82406 IN NS ns1.hostonfly.net.
hostonfly.net. 82406 IN NS ns2.hostonfly.net.
hostonfly.net. 82515 IN MX 10 mail2.hostonfly.net.
hostonfly.net. 82515 IN MX 20 mail1.hostonfly.net.
hostonfly.net. 82406 IN NS ns1.hostonfly.net.
hostonfly.net. 82406 IN NS ns2.hostonfly.net.
ns1.hostonfly.net. 132749 IN A 65.19.167.135 /* Not in our
hosting's network */
ns2.hostonfly.net. 132749 IN A 65.19.167.118 /* Not in our
hosting's network */
mail2.hostonfly.net. 82515 IN A 65.19.167.116 /* Not in our
hosting's network */
mail1.hostonfly.net. 82515 IN A 65.19.167.115 /* Not in our
hosting's network */


x-shop-x.com. 160027 IN NS ns1.hostonfly.net.
x-shop-x.com. 160027 IN NS ns2.hostonfly.net.
x-shop-x.com. 160027 IN NS ns1.hostonfly.net.
x-shop-x.com. 160027 IN NS ns2.hostonfly.net.
x-shop-x.com. 86400 IN MX 10 mail1.hostonfly.net.
x-shop-x.com. 86400 IN MX 20 mail2.hostonfly.net.
ns1.hostonfly.net. 132749 IN A 65.19.167.135 /* Not in our
hosting's network */
ns2.hostonfly.net. 132749 IN A 65.19.167.118 /* Not in our
hosting's network */

---------------------------------------------

1, 216.65.107.43, ionizer.x-shop-x.com


ionizer.x-shop-x.com. 19 IN A 216.65.107.95 /* Not in our
hosting's network */
x-shop-x.com. 160026 IN NS ns1.hostonfly.net.
x-shop-x.com. 160026 IN NS ns2.hostonfly.net.
ns1.hostonfly.net. 132748 IN A 65.19.167.135 /* Not in our
hosting's network */
ns2.hostonfly.net. 132748 IN A 65.19.167.118 /* Not in our
hosting's network */
ionizer.x-shop-x.com. IN MX
---------------------------------------------

1, 216.65.107.0 26, Maxim auragirls.com hostonfly.net


auragirls.com. 66110 IN NS ns1.hostonfly.net.
auragirls.com. 66110 IN NS ns2.hostonfly.net.
auragirls.com. 66110 IN NS ns1.hostonfly.net.
auragirls.com. 66110 IN NS ns2.hostonfly.net.
ns1.hostonfly.net. 132748 IN A 65.19.167.135 /* Not in our
hosting's network */
ns2.hostonfly.net. 132748 IN A 65.19.167.118 /* Not in our
hosting's network */
auragirls.com. 86400 IN MX 20 mail2.hostonfly.net.
auragirls.com. 86400 IN MX 10 mail1.hostonfly.net.

hostonfly.net. 82405 IN NS ns1.hostonfly.net.
hostonfly.net. 82405 IN NS ns2.hostonfly.net.
hostonfly.net. 82514 IN MX 10 mail2.hostonfly.net.
hostonfly.net. 82514 IN MX 20 mail1.hostonfly.net.
hostonfly.net. 82405 IN NS ns1.hostonfly.net.
hostonfly.net. 82405 IN NS ns2.hostonfly.net.
ns1.hostonfly.net. 132748 IN A 65.19.167.135 /* Not in our
hosting's network */
ns2.hostonfly.net. 132748 IN A 65.19.167.118 /* Not in our
hosting's network */
mail2.hostonfly.net. 82514 IN A 65.19.167.116 /* Not in our
hosting's network */
mail1.hostonfly.net. 82514 IN A 65.19.167.115 /* Not in our
hosting's network */


---------------------------------------------

2, 216.65.106.0 - 216.65.108.255, Maxim awmpartner.com hostonfly.net


awmpartner.com. 172593 IN NS invalid-address.joker.com.
awmpartner.com. 172593 IN NS invalid-address.joker.com.
invalid-address.joker.com. 3681 IN A 194.176.0.5 /* Not in our
hosting's network */
awmpartner.com. IN MX

hostonfly.net. 82404 IN NS ns1.hostonfly.net.
hostonfly.net. 82404 IN NS ns2.hostonfly.net.
hostonfly.net. 82513 IN MX 10 mail2.hostonfly.net.
hostonfly.net. 82513 IN MX 20 mail1.hostonfly.net.
hostonfly.net. 82404 IN NS ns1.hostonfly.net.
hostonfly.net. 82404 IN NS ns2.hostonfly.net.
ns1.hostonfly.net. 132747 IN A 65.19.167.135 /* Not in our
hosting's network */
ns2.hostonfly.net. 132747 IN A 65.19.167.118 /* Not in our
hosting's network */
mail2.hostonfly.net. 82513 IN A 65.19.167.116 /* Not in our
hosting's network */
mail1.hostonfly.net. 82513 IN A 65.19.167.115 /* Not in our
hosting's network */


---------------------------------------------

1, 211.73.8.16, ns3.dnsflyer.com ip-mail.com
ns3.dnsflyer.com. 172597 IN A 211.73.8.12
dnsflyer.com. 172597 IN NS ns1.dnsflyer.com.
dnsflyer.com. 172597 IN NS ns2.dnsflyer.com.
dnsflyer.com. 172597 IN NS ns3.dnsflyer.com.
dnsflyer.com. 172597 IN NS ns4.dnsflyer.com.
dnsflyer.com. 172597 IN NS ns5.dnsflyer.com.
dnsflyer.com. 172597 IN NS ns6.dnsflyer.com.
ns1.dnsflyer.com. 172597 IN A 195.5.22.228 /* Not in our
hosting's network */
ns2.dnsflyer.com. 172597 IN A 202.128.64.107 /* Not in our
hosting's network */
ns3.dnsflyer.com. 172597 IN A 211.73.8.12 /* Not in our
hosting's network */
ns4.dnsflyer.com. 172597 IN A 195.5.40.247 /* Not in our
hosting's network */
ns5.dnsflyer.com. 133526 IN A 217.6.115.178 /* Not in our
hosting's network */
ns6.dnsflyer.com. 172597 IN A 217.73.8.16 /* Not in our
hosting's network */


ip-mail.com. 160093 IN NS dns1.name-services.com.
ip-mail.com. 160093 IN NS dns2.name-services.com.
ip-mail.com. 160093 IN NS dns3.name-services.com.
ip-mail.com. 160093 IN NS dns4.name-services.com.
ip-mail.com. 160093 IN NS dns5.name-services.com.
ip-mail.com. 25 IN MX 10 mail.ip-mail.com.
ip-mail.com. 96 IN A 80.96.162.66 /* Not in our
hosting's network */
ip-mail.com. 160093 IN NS dns1.name-services.com.
ip-mail.com. 160093 IN NS dns2.name-services.com.
ip-mail.com. 160093 IN NS dns3.name-services.com.
ip-mail.com. 160093 IN NS dns4.name-services.com.
ip-mail.com. 160093 IN NS dns5.name-services.com.
dns1.name-services.com. 16036 IN A 63.251.163.102 /* Not in our
hosting's network */
dns2.name-services.com. 124831 IN A 216.52.184.230 /* Not in our
hosting's network */
dns3.name-services.com. 16036 IN A 63.251.83.36 /* Not in our
hosting's network */
dns4.name-services.com. 1965 IN A 64.74.96.242 /* Not in our
hosting's network */
dns5.name-services.com. 92101 IN A 212.118.244.163 /* Not in
our hosting's network */
dns5.name-services.com. 92101 IN A 212.118.244.164 /* Not in
our hosting's network */
dns5.name-services.com. 92101 IN A 212.118.244.169 /* Not in
our hosting's network */
mail.ip-mail.com. 25 IN A 80.96.162.66 /* Not in our
hosting's network */
--------------------------------------------
1, 211.73.8.12, ns3.dnsflyer.com
savecom.net.tw. 73714 IN NS dns.savecom.net.tw.
savecom.net.tw. 73714 IN NS dns1.savecom.net.tw.
savecom.net.tw. 73714 IN A 211.73.23.3 /* Not in our
hosting's network */
savecom.net.tw. 73714 IN MX 0 mail.savecom.net.tw.
savecom.net.tw. 73714 IN MX 20 wm1.savecom.net.tw.
savecom.net.tw. 73714 IN MX 30 tutelar.savecom.net.tw.
savecom.net.tw. 73714 IN NS dns.savecom.net.tw.
savecom.net.tw. 73714 IN NS dns1.savecom.net.tw.
dns.savecom.net.tw. 73713 IN A 211.73.31.7 /* Not in our
hosting's network */
dns1.savecom.net.tw. 73713 IN A 211.73.31.8 /* Not in our
hosting's network */
mail.savecom.net.tw. 73714 IN A 211.73.23.3 /* Not in our
hosting's network */
wm1.savecom.net.tw. 73714 IN A 211.73.23.40 /* Not in our
hosting's network */
tutelar.savecom.net.tw. 73714 IN A 211.73.23.8 /* Not in our
hosting's network */


ns3.dnsflyer.com. 172596 IN A 211.73.8.12 /* Not in our
hosting's network */
dnsflyer.com. 172596 IN NS ns1.dnsflyer.com.
dnsflyer.com. 172596 IN NS ns2.dnsflyer.com.
dnsflyer.com. 172596 IN NS ns3.dnsflyer.com.
dnsflyer.com. 172596 IN NS ns4.dnsflyer.com.
dnsflyer.com. 172596 IN NS ns5.dnsflyer.com.
dnsflyer.com. 172596 IN NS ns6.dnsflyer.com.
ns1.dnsflyer.com. 172596 IN A 195.5.22.228 /* Not in our
hosting's network */
ns2.dnsflyer.com. 172596 IN A 202.128.64.107 /* Not in our
hosting's network */
ns3.dnsflyer.com. 172596 IN A 211.73.8.12 /* Not in our
hosting's network */
ns4.dnsflyer.com. 172596 IN A 195.5.40.247 /* Not in our
hosting's network */
ns5.dnsflyer.com. 133525 IN A 217.6.115.178 /* Not in our
hosting's network */
ns6.dnsflyer.com. 172596 IN A 217.73.8.16 /* Not in our
hosting's network */

---------------------------------------------

2, 211.73.0.0 - 211.73.31.255, savecom.net.tw ns3.dnsflyer.com
ip-mail.com
savecom.net.tw. 73713 IN NS dns.savecom.net.tw.
savecom.net.tw. 73713 IN NS dns1.savecom.net.tw.
savecom.net.tw. 73713 IN A 211.73.23.3
savecom.net.tw. 73713 IN MX 0 mail.savecom.net.tw.
savecom.net.tw. 73713 IN MX 20 wm1.savecom.net.tw.
savecom.net.tw. 73713 IN MX 30 tutelar.savecom.net.tw.
savecom.net.tw. 73713 IN NS dns.savecom.net.tw.
savecom.net.tw. 73713 IN NS dns1.savecom.net.tw.
dns.savecom.net.tw. 73712 IN A 211.73.31.7 /* Not in our
hosting's network */
dns1.savecom.net.tw. 73712 IN A 211.73.31.8 /* Not in our
hosting's network */
mail.savecom.net.tw. 73713 IN A 211.73.23.3 /* Not in our
hosting's network */
wm1.savecom.net.tw. 73713 IN A 211.73.23.40 /* Not in our
hosting's network */
tutelar.savecom.net.tw. 73713 IN A 211.73.23.8 /* Not in our
hosting's network */

---------------------------------------------

1, 195.5.40.247, ns5.dnsflyer.com
ns5.dnsflyer.com. 172776 IN A 217.6.115.178 /* Not in our
hosting's network */
dnsflyer.com. 172776 IN NS ns1.dnsflyer.com.
dnsflyer.com. 172776 IN NS ns2.dnsflyer.com.
dnsflyer.com. 172776 IN NS ns3.dnsflyer.com.
dnsflyer.com. 172776 IN NS ns4.dnsflyer.com.
dnsflyer.com. 172776 IN NS ns5.dnsflyer.com.
dnsflyer.com. 172776 IN NS ns6.dnsflyer.com.
ns1.dnsflyer.com. 172776 IN A 195.5.22.228 /* Not in our
hosting's network */
ns2.dnsflyer.com. 172776 IN A 202.128.64.107 /* Not in our
hosting's network */
ns3.dnsflyer.com. 172776 IN A 211.73.8.12 /* Not in our
hosting's network */
ns4.dnsflyer.com. 172776 IN A 195.5.40.247 /* Not in our
hosting's network */
ns5.dnsflyer.com. 172776 IN A 217.6.115.178 /* Not in our
hosting's network */
ns6.dnsflyer.com. 172776 IN A 217.73.8.16 /* Not in our
hosting's network */

---------------------------------------------

1, 195.5.38.0 - 195.5.40.255, ukrtel.net ns5.dnsflyer.com
ukrtel.net. 130039 IN NS expert.ukrtel.net.
ukrtel.net. 130039 IN NS ns2.eu.concert.net.
ukrtel.net. 130039 IN NS ns.cw.net.
ukrtel.net. 130039 IN NS ckt.ukrtel.net.
ukrtel.net. 139393 IN A 195.5.6.10 /* Not in our
hosting's network */
ukrtel.net. 139394 IN MX 30
mail-fallback.eu.concert.net.
ukrtel.net. 139394 IN MX 10 expert.ukrtel.net.
ukrtel.net. 130039 IN NS expert.ukrtel.net.
ukrtel.net. 130039 IN NS ns2.eu.concert.net.
ukrtel.net. 130039 IN NS ns.cw.net.
ukrtel.net. 130039 IN NS ckt.ukrtel.net.
expert.ukrtel.net. 127247 IN A 195.5.6.10 /* Not in our
hosting's network */
ns2.eu.concert.net. 54149 IN A 195.99.65.212 /* Not in our
hosting's network */
ns.cw.net. 129341 IN A 204.70.128.1 /* Not in our
hosting's network */
ckt.ukrtel.net. 15362 IN A 195.5.6.16 /* Not in our
hosting's network */
mail-fallback.eu.concert.net. 3419 IN A 195.99.66.214 /* Not in our
hosting's network */

---------------------------------------------

1, 216.180.242.250, e-bulk.net caleb.host2010.com dead?

/* Dead */

---------------------------------------------

2, 216.180.242.0 25, e-bulk.net /* Dead */ dv2.net

dv2.net. 3419 IN MX 10 atlmail.dv2.net.
dv2.net. 3419 IN MX 20 mail2.dv2.net.
dv2.net. 3419 IN A 209.51.128.151 /* Not in our
hosting's network */
dv2.net. 3419 IN NS dns2.gnax.net.
dv2.net. 3419 IN NS dns1.gnax.net.
dv2.net. 3419 IN NS dns2.gnax.net.
dv2.net. 3419 IN NS dns1.gnax.net.
atlmail.dv2.net. 72521 IN A 209.51.128.18 /* Not in our
hosting's network */
mail2.dv2.net. 3419 IN A 209.51.128.8 /* Not in our
hosting's network */
dns2.gnax.net. 51796 IN A 209.51.128.18 /* Not in our
hosting's network */
dns1.gnax.net. 51796 IN A 209.51.128.17 /* Not in our
hosting's network */


---------------------------------------------

1, 216.240.146.8, ns2.bbasafehost.com pgsql.bbasafehost.com /* Dead */
www.proxydialup.com /* Dead */


ns2.bbasafehost.com. 66413 IN A 64.46.116.1 /* Dead */


---------------------------------------------

1, 216.240.148.20, dedicated03.sysvhost.com

/* Dead */

--------------------------------------------
1, 216.240.148.196, pilotholding.com /* Dead */ ns2.bbasafehost.com /*
Dead */ bbahost.com /* Dead */ calpop.com

calpop.com. 160250 IN NS ns1.calpop.com.
calpop.com. 160250 IN NS ns2.calpop.com.
calpop.com. 160250 IN NS ns3.calpop.com.
calpop.com. 160250 IN NS ns4.calpop.com.
calpop.com. 160250 IN NS ns1.calpop.com.
calpop.com. 160250 IN NS ns2.calpop.com.
calpop.com. 160250 IN NS ns3.calpop.com.
calpop.com. 160250 IN NS ns4.calpop.com.
ns1.calpop.com. 58937 IN A 216.240.130.2 /* Not in our
hosting's network */
ns2.calpop.com. 58937 IN A 216.240.150.2 /* Not in our
hosting's network */
ns3.calpop.com. 58937 IN A 216.240.152.3 /* Not in our
hosting's network */
ns4.calpop.com. 58937 IN A 216.240.152.4 /* Not in our
hosting's network */
calpop.com. 86400 IN MX 10 mail-netops.calpop.com.

---------------------------------------------

1, 216.240.148.197, mail.bbasafehost.com /* Dead */ calpop.com


calpop.com. 160250 IN NS ns1.calpop.com.
calpop.com. 160250 IN NS ns2.calpop.com.
calpop.com. 160250 IN NS ns3.calpop.com.
calpop.com. 160250 IN NS ns4.calpop.com.
calpop.com. 160250 IN NS ns1.calpop.com.
calpop.com. 160250 IN NS ns2.calpop.com.
calpop.com. 160250 IN NS ns3.calpop.com.
calpop.com. 160250 IN NS ns4.calpop.com.
ns1.calpop.com. 58937 IN A 216.240.130.2
ns2.calpop.com. 58937 IN A 216.240.150.2
ns3.calpop.com. 58937 IN A 216.240.152.3
ns4.calpop.com. 58937 IN A 216.240.152.4
calpop.com. 86400 IN MX 10 mail-netops.calpop.com.

---------------------------------------------

2, 216.240.148.0 24, calpop.com mail.bbasafehost.com /* Dead */


---------------------------------------------

1, 216.240.151.63, dedicated01.sysvhost.com

/* Dead */
---------------------------------------------

1, 216.240.151.67, dedicated02.sysvhost.com

/* Dead */
---------------------------------------------

2, 216.240.151.0 25, calpop.com dedicated02.sysvhost.com /* Dead */

---------------------------------------------
1, 64.46.113.132, dark-desires.com on datacolo.com spam house
dark-desires.com. 66901 IN NS ns1.privhosting.com.
dark-desires.com. 66901 IN NS ns2.privhosting.com.
dark-desires.com. 66901 IN NS ns1.privhosting.com.
dark-desires.com. 66901 IN NS ns2.privhosting.com.
ns1.privhosting.com. 21540 IN A 216.17.101.206 /* Not in our
hosting's network */
ns2.privhosting.com. 2909 IN A 216.17.101.206 /* Not in our
hosting's network */
dark-desires.com. 3600 IN MX 10 mail.dark-desires.com.
dark-desires.com. 62454 IN NS ns1.privhosting.com.
dark-desires.com. 62454 IN NS ns2.privhosting.com.
mail.dark-desires.com. 3600 IN A 216.17.101.206 /* Not in our
hosting's network */


datacolo.com. 117232 IN NS ns.datacolo.com.
datacolo.com. 117232 IN NS ns2.datacolo.com.
datacolo.com. 117232 IN NS ns.datacolo.com.
datacolo.com. 117232 IN NS ns2.datacolo.com.
ns.datacolo.com. 123403 IN A 64.46.101.30 /* Not in our
hosting's network */
ns2.datacolo.com. 123403 IN A 64.46.101.31 /* Not in our
hosting's network */

--------------------------------------------

1, 64.46.116.235, ns.easyboy.net on datacolo.com spam house
ns.easyboy.net. 67299 IN A 64.46.116.235 /* Dead */

datacolo.com. 6147 IN A 64.46.101.33 /* Not in our
hosting's network */
datacolo.com. 19244 IN NS ns.datacolo.com.
datacolo.com. 19244 IN NS ns2.datacolo.com.
datacolo.com. 19244 IN NS ns.datacolo.com.
datacolo.com. 19244 IN NS ns2.datacolo.com.
ns.datacolo.com. 172800 IN A 64.46.101.30 /* Not in our
hosting's network */
ns2.datacolo.com. 172800 IN A 64.46.101.31 /* Not in our
hosting's network */

---------------------------------------------

1, 64.46.116.250, ns2.easyboy.net on datacolo.com spam house
ns2.easyboy.net. 67311 IN A 64.46.116.250 /* Dead */

---------------------------------------------

1, 64.46.116.1, mail.proxydialup.com /* Dead */ mail.sysvhost.com /* Dead
*/ mail.bbasafehost.com /* Dead */


---------------------------------------------

1, 64.46.100.90, mail.advsites.net /* Dead */ NS1.BBASAFEHOST.COM /* Dead
*/ web02.sysvhost.com /* Dead */ on listed datacolo 3DWizards dsm spam
house

NS1.BBASAFEHOST.COM. 130684 IN A 64.46.100.90 /* Dead */


---------------------------------------------

1, 195.138.168.249, 1000freenotes.com odtel.net uptel.net
1000freenotes.com. 67465 IN NS dns1.name-services.com.
1000freenotes.com. 67465 IN NS dns2.name-services.com.
1000freenotes.com. 67465 IN NS dns3.name-services.com.
1000freenotes.com. 67465 IN NS dns4.name-services.com.
1000freenotes.com. 67465 IN NS dns5.name-services.com.
1000freenotes.com. 67465 IN NS dns1.name-services.com.
1000freenotes.com. 67465 IN NS dns2.name-services.com.
1000freenotes.com. 67465 IN NS dns3.name-services.com.
1000freenotes.com. 67465 IN NS dns4.name-services.com.
1000freenotes.com. 67465 IN NS dns5.name-services.com.
dns1.name-services.com. 16020 IN A 63.251.163.102 /* Not in our
hosting's network */
dns2.name-services.com. 124815 IN A 216.52.184.230 /* Not in our
hosting's network */
dns3.name-services.com. 16020 IN A 63.251.83.36 /* Not in our
hosting's network */
dns4.name-services.com. 1949 IN A 64.74.96.242 /* Not in our
hosting's network */
dns5.name-services.com. 92085 IN A 212.118.244.163 /* Not in
our hosting's network */
dns5.name-services.com. 92085 IN A 212.118.244.164 /* Not in
our hosting's network */
dns5.name-services.com. 92085 IN A 212.118.244.169 /* Not in
our hosting's network */
1000freenotes.com. 3601 IN MX 10
eforward2.name-services.com.
1000freenotes.com. 3601 IN MX 10
eforward1.name-services.com.
eforward1.name-services.com. 144 IN A 63.251.163.114 /* Not in our
hosting's network */
eforward2.name-services.com. 144 IN A 216.52.184.242 /* Not in our
hosting's network */

odtel.net. 31217 IN MX 40 relay4.paco.net.
odtel.net. 31217 IN MX 10 relay.odtel.net.
odtel.net. 31217 IN MX 30 relay.tn.odessa.ua.
odtel.net. 31888 IN NS ns.odtel.net.
odtel.net. 31888 IN NS ns2.odtel.net.
odtel.net. 31888 IN NS ns.tn.odessa.ua.
odtel.net. 31888 IN NS ns.odessa.ua.
odtel.net. 31888 IN NS ns.odtel.net.
odtel.net. 31888 IN NS ns2.odtel.net.
odtel.net. 31888 IN NS ns.tn.odessa.ua.
odtel.net. 31888 IN NS ns.odessa.ua.
relay4.paco.net. 30815 IN A 195.114.128.45 /* Not in our
hosting's network */
relay.odtel.net. 12693 IN A 195.138.160.43 /* Not in our
hosting's network */
ns.odtel.net. 33417 IN A 195.138.160.42 /* Not in our
hosting's network */
ns2.odtel.net. 31888 IN A 195.138.160.5 /* Not in our
hosting's network */
ns.tn.odessa.ua. 10247 IN A 195.138.160.3 /* Not in our
hosting's network */
ns.odessa.ua. 27400 IN A 195.114.128.50 /* Not in our
hosting's network */


uptel.net. 2871 IN NS ns.tn.odessa.ua.
uptel.net. 2871 IN NS ns.odtel.net.
uptel.net. 2871 IN NS ns.uptel.net.
uptel.net. 2871 IN NS ns.odessa.ua.
uptel.net. 2871 IN NS ns2.odtel.net.
uptel.net. 2871 IN NS ns.tn.odessa.ua.
uptel.net. 2871 IN NS ns.odtel.net.
uptel.net. 2871 IN NS ns.uptel.net.
uptel.net. 2871 IN NS ns.odessa.ua.
uptel.net. 2871 IN NS ns2.odtel.net.
ns.tn.odessa.ua. 10247 IN A 195.138.160.3 /* Not in our
hosting's network */
ns.odtel.net. 33417 IN A 195.138.160.42 /* Not in our
hosting's network */
ns.uptel.net. 102136 IN A 195.138.160.50 /* Not in our
hosting's network */
ns.odessa.ua. 27400 IN A 195.114.128.50 /* Not in our
hosting's network */
ns2.odtel.net. 31888 IN A 195.138.160.5 /* Not in our
hosting's network */
uptel.net. 3600 IN MX 20 relay.tn.odessa.ua. /*
Not in our hosting's network */
uptel.net. 3600 IN MX 50 relay.paco.net. /* Not in
our hosting's network */
uptel.net. 3600 IN MX 10 relay.uptel.net. /* Not
in our hosting's network */
relay.paco.net. 8013 IN A 195.114.128.20 /* Not in our
hosting's network */
relay.uptel.net. 1961 IN A 195.138.160.43 /* Not in our
hosting's network */

relay.tn.odessa.ua 195.138.160.3 /* Not in our hosting's network */
--------------------------------------------------
1, 195.138.168.252, ns1.dnsflyer.com witchtower.dark-desires.com ptrdname
= hydra.vc.ukrtel.net odtel.net uptel.net
ns1.dnsflyer.com. 65983 IN A 195.5.22.228 /* Not in our
hosting's network */
dnsflyer.com. 65983 IN NS ns1.dnsflyer.com.
dnsflyer.com. 65983 IN NS ns2.dnsflyer.com.
dnsflyer.com. 65983 IN NS ns3.dnsflyer.com.
dnsflyer.com. 65983 IN NS ns4.dnsflyer.com.
dnsflyer.com. 65983 IN NS ns5.dnsflyer.com.
dnsflyer.com. 65983 IN NS ns6.dnsflyer.com.
ns1.dnsflyer.com. 65983 IN A 195.5.22.228 /* Not in our
hosting's network */
ns2.dnsflyer.com. 65983 IN A 202.128.64.107 /* Not in our
hosting's network */
ns3.dnsflyer.com. 65983 IN A 211.73.8.12 /* Not in our
hosting's network */
ns4.dnsflyer.com. 65983 IN A 195.5.40.247 /* Not in our
hosting's network */
ns5.dnsflyer.com. 65983 IN A 217.6.115.178 /* Not in our
hosting's network */
ns6.dnsflyer.com. 65983 IN A 217.73.8.16 /* Not in our
hosting's network */

--------------------------------------------------
hydra.vc.ukrtel.net. 71301 IN A 213.179.228.11 /* Not in our
hosting's network */
vc.ukrtel.net. 32048 IN NS ns.vc.ukrtel.net.
vc.ukrtel.net. 32048 IN NS ns2.vc.ukrtel.net.
vc.ukrtel.net. 32048 IN NS ns3.vc.ukrtel.net.
vc.ukrtel.net. 32048 IN NS expert.ukrtel.net.
ns.vc.ukrtel.net. 14459 IN A 213.179.228.1 /* Not in our
hosting's network */
ns2.vc.ukrtel.net. 32048 IN A 213.179.228.2 /* Not in our
hosting's network */
ns3.vc.ukrtel.net. 32048 IN A 213.179.228.11 /* Not in our
hosting's network */
expert.ukrtel.net. 127236 IN A 195.5.6.10 /* Not in our
hosting's network */

---------------------------------------------

1, 195.138.168.0 25, ns1.dnsflyer.com

ns1.dnsflyer.com. 65981 IN A 195.5.22.228 /* Not in our
hosting's network */
dnsflyer.com. 65981 IN NS ns1.dnsflyer.com.
dnsflyer.com. 65981 IN NS ns2.dnsflyer.com.
dnsflyer.com. 65981 IN NS ns3.dnsflyer.com.
dnsflyer.com. 65981 IN NS ns4.dnsflyer.com.
dnsflyer.com. 65981 IN NS ns5.dnsflyer.com.
dnsflyer.com. 65981 IN NS ns6.dnsflyer.com.
ns1.dnsflyer.com. 65981 IN A 195.5.22.228 /* Not in our
hosting's network */
ns2.dnsflyer.com. 65981 IN A 202.128.64.107 /* Not in our
hosting's network */
ns3.dnsflyer.com. 65981 IN A 211.73.8.12 /* Not in our
hosting's network */
ns4.dnsflyer.com. 65981 IN A 195.5.40.247 /* Not in our
hosting's network */
ns5.dnsflyer.com. 65981 IN A 217.6.115.178 /* Not in our
hosting's network */
ns6.dnsflyer.com. 65981 IN A 217.73.8.16 /* Not in our
hosting's network */

---------------------------------------------

1, 212.42.69.246, evil.dark-desires.com /* Dead */ ukr.net

ukr.net. 40040 IN NS ns.ukr.net.
ukr.net. 40040 IN NS nss.ukr.net.
ukr.net. 40040 IN NS ns.tsystems.kiev.ua.
ukr.net. 40040 IN NS ns2.adamant.net.
ukr.net. 40040 IN NS ns1.donbass.net.
ukr.net. 267 IN A 212.42.64.10 /* Not in our
hosting's network */
ukr.net. 40040 IN NS ns.ukr.net.
ukr.net. 40040 IN NS nss.ukr.net.
ukr.net. 40040 IN NS ns.tsystems.kiev.ua.
ukr.net. 40040 IN NS ns2.adamant.net.
ukr.net. 40040 IN NS ns1.donbass.net.
ns.ukr.net. 40040 IN A 212.42.64.7 /* Not in our
hosting's network */
nss.ukr.net. 55863 IN A 212.42.64.9 /* Not in our
hosting's network */
ns.tsystems.kiev.ua. 34095 IN A 212.40.34.2 /* Not in our
hosting's network */
ns2.adamant.net. 34317 IN A 212.26.128.3 /* Not in our
hosting's network */
ns1.donbass.net. 10743 IN A 195.184.192.18 /* Not in our
hosting's network */
ukr.net. 2897 IN MX 15 mx-1.ukr.net.
ukr.net. 2897 IN MX 15 protez.ukr.net.
mx-1.ukr.net. 48781 IN A 212.42.65.67 /* Not in our
hosting's network */
protez.ukr.net. 42260 IN A 212.42.65.73 /* Not in our
hosting's network */

---------------------------------------------

2, 195.5.22.228, ptrdname = wtf.dnsflyer.com /* Dead */


Please, wait for the next parts.
Thank you once more for understanding.

With best regards,
Alex Polyakov

--

Anri Erinin

未讀,
2004年1月29日 清晨7:05:222004/1/29
收件者:
Alex Polyakov wrote:

> apologise for it. I'd like to make a stress on the fact that my company is
> not dealing with spam/spammers already for a half of year. Look when was the
> last record of spam events connected with my company name ?

Yea, hosting spamplanet.net does not count.
Hosting carderportal.org does not count either.
Hosting carderplanet.net/com/cc? Just a coincidence.
Hosting advsites? When it was?
Hosting proxydialup.com? Twice you said? It happens, you know how it is.
Hosting lists of trojaned machines? Minor problem.
Hosting crack/wares/appz sites? Who does not?

Alex, no one believes your mantra that you are clean for six months.
Every time you sing it again, I point you to another illegal site hosted
by you. The next day you post here again that you are clean for six months.

Let me quote your good friend and partner Alexey Panov:
<quote>
Spamming is like shooting heroin. Yea its great and your gonna wanna do
it again, but trust me, its not good for you.
</quote>

http://groups.google.com/groups?selm=bu0u2a%24bvspc%241%40ID-115151.news.uni-berlin.de

http://www.wtcracks.com/main.htm
<quote>
:.: Attention :.:
All of the content listed under this site is not to be downloaded,
viewed, or used under any circumstances. If you do choose to ignore
these rules, the webmaster and hosting organization is not responsible
for your actions pertaining to the information on this site. If you are
here because you're an Anti-Piracy related group or organization, you
are not allowed to enter this site and you can not download any content
listed under this site. If you enter this site and do not agree or
ignore these terms of agreement, you can not provide any treatment of
our hosting ISPs, or anyone choosing to store information on this site
because your actions will be a violation code no. 431.322.12 of the
Internet Privacy Act from 1995.
</quote>

>
> I'm trying to clear my name from false
> connections and prove you that BBA Safe Hosting is worth beeing removed from
> blocklists.

No, it is not. A spamhaus's place is in the blocklists.

P.S. I am not SPEWS, I am feed up with your lies and will not answer
your posts anymore because you have nothing to add to the case. I need
to prepare to meet the wrath of 'Capo' Borman and his 'sgarristas'.

E-Mail Sent to this address will be added to the BlackLists

未讀,
2004年1月29日 上午11:15:352004/1/29
收件者:
Alex Polyakov wrote:
<SNIP>

> Please understand that we have automated control system (H-SPHERE Control
> Panel), using which users can regiter, re-regiter, transfer, park (add dns
> zones for domaint located at another hosting, server, network, etc., that
> have no relations with our hosting) and delete domains in their accounts.
> Actually number of domains is so great that neither I nor my colleagues
> can't watch them all. I can provide anyone who would like it with a test
> account, so you can check it yourself. At the first abuse for any domain on
> aour hostng, account containing that domain is beeing deleted without
> warning. I don't want to have any relations with spam or any kind of fraud.
> Spamplanet was hosted at our company but unfortunately I learned about it
> only after your post and terminated this account immediately before it was
> blocklisted anywhere.
>
> Now we have checked all domains and wrote scripts, notifying administrators
> about creating domains containing words "spam/carding/fraud/scum" and
> watching attentively not to let hosting such domains.

You might consider writing scripts that constantly,
repeatedly check any/all domains in your registry,
and all IPs under your control;

for any mention in as many BlockLists / BlackLists as you can find.
(for starters look at the ones mentioned at moensted.dk/spam.)

for any mention in as many Spam / Abuse newsgroups as you can find.
{news.admin.net-abuse.*
alt.spam,
alt.stop.spamming,
comp.org.cauce,
grc.spam,
news.spamcop.net,
gmane.mail.spam.*,
hr.news.net-abuse,
dk.admin.netmisbrug,
fj.news.net-abuse,
sfnet.viestinta.roskapostit,
fr.usenet.abus.d,
de.admin.net-abuse.mail,
it.news.net-abuse,
japan.admin.abuse,
nl.internet.misbruik,
pl.news.mordplik,
ch.admin,
...}

It may be overkill;
on the other hand it might allow you to detect and resolve
problems sooner, and prevent future abuse and escalation.

--
E-Mail Sent to this address <Blac...@Griffin-Technologies.net>
will be added to the BlackLists.

Alex Polyakov

未讀,
2004年1月29日 晚上8:00:042004/1/29
收件者:

"Anri Erinin" <spamme...@rambler.ru> wrote in message
news:40190332...@rambler.ru...

> Alex Polyakov wrote:
>
> > apologise for it. I'd like to make a stress on the fact that my company
is
> > not dealing with spam/spammers already for a half of year. Look when was
the
> > last record of spam events connected with my company name ?
>
> Yea, hosting spamplanet.net does not count.
> Hosting carderportal.org does not count either.
> Hosting carderplanet.net/com/cc? Just a coincidence.
> Hosting advsites? When it was?
> Hosting proxydialup.com? Twice you said? It happens, you know how it is.
> Hosting lists of trojaned machines? Minor problem.
> Hosting crack/wares/appz sites? Who does not?

All sites from this list are removed and I described how it happened that we
hosted them in previous post. Can you please specify all domains at my
hosting that should be removed,
we're in the process of searching and removing of all illegal sites and your
help in that would be greatly appreciated.
Talking about C4 team and easyandquickloans.com. C4 team has stolen our
support icq uin and we were forced to register a new one ( uin# 231556749)
and we'd like to learn who they are very much. If you know something about
connection between easyandquickloans.com and C4 team please give us this
information.

onyx1.sysvhost.com was removed as soon as we learned about it as we did it
with domains specified upwards.

> And is still live at:

> 69.56.247.190/proj/stat-live.cgi/live.txt

ThePlanet is the one of bigest datacenters in America, as far as I know, and
this IP address is not belongs to our hosting. Here is nmap fingerprints:


nmap -O -p 1-1024 webmeat.sysvhost.com

Starting nmap 3.50 ( http://www.insecure.org/nmap/ ) at 2004-01-30 03:16 EET
+Interesting ports on 69-56-225-98.theplanet.com (69.56.225.98):
(The 1015 ports scanned but not shown below are in state: filtered)
PORT STATE SERVICE
20/tcp closed ftp-data
21/tcp open ftp
22/tcp open ssh
53/tcp open domain
80/tcp open http
123/tcp closed ntp
443/tcp open https
873/tcp closed rsync
1024/tcp closed kdm
Device type: general purpose
Running: Linux 2.4.X|2.5.X
OS details: Linux Kernel 2.4.0 - 2.5.20, Linux 2.4.18 - 2.4.20
Uptime 18.230 days (since Sun Jan 11 21:52:13 2004)

Nmap run completed -- 1 IP address (1 host up) scanned in 438.730 seconds


nmap -O -p 1-1024 69.56.247.190

Starting nmap 3.50 ( http://www.insecure.org/nmap/ ) at 2004-01-30 03:24 EET
Warning: OS detection will be MUCH less reliable because we did not find at
least 1 open and 1 closed TCP port
Interesting ports on 69-56-247-190.theplanet.com (69.56.247.190):
(The 1020 ports scanned but not shown below are in state: filtered)
PORT STATE SERVICE
21/tcp open ftp
22/tcp open ssh
80/tcp open http
443/tcp open https
Device type: router|general purpose
Running: FreeSCO Linux 2.0.X, Linux 2.4.X|2.5.X
OS details: FreeSCO 0.27 (Linux 2.0.38), Linux Kernel 2.4.0 - 2.5.20
Uptime 3.951 days (since Mon Jan 26 04:38:59 2004)

Nmap run completed -- 1 IP address (1 host up) scanned in 248.587 seconds

> Alex, no one believes your mantra that you are clean for six months.
> Every time you sing it again, I point you to another illegal site hosted
> by you. The next day you post here again that you are clean for six
months.
>
> Let me quote your good friend and partner Alexey Panov:
> <quote>
> Spamming is like shooting heroin. Yea its great and your gonna wanna do
> it again, but trust me, its not good for you.
> </quote>

He's not my partner and I even don't know who is this.
And yes, spam is really not good for me.


>
>
http://groups.google.com/groups?selm=bu0u2a%24bvspc%241%40ID-115151.news.uni


-berlin.de
>
> http://www.wtcracks.com/main.htm
> <quote>
> :.: Attention :.:
> All of the content listed under this site is not to be downloaded,
> viewed, or used under any circumstances. If you do choose to ignore
> these rules, the webmaster and hosting organization is not responsible
> for your actions pertaining to the information on this site. If you are
> here because you're an Anti-Piracy related group or organization, you
> are not allowed to enter this site and you can not download any content
> listed under this site. If you enter this site and do not agree or
> ignore these terms of agreement, you can not provide any treatment of
> our hosting ISPs, or anyone choosing to store information on this site
> because your actions will be a violation code no. 431.322.12 of the
> Internet Privacy Act from 1995.
> </quote>
>

This domain is not hosted by us, in our six month clean hosting period, as
you have said.

;; QUESTION SECTION:
;wtcracks.com. IN ANY

;; ANSWER SECTION:
wtcracks.com. 941 IN NS ns2.red.ru.
wtcracks.com. 941 IN NS aserver.red.ru.

;; AUTHORITY SECTION:
wtcracks.com. 941 IN NS ns2.red.ru.
wtcracks.com. 941 IN NS aserver.red.ru.

;; ADDITIONAL SECTION:
ns2.red.ru. 942 IN A 194.135.19.34
aserver.red.ru. 84707 IN A 194.135.19.34


> >
> > I'm trying to clear my name from false
> > connections and prove you that BBA Safe Hosting is worth beeing removed
from
> > blocklists.
>
> No, it is not. A spamhaus's place is in the blocklists.
>
> P.S. I am not SPEWS, I am feed up with your lies and will not answer
> your posts anymore because you have nothing to add to the case. I need
> to prepare to meet the wrath of 'Capo' Borman and his 'sgarristas'.

Anri, please understand, that you can be 'Capo' too, just for monthly
payment for advertising.
You don't want to believe anyone and your e-mail address is to eloquent for
you, but now
you are wrong and I'm asking you to help me clean out all illegal/spam
connected domains from hosting
as I see that you know more than I.
Is that possible ? I really want to eradicate the black heritage of the past
and to do a legal business.

With best regards,
Alex Polyakov

Alex Polyakov

未讀,
2004年1月29日 晚上8:36:162004/1/29
收件者:

"E-Mail Sent to this address will be added to the BlackLists"
<Blac...@Griffin-Technologies.net> wrote in message
news:4018DA0E...@Griffin-Technologies.net...

Thank you for a kind answer, and for a good link to know.


> for any mention in as many Spam / Abuse newsgroups as you can find.
> {news.admin.net-abuse.*
> alt.spam,
> alt.stop.spamming,
> comp.org.cauce,
> grc.spam,
> news.spamcop.net,
> gmane.mail.spam.*,
> hr.news.net-abuse,
> dk.admin.netmisbrug,
> fj.news.net-abuse,
> sfnet.viestinta.roskapostit,
> fr.usenet.abus.d,
> de.admin.net-abuse.mail,
> it.news.net-abuse,
> japan.admin.abuse,
> nl.internet.misbruik,
> pl.news.mordplik,
> ch.admin,
> ...}
>
> It may be overkill;
> on the other hand it might allow you to detect and resolve
> problems sooner, and prevent future abuse and escalation.

We have started to develop perl script that parses this news groups, for
all domains that are contained in standard formatted BIND dns zones.
We will post it here soon, to be public accessable and usefull for
increasing the speed of spam prevention.

With best regards,
Alex Polyakov

Alex Polyakov

未讀,
2004年1月29日 晚上8:35:222004/1/29
收件者:

"SomeOne... or Other!" <some...@r.other.easynews.com> wrote in message
news:hnLRb.6880705$Of.10...@news.easynews.com...

> To news.admin.net-abuse.blocklisting subscribers,
>
> > From: Alex Polyakov <apol...@sysvhost.com>,
>
> > Is that not enough to prove you that our hosting has stopped all spam
> > relations, and I as a owner of the company worth at least one chance.
> > We'll agree with any condition of cooperation.
>
> I'll answer your question more kindly.
>
> This is a bad place to ask about 'second chances' as nanab (a.k.a
> news.admin.net-abuse.blocklisting) is frequented by hardliners. Some
> said hardliners feel no penalty is too great if less spam results, and
> are very ready to say so.
We are not spamers...

>
> Eradicating spammers from your network isn't just to please the
> hardliners; it's to please everyone. Spam is consistently in the Top 5
> 'Internet Woes' when users are surveyed. This is an opportunity to be
> part of the solution.

Yes, we have deleted every spamer or related site from our hosting already
and working now on SPEWS listing record number S2547 to show that there is
no relations left.
Asking once more Anri to help us.

>
> Once the spammers are gone (_all_ services terminated), come here and
> say so (detailing the SPEWS record number(s)) and give an indication of
> how you will help stop them returning to your network. Refuse service
> to known spammers? Measures to enforce anti-abuse provisions of your
> Terms of Service/Acceptable Use Policy? Active monitoring and
> investigation of _all_ abuse reports? All of these make a good start.

Yes, we have started it all for the begining of our SPEWS delisting process,
and surely our AUP is of Zero Tolerance against SPAM
(http://www.bbasafehosting.com/services/policy.html)
We monitore our abuse@ boxes every 5 minutes.


> You can't change the past, but present and future are under your
> control. Ignore the rhetoric on sins of the past, focus on the problem
> at hand, and stop the spammers. The rhetoric will disappear of its own
> accord. As will - based on past experience only - the SPEWS listing(s).

We are now starting development of perl scripts of thr type offered by post
of <Blac...@Griffin-Technologies.net>

We will make them public accessable (under GNU license) and post them here
in one week.
Guys from spews, please delist us, and you will see that no spam operations
connected with our hosting will appear.
You have opportunity to list us again any time, just show mercy and you'll
see that we are NOT dealing with spammers
and really want to help you fighting against internet abuse.
We're experiencing lots of problems because of blacklisting, but we surely
wouldn't stop attemps to prove that we are clean.

Thank you and sorry once more.

Alex Polyakov

Alex Polyakov

未讀,
2004年1月30日 清晨7:18:012004/1/30
收件者:
Hello,

here's second part of result checking S2547 entries


---------------------------------------------

1, 213.83.19.101, dnsflyer.com mail.togethersoft.de

mail.togethersoft.de. 3600 IN A 213.83.19.101 /* Not in our
hosting's network */

togethersoft.de. 3600 IN NS ns.plusline.de.
togethersoft.de. 3600 IN NS ns.s.plusline.de.
ns.plusline.de. 86400 IN A 212.19.48.14 /* Not in our
hosting's network */

ns.s.plusline.de. 86400 IN A 212.19.40.14 /* Not in our
hosting's network */

---------------------------------------------
2, 216.215.209.58, www.specialgirls.net Hacked box?! Pretty lame. /* Dead
*/

--------------------------------------------

1, 210.51.12.53, www.e-bla.com on listed China Netcom /* Dead */

--------------------------------------------

1, 66.238.65.147, ns1.adultcolo.net
ns1.adultcolo.net. 67983 IN A 207.153.108.10 /* Not in our
hosting's network */

---------------------------------------------

1, 66.238.60.0 - 66.238.70.255, XO adultcolo.net /* Dead */

---------------------------------------------

1, 64.237.34.162, smtp.inkus.net 64.237.34.162.gigabits.us /* Dead */

---------------------------------------------

1, 194.105.213.150, inkus.net /* Dead */

---------------------------------------------

1, 194.105.213.0 - 194.105.213.255, leivo.ru inkus.net /* Dead */

---------------------------------------------

1, 213.182.190.157, inkus.net ns2.it-dev.ru /* Dead */

---------------------------------------------

1, 213.182.190.0 - 213.182.190.255, metrocom.ru inkus.net /* Dead */

---------------------------------------------

1, 65.207.158.47, www.secret-wish.info /* Dead */

---------------------------------------------

1, 65.207.158.0 24, www.secret-wish.info un-SWIP'd UUNet /* Dead */

---------------------------------------------

2, 65.207.156.0 22, www.secret-wish.info un-SWIP'd UUNet /* Dead */

1, 199.105.86.242, proxysite.com dead?
proxysite.com. 68283 IN NS horimed.relcom.ru.
proxysite.com. 68283 IN NS horimed.relcom.ru.

horimed.relcom.ru. 86377 IN A 194.220.4.1 /* Not in our
hosting's network */

ns.ru.net. 161467 IN A 193.124.22.65 /* Not in our
hosting's network */
ns.spb.su. 76121 IN A 193.124.83.69 /* Not in our
hosting's network */
ns1.relcom.ru. 85347 IN A 193.125.152.3 /* Not in our
hosting's network */

---------------------------------------------

1, 80.96.162.66, www.secret-wish.info dead? /* Dead */

---------------------------------------------

1, 194.58.35.26, members.proxysite.com /* Dead */

---------------------------------------------

1, 194.58.35.0 24, sunfl.net members.proxysite.com
sunfl.net. 68341 IN NS horimed.relcom.ru.
sunfl.net. 68341 IN NS horimed2.relcom.ru.
sunfl.net. 68341 IN NS horimed.relcom.ru.
sunfl.net. 68341 IN NS horimed2.relcom.ru.
horimed.relcom.ru. 86399 IN A 194.220.4.1 /* Not in our
hosting's network */

---------------------------------------------

2, 216.193.196.7, www.dvdvibe.com
www.dvdvibe.com. 3600 IN A 216.193.196.7 /* Not in our
hosting's network */
dvdvibe.com. 3600 IN NS ns1.dvdvibe.com.
ns1.dvdvibe.com. 172799 IN A 200.190.148.219 /* Not in


our hosting's network */

dvdvibe.com. 3600 IN MX 100 mail.dvdvibe.com.

mail.dvdvibe.com. 3600 IN A 200.190.148.219 /* Not in


our hosting's network */

ns1.dvdvibe.com. 172794 IN A 200.190.148.219 /* Not in


our hosting's network */

---------------------------------------------

2, 216.193.196.0 25, amrventures.com ADULTCOLO.NET dvdvibe.com
mzima.net dead?


amrventures.com. 68034 IN NS ns1.bignameserver.com.
amrventures.com. 68034 IN NS ns2.bignameserver.com.
ns1.bignameserver.com. 68034 IN A 200.190.148.219 /* Not in


our hosting's network */

ns2.bignameserver.com. 68034 IN A 66.63.162.180 /* Not in our
hosting's network */

dvdvibe.com. 3600 IN NS ns1.dvdvibe.com.
dvdvibe.com. 3600 IN NS ns1.dvdvibe.com.

mzima.net. 68419 IN NS ns1.lax01.mzima.net.
mzima.net. 68419 IN NS ns2.lax01.mzima.net.
mzima.net. 68419 IN NS ns3.lax01.mzima.net.
mzima.net. 68419 IN NS ns1.lax01.mzima.net.
mzima.net. 68419 IN NS ns2.lax01.mzima.net.
mzima.net. 68419 IN NS ns3.lax01.mzima.net.
ns1.lax01.mzima.net. 68419 IN A 64.235.224.4 /* Not in our
hosting's network */
ns2.lax01.mzima.net. 68419 IN A 64.235.224.6 /* Not in our
hosting's network */
ns3.lax01.mzima.net. 68419 IN A 64.235.224.8 /* Not in our
hosting's network */

mzima.net. 86400 IN MX 20 mail3.mzima.net.
mzima.net. 86400 IN MX 0 mail.mzima.net.
mail.mzima.net. 86400 IN A 64.235.224.10 /* Not in our
hosting's network */

---------------------------------------------

1, 200.207.128.163, inkus.net 200-207-128-163.speedyterra.com.br /* Dead */

---------------------------------------------

1, 66.208.40.137, ns3.powermailing.biz dead
ns3.powermailing.biz. 7200 IN A 203.199.124.117 /* Not in


our hosting's network */

powermailing.biz. 7200 IN NS NS3.DIRECTIHOSTING.COM.
powermailing.biz. 7200 IN NS NS4.DIRECTIHOSTING.COM.
NS3.DIRECTIHOSTING.COM. 12056 IN A 207.44.184.34 /* Not in our
hosting's network */
NS4.DIRECTIHOSTING.COM. 12056 IN A 209.61.162.6 /* Not in our
hosting's network */

powermailing.biz. 86400 IN MX 30 dmail.powermailing.biz.
dmail.powermailing.biz. 86400 IN A 203.199.107.94 /* Not in our
hosting's network */

---------------------------------------------

1, 61.65.53.249, ns2.powermailing.biz dead
ns2.powermailing.biz. 7200 IN A 203.199.124.118 /* Not in


our hosting's network */

powermailing.biz. 7200 IN NS NS3.DIRECTIHOSTING.COM.
powermailing.biz. 7200 IN NS NS4.DIRECTIHOSTING.COM.

---------------------------------------------

1, 63.173.194.24, bulkmails.org ns1.powermailing.biz
ns2.powermailing.biz ns4.powermailing.biz


bulkmails.org. 86400 IN NS ns3.powermailing.biz.
bulkmails.org. 86400 IN NS ns2.powermailing.biz.
bulkmails.org. 86400 IN NS ns1.powermailing.biz.
bulkmails.org. 86400 IN NS ns3.powermailing.biz.
bulkmails.org. 86400 IN NS ns2.powermailing.biz.
bulkmails.org. 86400 IN NS ns1.powermailing.biz.
ns3.powermailing.biz. 7198 IN A 203.199.124.117 /* Not in


our hosting's network */

ns1.powermailing.biz. 7200 IN A 61.109.209.215 /* Not in our
hosting's network */
ns1.powermailing.biz. 7200 IN A 203.199.124.116 /* Not in


our hosting's network */

powermailing.biz. 7200 IN NS NS2.powermailing.biz.
powermailing.biz. 7200 IN NS NS3.powermailing.biz.
powermailing.biz. 7200 IN NS ns1.powermailing.biz.
powermailing.biz. 7200 IN NS NS4.powermailing.biz.
powermailing.biz. 7200 IN NS NS3.DIRECTIHOSTING.COM.
powermailing.biz. 7200 IN NS NS4.DIRECTIHOSTING.COM.

NS2.powermailing.biz. 7200 IN A 203.199.124.118 /* Not in


our hosting's network */

NS3.powermailing.biz. 7200 IN A 203.199.124.117 /* Not in


our hosting's network */

ns1.powermailing.biz. 7200 IN A 61.109.209.215 /* Not in our
hosting's network */
ns1.powermailing.biz. 7200 IN A 203.199.124.116 /* Not in


our hosting's network */

NS4.powermailing.biz. 7200 IN A 203.199.124.115 /* Not in


our hosting's network */

---------------------------------------------

1, 63.173.194.0 23, netxinternet.com eshores.com ns1.powermailing.biz
ns2.powermailing.biz ns4.powermailing.biz Sprint


netxinternet.com. 68544 IN NS ns1.netxinternet.com.
netxinternet.com. 68544 IN NS ns2.netxinternet.com.
netxinternet.com. 68544 IN NS ns1.netxinternet.com.
netxinternet.com. 68544 IN NS ns2.netxinternet.com.
ns1.netxinternet.com. 68544 IN A 63.163.171.10 /* Not in our
hosting's network */
ns2.netxinternet.com. 68544 IN A 63.163.171.4 /* Not in our
hosting's network */


eshores.com. 68559 IN NS ns1.netxinternet.com.
eshores.com. 68559 IN NS ns2.netxinternet.com.
eshores.com. 68559 IN NS ns1.netxinternet.com.
eshores.com. 68559 IN NS ns2.netxinternet.com.
ns1.netxinternet.com. 68544 IN A 63.163.171.10 /* Not in our
hosting's network */
ns2.netxinternet.com. 68544 IN A 63.163.171.4 /* Not in our
hosting's network */

netxinternet.com. 259200 IN MX 5 mail.eshores.com.
mail.eshores.com. 259200 IN A 63.163.171.16 /* Not in our
hosting's network */

---------------------------------------------

1, 69.51.4.107, ns.xsitehosting.net on listed Hufnal spam house
ns.xsitehosting.net. 68601 IN A 69.51.4.107 /* Not in our
hosting's network */

---------------------------------------------

1, 63.246.157.52, damcash.com on sagonet.com spam house


damcash.com. 68622 IN NS ns.damhost.com.
damcash.com. 68622 IN NS ns2.damhost.com.
damcash.com. 6089 IN A 63.246.157.52 /* Not in our
hosting's network */
damcash.com. 68622 IN NS ns.damhost.com.
damcash.com. 68622 IN NS ns2.damhost.com.
ns.damhost.com. 68622 IN A 63.246.157.7 /* Not in our
hosting's network */
ns2.damhost.com. 68622 IN A 213.172.25.119 /* Not in our
hosting's network */

damcash.com. 86400 IN MX 10 webhost.xsitehost.com.
webhost.xsitehost.com. 3600 IN A 194.85.34.208 /* Not in our
hosting's network */

sagonet.com. 172800 IN NS ns1.sagonet.com.
sagonet.com. 172800 IN NS ns2.sagonet.com.
sagonet.com. 172800 IN NS ns1.sagonet.com.
sagonet.com. 172800 IN NS ns2.sagonet.com.
ns1.sagonet.com. 172800 IN A 66.118.128.2 /* Not in our
hosting's network */
ns2.sagonet.com. 172800 IN A 66.118.128.3 /* Not in our
hosting's network */

sagonet.com. 600 IN MX 0 mx.sagonet.com.
mx.sagonet.com. 600 IN A 66.118.148.16

---------------------------------------------

1, 203.197.204.223, www1.dvdvibe.com /* Dead */

---------------------------------------------

2, 203.197.204.0 - 203.197.204.255, vsnl.net.in amrventures.com
ADULTCOLO.NET dvdvibe.com


vsnl.net.in. 64319 IN NS dns.vsnl.net.in.
vsnl.net.in. 64319 IN NS ns3.vsnl.com.
vsnl.net.in. 64319 IN NS dns.vsnl.net.in.
vsnl.net.in. 64319 IN NS ns3.vsnl.com.
dns.vsnl.net.in. 64319 IN A 202.54.1.30 /* Not in our
hosting's network */
ns3.vsnl.com. 43678 IN A 203.197.12.42 /* Not in our
hosting's network */

vsnl.net.in. 75340 IN MX 10 mx2.vsnl.net.
vsnl.net.in. 75340 IN MX 0 mx1.vsnl.net.
mx1.vsnl.net. 75341 IN A 203.200.235.229 /* Not in


our hosting's network */

mx2.vsnl.net. 74048 IN A 203.200.235.178 /* Not in


our hosting's network */


amrventures.com. 68021 IN NS ns1.bignameserver.com.
amrventures.com. 68021 IN NS ns2.bignameserver.com.
ns1.bignameserver.com. 68021 IN A 200.190.148.219 /* Not in


our hosting's network */

ns2.bignameserver.com. 68021 IN A 66.63.162.180 /* Not in our
hosting's network */

amrventures.com. 38400 IN MX 100 mail.dvdvibe.com.
mail.dvdvibe.com. 2700 IN A 200.190.148.219 /* Not in


our hosting's network */

dvdvibe.com. 3587 IN NS ns1.dvdvibe.com.
dvdvibe.com. 3587 IN NS ns1.dvdvibe.com.

---------------------------------------------

1, 66.98.142.14, ns2.sysvhost.com not at all "innocent"


ns2.sysvhost.com. 143430 IN A 69.93.47.95 /* Our domain
that is wanted to be unlisted */

---------------------------------------------

1, 66.98.142.0 25, EV1 ns2.sysvhost.com /* Our domain that is wanted to be
unlisted */

---------------------------------------------

1, 216.127.68.199, ns1.sysvhost.com not at all "innocent" /* Our domain
that is wanted to be unlisted */

---------------------------------------------

1, 216.127.68.112, mail.sysvhost.com not at all "innocent" /* Dead */

---------------------------------------------

2, 216.127.68.0 24, EV1 ns2.sysvhost.com


ns2.sysvhost.com. 143427 IN A 69.93.47.95 /* Our domain
that is wanted to be unlisted */

---------------------------------------------

1, 69.56.225.115, proxydialup.com webmeat.sysvhost.com

proxydialup.com /* Dead */


webmeat.sysvhost.com. 10800 IN A 69.56.225.98 /* Our domain
that is wanted to be unlisted */
sysvhost.com. 10800 IN NS ns1.sysvhost.com.
sysvhost.com. 10800 IN NS ns2.sysvhost.com.
ns1.sysvhost.com. 143429 IN A 69.93.47.94 /* Our domain
that is wanted to be unlisted */
ns2.sysvhost.com. 143426 IN A 69.93.47.95 /* Our domain
that is wanted to be unlisted */

---------------------------------------------

1, 69.56.225.111, bbahost.com /* Dead */

---------------------------------------------

1, 69.56.225.0 24, proxydialup.com /* Dead */ theplanet.com


theplanet.com. 21499 IN NS ns2.theplanet.com.
theplanet.com. 21499 IN NS ns1.theplanet.com.
theplanet.com. 21499 IN NS ns2.theplanet.com.
theplanet.com. 21499 IN NS ns1.theplanet.com.
ns2.theplanet.com. 38516 IN A 12.96.160.115 /* Not in our
hosting's network */
ns1.theplanet.com. 38516 IN A 216.234.234.30 /* Not in our
hosting's network */

theplanet.com. 74224 IN MX 10 mail1.theplanet.com.
theplanet.com. 74224 IN MX 20 spooling.theplanet.com.
theplanet.com. 74224 IN MX 30 mail2.theplanet.com.

spooling.theplanet.com. 74224 IN A 69.56.141.4 /* Not in our
hosting's network */
ns1.theplanet.com. 159737 IN A 216.234.234.30 /* Not in our
hosting's network */
ns2.theplanet.com. 159737 IN A 12.96.160.115 /* Not in our
hosting's network */

---------------------------------------------

1, 69.56.223.0 - 69.56.227.255, proxydialup.com /* Dead */ theplanet.com

---------------------------------------------

1, 69.93.47.94/31, ns1.sysvhost.com / ns2.sysvhost.com

ns1.sysvhost.com. 143427 IN A 69.93.47.94 /* Our domain
that is wanted to be unlisted */
ns2.sysvhost.com. 143427 IN A 69.93.47.95 /* Our domain
that is wanted to be unlisted */

---------------------------------------------

1, 69.57.142.28, mysql.sysvhost.com

mysql.sysvhost.com. 10800 IN A 69.57.142.28 /* Our domain
that is wanted to be unlisted */

sysvhost.com. 5975 IN NS ns1.sysvhost.com.
sysvhost.com. 5975 IN NS ns2.sysvhost.com.

----------------------------------------------

1, 66.98.142.159, ns2.bbasafehosting.biz

ns2.bbasafehosting.biz. 7952 IN A 66.98.142.159 /* Our domain
that is wanted to be unlisted */

bbasafehosting.biz. 8927 IN NS ns1.bbasafehosting.biz.
bbasafehosting.biz. 8927 IN NS ns2.bbasafehosting.biz.

ns1.bbasafehosting.biz. 7952 IN A 216.127.68.231 /* Our domain
that is wanted to be unlisted */

---------------------------------------------

1, 216.127.68.112, mail.proxydialup.com /* Dead */ / mail.sysvhost.com /*
Dead */ / reseller.sysvhost.com /* Dead */ / mail.sysvhost.com /* Dead */ /
mail.bbasafehosting.biz /* Our domain that is wanted to be unlisted */
(live)


mail.bbasafehosting.biz. 8690 IN A 216.127.68.231 /* Our
domain that is wanted to be unlisted */

bbasafehosting.biz. 8690 IN NS ns2.bbasafehosting.biz.
bbasafehosting.biz. 8690 IN NS ns1.bbasafehosting.biz.

-----------------------------------------------

1, 216.127.68.231, mail.bbasafehosting.biz /* Our domain that is wanted to
be unlisted */ / cp.sysvhost.com /* Our domain that is wanted to be
unlisted */ / pi.sysvhost.com /* Our domain that is wanted to be unlisted
*/

mail.bbasafehosting.biz. 8690 IN A 216.127.68.231 /* Our
domain that is wanted to be unlisted */

cp.bbasafehosting.biz. 10800 IN A 66.98.142.159 /* Our domain
that is wanted to be unlisted */
pi.bbasafehosting.biz. 10800 IN A 66.98.142.159 /* Our domain
that is wanted to be unlisted */

bbasafehosting.biz. 8690 IN NS ns2.bbasafehosting.biz.
bbasafehosting.biz. 8690 IN NS ns1.bbasafehosting.biz.


Please, check the list and update it at your earliest convenience and we
justify your hopes.

Thank you in advance,

Alex Polyakov

Alex Polyakov

未讀,
2004年1月31日 凌晨12:33:122004/1/31
收件者:

Why do you hate me so much? I told you that my company never dealt with
internet fraud. My name is blackened by spam because at the moment of
purchasing the company and the domain by me, I had no facts about tearing
all connections with spam, I could offer to the newsgroups. It's a pity that
you're stressing that you're not afraid of me.The thing is that I come here
not to scare or quarrel but to apologise for the activities of the company
in the period it wasn't under my conrol, to clean the name of the company by
helping in fight against spam.
You want to do something useful in your life, for the people or the internet
as a good idea. So do I. Hosting is working for only 1 year, it wasn't built
during many years as you said in
(http://www.google.com/groups?selm=buu2ht%24lm226%241%40ID-115151.news.uni-b
erlin.de)
and now I'm trying to clean it's (as well as mine) name, to build a
buisness,to help people working for provide food and clothes for their
families.
I've invested money earned by several years of working as Java developer and
lead system administrator.
I see your abhorrence to our advertizing at carderplanet.com, I agree that
it attracts attention to hosting not only of security analysts, anti-fraud
departments, security systems developers, webmasters that would like to
protect themselves against the most modern kinds of internet fraud and even
You read it, but frauders as well. We warn every new cutomer by e-mail, icq
and AUP (you may read it at http://bbasafehosting.com/services/policy.html)
that for every illegal activity accounts are terminated without moneyback.
So there's no sense for frauders to host sites with us. 'Capo' status is
included in advertising fee, I told that we pay monthly for advertizing on
carderplanet forum and have no other relations with it 'Capo' status is
included in advertising fee, I told that we pay monthly for advertizing on
carderplanet forum and have no other relations with it.
And please stop offending me! You are violating all basics of polite
behaviour, I understand that you don't trust me but let's be polite with
each other untill my guilt that you insist on is not proved.
As I'm reading your posts I'm making sure that you're severely offended by
somebody. Or you're making such unproved conlusions to attract attention to
your person? What about writing of anti-spam project together? What will you
say?

What concernes snaikoil cert, it's a default generated by freely distribudet
openssl utiility certificate for encrypted connections.
Merlin.Com.UA is provider of a local network that is used by almost a half
of all internet users of our city, and I have just posted to newsgroup using
its news server.
The people who live there are more friendly than you seem to be and just
don't pay attention on it.


"Anri Erinin" <spamme...@rambler.ru> wrote in message

news:bv6ftm$njbrd$1...@ID-115151.news.uni-berlin.de...

0 則新訊息