From brian.nisbet at heanet.ie  Tue Mar  1 16:08:20 2011
From: brian.nisbet at heanet.ie (Brian Nisbet)
Date: Tue, 01 Mar 2011 15:08:20 +0000
Subject: [anti-abuse-wg] Working Group Co-Chairs - Final Call
Message-ID: <4D6D0BE4.2040307@heanet.ie>

Colleagues,

As registration for RIPE 62 has now been opened, it seems like a good 
time to finalise the recruitment of a new co-chair for the working 
group. This isn't the first time this has been discussed, but I wanted 
to mention it one final time. There has already been some expression of 
interest in the job, which is great, but that's no reason not to make 
sure someone hasn't missed it the first two times!

If you are interested in becoming co-chair of the group then please let 
me know (by email - aa-wg-chairs at ripe.net) before 16:00 UTC on Friday 
4th March. The precise details of selection will depend on the number of 
expressions of interest.

Thanks,

Brian.



From brian.nisbet at heanet.ie  Tue Mar  8 11:45:45 2011
From: brian.nisbet at heanet.ie (Brian Nisbet)
Date: Tue, 08 Mar 2011 10:45:45 +0000
Subject: [anti-abuse-wg] Call for Agenda Items - RIPE 62
Message-ID: <4D7608D9.6080406@heanet.ie>

Colleagues,

As the RIPE 62 meeting in Amsterdam is just two months away, now is a 
good time to solicit any items for the Anti-Abuse Working Group session 
at 14:00 on Thursday 5th May.

If you have any items you would like to present on or discuss, please 
let me know.

Thanks,

Brian.



From rfg at tristatelogic.com  Tue Mar  8 12:34:14 2011
From: rfg at tristatelogic.com (Ronald F. Guilmette)
Date: Tue, 08 Mar 2011 03:34:14 -0800
Subject: [anti-abuse-wg] RIPE policy
Message-ID: <28482.1299584054@tristatelogic.com>

I feel compelled to inquire as to how (or whether) it comports with
RIPE policy for holders of RIPE IPv4 space to be giving over sizable
chunks of that space for exclusive use by American bulk E-mail marketing
companies.


109.177.8.2 greenbox.statusrunning.com
109.177.8.3 triplethrone.statusrunning.com
109.177.8.4 clearhand.statusrunning.com
109.177.8.5 grayworm.statusrunning.com
109.177.8.5 statusrunning.com
109.177.8.6 browncellar.statusrunning.com
109.177.8.7 brightair.statusrunning.com
109.177.8.8 steepbase.statusrunning.com
109.177.8.9 pleasantscarf.statusrunning.com
109.177.8.10 shrillcard.statusrunning.com
109.177.8.11 quietboat.statusrunning.com
109.177.8.12 oddrock.statusrunning.com
109.177.8.13 wideowl.statusrunning.com
109.177.8.14 fastbasin.statusrunning.com
109.177.8.15 sadfeast.statusrunning.com
109.177.8.16 fragileguide.statusrunning.com
109.177.8.17 dryapple.statusrunning.com
109.177.8.18 smoothatom.statusrunning.com
109.177.8.19 friedgrape.statusrunning.com
109.177.8.20 fiercewire.statusrunning.com
109.177.8.21 minirabbit.statusrunning.com
109.177.8.22 icysteel.statusrunning.com
109.177.8.23 nicecollar.statusrunning.com
109.177.8.24 happygarden.statusrunning.com
109.177.8.25 oldbean.statusmonitor.net
109.177.8.26 broadcopy.statusmonitor.net
109.177.8.27 savorymachine.statusmonitor.net
109.177.8.27 statusmonitor.net
109.177.8.28 heavenlyball.statusmonitor.net
109.177.8.29 slownet.statusmonitor.net
109.177.8.30 mutejam.statusmonitor.net
109.177.8.31 freshtruck.statusmonitor.net
109.177.8.32 goodswing.statusmonitor.net
109.177.8.33 superwindow.statusmonitor.net
109.177.8.34 tidyrice.statusmonitor.net
109.177.8.35 twinclock.statusmonitor.net
109.177.8.36 cutearea.statusmonitor.net
109.177.8.37 alertarm.statusmonitor.net
109.177.8.38 flatsystem.statusmonitor.net
109.177.8.39 lightcity.statusmonitor.net
109.177.8.40 earlyfan.statusmonitor.net
109.177.8.41 richbook.statusmonitor.net
109.177.8.42 lateart.statusmonitor.net
109.177.8.43 leafydust.statusmonitor.net
109.177.8.44 topbranch.statusmonitor.net
109.177.8.45 roastedmeal.statusmonitor.net
109.177.8.46 realbox.statusmonitor.net
109.177.8.47 greenthrone.statusmonitor.net
109.177.8.48 triplehand.statustreat.com
109.177.8.49 clearworm.statustreat.com
109.177.8.50 graycellar.statustreat.com
109.177.8.51 brownair.statustreat.com
109.177.8.52 brightbase.statustreat.com
109.177.8.53 steepscarf.statustreat.com
109.177.8.54 pleasantcard.statustreat.com
109.177.8.55 shrillboat.statustreat.com
109.177.8.56 quietrock.statustreat.com
109.177.8.57 oddowl.statustreat.com
109.177.8.58 widebasin.statustreat.com
109.177.8.59 fastfeast.statustreat.com
109.177.8.60 sadguide.statustreat.com
109.177.8.61 fragileapple.statustreat.com
109.177.8.61 statustreat.com
109.177.8.62 dryatom.statustreat.com
109.177.8.63 smoothgrape.statustreat.com
109.177.8.64 friedwire.statustreat.com
109.177.8.65 fiercerabbit.statustreat.com
109.177.8.66 ministeel.statustreat.com
109.177.8.67 icycollar.statustreat.com
109.177.8.68 nicegarden.statustreat.com
109.177.8.69 happybean.statustreat.com
109.177.8.70 oldcopy.statustreat.com
109.177.8.71 broadmachine.statuslead.com
109.177.8.72 savoryball.statuslead.com
109.177.8.73 heavenlynet.statuslead.com
109.177.8.74 slowjam.statuslead.com
109.177.8.75 mutetruck.statuslead.com
109.177.8.76 freshswing.statuslead.com
109.177.8.77 goodwindow.statuslead.com
109.177.8.78 superrice.statuslead.com
109.177.8.79 tidyclock.statuslead.com
109.177.8.80 twinarea.statuslead.com
109.177.8.81 cutearm.statuslead.com
109.177.8.82 alertsystem.statuslead.com
109.177.8.83 flatcity.statuslead.com
109.177.8.84 lightfan.statuslead.com
109.177.8.85 earlybook.statuslead.com
109.177.8.86 richart.statuslead.com
109.177.8.87 latedust.statuslead.com
109.177.8.88 leafybranch.statuslead.com
109.177.8.89 topmeal.statuslead.com
109.177.8.90 roastedbox.statuslead.com
109.177.8.91 realthrone.statuslead.com
109.177.8.92 greenhand.statuslead.com
109.177.8.93 statuslead.com
109.177.8.93 tripleworm.statuslead.com
109.177.8.94 clearcellar.statustouch.net
109.177.8.95 grayair.statustouch.net
109.177.8.96 brownbase.statustouch.net
109.177.8.97 brightscarf.statustouch.net
109.177.8.98 steepcard.statustouch.net
109.177.8.99 pleasantboat.statustouch.net
109.177.8.100 shrillrock.statustouch.net
109.177.8.100 statustouch.net
109.177.8.101 quietowl.statustouch.net
109.177.8.102 oddbasin.statustouch.net
109.177.8.103 widefeast.statustouch.net
109.177.8.104 fastguide.statustouch.net
109.177.8.105 sadapple.statustouch.net
109.177.8.106 fragileatom.statustouch.net
109.177.8.107 drygrape.statustouch.net
109.177.8.108 smoothwire.statustouch.net
109.177.8.109 friedrabbit.statustouch.net
109.177.8.110 fiercesteel.statustouch.net
109.177.8.111 minicollar.statustouch.net
109.177.8.112 icygarden.statustouch.net
109.177.8.113 nicebean.statustouch.net
109.177.8.114 happycopy.statustouch.net
109.177.8.115 oldmachine.statustouch.net
109.177.8.116 broadball.statustouch.net
109.177.8.117 savorynet.statusconduct.com
109.177.8.117 statusconduct.com
109.177.8.118 heavenlyjam.statusconduct.com
109.177.8.119 slowtruck.statusconduct.com
109.177.8.120 muteswing.statusconduct.com
109.177.8.121 freshwindow.statusconduct.com
109.177.8.122 goodrice.statusconduct.com
109.177.8.123 superclock.statusconduct.com
109.177.8.124 tidyarea.statusconduct.com
109.177.8.125 twinarm.statusconduct.com
109.177.8.126 cutesystem.statusconduct.com
109.177.8.127 alertcity.statusconduct.com
109.177.8.128 flatfan.statusconduct.com
109.177.8.129 lightbook.statusconduct.com
109.177.8.130 earlyart.statusconduct.com
109.177.8.131 richdust.statusconduct.com
109.177.8.132 latebranch.statusconduct.com
109.177.8.133 leafymeal.statusconduct.com
109.177.8.134 topbox.statusconduct.com
109.177.8.135 roastedthrone.statusconduct.com
109.177.8.136 realhand.statusconduct.com
109.177.8.137 greenworm.statusconduct.com
109.177.8.138 triplecellar.statusconduct.com
109.177.8.139 clearair.statusconduct.com
109.177.8.140 graybase.statusdirect.net
109.177.8.141 brownscarf.statusdirect.net
109.177.8.142 brightcard.statusdirect.net
109.177.8.143 steepboat.statusdirect.net
109.177.8.144 pleasantrock.statusdirect.net
109.177.8.145 shrillowl.statusdirect.net
109.177.8.146 quietbasin.statusdirect.net
109.177.8.147 oddfeast.statusdirect.net
109.177.8.148 wideguide.statusdirect.net
109.177.8.149 fastapple.statusdirect.net
109.177.8.150 sadatom.statusdirect.net
109.177.8.151 fragilegrape.statusdirect.net
109.177.8.152 drywire.statusdirect.net
109.177.8.153 smoothrabbit.statusdirect.net
109.177.8.153 statusdirect.net
109.177.8.154 friedsteel.statusdirect.net
109.177.8.155 fiercecollar.statusdirect.net
109.177.8.156 minigarden.statusdirect.net
109.177.8.157 icybean.statusdirect.net
109.177.8.158 nicecopy.statusdirect.net
109.177.8.159 happymachine.statusdirect.net
109.177.8.160 oldball.statusdirect.net
109.177.8.161 broadnet.statusdirect.net
109.177.8.162 savoryjam.statusdirect.net
109.177.8.163 heavenlytruck.statusprocess.com
109.177.8.164 slowswing.statusprocess.com
109.177.8.165 mutewindow.statusprocess.com
109.177.8.166 freshrice.statusprocess.com
109.177.8.167 goodclock.statusprocess.com
109.177.8.168 superarea.statusprocess.com
109.177.8.169 tidyarm.statusprocess.com
109.177.8.170 twinsystem.statusprocess.com
109.177.8.171 cutecity.statusprocess.com
109.177.8.172 alertfan.statusprocess.com
109.177.8.173 flatbook.statusprocess.com
109.177.8.174 lightart.statusprocess.com
109.177.8.175 earlydust.statusprocess.com
109.177.8.176 richbranch.statusprocess.com
109.177.8.176 statusprocess.com
109.177.8.177 latemeal.statusprocess.com
109.177.8.178 leafybox.statusprocess.com
109.177.8.179 topthrone.statusprocess.com
109.177.8.180 roastedhand.statusprocess.com
109.177.8.181 realworm.statusprocess.com
109.177.8.182 greencellar.statusprocess.com
109.177.8.183 tripleair.statusprocess.com
109.177.8.184 clearbase.statusprocess.com
109.177.8.185 grayscarf.statusprocess.com
109.177.8.186 browncard.statuscoordinate.com
109.177.8.187 brightboat.statuscoordinate.com
109.177.8.188 steeprock.statuscoordinate.com
109.177.8.189 pleasantowl.statuscoordinate.com
109.177.8.190 shrillbasin.statuscoordinate.com
109.177.8.190 statuscoordinate.com
109.177.8.191 quietfeast.statuscoordinate.com
109.177.8.192 oddguide.statuscoordinate.com
109.177.8.193 wideapple.statuscoordinate.com
109.177.8.194 fastatom.statuscoordinate.com
109.177.8.195 sadgrape.statuscoordinate.com
109.177.8.196 fragilewire.statuscoordinate.com
109.177.8.197 dryrabbit.statuscoordinate.com
109.177.8.198 smoothsteel.statuscoordinate.com
109.177.8.199 friedcollar.statuscoordinate.com
109.177.8.200 fiercegarden.statuscoordinate.com
109.177.8.201 minibean.statuscoordinate.com
109.177.8.202 icycopy.statuscoordinate.com
109.177.8.203 nicemachine.statuscoordinate.com
109.177.8.204 happyball.statuscoordinate.com
109.177.8.205 oldnet.statuscoordinate.com
109.177.8.206 broadjam.statuscoordinate.com
109.177.8.207 savorytruck.statuscoordinate.com
109.177.8.208 heavenlyswing.statuscoordinate.com
109.177.8.209 slowwindow.statusmind.com
109.177.8.210 muterice.statusmind.com
109.177.8.211 freshclock.statusmind.com
109.177.8.212 goodarea.statusmind.com
109.177.8.213 statusmind.com
109.177.8.213 superarm.statusmind.com
109.177.8.214 tidysystem.statusmind.com
109.177.8.215 twincity.statusmind.com
109.177.8.216 cutefan.statusmind.com
109.177.8.217 alertbook.statusmind.com
109.177.8.218 flatart.statusmind.com
109.177.8.219 lightdust.statusmind.com
109.177.8.220 earlybranch.statusmind.com
109.177.8.221 richmeal.statusmind.com
109.177.8.222 latebox.statusmind.com
109.177.8.223 leafythrone.statusmind.com
109.177.8.224 tophand.statusmind.com
109.177.8.225 roastedworm.statusmind.com
109.177.8.226 realcellar.statusmind.com
109.177.8.227 greenair.statusmind.com
109.177.8.228 triplebase.statusmind.com
109.177.8.229 clearscarf.statusmind.com
109.177.8.230 graycard.statusmind.com
109.177.8.231 brownboat.statusmind.com
109.177.8.232 brightrock.newsmodify.com
109.177.8.233 steepowl.newsmodify.com
109.177.8.234 pleasantbasin.newsmodify.com
109.177.8.235 newsmodify.com
109.177.8.235 shrillfeast.newsmodify.com
109.177.8.236 quietguide.newsmodify.com
109.177.8.237 oddapple.newsmodify.com
109.177.8.238 wideatom.newsmodify.com
109.177.8.239 fastgrape.newsmodify.com
109.177.8.240 sadwire.newsmodify.com
109.177.8.241 fragilerabbit.newsmodify.com
109.177.8.242 drysteel.newsmodify.com
109.177.8.243 smoothcollar.newsmodify.com
109.177.8.244 friedgarden.newsmodify.com
109.177.8.245 fiercebean.newsmodify.com
109.177.8.246 minicopy.newsmodify.com
109.177.8.247 icymachine.newsmodify.com
109.177.8.248 niceball.newsmodify.com
109.177.8.249 happynet.newsmodify.com
109.177.8.250 oldjam.newsmodify.com
109.177.8.251 broadtruck.newsmodify.com
109.177.8.252 savoryswing.newsmodify.com
109.177.8.253 heavenlywindow.newsmodify.com
109.177.8.254 slowrice.newsmodify.com
109.177.9.2 wideair.formatupdate.com
109.177.9.3 cutecopy.formatupdate.com
109.177.9.4 niceworm.formatupdate.com
109.177.9.5 smoothbase.formatupdate.com
109.177.9.6 pleasantbean.formatupdate.com
109.177.9.7 broadbook.formatupdate.com
109.177.9.8 friedthrone.formatupdate.com
109.177.9.9 oddbranch.formatupdate.com
109.177.9.10 realart.formatupdate.com
109.177.9.11 leafyscarf.formatupdate.com
109.177.9.12 formatupdate.com
109.177.9.12 graycollar.formatupdate.com
109.177.9.13 happycard.formatupdate.com
109.177.9.14 sadcellar.formatupdate.com
109.177.9.15 brightguide.formatupdate.com
109.177.9.16 dryjam.formatupdate.com
109.177.9.17 freshsteel.formatupdate.com
109.177.9.18 fiercehand.formatupdate.com
109.177.9.19 triplewire.formatupdate.com
109.177.9.20 minitruck.formatupdate.com
109.177.9.21 goodgrape.formatupdate.com
109.177.9.22 shrilldust.formatupdate.com
109.177.9.23 savoryboat.formatupdate.com
109.177.9.24 laterice.formatupdate.com
109.177.9.25 fastowl.factupdate.com
109.177.9.26 earlycity.factupdate.com
109.177.9.27 quietarm.factupdate.com
109.177.9.28 flatarea.factupdate.com
109.177.9.29 brownmeal.factupdate.com
109.177.9.30 mutegarden.factupdate.com
109.177.9.31 oldfeast.factupdate.com
109.177.9.32 fragileclock.factupdate.com
109.177.9.33 alertfan.factupdate.com
109.177.9.34 richbox.factupdate.com
109.177.9.35 factupdate.com
109.177.9.35 supermachine.factupdate.com
109.177.9.36 heavenlyrabbit.factupdate.com
109.177.9.37 twinnet.factupdate.com
109.177.9.38 steepwindow.factupdate.com
109.177.9.39 greenball.factupdate.com
109.177.9.40 slowbasin.factupdate.com
109.177.9.41 topswing.factupdate.com
109.177.9.42 clearapple.factupdate.com
109.177.9.43 roastedsystem.factupdate.com
109.177.9.44 lightatom.factupdate.com
109.177.9.45 icyrock.factupdate.com
109.177.9.46 tidyair.factupdate.com
109.177.9.47 widecopy.factupdate.com
109.177.9.48 cuteworm.detailsupdate.net
109.177.9.49 nicebase.detailsupdate.net
109.177.9.50 smoothbean.detailsupdate.net
109.177.9.51 pleasantbook.detailsupdate.net
109.177.9.52 broadthrone.detailsupdate.net
109.177.9.53 friedbranch.detailsupdate.net
109.177.9.54 oddart.detailsupdate.net
109.177.9.55 detailsupdate.net
109.177.9.55 realscarf.detailsupdate.net
109.177.9.56 leafycollar.detailsupdate.net
109.177.9.57 graycard.detailsupdate.net
109.177.9.58 happycellar.detailsupdate.net
109.177.9.59 sadguide.detailsupdate.net
109.177.9.60 brightjam.detailsupdate.net
109.177.9.61 drysteel.detailsupdate.net
109.177.9.62 freshhand.detailsupdate.net
109.177.9.63 fiercewire.detailsupdate.net
109.177.9.64 tripletruck.detailsupdate.net
109.177.9.65 minigrape.detailsupdate.net
109.177.9.66 gooddust.detailsupdate.net
109.177.9.67 shrillboat.detailsupdate.net
109.177.9.68 savoryrice.detailsupdate.net
109.177.9.69 lateowl.detailsupdate.net
109.177.9.70 fastcity.detailsupdate.net
109.177.9.71 earlyarm.materialupdate.com
109.177.9.72 quietarea.materialupdate.com
109.177.9.73 flatmeal.materialupdate.com
109.177.9.74 browngarden.materialupdate.com
109.177.9.75 mutefeast.materialupdate.com
109.177.9.76 oldclock.materialupdate.com
109.177.9.77 fragilefan.materialupdate.com
109.177.9.78 alertbox.materialupdate.com
109.177.9.79 richmachine.materialupdate.com
109.177.9.80 superrabbit.materialupdate.com
109.177.9.81 heavenlynet.materialupdate.com
109.177.9.81 materialupdate.com
109.177.9.82 twinwindow.materialupdate.com
109.177.9.83 steepball.materialupdate.com
109.177.9.84 greenbasin.materialupdate.com
109.177.9.85 slowswing.materialupdate.com
109.177.9.86 topapple.materialupdate.com
109.177.9.87 clearsystem.materialupdate.com
109.177.9.88 roastedatom.materialupdate.com
109.177.9.89 lightrock.materialupdate.com
109.177.9.90 icyair.materialupdate.com
109.177.9.91 tidycopy.materialupdate.com
109.177.9.92 wideworm.materialupdate.com
109.177.9.93 cutebase.materialupdate.com
109.177.9.94 nicebean.informupdate.com
109.177.9.95 smoothbook.informupdate.com
109.177.9.96 pleasantthrone.informupdate.com
109.177.9.97 broadbranch.informupdate.com
109.177.9.98 friedart.informupdate.com
109.177.9.99 oddscarf.informupdate.com
109.177.9.100 realcollar.informupdate.com
109.177.9.101 leafycard.informupdate.com
109.177.9.102 graycellar.informupdate.com
109.177.9.103 happyguide.informupdate.com
109.177.9.104 sadjam.informupdate.com
109.177.9.105 brightsteel.informupdate.com
109.177.9.106 dryhand.informupdate.com
109.177.9.107 freshwire.informupdate.com
109.177.9.108 fiercetruck.informupdate.com
109.177.9.109 triplegrape.informupdate.com
109.177.9.110 minidust.informupdate.com
109.177.9.111 goodboat.informupdate.com
109.177.9.112 shrillrice.informupdate.com
109.177.9.113 savoryowl.informupdate.com
109.177.9.114 latecity.informupdate.com
109.177.9.115 fastarm.informupdate.com
109.177.9.115 informupdate.com
109.177.9.116 earlyarea.informupdate.com
109.177.9.117 quietmeal.serialupdate.com
109.177.9.118 flatgarden.serialupdate.com
109.177.9.118 serialupdate.com
109.177.9.119 brownfeast.serialupdate.com
109.177.9.120 muteclock.serialupdate.com
109.177.9.121 oldfan.serialupdate.com
109.177.9.122 fragilebox.serialupdate.com
109.177.9.123 alertmachine.serialupdate.com
109.177.9.124 richrabbit.serialupdate.com
109.177.9.125 supernet.serialupdate.com
109.177.9.126 heavenlywindow.serialupdate.com
109.177.9.127 twinball.serialupdate.com
109.177.9.128 steepbasin.serialupdate.com
109.177.9.129 greenswing.serialupdate.com
109.177.9.130 slowapple.serialupdate.com
109.177.9.131 topsystem.serialupdate.com
109.177.9.132 clearatom.serialupdate.com
109.177.9.133 roastedrock.serialupdate.com
109.177.9.134 lightair.serialupdate.com
109.177.9.135 icycopy.serialupdate.com
109.177.9.136 tidyworm.serialupdate.com
109.177.9.137 widebase.serialupdate.com
109.177.9.138 cutebean.serialupdate.com
109.177.9.139 nicebook.serialupdate.com
109.177.9.140 smooththrone.seriesupdate.net
109.177.9.141 pleasantbranch.seriesupdate.net
109.177.9.142 broadart.seriesupdate.net
109.177.9.143 friedscarf.seriesupdate.net
109.177.9.144 oddcollar.seriesupdate.net
109.177.9.145 realcard.seriesupdate.net
109.177.9.146 leafycellar.seriesupdate.net
109.177.9.147 grayguide.seriesupdate.net
109.177.9.148 happyjam.seriesupdate.net
109.177.9.149 sadsteel.seriesupdate.net
109.177.9.150 brighthand.seriesupdate.net
109.177.9.151 drywire.seriesupdate.net
109.177.9.151 seriesupdate.net
109.177.9.152 freshtruck.seriesupdate.net
109.177.9.153 fiercegrape.seriesupdate.net
109.177.9.154 tripledust.seriesupdate.net
109.177.9.155 miniboat.seriesupdate.net
109.177.9.156 goodrice.seriesupdate.net
109.177.9.157 shrillowl.seriesupdate.net
109.177.9.158 savorycity.seriesupdate.net
109.177.9.159 latearm.seriesupdate.net
109.177.9.160 fastarea.seriesupdate.net
109.177.9.161 earlymeal.seriesupdate.net
109.177.9.162 quietgarden.seriesupdate.net
109.177.9.163 flatfeast.spreadupdate.net
109.177.9.164 brownclock.spreadupdate.net
109.177.9.165 mutefan.spreadupdate.net
109.177.9.166 oldbox.spreadupdate.net
109.177.9.167 fragilemachine.spreadupdate.net
109.177.9.168 alertrabbit.spreadupdate.net
109.177.9.169 richnet.spreadupdate.net
109.177.9.170 superwindow.spreadupdate.net
109.177.9.171 heavenlyball.spreadupdate.net
109.177.9.172 twinbasin.spreadupdate.net
109.177.9.173 steepswing.spreadupdate.net
109.177.9.174 greenapple.spreadupdate.net
109.177.9.175 slowsystem.spreadupdate.net
109.177.9.176 topatom.spreadupdate.net
109.177.9.177 clearrock.spreadupdate.net
109.177.9.178 roastedair.spreadupdate.net
109.177.9.179 lightcopy.spreadupdate.net
109.177.9.180 icyworm.spreadupdate.net
109.177.9.181 tidybase.spreadupdate.net
109.177.9.182 widebean.spreadupdate.net
109.177.9.183 cutebook.spreadupdate.net
109.177.9.184 nicethrone.spreadupdate.net
109.177.9.184 spreadupdate.net
109.177.9.185 smoothbranch.spreadupdate.net
109.177.9.186 pleasantart.transmitupdate.com
109.177.9.187 broadscarf.transmitupdate.com
109.177.9.188 friedcollar.transmitupdate.com
109.177.9.189 oddcard.transmitupdate.com
109.177.9.190 realcellar.transmitupdate.com
109.177.9.191 leafyguide.transmitupdate.com
109.177.9.192 grayjam.transmitupdate.com
109.177.9.193 happysteel.transmitupdate.com
109.177.9.194 sadhand.transmitupdate.com
109.177.9.195 brightwire.transmitupdate.com
109.177.9.196 drytruck.transmitupdate.com
109.177.9.197 freshgrape.transmitupdate.com
109.177.9.198 fiercedust.transmitupdate.com
109.177.9.199 tripleboat.transmitupdate.com
109.177.9.200 minirice.transmitupdate.com
109.177.9.201 goodowl.transmitupdate.com
109.177.9.201 transmitupdate.com
109.177.9.202 shrillcity.transmitupdate.com
109.177.9.203 savoryarm.transmitupdate.com
109.177.9.204 latearea.transmitupdate.com
109.177.9.205 fastmeal.transmitupdate.com
109.177.9.206 earlygarden.transmitupdate.com
109.177.9.207 quietfeast.transmitupdate.com
109.177.9.208 flatclock.transmitupdate.com
109.177.9.209 brownfan.sendupdate.net
109.177.9.210 mutebox.sendupdate.net
109.177.9.211 oldmachine.sendupdate.net
109.177.9.212 fragilerabbit.sendupdate.net
109.177.9.213 alertnet.sendupdate.net
109.177.9.214 richwindow.sendupdate.net
109.177.9.215 superball.sendupdate.net
109.177.9.216 heavenlybasin.sendupdate.net
109.177.9.217 twinswing.sendupdate.net
109.177.9.218 sendupdate.net
109.177.9.218 steepapple.sendupdate.net
109.177.9.219 greensystem.sendupdate.net
109.177.9.220 slowatom.sendupdate.net
109.177.9.221 toprock.sendupdate.net
109.177.9.222 clearair.sendupdate.net
109.177.9.223 roastedcopy.sendupdate.net
109.177.9.224 lightworm.sendupdate.net
109.177.9.225 icybase.sendupdate.net
109.177.9.226 tidybean.sendupdate.net
109.177.9.227 widebook.sendupdate.net
109.177.9.228 cutethrone.sendupdate.net
109.177.9.229 nicebranch.sendupdate.net
109.177.9.230 smoothart.sendupdate.net
109.177.9.231 pleasantscarf.sendupdate.net
109.177.9.232 broadcollar.airupdate.net
109.177.9.233 friedcard.airupdate.net
109.177.9.234 oddcellar.airupdate.net
109.177.9.235 realguide.airupdate.net
109.177.9.236 leafyjam.airupdate.net
109.177.9.237 graysteel.airupdate.net
109.177.9.238 happyhand.airupdate.net
109.177.9.239 sadwire.airupdate.net
109.177.9.240 airupdate.net
109.177.9.240 brighttruck.airupdate.net
109.177.9.241 drygrape.airupdate.net
109.177.9.242 freshdust.airupdate.net
109.177.9.243 fierceboat.airupdate.net
109.177.9.244 triplerice.airupdate.net
109.177.9.245 miniowl.airupdate.net
109.177.9.246 goodcity.airupdate.net
109.177.9.247 shrillarm.airupdate.net
109.177.9.248 savoryarea.airupdate.net
109.177.9.249 latemeal.airupdate.net
109.177.9.250 fastgarden.airupdate.net
109.177.9.251 earlyfeast.airupdate.net
109.177.9.252 quietclock.airupdate.net
109.177.9.253 flatfan.airupdate.net
109.177.9.254 brownbox.airupdate.net
109.177.10.2 oddrock.beamupdate.com
109.177.10.3 steepcellar.beamupdate.com
109.177.10.4 tidycard.beamupdate.com
109.177.10.5 beamupdate.com
109.177.10.5 happysteel.beamupdate.com
109.177.10.6 quietwindow.beamupdate.com
109.177.10.7 icycollar.beamupdate.com
109.177.10.8 roastedguide.beamupdate.com
109.177.10.9 lightworm.beamupdate.com
109.177.10.10 friedowl.beamupdate.com
109.177.10.11 greengarden.beamupdate.com
109.177.10.12 oldatom.beamupdate.com
109.177.10.13 freshnet.beamupdate.com
109.177.10.14 dryswing.beamupdate.com
109.177.10.15 cleargrape.beamupdate.com
109.177.10.16 fiercecopy.beamupdate.com
109.177.10.17 topball.beamupdate.com
109.177.10.18 slowwire.beamupdate.com
109.177.10.19 minihand.beamupdate.com
109.177.10.20 tripleair.beamupdate.com
109.177.10.21 brightcity.beamupdate.com
109.177.10.22 latemachine.beamupdate.com
109.177.10.23 cutebase.beamupdate.com
109.177.10.24 fastbasin.beamupdate.com
109.177.10.25 sadboat.informationupdate.net
109.177.10.26 twinbox.informationupdate.net
109.177.10.27 superbook.informationupdate.net
109.177.10.28 earlyfan.informationupdate.net
109.177.10.29 richclock.informationupdate.net
109.177.10.30 muteapple.informationupdate.net
109.177.10.31 alertarea.informationupdate.net
109.177.10.32 brownart.informationupdate.net
109.177.10.33 leafyfeast.informationupdate.net
109.177.10.34 fragilejam.informationupdate.net
109.177.10.35 smoothbean.informationupdate.net
109.177.10.36 broaddust.informationupdate.net
109.177.10.37 savoryrice.informationupdate.net
109.177.10.38 goodbranch.informationupdate.net
109.177.10.39 realarm.informationupdate.net
109.177.10.40 flatthrone.informationupdate.net
109.177.10.41 widetruck.informationupdate.net
109.177.10.42 nicemeal.informationupdate.net
109.177.10.43 heavenlyscarf.informationupdate.net
109.177.10.44 grayrabbit.informationupdate.net
109.177.10.45 pleasantsystem.informationupdate.net
109.177.10.46 shrillrock.informationupdate.net
109.177.10.47 informationupdate.net
109.177.10.47 oddcellar.informationupdate.net
109.177.10.48 steepcard.broadcastupdate.net
109.177.10.49 tidysteel.broadcastupdate.net
109.177.10.50 happywindow.broadcastupdate.net
109.177.10.51 quietcollar.broadcastupdate.net
109.177.10.52 icyguide.broadcastupdate.net
109.177.10.53 roastedworm.broadcastupdate.net
109.177.10.54 lightowl.broadcastupdate.net
109.177.10.55 friedgarden.broadcastupdate.net
109.177.10.56 greenatom.broadcastupdate.net
109.177.10.57 oldnet.broadcastupdate.net
109.177.10.58 freshswing.broadcastupdate.net
109.177.10.59 drygrape.broadcastupdate.net
109.177.10.60 clearcopy.broadcastupdate.net
109.177.10.61 fierceball.broadcastupdate.net
109.177.10.62 topwire.broadcastupdate.net
109.177.10.63 broadcastupdate.net
109.177.10.63 slowhand.broadcastupdate.net
109.177.10.64 miniair.broadcastupdate.net
109.177.10.65 triplecity.broadcastupdate.net
109.177.10.66 brightmachine.broadcastupdate.net
109.177.10.67 latebase.broadcastupdate.net
109.177.10.68 cutebasin.broadcastupdate.net
109.177.10.69 fastboat.broadcastupdate.net
109.177.10.70 sadbox.broadcastupdate.net
109.177.10.71 twinbook.newmodify.net
109.177.10.72 superfan.newmodify.net
109.177.10.73 earlyclock.newmodify.net
109.177.10.74 richapple.newmodify.net
109.177.10.75 mutearea.newmodify.net
109.177.10.76 alertart.newmodify.net
109.177.10.77 brownfeast.newmodify.net
109.177.10.78 leafyjam.newmodify.net
109.177.10.79 fragilebean.newmodify.net
109.177.10.80 smoothdust.newmodify.net
109.177.10.81 broadrice.newmodify.net
109.177.10.82 savorybranch.newmodify.net
109.177.10.83 goodarm.newmodify.net
109.177.10.84 realthrone.newmodify.net
109.177.10.85 flattruck.newmodify.net
109.177.10.86 widemeal.newmodify.net
109.177.10.87 nicescarf.newmodify.net
109.177.10.88 heavenlyrabbit.newmodify.net
109.177.10.89 graysystem.newmodify.net
109.177.10.90 pleasantrock.newmodify.net
109.177.10.91 newmodify.net
109.177.10.91 shrillcellar.newmodify.net
109.177.10.92 oddcard.newmodify.net
109.177.10.93 steepsteel.newmodify.net
109.177.10.94 tidywindow.quickoffer.net
109.177.10.95 happycollar.quickoffer.net
109.177.10.96 quietguide.quickoffer.net
109.177.10.97 icyworm.quickoffer.net
109.177.10.98 roastedowl.quickoffer.net
109.177.10.99 lightgarden.quickoffer.net
109.177.10.100 friedatom.quickoffer.net
109.177.10.101 greennet.quickoffer.net
109.177.10.102 oldswing.quickoffer.net
109.177.10.103 freshgrape.quickoffer.net
109.177.10.104 drycopy.quickoffer.net
109.177.10.105 clearball.quickoffer.net
109.177.10.106 fiercewire.quickoffer.net
109.177.10.107 tophand.quickoffer.net
109.177.10.108 slowair.quickoffer.net
109.177.10.109 minicity.quickoffer.net
109.177.10.110 triplemachine.quickoffer.net
109.177.10.111 brightbase.quickoffer.net
109.177.10.112 latebasin.quickoffer.net
109.177.10.113 cuteboat.quickoffer.net
109.177.10.114 fastbox.quickoffer.net
109.177.10.115 sadbook.quickoffer.net
109.177.10.116 quickoffer.net
109.177.10.116 twinfan.quickoffer.net
109.177.10.117 superclock.quickcommand.net
109.177.10.118 earlyapple.quickcommand.net
109.177.10.119 richarea.quickcommand.net
109.177.10.120 muteart.quickcommand.net
109.177.10.121 alertfeast.quickcommand.net
109.177.10.121 quickcommand.net
109.177.10.122 brownjam.quickcommand.net
109.177.10.123 leafybean.quickcommand.net
109.177.10.124 fragiledust.quickcommand.net
109.177.10.125 smoothrice.quickcommand.net
109.177.10.126 broadbranch.quickcommand.net
109.177.10.127 savoryarm.quickcommand.net
109.177.10.128 goodthrone.quickcommand.net
109.177.10.129 realtruck.quickcommand.net
109.177.10.130 flatmeal.quickcommand.net
109.177.10.131 widescarf.quickcommand.net
109.177.10.132 nicerabbit.quickcommand.net
109.177.10.133 heavenlysystem.quickcommand.net
109.177.10.134 grayrock.quickcommand.net
109.177.10.135 pleasantcellar.quickcommand.net
109.177.10.136 shrillcard.quickcommand.net
109.177.10.137 oddsteel.quickcommand.net
109.177.10.138 steepwindow.quickcommand.net
109.177.10.139 tidycollar.quickcommand.net
109.177.10.140 happyguide.quickproposal.net
109.177.10.141 quietworm.quickproposal.net
109.177.10.142 icyowl.quickproposal.net
109.177.10.143 roastedgarden.quickproposal.net
109.177.10.144 lightatom.quickproposal.net
109.177.10.145 friednet.quickproposal.net
109.177.10.146 greenswing.quickproposal.net
109.177.10.147 oldgrape.quickproposal.net
109.177.10.148 freshcopy.quickproposal.net
109.177.10.149 dryball.quickproposal.net
109.177.10.150 clearwire.quickproposal.net
109.177.10.151 fiercehand.quickproposal.net
109.177.10.152 topair.quickproposal.net
109.177.10.153 slowcity.quickproposal.net
109.177.10.154 minimachine.quickproposal.net
109.177.10.155 quickproposal.net
109.177.10.155 triplebase.quickproposal.net
109.177.10.156 brightbasin.quickproposal.net
109.177.10.157 lateboat.quickproposal.net
109.177.10.158 cutebox.quickproposal.net
109.177.10.159 fastbook.quickproposal.net
109.177.10.160 sadfan.quickproposal.net
109.177.10.161 twinclock.quickproposal.net
109.177.10.162 superapple.quickproposal.net
109.177.10.163 earlyarea.quickreturn.net
109.177.10.164 richart.quickreturn.net
109.177.10.165 mutefeast.quickreturn.net
109.177.10.166 alertjam.quickreturn.net
109.177.10.167 brownbean.quickreturn.net
109.177.10.168 leafydust.quickreturn.net
109.177.10.169 fragilerice.quickreturn.net
109.177.10.170 quickreturn.net
109.177.10.170 smoothbranch.quickreturn.net
109.177.10.171 broadarm.quickreturn.net
109.177.10.172 savorythrone.quickreturn.net
109.177.10.173 goodtruck.quickreturn.net
109.177.10.174 realmeal.quickreturn.net
109.177.10.175 flatscarf.quickreturn.net
109.177.10.176 widerabbit.quickreturn.net
109.177.10.177 nicesystem.quickreturn.net
109.177.10.178 heavenlyrock.quickreturn.net
109.177.10.179 graycellar.quickreturn.net
109.177.10.180 pleasantcard.quickreturn.net
109.177.10.181 shrillsteel.quickreturn.net
109.177.10.182 oddwindow.quickreturn.net
109.177.10.183 steepcollar.quickreturn.net
109.177.10.184 tidyguide.quickreturn.net
109.177.10.185 happyworm.quickreturn.net
109.177.10.186 quietowl.quickcounter.net
109.177.10.187 icygarden.quickcounter.net
109.177.10.188 roastedatom.quickcounter.net
109.177.10.189 lightnet.quickcounter.net
109.177.10.190 friedswing.quickcounter.net
109.177.10.191 greengrape.quickcounter.net
109.177.10.192 oldcopy.quickcounter.net
109.177.10.192 quickcounter.net
109.177.10.193 freshball.quickcounter.net
109.177.10.194 drywire.quickcounter.net
109.177.10.195 clearhand.quickcounter.net
109.177.10.196 fierceair.quickcounter.net
109.177.10.197 topcity.quickcounter.net
109.177.10.198 slowmachine.quickcounter.net
109.177.10.199 minibase.quickcounter.net
109.177.10.200 triplebasin.quickcounter.net
109.177.10.201 brightboat.quickcounter.net
109.177.10.202 latebox.quickcounter.net
109.177.10.203 cutebook.quickcounter.net
109.177.10.204 fastfan.quickcounter.net
109.177.10.205 sadclock.quickcounter.net
109.177.10.206 twinapple.quickcounter.net
109.177.10.207 superarea.quickcounter.net
109.177.10.208 earlyart.quickcounter.net
109.177.10.209 richfeast.quickterm.net
109.177.10.210 mutejam.quickterm.net
109.177.10.211 alertbean.quickterm.net
109.177.10.212 browndust.quickterm.net
109.177.10.213 leafyrice.quickterm.net
109.177.10.214 fragilebranch.quickterm.net
109.177.10.215 smootharm.quickterm.net
109.177.10.216 broadthrone.quickterm.net
109.177.10.217 savorytruck.quickterm.net
109.177.10.218 goodmeal.quickterm.net
109.177.10.219 realscarf.quickterm.net
109.177.10.220 flatrabbit.quickterm.net
109.177.10.221 widesystem.quickterm.net
109.177.10.222 nicerock.quickterm.net
109.177.10.223 heavenlycellar.quickterm.net
109.177.10.223 quickterm.net
109.177.10.224 graycard.quickterm.net
109.177.10.225 pleasantsteel.quickterm.net
109.177.10.226 shrillwindow.quickterm.net
109.177.10.227 oddcollar.quickterm.net
109.177.10.228 steepguide.quickterm.net
109.177.10.229 tidyworm.quickterm.net
109.177.10.230 happyowl.quickterm.net
109.177.10.231 quietgarden.quickterm.net
109.177.10.232 icyatom.quickremark.net
109.177.10.233 roastednet.quickremark.net
109.177.10.234 lightswing.quickremark.net
109.177.10.235 friedgrape.quickremark.net
109.177.10.236 greencopy.quickremark.net
109.177.10.236 quickremark.net
109.177.10.237 oldball.quickremark.net
109.177.10.238 freshwire.quickremark.net
109.177.10.239 dryhand.quickremark.net
109.177.10.240 clearair.quickremark.net
109.177.10.241 fiercecity.quickremark.net
109.177.10.242 topmachine.quickremark.net
109.177.10.243 slowbase.quickremark.net
109.177.10.244 minibasin.quickremark.net
109.177.10.245 tripleboat.quickremark.net
109.177.10.246 brightbox.quickremark.net
109.177.10.247 latebook.quickremark.net
109.177.10.248 cutefan.quickremark.net
109.177.10.249 fastclock.quickremark.net
109.177.10.250 sadapple.quickremark.net
109.177.10.251 twinarea.quickremark.net
109.177.10.252 superart.quickremark.net
109.177.10.253 earlyfeast.quickremark.net
109.177.10.254 richjam.quickremark.net
109.177.11.2 icywire.quickstate.net
109.177.11.3 steepworm.quickstate.net
109.177.11.4 brighttruck.quickstate.net
109.177.11.5 goodmachine.quickstate.net
109.177.11.6 earlyboat.quickstate.net
109.177.11.7 graythrone.quickstate.net
109.177.11.8 flatguide.quickstate.net
109.177.11.9 latearm.quickstate.net
109.177.11.10 minirabbit.quickstate.net
109.177.11.10 quickstate.net
109.177.11.11 browngarden.quickstate.net
109.177.11.12 heavenlyhand.quickstate.net
109.177.11.13 fierceart.quickstate.net
109.177.11.14 leafyarea.quickstate.net
109.177.11.15 cuterock.quickstate.net
109.177.11.16 widebox.quickstate.net
109.177.11.17 alertclock.quickstate.net
109.177.11.18 oddcity.quickstate.net
109.177.11.19 friednet.quickstate.net
109.177.11.20 lightbean.quickstate.net
109.177.11.21 broadcellar.quickstate.net
109.177.11.22 triplescarf.quickstate.net
109.177.11.23 greengrape.quickstate.net
109.177.11.24 shrillwindow.quickstate.net
109.177.11.25 tidybook.quickregard.com
109.177.11.26 oldsystem.quickregard.com
109.177.11.27 pleasantmeal.quickregard.com
109.177.11.28 muteatom.quickregard.com
109.177.11.29 quickregard.com
109.177.11.29 topjam.quickregard.com
109.177.11.30 smoothfan.quickregard.com
109.177.11.31 richcollar.quickregard.com
109.177.11.32 freshbase.quickregard.com
109.177.11.33 fastfeast.quickregard.com
109.177.11.34 fragilebasin.quickregard.com
109.177.11.35 sadair.quickregard.com
109.177.11.36 superswing.quickregard.com
109.177.11.37 clearowl.quickregard.com
109.177.11.38 drydust.quickregard.com
109.177.11.39 savoryapple.quickregard.com
109.177.11.40 roastedsteel.quickregard.com
109.177.11.41 nicecard.quickregard.com
109.177.11.42 happyrice.quickregard.com
109.177.11.43 twinbranch.quickregard.com
109.177.11.44 realcopy.quickregard.com
109.177.11.45 slowball.quickregard.com
109.177.11.46 quietwire.quickregard.com
109.177.11.47 icyworm.quickregard.com
109.177.11.48 steeptruck.quickqualifier.net
109.177.11.49 brightmachine.quickqualifier.net
109.177.11.50 goodboat.quickqualifier.net
109.177.11.51 earlythrone.quickqualifier.net
109.177.11.52 grayguide.quickqualifier.net
109.177.11.53 flatarm.quickqualifier.net
109.177.11.54 laterabbit.quickqualifier.net
109.177.11.55 minigarden.quickqualifier.net
109.177.11.56 brownhand.quickqualifier.net
109.177.11.57 heavenlyart.quickqualifier.net
109.177.11.58 fiercearea.quickqualifier.net
109.177.11.59 leafyrock.quickqualifier.net
109.177.11.60 cutebox.quickqualifier.net
109.177.11.61 wideclock.quickqualifier.net
109.177.11.62 alertcity.quickqualifier.net
109.177.11.63 oddnet.quickqualifier.net
109.177.11.64 friedbean.quickqualifier.net
109.177.11.65 lightcellar.quickqualifier.net
109.177.11.66 broadscarf.quickqualifier.net
109.177.11.67 triplegrape.quickqualifier.net
109.177.11.68 greenwindow.quickqualifier.net
109.177.11.69 shrillbook.quickqualifier.net
109.177.11.70 quickqualifier.net
109.177.11.70 tidysystem.quickqualifier.net
109.177.11.71 oldmeal.quickreception.com
109.177.11.72 pleasantatom.quickreception.com
109.177.11.73 mutejam.quickreception.com
109.177.11.74 topfan.quickreception.com
109.177.11.75 smoothcollar.quickreception.com
109.177.11.76 richbase.quickreception.com
109.177.11.77 freshfeast.quickreception.com
109.177.11.78 fastbasin.quickreception.com
109.177.11.79 fragileair.quickreception.com
109.177.11.80 sadswing.quickreception.com
109.177.11.81 superowl.quickreception.com
109.177.11.82 cleardust.quickreception.com
109.177.11.83 dryapple.quickreception.com
109.177.11.84 quickreception.com
109.177.11.84 savorysteel.quickreception.com
109.177.11.85 roastedcard.quickreception.com
109.177.11.86 nicerice.quickreception.com
109.177.11.87 happybranch.quickreception.com
109.177.11.88 twincopy.quickreception.com
109.177.11.89 realball.quickreception.com
109.177.11.90 slowwire.quickreception.com
109.177.11.91 quietworm.quickreception.com
109.177.11.92 icytruck.quickreception.com
109.177.11.93 steepmachine.quickreception.com
109.177.11.94 brightboat.quickreaction.net
109.177.11.95 goodthrone.quickreaction.net
109.177.11.96 earlyguide.quickreaction.net
109.177.11.97 grayarm.quickreaction.net
109.177.11.98 flatrabbit.quickreaction.net
109.177.11.99 lategarden.quickreaction.net
109.177.11.100 minihand.quickreaction.net
109.177.11.101 brownart.quickreaction.net
109.177.11.102 heavenlyarea.quickreaction.net
109.177.11.103 fiercerock.quickreaction.net
109.177.11.104 leafybox.quickreaction.net
109.177.11.105 cuteclock.quickreaction.net
109.177.11.106 widecity.quickreaction.net
109.177.11.107 alertnet.quickreaction.net
109.177.11.108 oddbean.quickreaction.net
109.177.11.109 friedcellar.quickreaction.net
109.177.11.110 lightscarf.quickreaction.net
109.177.11.111 broadgrape.quickreaction.net
109.177.11.112 triplewindow.quickreaction.net
109.177.11.113 greenbook.quickreaction.net
109.177.11.114 shrillsystem.quickreaction.net
109.177.11.115 quickreaction.net
109.177.11.115 tidymeal.quickreaction.net
109.177.11.116 oldatom.quickreaction.net
109.177.11.117 pleasantjam.sideresponse.com
109.177.11.118 mutefan.sideresponse.com
109.177.11.119 topcollar.sideresponse.com
109.177.11.120 smoothbase.sideresponse.com
109.177.11.121 richfeast.sideresponse.com
109.177.11.122 freshbasin.sideresponse.com
109.177.11.123 fastair.sideresponse.com
109.177.11.124 fragileswing.sideresponse.com
109.177.11.125 sadowl.sideresponse.com
109.177.11.126 superdust.sideresponse.com
109.177.11.127 clearapple.sideresponse.com
109.177.11.128 drysteel.sideresponse.com
109.177.11.129 savorycard.sideresponse.com
109.177.11.129 sideresponse.com
109.177.11.130 roastedrice.sideresponse.com
109.177.11.131 nicebranch.sideresponse.com
109.177.11.132 happycopy.sideresponse.com
109.177.11.133 twinball.sideresponse.com
109.177.11.134 realwire.sideresponse.com
109.177.11.135 slowworm.sideresponse.com
109.177.11.136 quiettruck.sideresponse.com
109.177.11.137 icymachine.sideresponse.com
109.177.11.138 steepboat.sideresponse.com
109.177.11.139 brightthrone.sideresponse.com
109.177.11.140 goodguide.quickeasyrank.com
109.177.11.141 earlyarm.quickeasyrank.com
109.177.11.142 grayrabbit.quickeasyrank.com
109.177.11.143 flatgarden.quickeasyrank.com
109.177.11.143 quickeasyrank.com
109.177.11.144 latehand.quickeasyrank.com
109.177.11.145 miniart.quickeasyrank.com
109.177.11.146 brownarea.quickeasyrank.com
109.177.11.147 heavenlyrock.quickeasyrank.com
109.177.11.148 fiercebox.quickeasyrank.com
109.177.11.149 leafyclock.quickeasyrank.com
109.177.11.150 cutecity.quickeasyrank.com
109.177.11.151 widenet.quickeasyrank.com
109.177.11.152 alertbean.quickeasyrank.com
109.177.11.153 oddcellar.quickeasyrank.com
109.177.11.154 friedscarf.quickeasyrank.com
109.177.11.155 lightgrape.quickeasyrank.com
109.177.11.156 broadwindow.quickeasyrank.com
109.177.11.157 triplebook.quickeasyrank.com
109.177.11.158 greensystem.quickeasyrank.com
109.177.11.159 shrillmeal.quickeasyrank.com
109.177.11.160 tidyatom.quickeasyrank.com
109.177.11.161 oldjam.quickeasyrank.com
109.177.11.162 pleasantfan.quickeasyrank.com
109.177.11.163 mutecollar.quickeasyorder.com
109.177.11.164 topbase.quickeasyorder.com
109.177.11.165 smoothfeast.quickeasyorder.com
109.177.11.166 quickeasyorder.com
109.177.11.166 richbasin.quickeasyorder.com
109.177.11.167 freshair.quickeasyorder.com
109.177.11.168 fastswing.quickeasyorder.com
109.177.11.169 fragileowl.quickeasyorder.com
109.177.11.170 saddust.quickeasyorder.com
109.177.11.171 superapple.quickeasyorder.com
109.177.11.172 clearsteel.quickeasyorder.com
109.177.11.173 drycard.quickeasyorder.com
109.177.11.174 savoryrice.quickeasyorder.com
109.177.11.175 roastedbranch.quickeasyorder.com
109.177.11.176 nicecopy.quickeasyorder.com
109.177.11.177 happyball.quickeasyorder.com
109.177.11.178 twinwire.quickeasyorder.com
109.177.11.179 realworm.quickeasyorder.com
109.177.11.180 slowtruck.quickeasyorder.com
109.177.11.181 quietmachine.quickeasyorder.com
109.177.11.182 icyboat.quickeasyorder.com
109.177.11.183 steepthrone.quickeasyorder.com
109.177.11.184 brightguide.quickeasyorder.com
109.177.11.185 goodarm.quickeasyorder.com
109.177.11.186 earlyrabbit.quickeasygrade.com
109.177.11.187 graygarden.quickeasygrade.com
109.177.11.188 flathand.quickeasygrade.com
109.177.11.189 lateart.quickeasygrade.com
109.177.11.189 quickeasygrade.com
109.177.11.190 miniarea.quickeasygrade.com
109.177.11.191 brownrock.quickeasygrade.com
109.177.11.192 heavenlybox.quickeasygrade.com
109.177.11.193 fierceclock.quickeasygrade.com
109.177.11.194 leafycity.quickeasygrade.com
109.177.11.195 cutenet.quickeasygrade.com
109.177.11.196 widebean.quickeasygrade.com
109.177.11.197 alertcellar.quickeasygrade.com
109.177.11.198 oddscarf.quickeasygrade.com
109.177.11.199 friedgrape.quickeasygrade.com
109.177.11.200 lightwindow.quickeasygrade.com
109.177.11.201 broadbook.quickeasygrade.com
109.177.11.202 triplesystem.quickeasygrade.com
109.177.11.203 greenmeal.quickeasygrade.com
109.177.11.204 shrillatom.quickeasygrade.com
109.177.11.205 tidyjam.quickeasygrade.com
109.177.11.206 oldfan.quickeasygrade.com
109.177.11.207 pleasantcollar.quickeasygrade.com
109.177.11.208 mutebase.quickeasygrade.com
109.177.11.209 topfeast.ultimatecreativity.net
109.177.11.210 smoothbasin.ultimatecreativity.net
109.177.11.211 richair.ultimatecreativity.net
109.177.11.212 freshswing.ultimatecreativity.net
109.177.11.212 ultimatecreativity.net
109.177.11.213 fastowl.ultimatecreativity.net
109.177.11.214 fragiledust.ultimatecreativity.net
109.177.11.215 sadapple.ultimatecreativity.net
109.177.11.216 supersteel.ultimatecreativity.net
109.177.11.217 clearcard.ultimatecreativity.net
109.177.11.218 dryrice.ultimatecreativity.net
109.177.11.219 savorybranch.ultimatecreativity.net
109.177.11.220 roastedcopy.ultimatecreativity.net
109.177.11.221 niceball.ultimatecreativity.net
109.177.11.222 happywire.ultimatecreativity.net
109.177.11.223 twinworm.ultimatecreativity.net
109.177.11.224 realtruck.ultimatecreativity.net
109.177.11.225 slowmachine.ultimatecreativity.net
109.177.11.226 quietboat.ultimatecreativity.net
109.177.11.227 icythrone.ultimatecreativity.net
109.177.11.228 steepguide.ultimatecreativity.net
109.177.11.229 brightarm.ultimatecreativity.net
109.177.11.230 goodrabbit.ultimatecreativity.net
109.177.11.231 earlygarden.ultimatecreativity.net
109.177.11.232 grayhand.ultimateassist.net
109.177.11.233 flatart.ultimateassist.net
109.177.11.234 latearea.ultimateassist.net
109.177.11.234 ultimateassist.net
109.177.11.235 minirock.ultimateassist.net
109.177.11.236 brownbox.ultimateassist.net
109.177.11.237 heavenlyclock.ultimateassist.net
109.177.11.238 fiercecity.ultimateassist.net
109.177.11.239 leafynet.ultimateassist.net
109.177.11.240 cutebean.ultimateassist.net
109.177.11.241 widecellar.ultimateassist.net
109.177.11.242 alertscarf.ultimateassist.net
109.177.11.243 oddgrape.ultimateassist.net
109.177.11.244 friedwindow.ultimateassist.net
109.177.11.245 lightbook.ultimateassist.net
109.177.11.246 broadsystem.ultimateassist.net
109.177.11.247 triplemeal.ultimateassist.net
109.177.11.248 greenatom.ultimateassist.net
109.177.11.249 shrilljam.ultimateassist.net
109.177.11.250 tidyfan.ultimateassist.net
109.177.11.251 oldcollar.ultimateassist.net
109.177.11.252 pleasantbase.ultimateassist.net
109.177.11.253 mutefeast.ultimateassist.net
109.177.11.254 topbasin.ultimateassist.net
109.177.20.2 latewindow.ultimateaid.net
109.177.20.3 steepbasin.ultimateaid.net
109.177.20.4 roastedboat.ultimateaid.net
109.177.20.5 cutenet.ultimateaid.net
109.177.20.6 widebase.ultimateaid.net
109.177.20.7 fastball.ultimateaid.net
109.177.20.7 ultimateaid.net
109.177.20.8 slowwire.ultimateaid.net
109.177.20.9 minithrone.ultimateaid.net
109.177.20.10 smoothmachine.ultimateaid.net
109.177.20.11 superclock.ultimateaid.net
109.177.20.12 happyguide.ultimateaid.net
109.177.20.13 drycellar.ultimateaid.net
109.177.20.14 brightworm.ultimateaid.net
109.177.20.15 tidyscarf.ultimateaid.net
109.177.20.16 grayart.ultimateaid.net
109.177.20.17 leafyfan.ultimateaid.net
109.177.20.18 richair.ultimateaid.net
109.177.20.19 pleasantcity.ultimateaid.net
109.177.20.20 friedowl.ultimateaid.net
109.177.20.21 greentruck.ultimateaid.net
109.177.20.22 oddbean.ultimateaid.net
109.177.20.23 broadsystem.ultimateaid.net
109.177.20.24 lightgarden.ultimateaid.net
109.177.20.25 oldswing.ultimatespecialty.com
109.177.20.26 cleararm.ultimatespecialty.com
109.177.20.27 flatfeast.ultimatespecialty.com
109.177.20.28 fragilehand.ultimatespecialty.com
109.177.20.29 tripleatom.ultimatespecialty.com
109.177.20.30 icyapple.ultimatespecialty.com
109.177.20.31 alertbook.ultimatespecialty.com
109.177.20.32 savorycopy.ultimatespecialty.com
109.177.20.33 quietgrape.ultimatespecialty.com
109.177.20.34 fiercerabbit.ultimatespecialty.com
109.177.20.35 twinsteel.ultimatespecialty.com
109.177.20.36 nicecard.ultimatespecialty.com
109.177.20.37 sadbox.ultimatespecialty.com
109.177.20.38 mutebranch.ultimatespecialty.com
109.177.20.39 realmeal.ultimatespecialty.com
109.177.20.40 heavenlydust.ultimatespecialty.com
109.177.20.41 toprice.ultimatespecialty.com
109.177.20.42 goodarea.ultimatespecialty.com
109.177.20.43 brownrock.ultimatespecialty.com
109.177.20.44 shrilljam.ultimatespecialty.com
109.177.20.45 freshcollar.ultimatespecialty.com
109.177.20.46 earlywindow.ultimatespecialty.com
109.177.20.46 ultimatespecialty.com
109.177.20.47 latebasin.ultimatespecialty.com
109.177.20.48 steepboat.statusoversight.com
109.177.20.49 roastednet.statusoversight.com
109.177.20.50 cutebase.statusoversight.com
109.177.20.51 wideball.statusoversight.com
109.177.20.52 fastwire.statusoversight.com
109.177.20.53 slowthrone.statusoversight.com
109.177.20.54 minimachine.statusoversight.com
109.177.20.55 smoothclock.statusoversight.com
109.177.20.56 superguide.statusoversight.com
109.177.20.57 happycellar.statusoversight.com
109.177.20.58 dryworm.statusoversight.com
109.177.20.59 brightscarf.statusoversight.com
109.177.20.60 tidyart.statusoversight.com
109.177.20.61 grayfan.statusoversight.com
109.177.20.62 leafyair.statusoversight.com
109.177.20.63 richcity.statusoversight.com
109.177.20.64 pleasantowl.statusoversight.com
109.177.20.65 friedtruck.statusoversight.com
109.177.20.66 greenbean.statusoversight.com
109.177.20.67 oddsystem.statusoversight.com
109.177.20.68 broadgarden.statusoversight.com
109.177.20.69 lightswing.statusoversight.com
109.177.20.70 oldarm.statusoversight.com
109.177.20.70 statusoversight.com
109.177.20.71 clearfeast.statustreatment.com
109.177.20.72 flathand.statustreatment.com
109.177.20.73 fragileatom.statustreatment.com
109.177.20.73 statustreatment.com
109.177.20.74 tripleapple.statustreatment.com
109.177.20.75 icybook.statustreatment.com
109.177.20.76 alertcopy.statustreatment.com
109.177.20.77 savorygrape.statustreatment.com
109.177.20.78 quietrabbit.statustreatment.com
109.177.20.79 fiercesteel.statustreatment.com
109.177.20.80 twincard.statustreatment.com
109.177.20.81 nicebox.statustreatment.com
109.177.20.82 sadbranch.statustreatment.com
109.177.20.83 mutemeal.statustreatment.com
109.177.20.84 realdust.statustreatment.com
109.177.20.85 heavenlyrice.statustreatment.com
109.177.20.86 toparea.statustreatment.com
109.177.20.87 goodrock.statustreatment.com
109.177.20.88 brownjam.statustreatment.com
109.177.20.89 shrillcollar.statustreatment.com
109.177.20.90 freshwindow.statustreatment.com
109.177.20.91 earlybasin.statustreatment.com
109.177.20.92 lateboat.statustreatment.com
109.177.20.93 steepnet.statustreatment.com
109.177.20.94 roastedbase.statushandle.com
109.177.20.95 cuteball.statushandle.com
109.177.20.96 widewire.statushandle.com
109.177.20.97 fastthrone.statushandle.com
109.177.20.98 slowmachine.statushandle.com
109.177.20.99 miniclock.statushandle.com
109.177.20.100 smoothguide.statushandle.com
109.177.20.101 supercellar.statushandle.com
109.177.20.102 happyworm.statushandle.com
109.177.20.103 dryscarf.statushandle.com
109.177.20.104 brightart.statushandle.com
109.177.20.105 tidyfan.statushandle.com
109.177.20.106 grayair.statushandle.com
109.177.20.107 leafycity.statushandle.com
109.177.20.108 richowl.statushandle.com
109.177.20.109 pleasanttruck.statushandle.com
109.177.20.110 friedbean.statushandle.com
109.177.20.111 greensystem.statushandle.com
109.177.20.112 oddgarden.statushandle.com
109.177.20.113 broadswing.statushandle.com
109.177.20.114 lightarm.statushandle.com
109.177.20.115 oldfeast.statushandle.com
109.177.20.116 clearhand.statushandle.com
109.177.20.116 statushandle.com
109.177.20.117 flatatom.statusdeal.net
109.177.20.118 fragileapple.statusdeal.net
109.177.20.119 triplebook.statusdeal.net
109.177.20.120 icycopy.statusdeal.net
109.177.20.121 alertgrape.statusdeal.net
109.177.20.121 statusdeal.net
109.177.20.122 savoryrabbit.statusdeal.net
109.177.20.123 quietsteel.statusdeal.net
109.177.20.124 fiercecard.statusdeal.net
109.177.20.125 twinbox.statusdeal.net
109.177.20.126 nicebranch.statusdeal.net
109.177.20.127 sadmeal.statusdeal.net
109.177.20.128 mutedust.statusdeal.net
109.177.20.129 realrice.statusdeal.net
109.177.20.130 heavenlyarea.statusdeal.net
109.177.20.131 toprock.statusdeal.net
109.177.20.132 goodjam.statusdeal.net
109.177.20.133 browncollar.statusdeal.net
109.177.20.134 shrillwindow.statusdeal.net
109.177.20.135 freshbasin.statusdeal.net
109.177.20.136 earlyboat.statusdeal.net
109.177.20.137 latenet.statusdeal.net
109.177.20.138 steepbase.statusdeal.net
109.177.20.139 roastedball.statusdeal.net
109.177.20.140 cutewire.statuscare.net
109.177.20.141 statuscare.net
109.177.20.141 widethrone.statuscare.net
109.177.20.142 fastmachine.statuscare.net
109.177.20.143 slowclock.statuscare.net
109.177.20.144 miniguide.statuscare.net
109.177.20.145 smoothcellar.statuscare.net
109.177.20.146 superworm.statuscare.net
109.177.20.147 happyscarf.statuscare.net
109.177.20.148 dryart.statuscare.net
109.177.20.149 brightfan.statuscare.net
109.177.20.150 tidyair.statuscare.net
109.177.20.151 graycity.statuscare.net
109.177.20.152 leafyowl.statuscare.net
109.177.20.153 richtruck.statuscare.net
109.177.20.154 pleasantbean.statuscare.net
109.177.20.155 friedsystem.statuscare.net
109.177.20.156 greengarden.statuscare.net
109.177.20.157 oddswing.statuscare.net
109.177.20.158 broadarm.statuscare.net
109.177.20.159 lightfeast.statuscare.net
109.177.20.160 oldhand.statuscare.net
109.177.20.161 clearatom.statuscare.net
109.177.20.162 flatapple.statuscare.net
109.177.20.163 fragilebook.statusoversee.com
109.177.20.164 triplecopy.statusoversee.com
109.177.20.165 icygrape.statusoversee.com
109.177.20.166 alertrabbit.statusoversee.com
109.177.20.167 savorysteel.statusoversee.com
109.177.20.168 quietcard.statusoversee.com
109.177.20.169 fiercebox.statusoversee.com
109.177.20.170 twinbranch.statusoversee.com
109.177.20.171 nicemeal.statusoversee.com
109.177.20.172 saddust.statusoversee.com
109.177.20.173 muterice.statusoversee.com
109.177.20.174 realarea.statusoversee.com
109.177.20.175 heavenlyrock.statusoversee.com
109.177.20.176 topjam.statusoversee.com
109.177.20.177 goodcollar.statusoversee.com
109.177.20.178 brownwindow.statusoversee.com
109.177.20.179 shrillbasin.statusoversee.com
109.177.20.180 freshboat.statusoversee.com
109.177.20.181 earlynet.statusoversee.com
109.177.20.182 latebase.statusoversee.com
109.177.20.182 statusoversee.com
109.177.20.183 steepball.statusoversee.com
109.177.20.184 roastedwire.statusoversee.com
109.177.20.185 cutethrone.statusoversee.com
109.177.20.186 widemachine.statusmanage.com
109.177.20.187 fastclock.statusmanage.com
109.177.20.188 slowguide.statusmanage.com
109.177.20.189 minicellar.statusmanage.com
109.177.20.190 smoothworm.statusmanage.com
109.177.20.191 superscarf.statusmanage.com
109.177.20.192 happyart.statusmanage.com
109.177.20.193 dryfan.statusmanage.com
109.177.20.194 brightair.statusmanage.com
109.177.20.195 tidycity.statusmanage.com
109.177.20.196 grayowl.statusmanage.com
109.177.20.197 leafytruck.statusmanage.com
109.177.20.197 statusmanage.com
109.177.20.198 richbean.statusmanage.com
109.177.20.199 pleasantsystem.statusmanage.com
109.177.20.200 friedgarden.statusmanage.com
109.177.20.201 greenswing.statusmanage.com
109.177.20.202 oddarm.statusmanage.com
109.177.20.203 broadfeast.statusmanage.com
109.177.20.204 lighthand.statusmanage.com
109.177.20.205 oldatom.statusmanage.com
109.177.20.206 clearapple.statusmanage.com
109.177.20.207 flatbook.statusmanage.com
109.177.20.208 fragilecopy.statusmanage.com
109.177.20.209 triplegrape.statusdirection.com
109.177.20.210 icyrabbit.statusdirection.com
109.177.20.211 alertsteel.statusdirection.com
109.177.20.212 savorycard.statusdirection.com
109.177.20.213 quietbox.statusdirection.com
109.177.20.214 fiercebranch.statusdirection.com
109.177.20.215 twinmeal.statusdirection.com
109.177.20.216 nicedust.statusdirection.com
109.177.20.217 sadrice.statusdirection.com
109.177.20.218 mutearea.statusdirection.com
109.177.20.219 realrock.statusdirection.com
109.177.20.220 heavenlyjam.statusdirection.com
109.177.20.221 statusdirection.com
109.177.20.221 topcollar.statusdirection.com
109.177.20.222 goodwindow.statusdirection.com
109.177.20.223 brownbasin.statusdirection.com
109.177.20.224 shrillboat.statusdirection.com
109.177.20.225 freshnet.statusdirection.com
109.177.20.226 earlybase.statusdirection.com
109.177.20.227 lateball.statusdirection.com
109.177.20.228 steepwire.statusdirection.com
109.177.20.229 roastedthrone.statusdirection.com
109.177.20.230 cutemachine.statusdirection.com
109.177.20.231 wideclock.statusdirection.com
109.177.20.232 fastguide.stepmanagement.net
109.177.20.233 slowcellar.stepmanagement.net
109.177.20.234 miniworm.stepmanagement.net
109.177.20.235 smoothscarf.stepmanagement.net
109.177.20.235 stepmanagement.net
109.177.20.236 superart.stepmanagement.net
109.177.20.237 happyfan.stepmanagement.net
109.177.20.238 dryair.stepmanagement.net
109.177.20.239 brightcity.stepmanagement.net
109.177.20.240 tidyowl.stepmanagement.net
109.177.20.241 graytruck.stepmanagement.net
109.177.20.242 leafybean.stepmanagement.net
109.177.20.243 richsystem.stepmanagement.net
109.177.20.244 pleasantgarden.stepmanagement.net
109.177.20.245 friedswing.stepmanagement.net
109.177.20.246 greenarm.stepmanagement.net
109.177.20.247 oddfeast.stepmanagement.net
109.177.20.248 broadhand.stepmanagement.net
109.177.20.249 lightatom.stepmanagement.net
109.177.20.250 oldapple.stepmanagement.net
109.177.20.251 clearbook.stepmanagement.net
109.177.20.252 flatcopy.stepmanagement.net
109.177.20.253 fragilegrape.stepmanagement.net
109.177.20.254 triplerabbit.stepmanagement.net
109.177.21.2 leafynet.tiermanagement.net
109.177.21.3 steepworm.tiermanagement.net
109.177.21.4 smoothbranch.tiermanagement.net
109.177.21.5 realowl.tiermanagement.net
109.177.21.6 fastbook.tiermanagement.net
109.177.21.7 pleasantclock.tiermanagement.net
109.177.21.8 greenboat.tiermanagement.net
109.177.21.9 latemachine.tiermanagement.net
109.177.21.10 heavenlysteel.tiermanagement.net
109.177.21.11 savoryapple.tiermanagement.net
109.177.21.12 alerttruck.tiermanagement.net
109.177.21.13 quietarm.tiermanagement.net
109.177.21.14 slowwire.tiermanagement.net
109.177.21.15 minicard.tiermanagement.net
109.177.21.16 oddbase.tiermanagement.net
109.177.21.17 earlyart.tiermanagement.net
109.177.21.17 tiermanagement.net
109.177.21.18 cutesystem.tiermanagement.net
109.177.21.19 lightcity.tiermanagement.net
109.177.21.20 nicedust.tiermanagement.net
109.177.21.21 tophand.tiermanagement.net
109.177.21.22 triplewindow.tiermanagement.net
109.177.21.23 tidycopy.tiermanagement.net
109.177.21.24 twinair.tiermanagement.net
109.177.21.25 roastedbean.quickmodifier.com
109.177.21.26 broadmeal.quickmodifier.com
109.177.21.27 mutethrone.quickmodifier.com
109.177.21.28 widebox.quickmodifier.com
109.177.21.29 superatom.quickmodifier.com
109.177.21.30 friedfan.quickmodifier.com
109.177.21.30 quickmodifier.com
109.177.21.31 richcollar.quickmodifier.com
109.177.21.32 flatjam.quickmodifier.com
109.177.21.33 freshgrape.quickmodifier.com
109.177.21.34 fierceswing.quickmodifier.com
109.177.21.35 cleararea.quickmodifier.com
109.177.21.36 brownscarf.quickmodifier.com
109.177.21.37 grayfeast.quickmodifier.com
109.177.21.38 fragilerabbit.quickmodifier.com
109.177.21.39 icycellar.quickmodifier.com
109.177.21.40 brightgarden.quickmodifier.com
109.177.21.41 oldbasin.quickmodifier.com
109.177.21.42 sadrock.quickmodifier.com
109.177.21.43 shrillrice.quickmodifier.com
109.177.21.44 goodball.quickmodifier.com
109.177.21.45 dryguide.quickmodifier.com
109.177.21.46 happynet.quickmodifier.com
109.177.21.47 leafyworm.quickmodifier.com
109.177.21.48 steepbranch.quickword.net
109.177.21.49 smoothowl.quickword.net
109.177.21.50 realbook.quickword.net
109.177.21.51 fastclock.quickword.net
109.177.21.52 pleasantboat.quickword.net
109.177.21.53 greenmachine.quickword.net
109.177.21.54 latesteel.quickword.net
109.177.21.55 heavenlyapple.quickword.net
109.177.21.56 savorytruck.quickword.net
109.177.21.57 alertarm.quickword.net
109.177.21.58 quietwire.quickword.net
109.177.21.59 slowcard.quickword.net
109.177.21.60 minibase.quickword.net
109.177.21.61 oddart.quickword.net
109.177.21.62 earlysystem.quickword.net
109.177.21.63 cutecity.quickword.net
109.177.21.63 quickword.net
109.177.21.64 lightdust.quickword.net
109.177.21.65 nicehand.quickword.net
109.177.21.66 topwindow.quickword.net
109.177.21.67 triplecopy.quickword.net
109.177.21.68 tidyair.quickword.net
109.177.21.69 twinbean.quickword.net
109.177.21.70 roastedmeal.quickword.net
109.177.21.71 broadthrone.quickformulate.com
109.177.21.72 mutebox.quickformulate.com
109.177.21.73 wideatom.quickformulate.com
109.177.21.74 superfan.quickformulate.com
109.177.21.75 friedcollar.quickformulate.com
109.177.21.76 richjam.quickformulate.com
109.177.21.77 flatgrape.quickformulate.com
109.177.21.77 quickformulate.com
109.177.21.78 freshswing.quickformulate.com
109.177.21.79 fiercearea.quickformulate.com
109.177.21.80 clearscarf.quickformulate.com
109.177.21.81 brownfeast.quickformulate.com
109.177.21.82 grayrabbit.quickformulate.com
109.177.21.83 fragilecellar.quickformulate.com
109.177.21.84 icygarden.quickformulate.com
109.177.21.85 brightbasin.quickformulate.com
109.177.21.86 oldrock.quickformulate.com
109.177.21.87 sadrice.quickformulate.com
109.177.21.88 shrillball.quickformulate.com
109.177.21.89 goodguide.quickformulate.com
109.177.21.90 drynet.quickformulate.com
109.177.21.91 happyworm.quickformulate.com
109.177.21.92 leafybranch.quickformulate.com
109.177.21.93 steepowl.quickformulate.com
109.177.21.94 smoothbook.quickwind.net
109.177.21.95 realclock.quickwind.net
109.177.21.96 fastboat.quickwind.net
109.177.21.97 pleasantmachine.quickwind.net
109.177.21.98 greensteel.quickwind.net
109.177.21.99 lateapple.quickwind.net
109.177.21.100 heavenlytruck.quickwind.net
109.177.21.101 savoryarm.quickwind.net
109.177.21.102 alertwire.quickwind.net
109.177.21.103 quietcard.quickwind.net
109.177.21.104 slowbase.quickwind.net
109.177.21.105 miniart.quickwind.net
109.177.21.106 oddsystem.quickwind.net
109.177.21.107 earlycity.quickwind.net
109.177.21.108 cutedust.quickwind.net
109.177.21.109 lighthand.quickwind.net
109.177.21.110 nicewindow.quickwind.net
109.177.21.111 topcopy.quickwind.net
109.177.21.112 quickwind.net
109.177.21.112 tripleair.quickwind.net
109.177.21.113 tidybean.quickwind.net
109.177.21.114 twinmeal.quickwind.net
109.177.21.115 roastedthrone.quickwind.net
109.177.21.116 broadbox.quickwind.net
109.177.21.117 muteatom.quickshock.net
109.177.21.118 widefan.quickshock.net
109.177.21.119 supercollar.quickshock.net
109.177.21.120 friedjam.quickshock.net
109.177.21.121 richgrape.quickshock.net
109.177.21.122 flatswing.quickshock.net
109.177.21.123 fresharea.quickshock.net
109.177.21.124 fiercescarf.quickshock.net
109.177.21.124 quickshock.net
109.177.21.125 clearfeast.quickshock.net
109.177.21.126 brownrabbit.quickshock.net
109.177.21.127 graycellar.quickshock.net
109.177.21.128 fragilegarden.quickshock.net
109.177.21.129 icybasin.quickshock.net
109.177.21.130 brightrock.quickshock.net
109.177.21.131 oldrice.quickshock.net
109.177.21.132 sadball.quickshock.net
109.177.21.133 shrillguide.quickshock.net
109.177.21.134 goodnet.quickshock.net
109.177.21.135 dryworm.quickshock.net
109.177.21.136 happybranch.quickshock.net
109.177.21.137 leafyowl.quickshock.net
109.177.21.138 steepbook.quickshock.net
109.177.21.139 smoothclock.quickshock.net
109.177.21.140 realboat.quickflush.net
109.177.21.141 fastmachine.quickflush.net
109.177.21.142 pleasantsteel.quickflush.net
109.177.21.143 greenapple.quickflush.net
109.177.21.144 latetruck.quickflush.net
109.177.21.145 heavenlyarm.quickflush.net
109.177.21.146 savorywire.quickflush.net
109.177.21.147 alertcard.quickflush.net
109.177.21.148 quietbase.quickflush.net
109.177.21.149 slowart.quickflush.net
109.177.21.150 minisystem.quickflush.net
109.177.21.151 oddcity.quickflush.net
109.177.21.152 earlydust.quickflush.net
109.177.21.153 cutehand.quickflush.net
109.177.21.154 lightwindow.quickflush.net
109.177.21.155 nicecopy.quickflush.net
109.177.21.156 topair.quickflush.net
109.177.21.157 triplebean.quickflush.net
109.177.21.158 tidymeal.quickflush.net
109.177.21.159 twinthrone.quickflush.net
109.177.21.160 roastedbox.quickflush.net
109.177.21.161 broadatom.quickflush.net
109.177.21.162 mutefan.quickflush.net
109.177.21.162 quickflush.net
109.177.21.163 widecollar.quickblush.net
109.177.21.164 superjam.quickblush.net
109.177.21.165 friedgrape.quickblush.net
109.177.21.166 richswing.quickblush.net
109.177.21.167 flatarea.quickblush.net
109.177.21.168 freshscarf.quickblush.net
109.177.21.169 fiercefeast.quickblush.net
109.177.21.170 clearrabbit.quickblush.net
109.177.21.171 browncellar.quickblush.net
109.177.21.172 graygarden.quickblush.net
109.177.21.173 fragilebasin.quickblush.net
109.177.21.174 icyrock.quickblush.net
109.177.21.175 brightrice.quickblush.net
109.177.21.176 oldball.quickblush.net
109.177.21.177 sadguide.quickblush.net
109.177.21.178 shrillnet.quickblush.net
109.177.21.179 goodworm.quickblush.net
109.177.21.180 drybranch.quickblush.net
109.177.21.180 quickblush.net
109.177.21.181 happyowl.quickblush.net
109.177.21.182 leafybook.quickblush.net
109.177.21.183 steepclock.quickblush.net
109.177.21.184 smoothboat.quickblush.net
109.177.21.185 realmachine.quickblush.net
109.177.21.186 faststeel.quickwink.net
109.177.21.187 pleasantapple.quickwink.net
109.177.21.188 greentruck.quickwink.net
109.177.21.189 latearm.quickwink.net
109.177.21.190 heavenlywire.quickwink.net
109.177.21.191 savorycard.quickwink.net
109.177.21.192 alertbase.quickwink.net
109.177.21.193 quietart.quickwink.net
109.177.21.194 slowsystem.quickwink.net
109.177.21.195 minicity.quickwink.net
109.177.21.196 odddust.quickwink.net
109.177.21.197 earlyhand.quickwink.net
109.177.21.198 cutewindow.quickwink.net
109.177.21.199 lightcopy.quickwink.net
109.177.21.200 niceair.quickwink.net
109.177.21.201 topbean.quickwink.net
109.177.21.202 quickwink.net
109.177.21.202 triplemeal.quickwink.net
109.177.21.203 tidythrone.quickwink.net
109.177.21.204 twinbox.quickwink.net
109.177.21.205 roastedatom.quickwink.net
109.177.21.206 broadfan.quickwink.net
109.177.21.207 mutecollar.quickwink.net
109.177.21.208 widejam.quickwink.net
109.177.21.209 supergrape.quicknotice.net
109.177.21.210 friedswing.quicknotice.net
109.177.21.211 richarea.quicknotice.net
109.177.21.212 flatscarf.quicknotice.net
109.177.21.213 freshfeast.quicknotice.net
109.177.21.214 fiercerabbit.quicknotice.net
109.177.21.215 clearcellar.quicknotice.net
109.177.21.216 browngarden.quicknotice.net
109.177.21.217 graybasin.quicknotice.net
109.177.21.217 quicknotice.net
109.177.21.218 fragilerock.quicknotice.net
109.177.21.219 icyrice.quicknotice.net
109.177.21.220 brightball.quicknotice.net
109.177.21.221 oldguide.quicknotice.net
109.177.21.222 sadnet.quicknotice.net
109.177.21.223 shrillworm.quicknotice.net
109.177.21.224 goodbranch.quicknotice.net
109.177.21.225 dryowl.quicknotice.net
109.177.21.226 happybook.quicknotice.net
109.177.21.227 leafyclock.quicknotice.net
109.177.21.228 steepboat.quicknotice.net
109.177.21.229 smoothmachine.quicknotice.net
109.177.21.230 realsteel.quicknotice.net
109.177.21.231 fastapple.quicknotice.net
109.177.21.232 pleasanttruck.quickmarvel.com
109.177.21.233 greenarm.quickmarvel.com
109.177.21.234 latewire.quickmarvel.com
109.177.21.235 heavenlycard.quickmarvel.com
109.177.21.236 savorybase.quickmarvel.com
109.177.21.237 alertart.quickmarvel.com
109.177.21.238 quietsystem.quickmarvel.com
109.177.21.239 quickmarvel.com
109.177.21.239 slowcity.quickmarvel.com
109.177.21.240 minidust.quickmarvel.com
109.177.21.241 oddhand.quickmarvel.com
109.177.21.242 earlywindow.quickmarvel.com
109.177.21.243 cutecopy.quickmarvel.com
109.177.21.244 lightair.quickmarvel.com
109.177.21.245 nicebean.quickmarvel.com
109.177.21.246 topmeal.quickmarvel.com
109.177.21.247 triplethrone.quickmarvel.com
109.177.21.248 tidybox.quickmarvel.com
109.177.21.249 twinatom.quickmarvel.com
109.177.21.250 roastedfan.quickmarvel.com
109.177.21.251 broadcollar.quickmarvel.com
109.177.21.252 mutejam.quickmarvel.com
109.177.21.253 widegrape.quickmarvel.com
109.177.21.254 superswing.quickmarvel.com
109.177.22.2 heavenlyrabbit.ultimateforte.com
109.177.22.3 cutebasin.ultimateforte.com
109.177.22.4 graymachine.ultimateforte.com
109.177.22.5 pleasantart.ultimateforte.com
109.177.22.6 fragilecity.ultimateforte.com
109.177.22.7 oddapple.ultimateforte.com
109.177.22.8 leafyair.ultimateforte.com
109.177.22.9 roastedwindow.ultimateforte.com
109.177.22.10 greenball.ultimateforte.com
109.177.22.11 slowhand.ultimateforte.com
109.177.22.12 tripleworm.ultimateforte.com
109.177.22.13 friedcard.ultimateforte.com
109.177.22.14 sadgarden.ultimateforte.com
109.177.22.15 earlyboat.ultimateforte.com
109.177.22.16 topatom.ultimateforte.com
109.177.22.17 steeparea.ultimateforte.com
109.177.22.18 tidyswing.ultimateforte.com
109.177.22.19 browntruck.ultimateforte.com
109.177.22.20 goodfan.ultimateforte.com
109.177.22.21 richwire.ultimateforte.com
109.177.22.22 minifeast.ultimateforte.com
109.177.22.23 alertbranch.ultimateforte.com
109.177.22.24 realnet.ultimateforte.com
109.177.22.24 ultimateforte.com
109.177.22.25 happygrape.ultimatevantage.com
109.177.22.26 fiercebox.ultimatevantage.com
109.177.22.27 supercollar.ultimatevantage.com
109.177.22.28 freshguide.ultimatevantage.com
109.177.22.29 quietthrone.ultimatevantage.com
109.177.22.30 clearcellar.ultimatevantage.com
109.177.22.31 brightsystem.ultimatevantage.com
109.177.22.32 lightbase.ultimatevantage.com
109.177.22.32 ultimatevantage.com
109.177.22.33 fastrice.ultimatevantage.com
109.177.22.34 twinjam.ultimatevantage.com
109.177.22.35 smoothrock.ultimatevantage.com
109.177.22.36 shrillowl.ultimatevantage.com
109.177.22.37 drydust.ultimatevantage.com
109.177.22.38 savoryarm.ultimatevantage.com
109.177.22.39 flatsteel.ultimatevantage.com
109.177.22.40 nicebean.ultimatevantage.com
109.177.22.41 broadmeal.ultimatevantage.com
109.177.22.42 mutescarf.ultimatevantage.com
109.177.22.43 icybook.ultimatevantage.com
109.177.22.44 lateclock.ultimatevantage.com
109.177.22.45 oldcopy.ultimatevantage.com
109.177.22.46 widerabbit.ultimatevantage.com
109.177.22.47 heavenlybasin.ultimatevantage.com
109.177.22.48 cutemachine.ultimateassets.com
109.177.22.49 grayart.ultimateassets.com
109.177.22.50 pleasantcity.ultimateassets.com
109.177.22.51 fragileapple.ultimateassets.com
109.177.22.52 oddair.ultimateassets.com
109.177.22.53 leafywindow.ultimateassets.com
109.177.22.54 roastedball.ultimateassets.com
109.177.22.55 greenhand.ultimateassets.com
109.177.22.56 slowworm.ultimateassets.com
109.177.22.57 triplecard.ultimateassets.com
109.177.22.58 friedgarden.ultimateassets.com
109.177.22.59 sadboat.ultimateassets.com
109.177.22.60 earlyatom.ultimateassets.com
109.177.22.61 toparea.ultimateassets.com
109.177.22.62 steepswing.ultimateassets.com
109.177.22.63 tidytruck.ultimateassets.com
109.177.22.64 brownfan.ultimateassets.com
109.177.22.64 ultimateassets.com
109.177.22.65 goodwire.ultimateassets.com
109.177.22.66 richfeast.ultimateassets.com
109.177.22.67 minibranch.ultimateassets.com
109.177.22.68 alertnet.ultimateassets.com
109.177.22.69 realgrape.ultimateassets.com
109.177.22.70 happybox.ultimateassets.com
109.177.22.71 fiercecollar.ultimatehelp.net
109.177.22.72 superguide.ultimatehelp.net
109.177.22.73 freshthrone.ultimatehelp.net
109.177.22.74 quietcellar.ultimatehelp.net
109.177.22.75 clearsystem.ultimatehelp.net
109.177.22.76 brightbase.ultimatehelp.net
109.177.22.77 lightrice.ultimatehelp.net
109.177.22.78 fastjam.ultimatehelp.net
109.177.22.79 twinrock.ultimatehelp.net
109.177.22.80 smoothowl.ultimatehelp.net
109.177.22.81 shrilldust.ultimatehelp.net
109.177.22.82 dryarm.ultimatehelp.net
109.177.22.83 savorysteel.ultimatehelp.net
109.177.22.84 flatbean.ultimatehelp.net
109.177.22.85 nicemeal.ultimatehelp.net
109.177.22.86 broadscarf.ultimatehelp.net
109.177.22.87 mutebook.ultimatehelp.net
109.177.22.88 icyclock.ultimatehelp.net
109.177.22.89 latecopy.ultimatehelp.net
109.177.22.90 oldrabbit.ultimatehelp.net
109.177.22.90 ultimatehelp.net
109.177.22.91 widebasin.ultimatehelp.net
109.177.22.92 heavenlymachine.ultimatehelp.net
109.177.22.93 cuteart.ultimatehelp.net
109.177.22.94 graycity.ultimateassistance.net
109.177.22.94 ultimateassistance.net
109.177.22.95 pleasantapple.ultimateassistance.net
109.177.22.96 fragileair.ultimateassistance.net
109.177.22.97 oddwindow.ultimateassistance.net
109.177.22.98 leafyball.ultimateassistance.net
109.177.22.99 roastedhand.ultimateassistance.net
109.177.22.100 greenworm.ultimateassistance.net
109.177.22.101 slowcard.ultimateassistance.net
109.177.22.102 triplegarden.ultimateassistance.net
109.177.22.103 friedboat.ultimateassistance.net
109.177.22.104 sadatom.ultimateassistance.net
109.177.22.105 earlyarea.ultimateassistance.net
109.177.22.106 topswing.ultimateassistance.net
109.177.22.107 steeptruck.ultimateassistance.net
109.177.22.108 tidyfan.ultimateassistance.net
109.177.22.109 brownwire.ultimateassistance.net
109.177.22.110 goodfeast.ultimateassistance.net
109.177.22.111 richbranch.ultimateassistance.net
109.177.22.112 mininet.ultimateassistance.net
109.177.22.113 alertgrape.ultimateassistance.net
109.177.22.114 realbox.ultimateassistance.net
109.177.22.115 happycollar.ultimateassistance.net
109.177.22.116 fierceguide.ultimateassistance.net
109.177.22.117 superthrone.statusguide.net
109.177.22.118 freshcellar.statusguide.net
109.177.22.119 quietsystem.statusguide.net
109.177.22.120 clearbase.statusguide.net
109.177.22.121 brightrice.statusguide.net
109.177.22.121 statusguide.net
109.177.22.122 lightjam.statusguide.net
109.177.22.123 fastrock.statusguide.net
109.177.22.124 twinowl.statusguide.net
109.177.22.125 smoothdust.statusguide.net
109.177.22.126 shrillarm.statusguide.net
109.177.22.127 drysteel.statusguide.net
109.177.22.128 savorybean.statusguide.net
109.177.22.129 flatmeal.statusguide.net
109.177.22.130 nicescarf.statusguide.net
109.177.22.131 broadbook.statusguide.net
109.177.22.132 muteclock.statusguide.net
109.177.22.133 icycopy.statusguide.net
109.177.22.134 laterabbit.statusguide.net
109.177.22.135 oldbasin.statusguide.net
109.177.22.136 widemachine.statusguide.net
109.177.22.137 heavenlyart.statusguide.net
109.177.22.138 cutecity.statusguide.net
109.177.22.139 grayapple.statusguide.net
109.177.22.140 pleasantair.statuspermit.com
109.177.22.141 fragilewindow.statuspermit.com
109.177.22.142 oddball.statuspermit.com
109.177.22.142 statuspermit.com
109.177.22.143 leafyhand.statuspermit.com
109.177.22.144 roastedworm.statuspermit.com
109.177.22.145 greencard.statuspermit.com
109.177.22.146 slowgarden.statuspermit.com
109.177.22.147 tripleboat.statuspermit.com
109.177.22.148 friedatom.statuspermit.com
109.177.22.149 sadarea.statuspermit.com
109.177.22.150 earlyswing.statuspermit.com
109.177.22.151 toptruck.statuspermit.com
109.177.22.152 steepfan.statuspermit.com
109.177.22.153 tidywire.statuspermit.com
109.177.22.154 brownfeast.statuspermit.com
109.177.22.155 goodbranch.statuspermit.com
109.177.22.156 richnet.statuspermit.com
109.177.22.157 minigrape.statuspermit.com
109.177.22.158 alertbox.statuspermit.com
109.177.22.159 realcollar.statuspermit.com
109.177.22.160 happyguide.statuspermit.com
109.177.22.161 fiercethrone.statuspermit.com
109.177.22.162 supercellar.statuspermit.com
109.177.22.163 freshsystem.statuscertification.com
109.177.22.164 quietbase.statuscertification.com
109.177.22.165 clearrice.statuscertification.com
109.177.22.165 statuscertification.com
109.177.22.166 brightjam.statuscertification.com
109.177.22.167 lightrock.statuscertification.com
109.177.22.168 fastowl.statuscertification.com
109.177.22.169 twindust.statuscertification.com
109.177.22.170 smootharm.statuscertification.com
109.177.22.171 shrillsteel.statuscertification.com
109.177.22.172 drybean.statuscertification.com
109.177.22.173 savorymeal.statuscertification.com
109.177.22.174 flatscarf.statuscertification.com
109.177.22.175 nicebook.statuscertification.com
109.177.22.176 broadclock.statuscertification.com
109.177.22.177 mutecopy.statuscertification.com
109.177.22.178 icyrabbit.statuscertification.com
109.177.22.179 latebasin.statuscertification.com
109.177.22.180 oldmachine.statuscertification.com
109.177.22.181 wideart.statuscertification.com
109.177.22.182 heavenlycity.statuscertification.com
109.177.22.183 cuteapple.statuscertification.com
109.177.22.184 grayair.statuscertification.com
109.177.22.185 pleasantwindow.statuscertification.com
109.177.22.186 fragileball.statusclear.net
109.177.22.187 oddhand.statusclear.net
109.177.22.188 leafyworm.statusclear.net
109.177.22.189 roastedcard.statusclear.net
109.177.22.190 greengarden.statusclear.net
109.177.22.191 slowboat.statusclear.net
109.177.22.192 tripleatom.statusclear.net
109.177.22.193 friedarea.statusclear.net
109.177.22.194 sadswing.statusclear.net
109.177.22.195 earlytruck.statusclear.net
109.177.22.196 topfan.statusclear.net
109.177.22.197 steepwire.statusclear.net
109.177.22.198 tidyfeast.statusclear.net
109.177.22.199 brownbranch.statusclear.net
109.177.22.200 goodnet.statusclear.net
109.177.22.201 richgrape.statusclear.net
109.177.22.202 minibox.statusclear.net
109.177.22.203 alertcollar.statusclear.net
109.177.22.204 realguide.statusclear.net
109.177.22.205 happythrone.statusclear.net
109.177.22.206 fiercecellar.statusclear.net
109.177.22.206 statusclear.net
109.177.22.207 supersystem.statusclear.net
109.177.22.208 freshbase.statusclear.net
109.177.22.209 quietrice.statusempower.com
109.177.22.210 clearjam.statusempower.com
109.177.22.211 brightrock.statusempower.com
109.177.22.212 lightowl.statusempower.com
109.177.22.213 fastdust.statusempower.com
109.177.22.214 twinarm.statusempower.com
109.177.22.215 smoothsteel.statusempower.com
109.177.22.216 shrillbean.statusempower.com
109.177.22.217 drymeal.statusempower.com
109.177.22.218 savoryscarf.statusempower.com
109.177.22.219 flatbook.statusempower.com
109.177.22.220 niceclock.statusempower.com
109.177.22.221 broadcopy.statusempower.com
109.177.22.221 statusempower.com
109.177.22.222 muterabbit.statusempower.com
109.177.22.223 icybasin.statusempower.com
109.177.22.224 latemachine.statusempower.com
109.177.22.225 oldart.statusempower.com
109.177.22.226 widecity.statusempower.com
109.177.22.227 heavenlyapple.statusempower.com
109.177.22.228 cuteair.statusempower.com
109.177.22.229 graywindow.statusempower.com
109.177.22.230 pleasantball.statusempower.com
109.177.22.231 fragilehand.statusempower.com
109.177.22.232 oddworm.rangemanagement.net
109.177.22.233 leafycard.rangemanagement.net
109.177.22.234 roastedgarden.rangemanagement.net
109.177.22.235 greenboat.rangemanagement.net
109.177.22.236 slowatom.rangemanagement.net
109.177.22.237 triplearea.rangemanagement.net
109.177.22.238 friedswing.rangemanagement.net
109.177.22.239 sadtruck.rangemanagement.net
109.177.22.240 earlyfan.rangemanagement.net
109.177.22.241 topwire.rangemanagement.net
109.177.22.242 steepfeast.rangemanagement.net
109.177.22.243 tidybranch.rangemanagement.net
109.177.22.244 brownnet.rangemanagement.net
109.177.22.245 goodgrape.rangemanagement.net
109.177.22.246 richbox.rangemanagement.net
109.177.22.247 minicollar.rangemanagement.net
109.177.22.248 alertguide.rangemanagement.net
109.177.22.249 realthrone.rangemanagement.net
109.177.22.250 happycellar.rangemanagement.net
109.177.22.251 fiercesystem.rangemanagement.net
109.177.22.251 rangemanagement.net
109.177.22.252 superbase.rangemanagement.net
109.177.22.253 freshrice.rangemanagement.net
109.177.22.254 quietjam.rangemanagement.net
109.177.23.2 smoothnet.ratemanagement.net
109.177.23.3 fragilewire.ratemanagement.net
109.177.23.4 happyatom.ratemanagement.net
109.177.23.5 widearea.ratemanagement.net
109.177.23.6 tidyfeast.ratemanagement.net
109.177.23.7 brightguide.ratemanagement.net
109.177.23.8 drycollar.ratemanagement.net
109.177.23.9 alertjam.ratemanagement.net
109.177.23.10 freshgrape.ratemanagement.net
109.177.23.11 friedgarden.ratemanagement.net
109.177.23.12 oldboat.ratemanagement.net
109.177.23.13 miniball.ratemanagement.net
109.177.23.14 clearbase.ratemanagement.net
109.177.23.15 latebean.ratemanagement.net
109.177.23.16 broaddust.ratemanagement.net
109.177.23.17 savoryscarf.ratemanagement.net
109.177.23.18 grayswing.ratemanagement.net
109.177.23.18 ratemanagement.net
109.177.23.19 fastmachine.ratemanagement.net
109.177.23.20 heavenlyclock.ratemanagement.net
109.177.23.21 cutecard.ratemanagement.net
109.177.23.22 realbook.ratemanagement.net
109.177.23.23 earlymeal.ratemanagement.net
109.177.23.24 muteapple.ratemanagement.net
109.177.23.25 steepair.honormanagement.net
109.177.23.26 leafybranch.honormanagement.net
109.177.23.27 topcellar.honormanagement.net
109.177.23.28 triplefan.honormanagement.net
109.177.23.29 richart.honormanagement.net
109.177.23.30 quiethand.honormanagement.net
109.177.23.31 fiercerice.honormanagement.net
109.177.23.32 twinrock.honormanagement.net
109.177.23.33 shrillrabbit.honormanagement.net
109.177.23.34 honormanagement.net
109.177.23.34 icycopy.honormanagement.net
109.177.23.35 flatcity.honormanagement.net
109.177.23.36 oddsystem.honormanagement.net
109.177.23.37 lightworm.honormanagement.net
109.177.23.38 pleasanttruck.honormanagement.net
109.177.23.39 goodwindow.honormanagement.net
109.177.23.40 greenbasin.honormanagement.net
109.177.23.41 sadbox.honormanagement.net
109.177.23.42 supersteel.honormanagement.net
109.177.23.43 nicearm.honormanagement.net
109.177.23.44 brownthrone.honormanagement.net
109.177.23.45 slowowl.honormanagement.net
109.177.23.46 roastednet.honormanagement.net
109.177.23.47 smoothwire.honormanagement.net
109.177.23.48 fragileatom.equalizemanagement.com
109.177.23.49 happyarea.equalizemanagement.com
109.177.23.50 widefeast.equalizemanagement.com
109.177.23.51 tidyguide.equalizemanagement.com
109.177.23.52 brightcollar.equalizemanagement.com
109.177.23.53 dryjam.equalizemanagement.com
109.177.23.54 alertgrape.equalizemanagement.com
109.177.23.55 freshgarden.equalizemanagement.com
109.177.23.56 friedboat.equalizemanagement.com
109.177.23.57 oldball.equalizemanagement.com
109.177.23.58 minibase.equalizemanagement.com
109.177.23.59 clearbean.equalizemanagement.com
109.177.23.60 latedust.equalizemanagement.com
109.177.23.61 broadscarf.equalizemanagement.com
109.177.23.62 equalizemanagement.com
109.177.23.62 savoryswing.equalizemanagement.com
109.177.23.63 graymachine.equalizemanagement.com
109.177.23.64 fastclock.equalizemanagement.com
109.177.23.65 heavenlycard.equalizemanagement.com
109.177.23.66 cutebook.equalizemanagement.com
109.177.23.67 realmeal.equalizemanagement.com
109.177.23.68 earlyapple.equalizemanagement.com
109.177.23.69 muteair.equalizemanagement.com
109.177.23.70 steepbranch.equalizemanagement.com
109.177.23.71 leafycellar.equalmanagement.net
109.177.23.72 topfan.equalmanagement.net
109.177.23.73 tripleart.equalmanagement.net
109.177.23.74 richhand.equalmanagement.net
109.177.23.75 quietrice.equalmanagement.net
109.177.23.76 fiercerock.equalmanagement.net
109.177.23.77 twinrabbit.equalmanagement.net
109.177.23.78 shrillcopy.equalmanagement.net
109.177.23.79 icycity.equalmanagement.net
109.177.23.80 flatsystem.equalmanagement.net
109.177.23.81 oddworm.equalmanagement.net
109.177.23.82 lighttruck.equalmanagement.net
109.177.23.83 equalmanagement.net
109.177.23.83 pleasantwindow.equalmanagement.net
109.177.23.84 goodbasin.equalmanagement.net
109.177.23.85 greenbox.equalmanagement.net
109.177.23.86 sadsteel.equalmanagement.net
109.177.23.87 superarm.equalmanagement.net
109.177.23.88 nicethrone.equalmanagement.net
109.177.23.89 brownowl.equalmanagement.net
109.177.23.90 slownet.equalmanagement.net
109.177.23.91 roastedwire.equalmanagement.net
109.177.23.92 smoothatom.equalmanagement.net
109.177.23.93 fragilearea.equalmanagement.net
109.177.23.94 happyfeast.purifymanagement.com
109.177.23.95 wideguide.purifymanagement.com
109.177.23.96 tidycollar.purifymanagement.com
109.177.23.97 brightjam.purifymanagement.com
109.177.23.97 purifymanagement.com
109.177.23.98 drygrape.purifymanagement.com
109.177.23.99 alertgarden.purifymanagement.com
109.177.23.100 freshboat.purifymanagement.com
109.177.23.101 friedball.purifymanagement.com
109.177.23.102 oldbase.purifymanagement.com
109.177.23.103 minibean.purifymanagement.com
109.177.23.104 cleardust.purifymanagement.com
109.177.23.105 latescarf.purifymanagement.com
109.177.23.106 broadswing.purifymanagement.com
109.177.23.107 savorymachine.purifymanagement.com
109.177.23.108 grayclock.purifymanagement.com
109.177.23.109 fastcard.purifymanagement.com
109.177.23.110 heavenlybook.purifymanagement.com
109.177.23.111 cutemeal.purifymanagement.com
109.177.23.112 realapple.purifymanagement.com
109.177.23.113 earlyair.purifymanagement.com
109.177.23.114 mutebranch.purifymanagement.com
109.177.23.115 steepcellar.purifymanagement.com
109.177.23.116 leafyfan.purifymanagement.com
109.177.23.117 topart.purgemanagement.com
109.177.23.118 triplehand.purgemanagement.com
109.177.23.119 richrice.purgemanagement.com
109.177.23.120 quietrock.purgemanagement.com
109.177.23.121 fiercerabbit.purgemanagement.com
109.177.23.122 twincopy.purgemanagement.com
109.177.23.123 shrillcity.purgemanagement.com
109.177.23.124 icysystem.purgemanagement.com
109.177.23.125 flatworm.purgemanagement.com
109.177.23.126 oddtruck.purgemanagement.com
109.177.23.127 lightwindow.purgemanagement.com
109.177.23.127 purgemanagement.com
109.177.23.128 pleasantbasin.purgemanagement.com
109.177.23.129 goodbox.purgemanagement.com
109.177.23.130 greensteel.purgemanagement.com
109.177.23.131 sadarm.purgemanagement.com
109.177.23.132 superthrone.purgemanagement.com
109.177.23.133 niceowl.purgemanagement.com
109.177.23.134 brownnet.purgemanagement.com
109.177.23.135 slowwire.purgemanagement.com
109.177.23.136 roastedatom.purgemanagement.com
109.177.23.137 smootharea.purgemanagement.com
109.177.23.138 fragilefeast.purgemanagement.com
109.177.23.139 happyguide.purgemanagement.com
109.177.23.140 widecollar.entermanagement.net
109.177.23.141 tidyjam.entermanagement.net
109.177.23.142 brightgrape.entermanagement.net
109.177.23.143 drygarden.entermanagement.net
109.177.23.144 alertboat.entermanagement.net
109.177.23.145 freshball.entermanagement.net
109.177.23.146 friedbase.entermanagement.net
109.177.23.147 oldbean.entermanagement.net
109.177.23.148 minidust.entermanagement.net
109.177.23.149 clearscarf.entermanagement.net
109.177.23.150 lateswing.entermanagement.net
109.177.23.151 broadmachine.entermanagement.net
109.177.23.152 savoryclock.entermanagement.net
109.177.23.153 entermanagement.net
109.177.23.153 graycard.entermanagement.net
109.177.23.154 fastbook.entermanagement.net
109.177.23.155 heavenlymeal.entermanagement.net
109.177.23.156 cuteapple.entermanagement.net
109.177.23.157 realair.entermanagement.net
109.177.23.158 earlybranch.entermanagement.net
109.177.23.159 mutecellar.entermanagement.net
109.177.23.160 steepfan.entermanagement.net
109.177.23.161 leafyart.entermanagement.net
109.177.23.162 tophand.entermanagement.net
109.177.23.163 triplerice.improvemanagement.net
109.177.23.164 richrock.improvemanagement.net
109.177.23.165 quietrabbit.improvemanagement.net
109.177.23.166 fiercecopy.improvemanagement.net
109.177.23.167 twincity.improvemanagement.net
109.177.23.168 shrillsystem.improvemanagement.net
109.177.23.169 icyworm.improvemanagement.net
109.177.23.170 flattruck.improvemanagement.net
109.177.23.170 improvemanagement.net
109.177.23.171 oddwindow.improvemanagement.net
109.177.23.172 lightbasin.improvemanagement.net
109.177.23.173 pleasantbox.improvemanagement.net
109.177.23.174 goodsteel.improvemanagement.net
109.177.23.175 greenarm.improvemanagement.net
109.177.23.176 sadthrone.improvemanagement.net
109.177.23.177 superowl.improvemanagement.net
109.177.23.178 nicenet.improvemanagement.net
109.177.23.179 brownwire.improvemanagement.net
109.177.23.180 slowatom.improvemanagement.net
109.177.23.181 roastedarea.improvemanagement.net
109.177.23.182 smoothfeast.improvemanagement.net
109.177.23.183 fragileguide.improvemanagement.net
109.177.23.184 happycollar.improvemanagement.net
109.177.23.185 widejam.improvemanagement.net
109.177.23.186 tidygrape.perfectionmanagement.com
109.177.23.187 brightgarden.perfectionmanagement.com
109.177.23.188 dryboat.perfectionmanagement.com
109.177.23.189 alertball.perfectionmanagement.com
109.177.23.190 freshbase.perfectionmanagement.com
109.177.23.191 friedbean.perfectionmanagement.com
109.177.23.192 olddust.perfectionmanagement.com
109.177.23.193 miniscarf.perfectionmanagement.com
109.177.23.194 clearswing.perfectionmanagement.com
109.177.23.195 latemachine.perfectionmanagement.com
109.177.23.196 broadclock.perfectionmanagement.com
109.177.23.197 savorycard.perfectionmanagement.com
109.177.23.198 graybook.perfectionmanagement.com
109.177.23.198 perfectionmanagement.com
109.177.23.199 fastmeal.perfectionmanagement.com
109.177.23.200 heavenlyapple.perfectionmanagement.com
109.177.23.201 cuteair.perfectionmanagement.com
109.177.23.202 realbranch.perfectionmanagement.com
109.177.23.203 earlycellar.perfectionmanagement.com
109.177.23.204 mutefan.perfectionmanagement.com
109.177.23.205 steepart.perfectionmanagement.com
109.177.23.206 leafyhand.perfectionmanagement.com
109.177.23.207 toprice.perfectionmanagement.com
109.177.23.208 triplerock.perfectionmanagement.com
109.177.23.209 fluxmanagement.net
109.177.23.209 richrabbit.fluxmanagement.net
109.177.23.210 quietcopy.fluxmanagement.net
109.177.23.211 fiercecity.fluxmanagement.net
109.177.23.212 twinsystem.fluxmanagement.net
109.177.23.213 shrillworm.fluxmanagement.net
109.177.23.214 icytruck.fluxmanagement.net
109.177.23.215 flatwindow.fluxmanagement.net
109.177.23.216 oddbasin.fluxmanagement.net
109.177.23.217 lightbox.fluxmanagement.net
109.177.23.218 pleasantsteel.fluxmanagement.net
109.177.23.219 goodarm.fluxmanagement.net
109.177.23.220 greenthrone.fluxmanagement.net
109.177.23.221 sadowl.fluxmanagement.net
109.177.23.222 supernet.fluxmanagement.net
109.177.23.223 nicewire.fluxmanagement.net
109.177.23.224 brownatom.fluxmanagement.net
109.177.23.225 slowarea.fluxmanagement.net
109.177.23.226 roastedfeast.fluxmanagement.net
109.177.23.227 smoothguide.fluxmanagement.net
109.177.23.228 fragilecollar.fluxmanagement.net
109.177.23.229 happyjam.fluxmanagement.net
109.177.23.230 widegrape.fluxmanagement.net
109.177.23.231 tidygarden.fluxmanagement.net
109.177.23.232 brightboat.wildmanagement.net
109.177.23.233 dryball.wildmanagement.net
109.177.23.234 alertbase.wildmanagement.net
109.177.23.235 freshbean.wildmanagement.net
109.177.23.236 frieddust.wildmanagement.net
109.177.23.237 oldscarf.wildmanagement.net
109.177.23.238 miniswing.wildmanagement.net
109.177.23.239 clearmachine.wildmanagement.net
109.177.23.240 lateclock.wildmanagement.net
109.177.23.241 broadcard.wildmanagement.net
109.177.23.242 savorybook.wildmanagement.net
109.177.23.243 graymeal.wildmanagement.net
109.177.23.244 fastapple.wildmanagement.net
109.177.23.245 heavenlyair.wildmanagement.net
109.177.23.246 cutebranch.wildmanagement.net
109.177.23.246 wildmanagement.net
109.177.23.247 realcellar.wildmanagement.net
109.177.23.248 earlyfan.wildmanagement.net
109.177.23.249 muteart.wildmanagement.net
109.177.23.250 steephand.wildmanagement.net
109.177.23.251 leafyrice.wildmanagement.net
109.177.23.252 toprock.wildmanagement.net
109.177.23.253 triplerabbit.wildmanagement.net
109.177.23.254 richcopy.wildmanagement.net

178.215.176.2 cleargarden.fromhomeservices.com
178.215.176.3 dryswing.fromhomeservices.com
178.215.176.4 fromhomeservices.com
178.215.176.4 topguide.fromhomeservices.com
178.215.176.5 lightworm.fromhomeservices.com
178.215.176.6 twinsystem.reflectcontent.com
178.215.176.7 pleasantcard.reflectcontent.com
178.215.176.8 superfan.reflectcontent.com
178.215.176.9 reflectcontent.com
178.215.176.9 richboat.reflectcontent.com
178.215.176.10 lateowl.takecontent.net
178.215.176.11 minimachine.takecontent.net
178.215.176.11 takecontent.net
178.215.176.12 olddust.takecontent.net
178.215.176.13 savoryrice.takecontent.net
178.215.176.14 heavenlyapple.traincontent.com
178.215.176.15 alerttruck.traincontent.com
178.215.176.15 traincontent.com
178.215.176.16 goodwindow.traincontent.com
178.215.176.17 greenrock.traincontent.com
178.215.176.18 shrillsteel.addresscontent.net
178.215.176.19 niceclock.addresscontent.net
178.215.176.20 cutegrape.addresscontent.net
178.215.176.21 addresscontent.net
178.215.176.21 fiercecellar.addresscontent.net
178.215.176.22 earlynet.sailcontent.net
178.215.176.23 sailcontent.net
178.215.176.23 smoothbase.sailcontent.net
178.215.176.24 fastrabbit.sailcontent.net
178.215.176.25 icybox.sailcontent.net
178.215.176.26 steepball.commandcontent.com
178.215.176.27 slowjam.commandcontent.com
178.215.176.28 commandcontent.com
178.215.176.28 freshscarf.commandcontent.com
178.215.176.29 graybasin.commandcontent.com
178.215.176.30 controlcontent.net
178.215.176.30 sadbook.controlcontent.net
178.215.176.31 quietcopy.controlcontent.net
178.215.176.32 brightcity.controlcontent.net
178.215.176.33 oddhand.controlcontent.net
178.215.176.34 triplecollar.drivingcontent.net
178.215.176.35 happymeal.drivingcontent.net
178.215.176.36 mutebranch.drivingcontent.net
178.215.176.37 drivingcontent.net
178.215.176.37 realbean.drivingcontent.net
178.215.176.38 broadarm.ushercontent.com
178.215.176.38 ushercontent.com
178.215.176.39 flatatom.ushercontent.com
178.215.176.40 friedart.ushercontent.com
178.215.176.41 leafyarea.ushercontent.com
178.215.176.42 brownthrone.forefrontcontent.com
178.215.176.42 forefrontcontent.com
178.215.176.43 widefeast.forefrontcontent.com
178.215.176.44 fragilewire.forefrontcontent.com
178.215.176.45 roastedair.forefrontcontent.com
178.215.176.46 tidygarden.headwaycontent.com
178.215.176.47 clearswing.headwaycontent.com
178.215.176.47 headwaycontent.com
178.215.176.48 dryguide.headwaycontent.com
178.215.176.49 topworm.headwaycontent.com
178.215.176.50 dockcontent.com
178.215.176.50 lightsystem.dockcontent.com
178.215.176.51 twincard.dockcontent.com
178.215.176.52 pleasantfan.dockcontent.com
178.215.176.53 superboat.dockcontent.com
178.215.176.54 richowl.sheercontent.net
178.215.176.55 latemachine.sheercontent.net
178.215.176.55 sheercontent.net
178.215.176.56 minidust.sheercontent.net
178.215.176.57 oldrice.sheercontent.net
178.215.176.58 savoryapple.parkcontent.net
178.215.176.59 heavenlytruck.parkcontent.net
178.215.176.60 alertwindow.parkcontent.net
178.215.176.61 goodrock.parkcontent.net
178.215.176.61 parkcontent.net
178.215.176.62 greensteel.shortcontent.net
178.215.176.63 shrillclock.shortcontent.net
178.215.176.64 nicegrape.shortcontent.net
178.215.176.64 shortcontent.net
178.215.176.65 cutecellar.shortcontent.net
178.215.176.66 fiercenet.polecontent.com
178.215.176.67 earlybase.polecontent.com
178.215.176.68 smoothrabbit.polecontent.com
178.215.176.69 fastbox.polecontent.com
178.215.176.69 polecontent.com
178.215.176.70 icyball.terminalcontent.com
178.215.176.71 steepjam.terminalcontent.com
178.215.176.71 terminalcontent.com
178.215.176.72 slowscarf.terminalcontent.com
178.215.176.73 freshbasin.terminalcontent.com
178.215.176.74 graybook.treadcontent.com
178.215.176.75 sadcopy.treadcontent.com
178.215.176.75 treadcontent.com
178.215.176.76 quietcity.treadcontent.com
178.215.176.77 brighthand.treadcontent.com
178.215.176.78 oddcollar.wipercontent.com
178.215.176.79 triplemeal.wipercontent.com
178.215.176.79 wipercontent.com
178.215.176.80 happybranch.wipercontent.com
178.215.176.81 mutebean.wipercontent.com
178.215.176.82 realarm.ignitioncontent.net
178.215.176.83 broadatom.ignitioncontent.net
178.215.176.84 flatart.ignitioncontent.net
178.215.176.85 friedarea.ignitioncontent.net
178.215.176.85 ignitioncontent.net
178.215.176.86 leafythrone.dealcontent.com
178.215.176.87 brownfeast.dealcontent.com
178.215.176.87 dealcontent.com
178.215.176.88 widewire.dealcontent.com
178.215.176.89 fragileair.dealcontent.com
178.215.176.90 roastedgarden.lotcontent.com
178.215.176.91 tidyswing.lotcontent.com
178.215.176.92 clearguide.lotcontent.com
178.215.176.92 lotcontent.com
178.215.176.93 dryworm.lotcontent.com
178.215.176.94 topsystem.goalcontent.com
178.215.176.95 lightcard.goalcontent.com
178.215.176.96 goalcontent.com
178.215.176.96 twinfan.goalcontent.com
178.215.176.97 pleasantboat.goalcontent.com
178.215.176.98 superowl.tipcontent.com
178.215.176.99 richmachine.tipcontent.com
178.215.176.99 tipcontent.com
178.215.176.100 latedust.tipcontent.com
178.215.176.101 minirice.tipcontent.com
178.215.176.102 oldapple.stabcontent.com
178.215.176.103 savorytruck.stabcontent.com
178.215.176.104 heavenlywindow.stabcontent.com
178.215.176.104 stabcontent.com
178.215.176.105 alertrock.stabcontent.com
178.215.176.106 goodsteel.choppercontent.com
178.215.176.107 choppercontent.com
178.215.176.107 greenclock.choppercontent.com
178.215.176.108 shrillgrape.choppercontent.com
178.215.176.109 nicecellar.choppercontent.com
178.215.176.110 arrowcontent.com
178.215.176.110 cutenet.arrowcontent.com
178.215.176.111 fiercebase.arrowcontent.com
178.215.176.112 earlyrabbit.arrowcontent.com
178.215.176.113 smoothbox.arrowcontent.com
178.215.176.114 fastball.hookcontent.com
178.215.176.114 hookcontent.com
178.215.176.115 icyjam.hookcontent.com
178.215.176.116 steepscarf.hookcontent.com
178.215.176.117 slowbasin.hookcontent.com
178.215.176.118 freshbook.spearcontent.com
178.215.176.118 spearcontent.com
178.215.176.119 graycopy.spearcontent.com
178.215.176.120 sadcity.spearcontent.com
178.215.176.121 quiethand.spearcontent.com
178.215.176.122 brightcollar.dolecontent.com
178.215.176.122 dolecontent.com
178.215.176.123 oddmeal.dolecontent.com
178.215.176.124 triplebranch.dolecontent.com
178.215.176.125 happybean.dolecontent.com
178.215.176.126 mutearm.bootcontent.com
178.215.176.127 realatom.bootcontent.com
178.215.176.128 broadart.bootcontent.com
178.215.176.129 bootcontent.com
178.215.176.129 flatarea.bootcontent.com
178.215.176.130 friedthrone.lodgecontent.com
178.215.176.131 leafyfeast.lodgecontent.com
178.215.176.132 brownwire.lodgecontent.com
178.215.176.133 lodgecontent.com
178.215.176.133 wideair.lodgecontent.com
178.215.176.134 fragilegarden.jollycontent.com
178.215.176.135 roastedswing.jollycontent.com
178.215.176.136 tidyguide.jollycontent.com
178.215.176.137 clearworm.jollycontent.com
178.215.176.137 jollycontent.com
178.215.176.138 drysystem.pitchcontent.net
178.215.176.139 pitchcontent.net
178.215.176.139 topcard.pitchcontent.net
178.215.176.140 lightfan.pitchcontent.net
178.215.176.141 twinboat.pitchcontent.net
178.215.176.142 pleasantowl.ratescontent.com
178.215.176.143 ratescontent.com
178.215.176.143 supermachine.ratescontent.com
178.215.176.144 richdust.ratescontent.com
178.215.176.145 laterice.ratescontent.com
178.215.176.146 miniapple.stonecontent.net
178.215.176.147 oldtruck.stonecontent.net
178.215.176.148 savorywindow.stonecontent.net
178.215.176.149 heavenlyrock.stonecontent.net
178.215.176.149 stonecontent.net
178.215.176.150 alertsteel.bitcontent.net
178.215.176.150 bitcontent.net
178.215.176.151 goodclock.bitcontent.net
178.215.176.152 greengrape.bitcontent.net
178.215.176.153 shrillcellar.bitcontent.net
178.215.176.154 nicenet.spotcontent.net
178.215.176.154 spotcontent.net
178.215.176.155 cutebase.spotcontent.net
178.215.176.156 fiercerabbit.spotcontent.net
178.215.176.157 earlybox.spotcontent.net
178.215.176.158 smoothball.specificcontent.net
178.215.176.159 fastjam.specificcontent.net
178.215.176.160 icyscarf.specificcontent.net
178.215.176.161 specificcontent.net
178.215.176.161 steepbasin.specificcontent.net
178.215.176.162 slowbook.casecontent.com
178.215.176.163 casecontent.com
178.215.176.163 freshcopy.casecontent.com
178.215.176.164 graycity.casecontent.com
178.215.176.165 sadhand.casecontent.com
178.215.176.166 quietcollar.scorecontent.com
178.215.176.166 scorecontent.com
178.215.176.167 brightmeal.scorecontent.com
178.215.176.168 oddbranch.scorecontent.com
178.215.176.169 triplebean.scorecontent.com
178.215.176.170 happyarm.truthcontent.com
178.215.176.170 truthcontent.com
178.215.176.171 muteatom.truthcontent.com
178.215.176.172 realart.truthcontent.com
178.215.176.173 broadarea.truthcontent.com
178.215.176.174 flatthrone.performancetechnique.net
178.215.176.174 performancetechnique.net
178.215.176.175 friedfeast.performancetechnique.net
178.215.176.176 leafywire.performancetechnique.net
178.215.176.177 brownair.performancetechnique.net
178.215.176.178 widegarden.performanceresult.net
178.215.176.179 fragileswing.performanceresult.net
178.215.176.180 performanceresult.net
178.215.176.180 roastedguide.performanceresult.net
178.215.176.181 tidyworm.performanceresult.net
178.215.176.182 clearsystem.performancesolver.com
178.215.176.183 drycard.performancesolver.com
178.215.176.184 performancesolver.com
178.215.176.184 topfan.performancesolver.com
178.215.176.185 lightboat.performancesolver.com
178.215.176.186 twinowl.performancequalifying.com
178.215.176.187 pleasantmachine.performancequalifying.com
178.215.176.188 superdust.performancequalifying.com
178.215.176.189 performancequalifying.com
178.215.176.189 richrice.performancequalifying.com
178.215.176.190 lateapple.performancestatement.com
178.215.176.191 minitruck.performancestatement.com
178.215.176.192 oldwindow.performancestatement.com
178.215.176.192 performancestatement.com
178.215.176.193 savoryrock.performancestatement.com
178.215.176.194 heavenlysteel.performancemethod.net
178.215.176.194 performancemethod.net
178.215.176.195 alertclock.performancemethod.net
178.215.176.196 goodgrape.performancemethod.net
178.215.176.197 greencellar.performancemethod.net
178.215.176.198 shrillnet.performancelick.com
178.215.176.199 nicebase.performancelick.com
178.215.176.199 performancelick.com
178.215.176.200 cuterabbit.performancelick.com
178.215.176.201 fiercebox.performancelick.com
178.215.176.202 earlyball.performancework.net
178.215.176.203 smoothjam.performancework.net
178.215.176.204 fastscarf.performancework.net
178.215.176.205 icybasin.performancework.net
178.215.176.205 performancework.net
178.215.176.206 steepbook.performanceroot.com
178.215.176.207 slowcopy.performanceroot.com
178.215.176.208 freshcity.performanceroot.com
178.215.176.209 grayhand.performanceroot.com
178.215.176.209 performanceroot.com
178.215.176.210 sadcollar.servesolution.com
178.215.176.211 quietmeal.servesolution.com
178.215.176.212 brightbranch.servesolution.com
178.215.176.212 servesolution.com
178.215.176.213 oddbean.servesolution.com
178.215.176.214 triplearm.supportfinance.net
178.215.176.215 happyatom.supportfinance.net
178.215.176.216 muteart.supportfinance.net
178.215.176.216 supportfinance.net
178.215.176.217 realarea.supportfinance.net
178.215.176.218 broadthrone.supportmanage.com
178.215.176.219 flatfeast.supportmanage.com
178.215.176.219 supportmanage.com
178.215.176.220 friedwire.supportmanage.com
178.215.176.221 leafyair.supportmanage.com
178.215.176.222 browngarden.spearheadmanagement.com
178.215.176.223 spearheadmanagement.com
178.215.176.223 wideswing.spearheadmanagement.com
178.215.176.224 fragileguide.spearheadmanagement.com
178.215.176.225 roastedworm.spearheadmanagement.com
178.215.176.226 tidysystem.umbrellamanagement.net
178.215.176.226 umbrellamanagement.net
178.215.176.227 clearcard.umbrellamanagement.net
178.215.176.228 dryfan.umbrellamanagement.net
178.215.176.229 topboat.umbrellamanagement.net
178.215.176.230 lightowl.matchmanagement.net
178.215.176.230 matchmanagement.net
178.215.176.231 twinmachine.matchmanagement.net
178.215.176.232 pleasantdust.matchmanagement.net
178.215.176.233 superrice.matchmanagement.net
178.215.176.234 richapple.webinquiredrill.com
178.215.176.235 latetruck.webinquiredrill.com
178.215.176.236 miniwindow.webinquiredrill.com
178.215.176.237 oldrock.webinquiredrill.com
178.215.176.237 webinquiredrill.com
178.215.176.242 greennet.webrequesttool.com
178.215.176.243 shrillbase.webrequesttool.com
178.215.176.244 nicerabbit.webrequesttool.com
178.215.176.245 cutebox.webrequesttool.com
178.215.176.245 webrequesttool.com
178.215.176.250 icybook.webquerytool.com
178.215.176.251 steepcopy.webquerytool.com
178.215.176.252 slowcity.webquerytool.com
178.215.176.253 freshhand.webquerytool.com
178.215.176.254 graycollar.webquerytool.com
178.215.176.254 webquerytool.com
178.215.177.2 fragilebranch.netinquiretool.com
178.215.177.2 netinquiretool.com
178.215.177.3 realbase.netinquiretool.com
178.215.177.4 muteworm.netinquiretool.com
178.215.177.5 smoothnet.netinquiretool.com
178.215.177.6 pleasantgrape.inquiretool.com
178.215.177.7 clearmachine.inquiretool.com
178.215.177.8 fierceapple.inquiretool.com
178.215.177.9 friedswing.inquiretool.com
178.215.177.9 inquiretool.com
178.215.177.10 steepowl.logicalpositivism.net
178.215.177.11 broadbox.logicalpositivism.net
178.215.177.12 latefeast.logicalpositivism.net
178.215.177.12 logicalpositivism.net
178.215.177.13 brightboat.logicalpositivism.net
178.215.177.14 shrillcity.truedocument.net
178.215.177.15 oddcollar.truedocument.net
178.215.177.16 flatsystem.truedocument.net
178.215.177.16 truedocument.net
178.215.177.17 lightbean.truedocument.net
178.215.177.18 on-keycommunication.com
178.215.177.18 richscarf.on-keycommunication.com
178.215.177.19 grayjam.on-keycommunication.com
178.215.177.20 freshcard.on-keycommunication.com
178.215.177.21 happygarden.on-keycommunication.com
178.215.177.22 tidyrock.evencommunication.net
178.215.177.23 fastcopy.evencommunication.net
178.215.177.24 quietair.evencommunication.net
178.215.177.25 evencommunication.net
178.215.177.25 topclock.evencommunication.net
178.215.177.26 alertball.straightcommunication.com
178.215.177.27 slowguide.straightcommunication.com
178.215.177.27 straightcommunication.com
178.215.177.28 dryrabbit.straightcommunication.com
178.215.177.29 icybasin.straightcommunication.com
178.215.177.30 sadcellar.highasset.net
178.215.177.31 cutearea.highasset.net
178.215.177.32 supersteel.highasset.net
178.215.177.33 highasset.net
178.215.177.33 nicebook.highasset.net
178.215.177.34 earlydust.highvantage.net
178.215.177.35 savorywire.highvantage.net
178.215.177.36 minithrone.highvantage.net
178.215.177.37 highvantage.net
178.215.177.37 wideart.highvantage.net
178.215.177.38 highreward.net
178.215.177.38 leafytruck.highreward.net
178.215.177.39 goodarm.highreward.net
178.215.177.40 brownmeal.highreward.net
178.215.177.41 heavenlyrice.highreward.net
178.215.177.42 twinhand.piercingadvantage.com
178.215.177.43 piercingadvantage.com
178.215.177.43 triplewindow.piercingadvantage.com
178.215.177.44 greenatom.piercingadvantage.com
178.215.177.45 oldfan.piercingadvantage.com
178.215.177.46 higheradvantage.net
178.215.177.46 roastedbranch.higheradvantage.net
178.215.177.47 fragilebase.higheradvantage.net
178.215.177.48 realworm.higheradvantage.net
178.215.177.49 mutenet.higheradvantage.net
178.215.177.50 smoothgrape.upperadvantage.com
178.215.177.50 upperadvantage.com
178.215.177.51 pleasantmachine.upperadvantage.com
178.215.177.52 clearapple.upperadvantage.com
178.215.177.53 fierceswing.upperadvantage.com
178.215.177.54 friedowl.high-leveladvantage.com
178.215.177.55 steepbox.high-leveladvantage.com
178.215.177.56 broadfeast.high-leveladvantage.com
178.215.177.56 high-leveladvantage.com
178.215.177.57 lateboat.high-leveladvantage.com
178.215.177.58 brightcity.commandingadvantage.com
178.215.177.59 commandingadvantage.com
178.215.177.59 shrillcollar.commandingadvantage.com
178.215.177.60 oddsystem.commandingadvantage.com
178.215.177.61 flatbean.commandingadvantage.com
178.215.177.62 lightscarf.headclaimtest.com
178.215.177.63 richjam.headclaimtest.com
178.215.177.64 graycard.headclaimtest.com
178.215.177.65 freshgarden.headclaimtest.com
178.215.177.65 headclaimtest.com
178.215.177.66 detailstechnology.com
178.215.177.66 happyrock.detailstechnology.com
178.215.177.67 tidycopy.detailstechnology.com
178.215.177.68 fastair.detailstechnology.com
178.215.177.69 quietclock.detailstechnology.com
178.215.177.70 topball.materialtechnology.net
178.215.177.71 alertguide.materialtechnology.net
178.215.177.72 slowrabbit.materialtechnology.net
178.215.177.73 drybasin.materialtechnology.net
178.215.177.73 materialtechnology.net
178.215.177.74 icycellar.ammunitiontechnology.com
178.215.177.75 sadarea.ammunitiontechnology.com
178.215.177.76 ammunitiontechnology.com
178.215.177.76 cutesteel.ammunitiontechnology.com
178.215.177.77 superbook.ammunitiontechnology.com
178.215.177.78 nicedust.brushupmedia.com
178.215.177.79 earlywire.brushupmedia.com
178.215.177.80 savorythrone.brushupmedia.com
178.215.177.81 brushupmedia.com
178.215.177.81 miniart.brushupmedia.com
178.215.177.82 optimisemedia.net
178.215.177.82 widetruck.optimisemedia.net
178.215.177.83 leafyarm.optimisemedia.net
178.215.177.84 goodmeal.optimisemedia.net
178.215.177.85 brownrice.optimisemedia.net
178.215.177.86 heavenlyhand.perfectionmedia.net
178.215.177.86 perfectionmedia.net
178.215.177.87 twinwindow.perfectionmedia.net
178.215.177.88 tripleatom.perfectionmedia.net
178.215.177.89 greenfan.perfectionmedia.net
178.215.177.90 oldbranch.honemedia.net
178.215.177.91 roastedbase.honemedia.net
178.215.177.92 fragileworm.honemedia.net
178.215.177.92 honemedia.net
178.215.177.93 realnet.honemedia.net
178.215.177.94 mutegrape.idyllicmedia.net
178.215.177.95 smoothmachine.idyllicmedia.net
178.215.177.96 pleasantapple.idyllicmedia.net
178.215.177.97 clearswing.idyllicmedia.net
178.215.177.97 idyllicmedia.net
178.215.177.98 fierceowl.starkmedia.net
178.215.177.99 friedbox.starkmedia.net
178.215.177.100 steepfeast.starkmedia.net
178.215.177.101 broadboat.starkmedia.net
178.215.177.101 starkmedia.net
178.215.177.102 latecity.changesource.net
178.215.177.103 brightcollar.changesource.net
178.215.177.104 shrillsystem.changesource.net
178.215.177.105 changesource.net
178.215.177.105 oddbean.changesource.net
178.215.177.106 flatscarf.movementsource.net
178.215.177.107 lightjam.movementsource.net
178.215.177.108 movementsource.net
178.215.177.108 richcard.movementsource.net
178.215.177.109 graygarden.movementsource.net
178.215.177.110 freshrock.transferralsource.com
178.215.177.111 happycopy.transferralsource.com
178.215.177.112 tidyair.transferralsource.com
178.215.177.112 transferralsource.com
178.215.177.113 fastclock.transferralsource.com
178.215.177.114 quietball.mediaadministration.com
178.215.177.115 mediaadministration.com
178.215.177.115 topguide.mediaadministration.com
178.215.177.116 alertrabbit.mediaadministration.com
178.215.177.117 slowbasin.mediaadministration.com
178.215.177.118 drycellar.mediasocialcontrol.com
178.215.177.118 mediasocialcontrol.com
178.215.177.119 icyarea.mediasocialcontrol.com
178.215.177.120 sadsteel.mediasocialcontrol.com
178.215.177.121 cutebook.mediasocialcontrol.com
178.215.177.122 superdust.datacommunicationaffect.com
178.215.177.123 datacommunicationaffect.com
178.215.177.123 nicewire.datacommunicationaffect.com
178.215.177.124 earlythrone.datacommunicationaffect.com
178.215.177.125 savoryart.datacommunicationaffect.com
178.215.177.126 minitruck.datawrittencommunication.com
178.215.177.127 widearm.datawrittencommunication.com
178.215.177.128 datawrittencommunication.com
178.215.177.128 leafymeal.datawrittencommunication.com
178.215.177.129 goodrice.datawrittencommunication.com
178.215.177.130 brownhand.rapidintelligenceshare.com
178.215.177.131 heavenlywindow.rapidintelligenceshare.com
178.215.177.132 twinatom.rapidintelligenceshare.com
178.215.177.133 rapidintelligenceshare.com
178.215.177.133 triplefan.rapidintelligenceshare.com
178.215.177.134 greenbranch.challengesmetnow.com
178.215.177.135 oldbase.challengesmetnow.com
178.215.177.136 roastedworm.challengesmetnow.com
178.215.177.137 challengesmetnow.com
178.215.177.137 fragilenet.challengesmetnow.com
178.215.177.138 realgrape.laborofthemonth.com
178.215.177.139 laborofthemonth.com
178.215.177.139 mutemachine.laborofthemonth.com
178.215.177.140 smoothapple.laborofthemonth.com
178.215.177.141 pleasantswing.laborofthemonth.com
178.215.177.142 clearowl.primeopportunityknocks.com
178.215.177.143 fiercebox.primeopportunityknocks.com
178.215.177.143 primeopportunityknocks.com
178.215.177.144 friedfeast.primeopportunityknocks.com
178.215.177.145 steepboat.primeopportunityknocks.com
178.215.177.146 broadcity.commonopportunityknocks.com
178.215.177.146 commonopportunityknocks.com
178.215.177.147 latecollar.commonopportunityknocks.com
178.215.177.148 brightsystem.commonopportunityknocks.com
178.215.177.149 shrillbean.commonopportunityknocks.com
178.215.177.150 oddscarf.primeadvantagesource.com
178.215.177.151 flatjam.primeadvantagesource.com
178.215.177.152 lightcard.primeadvantagesource.com
178.215.177.153 primeadvantagesource.com
178.215.177.153 richgarden.primeadvantagesource.com
178.215.177.154 advantageindulgence.com
178.215.177.154 grayrock.advantageindulgence.com
178.215.177.155 freshcopy.advantageindulgence.com
178.215.177.156 happyair.advantageindulgence.com
178.215.177.157 tidyclock.advantageindulgence.com
178.215.177.158 fastball.relevancecheck.com
178.215.177.159 quietguide.relevancecheck.com
178.215.177.159 relevancecheck.com
178.215.177.160 toprabbit.relevancecheck.com
178.215.177.161 alertbasin.relevancecheck.com
178.215.177.162 slowcellar.utilityworkvalue.com
178.215.177.163 dryarea.utilityworkvalue.com
178.215.177.164 icysteel.utilityworkvalue.com
178.215.177.165 sadbook.utilityworkvalue.com
178.215.177.165 utilityworkvalue.com
178.215.177.166 cutedust.youronlinefinancialnews.com
178.215.177.167 superwire.youronlinefinancialnews.com
178.215.177.167 youronlinefinancialnews.com
178.215.177.168 nicethrone.youronlinefinancialnews.com
178.215.177.169 earlyart.youronlinefinancialnews.com
178.215.177.170 savorytruck.presentsimplesolutions.com
178.215.177.171 miniarm.presentsimplesolutions.com
178.215.177.171 presentsimplesolutions.com
178.215.177.172 widemeal.presentsimplesolutions.com
178.215.177.173 leafyrice.presentsimplesolutions.com
178.215.177.174 goodhand.spinsolution.net
178.215.177.174 spinsolution.net
178.215.177.175 brownwindow.spinsolution.net
178.215.177.176 heavenlyatom.spinsolution.net
178.215.177.177 twinfan.spinsolution.net
178.215.177.178 exposuresolution.com
178.215.177.178 triplebranch.exposuresolution.com
178.215.177.179 greenbase.exposuresolution.com
178.215.177.180 oldworm.exposuresolution.com
178.215.177.181 roastednet.exposuresolution.com
178.215.177.182 fragilegrape.practicesolution.net
178.215.177.183 realmachine.practicesolution.net
178.215.177.184 muteapple.practicesolution.net
178.215.177.185 practicesolution.net
178.215.177.185 smoothswing.practicesolution.net
178.215.177.186 pleasantowl.cutsolution.net
178.215.177.187 clearbox.cutsolution.net
178.215.177.188 fiercefeast.cutsolution.net
178.215.177.189 cutsolution.net
178.215.177.189 friedboat.cutsolution.net
178.215.177.190 carrysolution.com
178.215.177.190 steepcity.carrysolution.com
178.215.177.191 broadcollar.carrysolution.com
178.215.177.192 latesystem.carrysolution.com
178.215.177.193 brightbean.carrysolution.com
178.215.177.194 shrillscarf.runsolution.net
178.215.177.195 oddjam.runsolution.net
178.215.177.196 flatcard.runsolution.net
178.215.177.196 runsolution.net
178.215.177.197 lightgarden.runsolution.net
178.215.177.198 richrock.operatesolution.com
178.215.177.199 graycopy.operatesolution.com
178.215.177.200 freshair.operatesolution.com
178.215.177.201 happyclock.operatesolution.com
178.215.177.201 operatesolution.com
178.215.177.202 tidyball.turnsolution.com
178.215.177.202 turnsolution.com
178.215.177.203 fastguide.turnsolution.com
178.215.177.204 quietrabbit.turnsolution.com
178.215.177.205 topbasin.turnsolution.com
178.215.177.206 alertcellar.routinesolution.com
178.215.177.206 routinesolution.com
178.215.177.207 slowarea.routinesolution.com
178.215.177.208 drysteel.routinesolution.com
178.215.177.209 icybook.routinesolution.com
178.215.177.210 saddust.programsolution.net
178.215.177.211 cutewire.programsolution.net
178.215.177.212 programsolution.net
178.215.177.212 superthrone.programsolution.net
178.215.177.213 niceart.programsolution.net
178.215.177.214 earlytruck.internetnewsfeeds.com
178.215.177.214 internetnewsfeeds.com
178.215.177.215 savoryarm.internetnewsfeeds.com
178.215.177.216 minimeal.internetnewsfeeds.com
178.215.177.217 widerice.internetnewsfeeds.com
178.215.177.218 leafyhand.besthelpfound.com
178.215.177.219 goodwindow.besthelpfound.com
178.215.177.220 besthelpfound.com
178.215.177.220 brownatom.besthelpfound.com
178.215.177.221 heavenlyfan.besthelpfound.com
178.215.177.222 twinbranch.upliftingnetnews.com
178.215.177.223 triplebase.upliftingnetnews.com
178.215.177.224 greenworm.upliftingnetnews.com
178.215.177.224 upliftingnetnews.com
178.215.177.225 oldnet.upliftingnetnews.com
178.215.177.226 roastedgrape.realtimeresponder.com
178.215.177.227 fragilemachine.realtimeresponder.com
178.215.177.228 realapple.realtimeresponder.com
178.215.177.229 muteswing.realtimeresponder.com
178.215.177.229 realtimeresponder.com
178.215.177.230 smoothowl.livehelpfeed.com
178.215.177.231 pleasantbox.livehelpfeed.com
178.215.177.232 clearfeast.livehelpfeed.com
178.215.177.233 fierceboat.livehelpfeed.com
178.215.177.233 livehelpfeed.com
178.215.177.238 brightscarf.followupreturns.com
178.215.177.239 followupreturns.com
178.215.177.239 shrilljam.followupreturns.com
178.215.177.240 oddcard.followupreturns.com
178.215.177.241 flatgarden.followupreturns.com
178.215.177.242 lightrock.easyfinancialaccess.com
178.215.177.243 easyfinancialaccess.com
178.215.177.243 richcopy.easyfinancialaccess.com
178.215.177.244 grayair.easyfinancialaccess.com
178.215.177.245 freshclock.easyfinancialaccess.com
178.215.177.246 createoppsnow.com
178.215.177.246 happyball.createoppsnow.com
178.215.177.247 tidyguide.createoppsnow.com
178.215.177.248 fastrabbit.createoppsnow.com
178.215.177.249 quietbasin.createoppsnow.com
178.215.177.250 betterdealswebonline.com
178.215.177.250 topcellar.betterdealswebonline.com
178.215.177.251 alertarea.betterdealswebonline.com
178.215.177.252 slowsteel.betterdealswebonline.com
178.215.177.253 drybook.betterdealswebonline.com
178.215.177.254 icydust.betterdealswebonline.com
178.215.178.2 brightmachine.webdirectinfo.com
178.215.178.3 slowrabbit.webdirectinfo.com
178.215.178.4 clearrice.webdirectinfo.com
178.215.178.5 tidyball.webdirectinfo.com
178.215.178.5 webdirectinfo.com
178.215.178.6 savoryfeast.webanswerstoday.com
178.215.178.7 mutewindow.webanswerstoday.com
178.215.178.8 nicesteel.webanswerstoday.com
178.215.178.9 smootharea.webanswerstoday.com
178.215.178.9 webanswerstoday.com
178.215.178.10 friedbase.viewyourfinancialfuture.com
178.215.178.11 dryarm.viewyourfinancialfuture.com
178.215.178.12 heavenlyatom.viewyourfinancialfuture.com
178.215.178.13 fragileclock.viewyourfinancialfuture.com
178.215.178.13 viewyourfinancialfuture.com
178.215.178.14 cutenet.useurmoneywisely.com
178.215.178.15 steepwire.useurmoneywisely.com
178.215.178.15 useurmoneywisely.com
178.215.178.16 minicellar.useurmoneywisely.com
178.215.178.17 fasthand.useurmoneywisely.com
178.215.178.18 triplecity.totalchatshare.com
178.215.178.19 twinscarf.totalchatshare.com
178.215.178.20 grayworm.totalchatshare.com
178.215.178.20 totalchatshare.com
178.215.178.21 pleasantjam.totalchatshare.com
178.215.178.22 brownmeal.topservicelink.com
178.215.178.23 oddbranch.topservicelink.com
178.215.178.23 topservicelink.com
178.215.178.24 roastedrock.topservicelink.com
178.215.178.25 shrillboat.topservicelink.com
178.215.178.26 flatcard.topnotchchoices.com
178.215.178.27 happytruck.topnotchchoices.com
178.215.178.28 goodthrone.topnotchchoices.com
178.215.178.29 topnotchchoices.com
178.215.178.29 widegarden.topnotchchoices.com
178.215.178.30 realcopy.thinkonlinesolutions.com
178.215.178.31 quietcollar.thinkonlinesolutions.com
178.215.178.32 freshsystem.thinkonlinesolutions.com
178.215.178.33 lategrape.thinkonlinesolutions.com
178.215.178.33 thinkonlinesolutions.com
178.215.178.34 fiercefan.thebenchmarkstatus.com
178.215.178.34 thebenchmarkstatus.com
178.215.178.35 richbook.thebenchmarkstatus.com
178.215.178.36 earlyowl.thebenchmarkstatus.com
178.215.178.37 greenswing.thebenchmarkstatus.com
178.215.178.38 lightapple.submityourquery.com
178.215.178.38 submityourquery.com
178.215.178.39 alertair.submityourquery.com
178.215.178.40 oldbox.submityourquery.com
178.215.178.41 superbasin.submityourquery.com
178.215.178.42 sadbean.statusupgrade.com
178.215.178.42 statusupgrade.com
178.215.178.43 broadart.statusupgrade.com
178.215.178.44 leafyguide.statusupgrade.com
178.215.178.45 icydust.statusupgrade.com
178.215.178.46 topmachine.starservicenow.com
178.215.178.47 brightrabbit.starservicenow.com
178.215.178.47 starservicenow.com
178.215.178.48 slowrice.starservicenow.com
178.215.178.49 clearball.starservicenow.com
178.215.178.50 tidyfeast.solutionspackagedonline.com
178.215.178.51 savorywindow.solutionspackagedonline.com
178.215.178.51 solutionspackagedonline.com
178.215.178.52 mutesteel.solutionspackagedonline.com
178.215.178.53 nicearea.solutionspackagedonline.com
178.215.178.54 smoothbase.solidcoordination.com
178.215.178.55 friedarm.solidcoordination.com
178.215.178.55 solidcoordination.com
178.215.178.56 dryatom.solidcoordination.com
178.215.178.57 heavenlyclock.solidcoordination.com
178.215.178.62 fastcity.sharedconstitution.com
178.215.178.63 triplescarf.sharedconstitution.com
178.215.178.64 sharedconstitution.com
178.215.178.64 twinworm.sharedconstitution.com
178.215.178.65 grayjam.sharedconstitution.com
178.215.178.66 pleasantmeal.securehelpsource.com
178.215.178.67 brownbranch.securehelpsource.com
178.215.178.68 oddrock.securehelpsource.com
178.215.178.69 roastedboat.securehelpsource.com
178.215.178.69 securehelpsource.com
178.215.178.70 shrillcard.returnthebenifits.com
178.215.178.71 flattruck.returnthebenifits.com
178.215.178.72 happythrone.returnthebenifits.com
178.215.178.72 returnthebenifits.com
178.215.178.73 goodgarden.returnthebenifits.com
178.215.178.74 widecopy.resurfacedknowledge.com
178.215.178.75 realcollar.resurfacedknowledge.com
178.215.178.75 resurfacedknowledge.com
178.215.178.76 quietsystem.resurfacedknowledge.com
178.215.178.77 freshgrape.resurfacedknowledge.com
178.215.178.82 greenapple.rationalconcern.com
178.215.178.83 lightair.rationalconcern.com
178.215.178.83 rationalconcern.com
178.215.178.84 alertbox.rationalconcern.com
178.215.178.85 oldbasin.rationalconcern.com
178.215.178.86 superbean.qualityhelpsearch.com
178.215.178.87 sadart.qualityhelpsearch.com
178.215.178.88 broadguide.qualityhelpsearch.com
178.215.178.88 qualityhelpsearch.com
178.215.178.89 leafydust.qualityhelpsearch.com
178.215.178.90 icymachine.publicreminder.com
178.215.178.91 toprabbit.publicreminder.com
178.215.178.92 brightrice.publicreminder.com
178.215.178.92 publicreminder.com
178.215.178.93 slowball.publicreminder.com
178.215.178.94 clearfeast.provenqualitynow.com
178.215.178.95 provenqualitynow.com
178.215.178.95 tidywindow.provenqualitynow.com
178.215.178.96 savorysteel.provenqualitynow.com
178.215.178.97 mutearea.provenqualitynow.com
178.215.178.102 heavenlynet.privateaidsupport.com
178.215.178.102 privateaidsupport.com
178.215.178.103 fragilewire.privateaidsupport.com
178.215.178.104 cutecellar.privateaidsupport.com
178.215.178.105 steephand.privateaidsupport.com
178.215.178.106 minicity.practicaladvisory.com
178.215.178.107 fastscarf.practicaladvisory.com
178.215.178.108 practicaladvisory.com
178.215.178.108 tripleworm.practicaladvisory.com
178.215.178.109 twinjam.practicaladvisory.com
178.215.178.110 graymeal.placementreturns.com
178.215.178.111 pleasantbranch.placementreturns.com
178.215.178.112 brownrock.placementreturns.com
178.215.178.113 oddboat.placementreturns.com
178.215.178.113 placementreturns.com
178.215.178.114 roastedcard.oppstorenet.com
178.215.178.115 shrilltruck.oppstorenet.com
178.215.178.116 flatthrone.oppstorenet.com
178.215.178.117 happygarden.oppstorenet.com
178.215.178.117 oppstorenet.com
178.215.178.118 goodcopy.onlinelifesaver.com
178.215.178.119 widecollar.onlinelifesaver.com
178.215.178.120 realsystem.onlinelifesaver.com
178.215.178.121 onlinelifesaver.com
178.215.178.121 quietgrape.onlinelifesaver.com
178.215.178.122 freshfan.notroublereturns.com
178.215.178.122 notroublereturns.com
178.215.178.123 latebook.notroublereturns.com
178.215.178.124 fierceowl.notroublereturns.com
178.215.178.125 richswing.notroublereturns.com
178.215.178.126 earlyapple.newstomorrowtoday.com
178.215.178.126 newstomorrowtoday.com
178.215.178.127 greenair.newstomorrowtoday.com
178.215.178.128 lightbox.newstomorrowtoday.com
178.215.178.129 alertbasin.newstomorrowtoday.com
178.215.178.130 oldbean.newsdelivereddaily.com
178.215.178.131 superart.newsdelivereddaily.com
178.215.178.132 newsdelivereddaily.com
178.215.178.132 sadguide.newsdelivereddaily.com
178.215.178.133 broaddust.newsdelivereddaily.com
178.215.178.134 leafymachine.neededhelptoday.com
178.215.178.135 icyrabbit.neededhelptoday.com
178.215.178.136 toprice.neededhelptoday.com
178.215.178.137 brightball.neededhelptoday.com
178.215.178.137 neededhelptoday.com
178.215.178.138 slowfeast.mostsensibleanswer.com
178.215.178.139 clearwindow.mostsensibleanswer.com
178.215.178.140 tidysteel.mostsensibleanswer.com
178.215.178.141 mostsensibleanswer.com
178.215.178.141 savoryarea.mostsensibleanswer.com
178.215.178.142 mutebase.mission-objective.com
178.215.178.143 nicearm.mission-objective.com
178.215.178.144 smoothatom.mission-objective.com
178.215.178.145 friedclock.mission-objective.com
178.215.178.145 mission-objective.com
178.215.178.146 drynet.messageresponder.com
178.215.178.147 heavenlywire.messageresponder.com
178.215.178.148 fragilecellar.messageresponder.com
178.215.178.149 cutehand.messageresponder.com
178.215.178.149 messageresponder.com
178.215.178.150 steepcity.luckydaymade.com
178.215.178.151 miniscarf.luckydaymade.com
178.215.178.152 fastworm.luckydaymade.com
178.215.178.153 luckydaymade.com
178.215.178.153 triplejam.luckydaymade.com
178.215.178.154 twinmeal.livelifeharmoniously.com
178.215.178.155 graybranch.livelifeharmoniously.com
178.215.178.156 livelifeharmoniously.com
178.215.178.156 pleasantrock.livelifeharmoniously.com
178.215.178.157 brownboat.livelifeharmoniously.com
178.215.178.158 oddcard.knockoutthewall.com
178.215.178.159 knockoutthewall.com
178.215.178.159 roastedtruck.knockoutthewall.com
178.215.178.160 shrillthrone.knockoutthewall.com
178.215.178.161 flatgarden.knockoutthewall.com
178.215.178.162 happycopy.jobvaluefocus.com
178.215.178.163 goodcollar.jobvaluefocus.com
178.215.178.164 jobvaluefocus.com
178.215.178.164 widesystem.jobvaluefocus.com
178.215.178.165 realgrape.jobvaluefocus.com
178.215.178.166 quietfan.internethelpsource.com
178.215.178.167 freshbook.internethelpsource.com
178.215.178.167 internethelpsource.com
178.215.178.168 lateowl.internethelpsource.com
178.215.178.169 fierceswing.internethelpsource.com
178.215.178.170 richapple.instantresultsnow.com
178.215.178.171 earlyair.instantresultsnow.com
178.215.178.172 greenbox.instantresultsnow.com
178.215.178.173 instantresultsnow.com
178.215.178.173 lightbasin.instantresultsnow.com
178.215.178.174 alertbean.instanthelproute.com
178.215.178.175 oldart.instanthelproute.com
178.215.178.176 superguide.instanthelproute.com
178.215.178.177 instanthelproute.com
178.215.178.177 saddust.instanthelproute.com
178.215.178.178 broadmachine.inspiredsensibility.com
178.215.178.179 leafyrabbit.inspiredsensibility.com
178.215.178.180 icyrice.inspiredsensibility.com
178.215.178.181 inspiredsensibility.com
178.215.178.181 topball.inspiredsensibility.com
178.215.178.182 brightfeast.infocentralnow.com
178.215.178.183 slowwindow.infocentralnow.com
178.215.178.184 clearsteel.infocentralnow.com
178.215.178.185 infocentralnow.com
178.215.178.185 tidyarea.infocentralnow.com
178.215.178.186 savorybase.hundredpercenthelp.com
178.215.178.187 hundredpercenthelp.com
178.215.178.187 mutearm.hundredpercenthelp.com
178.215.178.188 niceatom.hundredpercenthelp.com
178.215.178.189 smoothclock.hundredpercenthelp.com
178.215.178.190 friednet.honestnetworkdeals.com
178.215.178.191 drywire.honestnetworkdeals.com
178.215.178.191 honestnetworkdeals.com
178.215.178.192 heavenlycellar.honestnetworkdeals.com
178.215.178.193 fragilehand.honestnetworkdeals.com
178.215.178.194 cutecity.hicaliberpromos.com
178.215.178.195 hicaliberpromos.com
178.215.178.195 steepscarf.hicaliberpromos.com
178.215.178.196 miniworm.hicaliberpromos.com
178.215.178.197 fastjam.hicaliberpromos.com
178.215.178.202 browncard.digitalnewsarchive.com
178.215.178.203 oddtruck.digitalnewsarchive.com
178.215.178.204 digitalnewsarchive.com
178.215.178.204 roastedthrone.digitalnewsarchive.com
178.215.178.205 shrillgarden.digitalnewsarchive.com
178.215.178.206 flatcopy.datawebnetwork.com
178.215.178.207 datawebnetwork.com
178.215.178.207 happycollar.datawebnetwork.com
178.215.178.208 goodsystem.datawebnetwork.com
178.215.178.209 widegrape.datawebnetwork.com
178.215.178.210 datanetworkregistry.com
178.215.178.210 realfan.datanetworkregistry.com
178.215.178.211 quietbook.datanetworkregistry.com
178.215.178.212 freshowl.datanetworkregistry.com
178.215.178.213 lateswing.datanetworkregistry.com
178.215.178.214 fierceapple.dailytestimonynow.com
178.215.178.215 richair.dailytestimonynow.com
178.215.178.216 earlybox.dailytestimonynow.com
178.215.178.217 dailytestimonynow.com
178.215.178.217 greenbasin.dailytestimonynow.com
178.215.178.218 dailynewsportal.net
178.215.178.218 lightbean.dailynewsportal.net
178.215.178.219 alertart.dailynewsportal.net
178.215.178.220 oldguide.dailynewsportal.net
178.215.178.221 superdust.dailynewsportal.net
178.215.178.222 dailycentralbulletin.com
178.215.178.222 sadmachine.dailycentralbulletin.com
178.215.178.223 broadrabbit.dailycentralbulletin.com
178.215.178.224 leafyrice.dailycentralbulletin.com
178.215.178.225 icyball.dailycentralbulletin.com
178.215.178.226 topfeast.buildingrelationship.net
178.215.178.227 brightwindow.buildingrelationship.net
178.215.178.228 slowsteel.buildingrelationship.net
178.215.178.229 buildingrelationship.net
178.215.178.229 cleararea.buildingrelationship.net
178.215.178.230 basicsurfenterprise.com
178.215.178.230 tidybase.basicsurfenterprise.com
178.215.178.231 savoryarm.basicsurfenterprise.com
178.215.178.232 muteatom.basicsurfenterprise.com
178.215.178.233 niceclock.basicsurfenterprise.com
178.215.178.234 smoothnet.activehostsolution.com
178.215.178.235 friedwire.activehostsolution.com
178.215.178.236 drycellar.activehostsolution.com
178.215.178.237 activehostsolution.com
178.215.178.237 heavenlyhand.activehostsolution.com
178.215.178.238 fragilecity.greatideasgreatbenefits.com
178.215.178.239 cutescarf.greatideasgreatbenefits.com
178.215.178.240 greatideasgreatbenefits.com
178.215.178.240 steepworm.greatideasgreatbenefits.com
178.215.178.241 minijam.greatideasgreatbenefits.com
178.215.178.242 fastmeal.speedyinfoshare.com
178.215.178.243 speedyinfoshare.com
178.215.178.243 triplebranch.speedyinfoshare.com
178.215.178.244 twinrock.speedyinfoshare.com
178.215.178.245 grayboat.speedyinfoshare.com
178.215.178.246 pleasantcard.risingwebsearch.com
178.215.178.247 browntruck.risingwebsearch.com
178.215.178.247 risingwebsearch.com
178.215.178.248 oddthrone.risingwebsearch.com
178.215.178.249 roastedgarden.risingwebsearch.com
178.215.178.250 shrillcopy.recentwebsearch.com
178.215.178.251 flatcollar.recentwebsearch.com
178.215.178.252 happysystem.recentwebsearch.com
178.215.178.253 goodgrape.recentwebsearch.com
178.215.178.254 recentwebsearch.com
178.215.178.254 widefan.recentwebsearch.com
178.215.179.2 slowcity.rapidnetmedia.com
178.215.179.3 quietcopy.rapidnetmedia.com
178.215.179.4 freshbook.rapidnetmedia.com
178.215.179.4 rapidnetmedia.com
178.215.179.5 earlybox.rapidnetmedia.com
178.215.179.6 roastedscarf.rapidinformationshare.com
178.215.179.7 cutefeast.rapidinformationshare.com
178.215.179.8 latecollar.rapidinformationshare.com
178.215.179.8 rapidinformationshare.com
178.215.179.9 oddclock.rapidinformationshare.com
178.215.179.10 realboat.rapidfactshare.com
178.215.179.11 tidyair.rapidfactshare.com
178.215.179.12 rapidfactshare.com
178.215.179.12 shrillarea.rapidfactshare.com
178.215.179.13 flatball.rapidfactshare.com
178.215.179.14 graywire.rapidcontentshare.com
178.215.179.15 miniart.rapidcontentshare.com
178.215.179.15 rapidcontentshare.com
178.215.179.16 gooddust.rapidcontentshare.com
178.215.179.17 savoryswing.rapidcontentshare.com
178.215.179.18 leafyatom.novelwebsearch.com
178.215.179.18 novelwebsearch.com
178.215.179.19 friedfan.novelwebsearch.com
178.215.179.20 richapple.novelwebsearch.com
178.215.179.21 clearguide.novelwebsearch.com
178.215.179.22 drytruck.newtrapsearch.com
178.215.179.23 supersystem.newtrapsearch.com
178.215.179.24 lightbase.newtrapsearch.com
178.215.179.25 fastarm.newtrapsearch.com
178.215.179.25 newtrapsearch.com
178.215.179.26 sadsteel.newtowebsearch.com
178.215.179.27 nicecard.newtowebsearch.com
178.215.179.28 happyrock.newtowebsearch.com
178.215.179.29 alertgarden.newtowebsearch.com
178.215.179.29 newtowebsearch.com
178.215.179.34 twinhand.newfeathersearch.com
178.215.179.35 triplerabbit.newfeathersearch.com
178.215.179.36 icyworm.newfeathersearch.com
178.215.179.37 newfeathersearch.com
178.215.179.37 pleasantcellar.newfeathersearch.com
178.215.179.38 brightbean.newentanglementsearch.com
178.215.179.38 newentanglementsearch.com
178.215.179.39 broadmeal.newentanglementsearch.com
178.215.179.40 mutejam.newentanglementsearch.com
178.215.179.41 smoothnet.newentanglementsearch.com
178.215.179.46 browncity.new-sprungwebsearch.com
178.215.179.47 new-sprungwebsearch.com
178.215.179.47 slowcopy.new-sprungwebsearch.com
178.215.179.48 quietbook.new-sprungwebsearch.com
178.215.179.49 freshbox.new-sprungwebsearch.com
178.215.179.50 earlyscarf.netsourcecore.com
178.215.179.51 netsourcecore.com
178.215.179.51 roastedfeast.netsourcecore.com
178.215.179.52 cutecollar.netsourcecore.com
178.215.179.53 lateclock.netsourcecore.com
178.215.179.54 freshwebsearch.com
178.215.179.54 oddboat.freshwebsearch.com
178.215.179.55 realair.freshwebsearch.com
178.215.179.56 tidyarea.freshwebsearch.com
178.215.179.57 shrillball.freshwebsearch.com
178.215.179.62 savoryatom.earlywebsearch.com
178.215.179.63 leafyfan.earlywebsearch.com
178.215.179.64 earlywebsearch.com
178.215.179.64 friedapple.earlywebsearch.com
178.215.179.65 richguide.earlywebsearch.com
178.215.179.66 cleartruck.currentwebsearch.com
178.215.179.67 drysystem.currentwebsearch.com
178.215.179.68 superbase.currentwebsearch.com
178.215.179.69 currentwebsearch.com
178.215.179.69 lightarm.currentwebsearch.com
178.215.179.70 faststeel.currentweblookout.com
178.215.179.71 currentweblookout.com
178.215.179.71 sadcard.currentweblookout.com
178.215.179.72 nicerock.currentweblookout.com
178.215.179.73 happygarden.currentweblookout.com
178.215.179.74 alertthrone.availmailadvantage.com
178.215.179.75 oldmachine.availmailadvantage.com
178.215.179.76 widebasin.availmailadvantage.com
178.215.179.77 availmailadvantage.com
178.215.179.77 heavenlyrice.availmailadvantage.com
178.215.179.78 tophand.openingsopportunity.com
178.215.179.79 openingsopportunity.com
178.215.179.79 twinrabbit.openingsopportunity.com
178.215.179.80 tripleworm.openingsopportunity.com
178.215.179.81 icycellar.openingsopportunity.com
178.215.179.82 fromhomeservice.com
178.215.179.82 pleasantbean.fromhomeservice.com
178.215.179.83 brightmeal.fromhomeservice.com
178.215.179.84 broadjam.fromhomeservice.com
178.215.179.85 mutenet.fromhomeservice.com
178.215.179.86 smoothwindow.fromhomeservice.com
178.215.179.87 steepgrape.fromhomeservice.com
178.215.179.88 greenowl.fromhomeservice.com
178.215.179.89 fiercebranch.fromhomeservice.com
178.215.179.90 fragilecity.straightforwardnet.com
178.215.179.91 browncopy.straightforwardnet.com
178.215.179.91 straightforwardnet.com
178.215.179.92 slowbook.straightforwardnet.com
178.215.179.93 quietbox.straightforwardnet.com
178.215.179.98 lateboat.financialdefinition.com
178.215.179.99 oddair.financialdefinition.com
178.215.179.100 financialdefinition.com
178.215.179.100 realarea.financialdefinition.com
178.215.179.101 tidyball.financialdefinition.com
178.215.179.102 shrillwire.financialaidoutreach.com
178.215.179.103 financialaidoutreach.com
178.215.179.103 flatart.financialaidoutreach.com
178.215.179.104 graydust.financialaidoutreach.com
178.215.179.105 miniswing.financialaidoutreach.com
178.215.179.106 goodatom.fighteconomicrecession.com
178.215.179.107 savoryfan.fighteconomicrecession.com
178.215.179.108 fighteconomicrecession.com
178.215.179.108 leafyapple.fighteconomicrecession.com
178.215.179.109 friedguide.fighteconomicrecession.com
178.215.179.110 richtruck.fastactionresponse.com
178.215.179.111 clearsystem.fastactionresponse.com
178.215.179.112 drybase.fastactionresponse.com
178.215.179.112 fastactionresponse.com
178.215.179.113 superarm.fastactionresponse.com
178.215.179.114 lightsteel.exclusivecommunication.net
178.215.179.115 fastcard.exclusivecommunication.net
178.215.179.116 exclusivecommunication.net
178.215.179.116 sadrock.exclusivecommunication.net
178.215.179.117 nicegarden.exclusivecommunication.net
178.215.179.118 happythrone.directprofessionalhelp.com
178.215.179.119 alertmachine.directprofessionalhelp.com
178.215.179.119 directprofessionalhelp.com
178.215.179.120 oldbasin.directprofessionalhelp.com
178.215.179.121 widerice.directprofessionalhelp.com
178.215.179.122 heavenlyhand.directactionweb.com
178.215.179.123 directactionweb.com
178.215.179.123 toprabbit.directactionweb.com
178.215.179.124 twinworm.directactionweb.com
178.215.179.125 triplecellar.directactionweb.com
178.215.179.126 icybean.fullverseoptions.com
178.215.179.127 pleasantmeal.fullverseoptions.com
178.215.179.128 brightjam.fullverseoptions.com
178.215.179.129 broadnet.fullverseoptions.com
178.215.179.129 fullverseoptions.com
178.215.179.130 mutewindow.freewebtransaction.com
178.215.179.131 freewebtransaction.com
178.215.179.131 smoothgrape.freewebtransaction.com
178.215.179.132 steepowl.freewebtransaction.com
178.215.179.133 greenbranch.freewebtransaction.com
178.215.179.134 fiercecity.freewebnotice.com
178.215.179.135 fragilecopy.freewebnotice.com
178.215.179.136 brownbook.freewebnotice.com
178.215.179.137 freewebnotice.com
178.215.179.137 slowbox.freewebnotice.com
178.215.179.138 freeflowstrategy.com
178.215.179.138 quietscarf.freeflowstrategy.com
178.215.179.139 freshfeast.freeflowstrategy.com
178.215.179.140 earlycollar.freeflowstrategy.com
178.215.179.141 roastedclock.freeflowstrategy.com
178.215.179.142 cuteboat.perstateidentified.com
178.215.179.143 lateair.perstateidentified.com
178.215.179.144 oddarea.perstateidentified.com
178.215.179.144 perstateidentified.com
178.215.179.145 realball.perstateidentified.com
178.215.179.146 tidywire.onlinesupportdome.com
178.215.179.147 shrillart.onlinesupportdome.com
178.215.179.148 flatdust.onlinesupportdome.com
178.215.179.148 onlinesupportdome.com
178.215.179.149 grayswing.onlinesupportdome.com
178.215.179.154 friedtruck.newonlinefeature.com
178.215.179.155 richsystem.newonlinefeature.com
178.215.179.156 clearbase.newonlinefeature.com
178.215.179.157 dryarm.newonlinefeature.com
178.215.179.157 newonlinefeature.com
178.215.179.158 supersteel.newoffersearch.com
178.215.179.159 lightcard.newoffersearch.com
178.215.179.160 fastrock.newoffersearch.com
178.215.179.161 newoffersearch.com
178.215.179.161 sadgarden.newoffersearch.com
178.215.179.162 nicethrone.mychattertag.com
178.215.179.163 happymachine.mychattertag.com
178.215.179.164 alertbasin.mychattertag.com
178.215.179.165 mychattertag.com
178.215.179.165 oldrice.mychattertag.com
178.215.179.166 widehand.instanthelpaccess.com
178.215.179.167 heavenlyrabbit.instanthelpaccess.com
178.215.179.168 instanthelpaccess.com
178.215.179.168 topworm.instanthelpaccess.com
178.215.179.169 twincellar.instanthelpaccess.com
178.215.179.170 triplebean.informationport.net
178.215.179.171 icymeal.informationport.net
178.215.179.171 informationport.net
178.215.179.172 pleasantjam.informationport.net
178.215.179.173 brightnet.informationport.net
178.215.179.174 broadwindow.indepthsolution.com
178.215.179.175 mutegrape.indepthsolution.com
178.215.179.176 smoothowl.indepthsolution.com
178.215.179.177 indepthsolution.com
178.215.179.177 steepbranch.indepthsolution.com
178.215.179.178 greencity.hundredpercentaid.com
178.215.179.178 hundredpercentaid.com
178.215.179.179 fiercecopy.hundredpercentaid.com
178.215.179.180 fragilebook.hundredpercentaid.com
178.215.179.181 brownbox.hundredpercentaid.com
178.215.179.182 slowscarf.helpavailonline.com
178.215.179.183 quietfeast.helpavailonline.com
178.215.179.184 freshcollar.helpavailonline.com
178.215.179.185 earlyclock.helpavailonline.com
178.215.179.185 helpavailonline.com
178.215.179.186 roastedboat.thoughtcubecareers.com
178.215.179.187 cuteair.thoughtcubecareers.com
178.215.179.188 latearea.thoughtcubecareers.com
178.215.179.188 thoughtcubecareers.com
178.215.179.189 oddball.thoughtcubecareers.com
178.215.179.190 realwire.thecorestrength.com
178.215.179.191 thecorestrength.com
178.215.179.191 tidyart.thecorestrength.com
178.215.179.192 shrilldust.thecorestrength.com
178.215.179.193 flatswing.thecorestrength.com
178.215.179.198 leafytruck.smartsolutionscampaign.com
178.215.179.199 friedsystem.smartsolutionscampaign.com
178.215.179.200 richbase.smartsolutionscampaign.com
178.215.179.201 cleararm.smartsolutionscampaign.com
178.215.179.201 smartsolutionscampaign.com
178.215.179.206 sadthrone.quickscoresearch.com
178.215.179.207 nicemachine.quickscoresearch.com
178.215.179.208 happybasin.quickscoresearch.com
178.215.179.209 alertrice.quickscoresearch.com
178.215.179.209 quickscoresearch.com
178.215.179.210 oldhand.quickdigitalfix.com
178.215.179.211 widerabbit.quickdigitalfix.com
178.215.179.212 heavenlyworm.quickdigitalfix.com
178.215.179.212 quickdigitalfix.com
178.215.179.213 topcellar.quickdigitalfix.com
178.215.179.214 twinbean.provenqualityhow.com
178.215.179.215 triplemeal.provenqualityhow.com
178.215.179.216 icyjam.provenqualityhow.com
178.215.179.216 provenqualityhow.com
178.215.179.217 pleasantnet.provenqualityhow.com
178.215.179.218 brightwindow.productivedecision.com
178.215.179.219 broadgrape.productivedecision.com
178.215.179.220 muteowl.productivedecision.com
178.215.179.220 productivedecision.com
178.215.179.221 smoothbranch.productivedecision.com
178.215.179.222 steepcity.prodinformation.com
178.215.179.223 greencopy.prodinformation.com
178.215.179.223 prodinformation.com
178.215.179.224 fiercebook.prodinformation.com
178.215.179.225 fragilebox.prodinformation.com
178.215.179.230 earlyboat.advancewebdominance.com
178.215.179.231 advancewebdominance.com
178.215.179.231 roastedair.advancewebdominance.com
178.215.179.232 cutearea.advancewebdominance.com
178.215.179.233 lateball.advancewebdominance.com
178.215.179.234 oddwire.additionaladvocate.com
178.215.179.235 additionaladvocate.com
178.215.179.235 realart.additionaladvocate.com
178.215.179.236 tidydust.additionaladvocate.com
178.215.179.237 shrillswing.additionaladvocate.com
178.215.179.238 flatatom.webcentricdeliveries.com
178.215.179.239 grayfan.webcentricdeliveries.com
178.215.179.240 miniapple.webcentricdeliveries.com
178.215.179.240 webcentricdeliveries.com
178.215.179.241 goodguide.webcentricdeliveries.com
178.215.179.246 clearsteel.virtuallibrarysolution.com
178.215.179.247 drycard.virtuallibrarysolution.com
178.215.179.247 virtuallibrarysolution.com
178.215.179.248 superrock.virtuallibrarysolution.com
178.215.179.249 lightgarden.virtuallibrarysolution.com
178.215.179.250 fastthrone.virtualdatabank.net
178.215.179.250 virtualdatabank.net
178.215.179.251 sadmachine.virtualdatabank.net
178.215.179.252 nicebasin.virtualdatabank.net
178.215.179.253 happyrice.virtualdatabank.net
178.215.179.254 alerthand.virtualdatabank.net
178.215.180.2 hcpcq.standcommunicationstatus.com
178.215.180.3 newkzg.standcommunicationstatus.com
178.215.180.4 ovnil.standcommunicationstatus.com
178.215.180.5 dhtlgjw.standcommunicationstatus.com
178.215.180.6 spnfwpv.standcommunicationstatus.com
178.215.180.7 ffm.standcommunicationstatus.com
178.215.180.8 cwjjix.standcommunicationstatus.com
178.215.180.9 vfqajyt.standcommunicationstatus.com
178.215.180.10 ecqg.standcommunicationstatus.com
178.215.180.11 gtb.standcommunicationstatus.com
178.215.180.12 ixbodox.standcommunicationstatus.com
178.215.180.13 lhptft.standcommunicationstatus.com
178.215.180.13 standcommunicationstatus.com
178.215.180.14 kjpuh.standcommunicationstatus.com
178.215.180.15 ommfsh.standcommunicationstatus.com
178.215.180.16 ljnug.standcommunicationstatus.com
178.215.180.17 ikdg.standcommunicationstatus.com
178.215.180.18 pofi.standcommunicationstatus.com
178.215.180.19 zxej.standcommunicationstatus.com
178.215.180.20 yrwmd.standcommunicationstatus.com
178.215.180.21 rwqdia.standcommunicationstatus.com
178.215.180.22 chgl.standcommunicationstatus.com
178.215.180.23 krhz.standcommunicationstatus.com
178.215.180.24 nizmgd.standcommunicationstatus.com
178.215.180.25 tbm.ratecommunicationstatus.com
178.215.180.26 nqzf.ratecommunicationstatus.com
178.215.180.27 pjuqa.ratecommunicationstatus.com
178.215.180.28 xgi.ratecommunicationstatus.com
178.215.180.29 rawqg.ratecommunicationstatus.com
178.215.180.30 zfvfiq.ratecommunicationstatus.com
178.215.180.31 kdp.ratecommunicationstatus.com
178.215.180.31 ratecommunicationstatus.com
178.215.180.32 tod.ratecommunicationstatus.com
178.215.180.33 emaumx.ratecommunicationstatus.com
178.215.180.34 tgfk.ratecommunicationstatus.com
178.215.180.35 bbnlat.ratecommunicationstatus.com
178.215.180.36 gbxelb.ratecommunicationstatus.com
178.215.180.37 juin.ratecommunicationstatus.com
178.215.180.38 mabgnzy.ratecommunicationstatus.com
178.215.180.39 fdsmft.ratecommunicationstatus.com
178.215.180.40 rutxauv.ratecommunicationstatus.com
178.215.180.41 gwzqri.ratecommunicationstatus.com
178.215.180.42 suetbst.ratecommunicationstatus.com
178.215.180.43 zzc.ratecommunicationstatus.com
178.215.180.44 lill.ratecommunicationstatus.com
178.215.180.45 gfx.ratecommunicationstatus.com
178.215.180.46 ztmgpm.ratecommunicationstatus.com
178.215.180.47 hub.ratecommunicationstatus.com
178.215.180.48 znpy.rankcommunicationstatus.com
178.215.180.49 sqybb.rankcommunicationstatus.com
178.215.180.50 aipypp.rankcommunicationstatus.com
178.215.180.51 cvho.rankcommunicationstatus.com
178.215.180.52 pjvo.rankcommunicationstatus.com
178.215.180.53 bio.rankcommunicationstatus.com
178.215.180.54 veziwpg.rankcommunicationstatus.com
178.215.180.55 rqy.rankcommunicationstatus.com
178.215.180.56 fxo.rankcommunicationstatus.com
178.215.180.57 orqw.rankcommunicationstatus.com
178.215.180.58 jlpeao.rankcommunicationstatus.com
178.215.180.59 jdhfhg.rankcommunicationstatus.com
178.215.180.60 ewubn.rankcommunicationstatus.com
178.215.180.61 anqxb.rankcommunicationstatus.com
178.215.180.62 msbjy.rankcommunicationstatus.com
178.215.180.62 rankcommunicationstatus.com
178.215.180.63 voqvc.rankcommunicationstatus.com
178.215.180.64 ffe.rankcommunicationstatus.com
178.215.180.65 nlyrhs.rankcommunicationstatus.com
178.215.180.66 vcti.rankcommunicationstatus.com
178.215.180.67 rkee.rankcommunicationstatus.com
178.215.180.68 fncriqh.rankcommunicationstatus.com
178.215.180.69 sejyjtl.rankcommunicationstatus.com
178.215.180.70 rcck.rankcommunicationstatus.com
178.215.180.71 xmp.rangecommunicationstatus.com
178.215.180.72 fhqjlt.rangecommunicationstatus.com
178.215.180.73 zvgim.rangecommunicationstatus.com
178.215.180.74 nfswd.rangecommunicationstatus.com
178.215.180.75 qpxiszs.rangecommunicationstatus.com
178.215.180.76 xfedl.rangecommunicationstatus.com
178.215.180.77 uvxok.rangecommunicationstatus.com
178.215.180.78 krg.rangecommunicationstatus.com
178.215.180.79 ftb.rangecommunicationstatus.com
178.215.180.80 qfb.rangecommunicationstatus.com
178.215.180.80 rangecommunicationstatus.com
178.215.180.81 vypnxh.rangecommunicationstatus.com
178.215.180.82 vngyyst.rangecommunicationstatus.com
178.215.180.83 qheo.rangecommunicationstatus.com
178.215.180.84 wuoc.rangecommunicationstatus.com
178.215.180.85 qbevc.rangecommunicationstatus.com
178.215.180.86 qazey.rangecommunicationstatus.com
178.215.180.87 gtunst.rangecommunicationstatus.com
178.215.180.88 lnxtrl.rangecommunicationstatus.com
178.215.180.89 ogzqu.rangecommunicationstatus.com
178.215.180.90 rylt.rangecommunicationstatus.com
178.215.180.91 cujgsq.rangecommunicationstatus.com
178.215.180.92 llbdf.rangecommunicationstatus.com
178.215.180.93 psgijs.rangecommunicationstatus.com
178.215.180.94 yyuo.thinkcommunicationstatus.com
178.215.180.95 kfrw.thinkcommunicationstatus.com
178.215.180.96 byt.thinkcommunicationstatus.com
178.215.180.97 flbtwm.thinkcommunicationstatus.com
178.215.180.98 ard.thinkcommunicationstatus.com
178.215.180.99 kkzu.thinkcommunicationstatus.com
178.215.180.100 tsaogty.thinkcommunicationstatus.com
178.215.180.101 lvlmt.thinkcommunicationstatus.com
178.215.180.102 wzpxtmk.thinkcommunicationstatus.com
178.215.180.103 ncsdm.thinkcommunicationstatus.com
178.215.180.104 cgewzek.thinkcommunicationstatus.com
178.215.180.105 yjrjec.thinkcommunicationstatus.com
178.215.180.106 ygs.thinkcommunicationstatus.com
178.215.180.107 wqq.thinkcommunicationstatus.com
178.215.180.108 bfvexz.thinkcommunicationstatus.com
178.215.180.109 zcyd.thinkcommunicationstatus.com
178.215.180.110 xij.thinkcommunicationstatus.com
178.215.180.111 hstqxwm.thinkcommunicationstatus.com
178.215.180.112 cft.thinkcommunicationstatus.com
178.215.180.113 vkh.thinkcommunicationstatus.com
178.215.180.114 pdb.thinkcommunicationstatus.com
178.215.180.115 csmeq.thinkcommunicationstatus.com
178.215.180.116 dozn.thinkcommunicationstatus.com
178.215.180.116 thinkcommunicationstatus.com
178.215.180.117 gfkx.confirmcommunicationstatus.com
178.215.180.118 gjzjpsi.confirmcommunicationstatus.com
178.215.180.119 cqist.confirmcommunicationstatus.com
178.215.180.120 ewcrbt.confirmcommunicationstatus.com
178.215.180.121 fhgsym.confirmcommunicationstatus.com
178.215.180.122 ijb.confirmcommunicationstatus.com
178.215.180.123 tazi.confirmcommunicationstatus.com
178.215.180.124 iuvy.confirmcommunicationstatus.com
178.215.180.125 nsnspqj.confirmcommunicationstatus.com
178.215.180.126 jrwr.confirmcommunicationstatus.com
178.215.180.127 oqk.confirmcommunicationstatus.com
178.215.180.128 ztoon.confirmcommunicationstatus.com
178.215.180.129 owixq.confirmcommunicationstatus.com
178.215.180.130 wtrogke.confirmcommunicationstatus.com
178.215.180.131 tvg.confirmcommunicationstatus.com
178.215.180.132 confirmcommunicationstatus.com
178.215.180.132 syigo.confirmcommunicationstatus.com
178.215.180.133 tnmi.confirmcommunicationstatus.com
178.215.180.134 axrwfon.confirmcommunicationstatus.com
178.215.180.135 khbzol.confirmcommunicationstatus.com
178.215.180.136 lfzrqrq.confirmcommunicationstatus.com
178.215.180.137 yer.confirmcommunicationstatus.com
178.215.180.138 sebu.confirmcommunicationstatus.com
178.215.180.139 ymbeapn.confirmcommunicationstatus.com
178.215.180.140 wojka.supportcommunicationstatus.com
178.215.180.141 vfnnw.supportcommunicationstatus.com
178.215.180.142 dveimx.supportcommunicationstatus.com
178.215.180.143 rywvxix.supportcommunicationstatus.com
178.215.180.144 imosidc.supportcommunicationstatus.com
178.215.180.145 dqpj.supportcommunicationstatus.com
178.215.180.146 cfjganp.supportcommunicationstatus.com
178.215.180.147 kqejm.supportcommunicationstatus.com
178.215.180.148 guw.supportcommunicationstatus.com
178.215.180.149 cjwvrz.supportcommunicationstatus.com
178.215.180.150 lcp.supportcommunicationstatus.com
178.215.180.151 mtcrcjr.supportcommunicationstatus.com
178.215.180.151 supportcommunicationstatus.com
178.215.180.152 yeao.supportcommunicationstatus.com
178.215.180.153 kaiqvf.supportcommunicationstatus.com
178.215.180.154 ypu.supportcommunicationstatus.com
178.215.180.155 gtss.supportcommunicationstatus.com
178.215.180.156 isi.supportcommunicationstatus.com
178.215.180.157 vadertd.supportcommunicationstatus.com
178.215.180.158 urf.supportcommunicationstatus.com
178.215.180.159 sownuu.supportcommunicationstatus.com
178.215.180.160 jogqi.supportcommunicationstatus.com
178.215.180.161 ieh.supportcommunicationstatus.com
178.215.180.162 niwnmbf.supportcommunicationstatus.com
178.215.180.163 ecbvhg.clearcommunicationstatus.com
178.215.180.164 wcbqw.clearcommunicationstatus.com
178.215.180.165 altqt.clearcommunicationstatus.com
178.215.180.166 zyaa.clearcommunicationstatus.com
178.215.180.167 ixzvy.clearcommunicationstatus.com
178.215.180.168 bchdyoj.clearcommunicationstatus.com
178.215.180.169 lmocj.clearcommunicationstatus.com
178.215.180.170 cvwtops.clearcommunicationstatus.com
178.215.180.171 ptzyq.clearcommunicationstatus.com
178.215.180.172 tpe.clearcommunicationstatus.com
178.215.180.173 slz.clearcommunicationstatus.com
178.215.180.174 aiem.clearcommunicationstatus.com
178.215.180.175 tof.clearcommunicationstatus.com
178.215.180.176 ras.clearcommunicationstatus.com
178.215.180.177 phdcxw.clearcommunicationstatus.com
178.215.180.178 wncpchl.clearcommunicationstatus.com
178.215.180.179 skm.clearcommunicationstatus.com
178.215.180.180 tqgp.clearcommunicationstatus.com
178.215.180.181 uuflvy.clearcommunicationstatus.com
178.215.180.182 kgz.clearcommunicationstatus.com
178.215.180.183 dvpzj.clearcommunicationstatus.com
178.215.180.184 clearcommunicationstatus.com
178.215.180.184 plzb.clearcommunicationstatus.com
178.215.180.185 smtmfk.clearcommunicationstatus.com
178.215.180.186 vump.approvalcommunicationstatus.com
178.215.180.187 yky.approvalcommunicationstatus.com
178.215.180.188 veti.approvalcommunicationstatus.com
178.215.180.189 pyhyqx.approvalcommunicationstatus.com
178.215.180.190 pyrhkk.approvalcommunicationstatus.com
178.215.180.191 qull.approvalcommunicationstatus.com
178.215.180.192 yboxm.approvalcommunicationstatus.com
178.215.180.193 rhqlq.approvalcommunicationstatus.com
178.215.180.194 bog.approvalcommunicationstatus.com
178.215.180.195 edk.approvalcommunicationstatus.com
178.215.180.196 bbbm.approvalcommunicationstatus.com
178.215.180.197 vdhho.approvalcommunicationstatus.com
178.215.180.198 fqk.approvalcommunicationstatus.com
178.215.180.199 cxvkoga.approvalcommunicationstatus.com
178.215.180.200 hotht.approvalcommunicationstatus.com
178.215.180.201 rny.approvalcommunicationstatus.com
178.215.180.202 plfk.approvalcommunicationstatus.com
178.215.180.203 mrdix.approvalcommunicationstatus.com
178.215.180.204 approvalcommunicationstatus.com
178.215.180.204 tbvr.approvalcommunicationstatus.com
178.215.180.205 tkunsn.approvalcommunicationstatus.com
178.215.180.206 jajcq.approvalcommunicationstatus.com
178.215.180.207 haiu.approvalcommunicationstatus.com
178.215.180.208 mcqf.approvalcommunicationstatus.com
178.215.180.209 rbn.performanceformula.net
178.215.180.210 htrnn.performanceformula.net
178.215.180.211 hauvldw.performanceformula.net
178.215.180.212 gmpo.performanceformula.net
178.215.180.213 yifkl.performanceformula.net
178.215.180.214 pho.performanceformula.net
178.215.180.215 vcxo.performanceformula.net
178.215.180.216 kcvs.performanceformula.net
178.215.180.217 pnotjiz.performanceformula.net
178.215.180.218 xnj.performanceformula.net
178.215.180.219 wof.performanceformula.net
178.215.180.220 lvpamk.performanceformula.net
178.215.180.221 jzwubrm.performanceformula.net
178.215.180.222 hasajaz.performanceformula.net
178.215.180.223 ynoukd.performanceformula.net
178.215.180.224 sovhphs.performanceformula.net
178.215.180.225 rrol.performanceformula.net
178.215.180.226 fyxn.performanceformula.net
178.215.180.227 pnh.performanceformula.net
178.215.180.228 nnpb.performanceformula.net
178.215.180.228 performanceformula.net
178.215.180.229 jlfketf.performanceformula.net
178.215.180.230 jneaf.performanceformula.net
178.215.180.231 oqp.performanceformula.net
178.215.180.232 pnhn.tricksolution.com
178.215.180.233 vvtiijk.tricksolution.com
178.215.180.234 tvpdaj.tricksolution.com
178.215.180.235 mswrsb.tricksolution.com
178.215.180.236 hsdch.tricksolution.com
178.215.180.237 kvtf.tricksolution.com
178.215.180.238 moyw.tricksolution.com
178.215.180.239 ipu.tricksolution.com
178.215.180.240 suh.tricksolution.com
178.215.180.241 hzyyral.tricksolution.com
178.215.180.242 tpc.tricksolution.com
178.215.180.243 fmwyrml.tricksolution.com
178.215.180.244 lheuxy.tricksolution.com
178.215.180.245 ptzr.tricksolution.com
178.215.180.246 tricksolution.com
178.215.180.246 yqyqrkq.tricksolution.com
178.215.180.247 zsmee.tricksolution.com
178.215.180.248 dwvocg.tricksolution.com
178.215.180.249 hbt.tricksolution.com
178.215.180.250 tjzsaa.tricksolution.com
178.215.180.251 ryhi.tricksolution.com
178.215.180.252 xtjpfo.tricksolution.com
178.215.180.253 nrqi.tricksolution.com
178.215.180.254 tpdaqw.tricksolution.com

178.218.252.2 mail.powerpointcontent.com
178.218.252.2 ns1.powerpointcontent.com
178.218.252.2 powerpointcontent.com
178.218.252.2 superjam.powerpointcontent.com
178.218.252.2 www.powerpointcontent.com
178.218.252.3 goodarm.powerpointcontent.com
178.218.252.3 ns2.powerpointcontent.com
178.218.252.4 flatboat.powerpointcontent.com
178.218.252.5 greencard.powerpointcontent.com
178.218.252.6 richart.powerpointcontent.com
178.218.252.7 slowwire.powerpointcontent.com
178.218.252.8 minigarden.powerpointcontent.com
178.218.252.9 fastfan.powerpointcontent.com
178.218.252.10 fragilebase.powerpointcontent.com
178.218.252.11 fiercebranch.powerpointcontent.com
178.218.252.12 widebean.powerpointcontent.com
178.218.252.13 broadnet.powerpointcontent.com
178.218.252.14 steepthrone.powerpointcontent.com
178.218.252.15 clearbook.powerpointcontent.com
178.218.252.16 graytruck.powerpointcontent.com
178.218.252.17 happymeal.powerpointcontent.com
178.218.252.18 mutemachine.powerpointcontent.com
178.218.252.19 heavenlyrabbit.powerpointcontent.com
178.218.252.20 earlysystem.powerpointcontent.com
178.218.252.21 roastedcollar.powerpointcontent.com
178.218.252.22 freshcity.powerpointcontent.com
178.218.252.23 oddguide.powerpointcontent.com
178.218.252.24 latewindow.powerpointcontent.com
178.218.252.25 detailcontent.com
178.218.252.25 mail.detailcontent.com
178.218.252.25 tidyhand.detailcontent.com
178.218.252.25 www.detailcontent.com
178.218.252.26 triplebasin.detailcontent.com
178.218.252.27 topsteel.detailcontent.com
178.218.252.28 nicerice.detailcontent.com
178.218.252.29 twinball.detailcontent.com
178.218.252.30 pleasantdust.detailcontent.com
178.218.252.31 savoryclock.detailcontent.com
178.218.252.32 cuteswing.detailcontent.com
178.218.252.33 lightair.detailcontent.com
178.218.252.34 oldworm.detailcontent.com
178.218.252.35 smoothbox.detailcontent.com
178.218.252.36 quietapple.detailcontent.com
178.218.252.37 alertowl.detailcontent.com
178.218.252.38 dryscarf.detailcontent.com
178.218.252.39 icycopy.detailcontent.com
178.218.252.40 leafyrock.detailcontent.com
178.218.252.41 shrillarea.detailcontent.com
178.218.252.42 browncellar.detailcontent.com
178.218.252.43 brightatom.detailcontent.com
178.218.252.44 friedgrape.detailcontent.com
178.218.252.45 realfeast.detailcontent.com
178.218.252.46 sadjam.detailcontent.com
178.218.252.47 superarm.detailcontent.com
178.218.252.48 goodboat.itemcontent.com
178.218.252.48 itemcontent.com
178.218.252.48 mail.itemcontent.com
178.218.252.48 www.itemcontent.com
178.218.252.49 flatcard.itemcontent.com
178.218.252.50 greenart.itemcontent.com
178.218.252.51 richwire.itemcontent.com
178.218.252.52 slowgarden.itemcontent.com
178.218.252.53 minifan.itemcontent.com
178.218.252.54 fastbase.itemcontent.com
178.218.252.55 fragilebranch.itemcontent.com
178.218.252.56 fiercebean.itemcontent.com
178.218.252.57 widenet.itemcontent.com
178.218.252.58 broadthrone.itemcontent.com
178.218.252.59 steepbook.itemcontent.com
178.218.252.60 cleartruck.itemcontent.com
178.218.252.61 graymeal.itemcontent.com
178.218.252.62 happymachine.itemcontent.com
178.218.252.63 muterabbit.itemcontent.com
178.218.252.64 heavenlysystem.itemcontent.com
178.218.252.65 earlycollar.itemcontent.com
178.218.252.66 roastedcity.itemcontent.com
178.218.252.67 freshguide.itemcontent.com
178.218.252.68 oddwindow.itemcontent.com
178.218.252.69 latehand.itemcontent.com
178.218.252.70 tidybasin.itemcontent.com
178.218.252.71 fullpointcontent.com
178.218.252.71 mail.fullpointcontent.com
178.218.252.71 triplesteel.fullpointcontent.com
178.218.252.71 www.fullpointcontent.com
178.218.252.72 toprice.fullpointcontent.com
178.218.252.73 niceball.fullpointcontent.com
178.218.252.74 twindust.fullpointcontent.com
178.218.252.75 pleasantclock.fullpointcontent.com
178.218.252.76 savoryswing.fullpointcontent.com
178.218.252.77 cuteair.fullpointcontent.com
178.218.252.78 lightworm.fullpointcontent.com
178.218.252.79 oldbox.fullpointcontent.com
178.218.252.80 smoothapple.fullpointcontent.com
178.218.252.81 quietowl.fullpointcontent.com
178.218.252.82 alertscarf.fullpointcontent.com
178.218.252.83 drycopy.fullpointcontent.com
178.218.252.84 icyrock.fullpointcontent.com
178.218.252.85 leafyarea.fullpointcontent.com
178.218.252.86 shrillcellar.fullpointcontent.com
178.218.252.87 brownatom.fullpointcontent.com
178.218.252.88 brightgrape.fullpointcontent.com
178.218.252.89 friedfeast.fullpointcontent.com
178.218.252.90 realjam.fullpointcontent.com
178.218.252.91 sadarm.fullpointcontent.com
178.218.252.92 superboat.fullpointcontent.com
178.218.252.93 goodcard.fullpointcontent.com
178.218.252.94 flatart.periodcontent.com
178.218.252.94 mail.periodcontent.com
178.218.252.94 periodcontent.com
178.218.252.94 www.periodcontent.com
178.218.252.95 greenwire.periodcontent.com
178.218.252.96 richgarden.periodcontent.com
178.218.252.97 slowfan.periodcontent.com
178.218.252.98 minibase.periodcontent.com
178.218.252.99 fastbranch.periodcontent.com
178.218.252.100 fragilebean.periodcontent.com
178.218.252.101 fiercenet.periodcontent.com
178.218.252.102 widethrone.periodcontent.com
178.218.252.103 broadbook.periodcontent.com
178.218.252.104 steeptruck.periodcontent.com
178.218.252.105 clearmeal.periodcontent.com
178.218.252.106 graymachine.periodcontent.com
178.218.252.107 happyrabbit.periodcontent.com
178.218.252.108 mutesystem.periodcontent.com
178.218.252.109 heavenlycollar.periodcontent.com
178.218.252.110 earlycity.periodcontent.com
178.218.252.111 roastedguide.periodcontent.com
178.218.252.112 freshwindow.periodcontent.com
178.218.252.113 oddhand.periodcontent.com
178.218.252.114 latebasin.periodcontent.com
178.218.252.115 tidysteel.periodcontent.com
178.218.252.116 triplerice.periodcontent.com
178.218.252.117 degreecontent.com
178.218.252.117 mail.degreecontent.com
178.218.252.117 topball.degreecontent.com
178.218.252.117 www.degreecontent.com
178.218.252.118 nicedust.degreecontent.com
178.218.252.119 twinclock.degreecontent.com
178.218.252.120 pleasantswing.degreecontent.com
178.218.252.121 savoryair.degreecontent.com
178.218.252.122 cuteworm.degreecontent.com
178.218.252.123 lightbox.degreecontent.com
178.218.252.124 oldapple.degreecontent.com
178.218.252.125 smoothowl.degreecontent.com
178.218.252.126 quietscarf.degreecontent.com
178.218.252.127 alertcopy.degreecontent.com
178.218.252.128 dryrock.degreecontent.com
178.218.252.129 icyarea.degreecontent.com
178.218.252.130 leafycellar.degreecontent.com
178.218.252.131 shrillatom.degreecontent.com
178.218.252.132 browngrape.degreecontent.com
178.218.252.133 brightfeast.degreecontent.com
178.218.252.134 friedjam.degreecontent.com
178.218.252.135 realarm.degreecontent.com
178.218.252.136 sadboat.degreecontent.com
178.218.252.137 supercard.degreecontent.com
178.218.252.138 goodart.degreecontent.com
178.218.252.139 flatwire.degreecontent.com
178.218.252.140 greengarden.stagecontent.com
178.218.252.140 mail.stagecontent.com
178.218.252.140 stagecontent.com
178.218.252.140 www.stagecontent.com
178.218.252.141 richfan.stagecontent.com
178.218.252.142 slowbase.stagecontent.com
178.218.252.143 minibranch.stagecontent.com
178.218.252.144 fastbean.stagecontent.com
178.218.252.145 fragilenet.stagecontent.com
178.218.252.146 fiercethrone.stagecontent.com
178.218.252.147 widebook.stagecontent.com
178.218.252.148 broadtruck.stagecontent.com
178.218.252.149 steepmeal.stagecontent.com
178.218.252.150 clearmachine.stagecontent.com
178.218.252.151 grayrabbit.stagecontent.com
178.218.252.152 happysystem.stagecontent.com
178.218.252.153 mutecollar.stagecontent.com
178.218.252.154 heavenlycity.stagecontent.com
178.218.252.155 earlyguide.stagecontent.com
178.218.252.156 roastedwindow.stagecontent.com
178.218.252.157 freshhand.stagecontent.com
178.218.252.158 oddbasin.stagecontent.com
178.218.252.159 latesteel.stagecontent.com
178.218.252.160 tidyrice.stagecontent.com
178.218.252.161 tripleball.stagecontent.com
178.218.252.162 topdust.stagecontent.com
178.218.252.163 mail.repointcontent.com
178.218.252.163 niceclock.repointcontent.com
178.218.252.163 repointcontent.com
178.218.252.163 www.repointcontent.com
178.218.252.164 twinswing.repointcontent.com
178.218.252.165 pleasantair.repointcontent.com
178.218.252.166 savoryworm.repointcontent.com
178.218.252.167 cutebox.repointcontent.com
178.218.252.168 lightapple.repointcontent.com
178.218.252.169 oldowl.repointcontent.com
178.218.252.170 smoothscarf.repointcontent.com
178.218.252.171 quietcopy.repointcontent.com
178.218.252.172 alertrock.repointcontent.com
178.218.252.173 dryarea.repointcontent.com
178.218.252.174 icycellar.repointcontent.com
178.218.252.175 leafyatom.repointcontent.com
178.218.252.176 shrillgrape.repointcontent.com
178.218.252.177 brownfeast.repointcontent.com
178.218.252.178 brightjam.repointcontent.com
178.218.252.179 friedarm.repointcontent.com
178.218.252.180 realboat.repointcontent.com
178.218.252.181 sadcard.repointcontent.com
178.218.252.182 superart.repointcontent.com
178.218.252.183 goodwire.repointcontent.com
178.218.252.184 flatgarden.repointcontent.com
178.218.252.185 greenfan.repointcontent.com
178.218.252.186 mail.signalcontent.net
178.218.252.186 richbase.signalcontent.net
178.218.252.186 signalcontent.net
178.218.252.186 www.signalcontent.net
178.218.252.187 slowbranch.signalcontent.net
178.218.252.188 minibean.signalcontent.net
178.218.252.189 fastnet.signalcontent.net
178.218.252.190 fragilethrone.signalcontent.net
178.218.252.191 fiercebook.signalcontent.net
178.218.252.192 widetruck.signalcontent.net
178.218.252.193 broadmeal.signalcontent.net
178.218.252.194 steepmachine.signalcontent.net
178.218.252.195 clearrabbit.signalcontent.net
178.218.252.196 graysystem.signalcontent.net
178.218.252.197 happycollar.signalcontent.net
178.218.252.198 mutecity.signalcontent.net
178.218.252.199 heavenlyguide.signalcontent.net
178.218.252.200 earlywindow.signalcontent.net
178.218.252.201 roastedhand.signalcontent.net
178.218.252.202 freshbasin.signalcontent.net
178.218.252.203 oddsteel.signalcontent.net
178.218.252.204 laterice.signalcontent.net
178.218.252.205 tidyball.signalcontent.net
178.218.252.206 tripledust.signalcontent.net
178.218.252.207 topclock.signalcontent.net
178.218.252.208 niceswing.signalcontent.net
178.218.252.209 indicatecontent.com
178.218.252.209 mail.indicatecontent.com
178.218.252.209 twinair.indicatecontent.com
178.218.252.209 www.indicatecontent.com
178.218.252.210 pleasantworm.indicatecontent.com
178.218.252.211 savorybox.indicatecontent.com
178.218.252.212 cuteapple.indicatecontent.com
178.218.252.213 lightowl.indicatecontent.com
178.218.252.214 oldscarf.indicatecontent.com
178.218.252.215 smoothcopy.indicatecontent.com
178.218.252.216 quietrock.indicatecontent.com
178.218.252.217 alertarea.indicatecontent.com
178.218.252.218 drycellar.indicatecontent.com
178.218.252.219 icyatom.indicatecontent.com
178.218.252.220 leafygrape.indicatecontent.com
178.218.252.221 shrillfeast.indicatecontent.com
178.218.252.222 brownjam.indicatecontent.com
178.218.252.223 brightarm.indicatecontent.com
178.218.252.224 friedboat.indicatecontent.com
178.218.252.225 realcard.indicatecontent.com
178.218.252.226 sadart.indicatecontent.com
178.218.252.227 superwire.indicatecontent.com
178.218.252.228 goodgarden.indicatecontent.com
178.218.252.229 flatfan.indicatecontent.com
178.218.252.230 greenbase.indicatecontent.com
178.218.252.231 richbranch.indicatecontent.com
178.218.252.232 mail.showcontent.net
178.218.252.232 showcontent.net
178.218.252.232 slowbean.showcontent.net
178.218.252.232 www.showcontent.net
178.218.252.233 mininet.showcontent.net
178.218.252.234 fastthrone.showcontent.net
178.218.252.235 fragilebook.showcontent.net
178.218.252.236 fiercetruck.showcontent.net
178.218.252.237 widemeal.showcontent.net
178.218.252.238 broadmachine.showcontent.net
178.218.252.239 steeprabbit.showcontent.net
178.218.252.240 clearsystem.showcontent.net
178.218.252.241 graycollar.showcontent.net
178.218.252.242 happycity.showcontent.net
178.218.252.243 muteguide.showcontent.net
178.218.252.244 heavenlywindow.showcontent.net
178.218.252.245 earlyhand.showcontent.net
178.218.252.246 roastedbasin.showcontent.net
178.218.252.247 freshsteel.showcontent.net
178.218.252.248 oddrice.showcontent.net
178.218.252.249 lateball.showcontent.net
178.218.252.250 tidydust.showcontent.net
178.218.252.251 tripleclock.showcontent.net
178.218.252.252 topswing.showcontent.net
178.218.252.253 niceair.showcontent.net
178.218.252.254 twinworm.showcontent.net
178.218.253.2 fierceball.guidecontent.net
178.218.253.2 guidecontent.net
178.218.253.2 mail.guidecontent.net
178.218.253.2 ns1.guidecontent.net
178.218.253.2 www.guidecontent.net
178.218.253.3 mutemeal.guidecontent.net
178.218.253.3 ns2.guidecontent.net
178.218.253.4 alertrabbit.guidecontent.net
178.218.253.5 drydust.guidecontent.net
178.218.253.6 smoothcity.guidecontent.net
178.218.253.7 oddclock.guidecontent.net
178.218.253.8 slowarm.guidecontent.net
178.218.253.9 topapple.guidecontent.net
178.218.253.10 fastboat.guidecontent.net
178.218.253.11 savorycellar.guidecontent.net
178.218.253.12 brightbean.guidecontent.net
178.218.253.13 broadhand.guidecontent.net
178.218.253.14 tripleart.guidecontent.net
178.218.253.15 earlywindow.guidecontent.net
178.218.253.16 tidysteel.guidecontent.net
178.218.253.17 cutesystem.guidecontent.net
178.218.253.18 lightbook.guidecontent.net
178.218.253.19 flatfan.guidecontent.net
178.218.253.20 richgarden.guidecontent.net
178.218.253.21 oldgrape.guidecontent.net
178.218.253.22 icyscarf.guidecontent.net
178.218.253.23 graycopy.guidecontent.net
178.218.253.24 quietworm.guidecontent.net
178.218.253.25 mail.namecontent.net
178.218.253.25 namecontent.net
178.218.253.25 pleasantbase.namecontent.net
178.218.253.25 www.namecontent.net
178.218.253.26 goodswing.namecontent.net
178.218.253.27 clearair.namecontent.net
178.218.253.28 roastedthrone.namecontent.net
178.218.253.29 widemachine.namecontent.net
178.218.253.30 heavenlyowl.namecontent.net
178.218.253.31 greenatom.namecontent.net
178.218.253.32 friedbasin.namecontent.net
178.218.253.33 sadcollar.namecontent.net
178.218.253.34 latebranch.namecontent.net
178.218.253.35 realnet.namecontent.net
178.218.253.36 steeprice.namecontent.net
178.218.253.37 twinjam.namecontent.net
178.218.253.38 freshcard.namecontent.net
178.218.253.39 happyarea.namecontent.net
178.218.253.40 brownbox.namecontent.net
178.218.253.41 superfeast.namecontent.net
178.218.253.42 fragiletruck.namecontent.net
178.218.253.43 nicerock.namecontent.net
178.218.253.44 shrillguide.namecontent.net
178.218.253.45 miniwire.namecontent.net
178.218.253.46 leafyball.namecontent.net
178.218.253.47 fiercemeal.namecontent.net
178.218.253.48 contactcontent.net
178.218.253.48 mail.contactcontent.net
178.218.253.48 muterabbit.contactcontent.net
178.218.253.48 www.contactcontent.net
178.218.253.49 alertdust.contactcontent.net
178.218.253.50 drycity.contactcontent.net
178.218.253.51 smoothclock.contactcontent.net
178.218.253.52 oddarm.contactcontent.net
178.218.253.53 slowapple.contactcontent.net
178.218.253.54 topboat.contactcontent.net
178.218.253.55 fastcellar.contactcontent.net
178.218.253.56 savorybean.contactcontent.net
178.218.253.57 brighthand.contactcontent.net
178.218.253.58 broadart.contactcontent.net
178.218.253.59 triplewindow.contactcontent.net
178.218.253.60 earlysteel.contactcontent.net
178.218.253.61 tidysystem.contactcontent.net
178.218.253.62 cutebook.contactcontent.net
178.218.253.63 lightfan.contactcontent.net
178.218.253.64 flatgarden.contactcontent.net
178.218.253.65 richgrape.contactcontent.net
178.218.253.66 oldscarf.contactcontent.net
178.218.253.67 icycopy.contactcontent.net
178.218.253.68 grayworm.contactcontent.net
178.218.253.69 quietbase.contactcontent.net
178.218.253.70 pleasantswing.contactcontent.net
178.218.253.71 goodair.steercontent.com
178.218.253.71 mail.steercontent.com
178.218.253.71 steercontent.com
178.218.253.71 www.steercontent.com
178.218.253.72 clearthrone.steercontent.com
178.218.253.73 roastedmachine.steercontent.com
178.218.253.74 wideowl.steercontent.com
178.218.253.75 heavenlyatom.steercontent.com
178.218.253.76 greenbasin.steercontent.com
178.218.253.77 friedcollar.steercontent.com
178.218.253.78 sadbranch.steercontent.com
178.218.253.79 latenet.steercontent.com
178.218.253.80 realrice.steercontent.com
178.218.253.81 steepjam.steercontent.com
178.218.253.82 twincard.steercontent.com
178.218.253.83 fresharea.steercontent.com
178.218.253.84 happybox.steercontent.com
178.218.253.85 brownfeast.steercontent.com
178.218.253.86 supertruck.steercontent.com
178.218.253.87 fragilerock.steercontent.com
178.218.253.88 niceguide.steercontent.com
178.218.253.89 shrillwire.steercontent.com
178.218.253.90 miniball.steercontent.com
178.218.253.91 leafymeal.steercontent.com
178.218.253.92 fiercerabbit.steercontent.com
178.218.253.93 mutedust.steercontent.com
178.218.253.94 alertcity.orientcontent.com
178.218.253.94 mail.orientcontent.com
178.218.253.94 orientcontent.com
178.218.253.94 www.orientcontent.com
178.218.253.95 dryclock.orientcontent.com
178.218.253.96 smootharm.orientcontent.com
178.218.253.97 oddapple.orientcontent.com
178.218.253.98 slowboat.orientcontent.com
178.218.253.99 topcellar.orientcontent.com
178.218.253.100 fastbean.orientcontent.com
178.218.253.101 savoryhand.orientcontent.com
178.218.253.102 brightart.orientcontent.com
178.218.253.103 broadwindow.orientcontent.com
178.218.253.104 triplesteel.orientcontent.com
178.218.253.105 earlysystem.orientcontent.com
178.218.253.106 tidybook.orientcontent.com
178.218.253.107 cutefan.orientcontent.com
178.218.253.108 lightgarden.orientcontent.com
178.218.253.109 flatgrape.orientcontent.com
178.218.253.110 richscarf.orientcontent.com
178.218.253.111 oldcopy.orientcontent.com
178.218.253.112 icyworm.orientcontent.com
178.218.253.113 graybase.orientcontent.com
178.218.253.114 quietswing.orientcontent.com
178.218.253.115 pleasantair.orientcontent.com
178.218.253.116 goodthrone.orientcontent.com
178.218.253.117 clearmachine.endcontent.com
178.218.253.117 endcontent.com
178.218.253.117 mail.endcontent.com
178.218.253.117 www.endcontent.com
178.218.253.118 roastedowl.endcontent.com
178.218.253.119 wideatom.endcontent.com
178.218.253.120 heavenlybasin.endcontent.com
178.218.253.121 greencollar.endcontent.com
178.218.253.122 friedbranch.endcontent.com
178.218.253.123 sadnet.endcontent.com
178.218.253.124 laterice.endcontent.com
178.218.253.125 realjam.endcontent.com
178.218.253.126 steepcard.endcontent.com
178.218.253.127 twinarea.endcontent.com
178.218.253.128 freshbox.endcontent.com
178.218.253.129 happyfeast.endcontent.com
178.218.253.130 browntruck.endcontent.com
178.218.253.131 superrock.endcontent.com
178.218.253.132 fragileguide.endcontent.com
178.218.253.133 nicewire.endcontent.com
178.218.253.134 shrillball.endcontent.com
178.218.253.135 minimeal.endcontent.com
178.218.253.136 leafyrabbit.endcontent.com
178.218.253.137 fiercedust.endcontent.com
178.218.253.138 mutecity.endcontent.com
178.218.253.139 alertclock.endcontent.com
178.218.253.140 dryarm.sharpencontent.com
178.218.253.140 mail.sharpencontent.com
178.218.253.140 sharpencontent.com
178.218.253.140 www.sharpencontent.com
178.218.253.141 smoothapple.sharpencontent.com
178.218.253.142 oddboat.sharpencontent.com
178.218.253.143 slowcellar.sharpencontent.com
178.218.253.144 topbean.sharpencontent.com
178.218.253.145 fasthand.sharpencontent.com
178.218.253.146 savoryart.sharpencontent.com
178.218.253.147 brightwindow.sharpencontent.com
178.218.253.148 broadsteel.sharpencontent.com
178.218.253.149 triplesystem.sharpencontent.com
178.218.253.150 earlybook.sharpencontent.com
178.218.253.151 tidyfan.sharpencontent.com
178.218.253.152 cutegarden.sharpencontent.com
178.218.253.153 lightgrape.sharpencontent.com
178.218.253.154 flatscarf.sharpencontent.com
178.218.253.155 richcopy.sharpencontent.com
178.218.253.156 oldworm.sharpencontent.com
178.218.253.157 icybase.sharpencontent.com
178.218.253.158 grayswing.sharpencontent.com
178.218.253.159 quietair.sharpencontent.com
178.218.253.160 pleasantthrone.sharpencontent.com
178.218.253.161 goodmachine.sharpencontent.com
178.218.253.162 clearowl.sharpencontent.com
178.218.253.163 mail.outletcontent.com
178.218.253.163 outletcontent.com
178.218.253.163 roastedatom.outletcontent.com
178.218.253.163 www.outletcontent.com
178.218.253.164 widebasin.outletcontent.com
178.218.253.165 heavenlycollar.outletcontent.com
178.218.253.166 greenbranch.outletcontent.com
178.218.253.167 friednet.outletcontent.com
178.218.253.168 sadrice.outletcontent.com
178.218.253.169 latejam.outletcontent.com
178.218.253.170 realcard.outletcontent.com
178.218.253.171 steeparea.outletcontent.com
178.218.253.172 twinbox.outletcontent.com
178.218.253.173 freshfeast.outletcontent.com
178.218.253.174 happytruck.outletcontent.com
178.218.253.175 brownrock.outletcontent.com
178.218.253.176 superguide.outletcontent.com
178.218.253.177 fragilewire.outletcontent.com
178.218.253.178 niceball.outletcontent.com
178.218.253.179 shrillmeal.outletcontent.com
178.218.253.180 minirabbit.outletcontent.com
178.218.253.181 leafydust.outletcontent.com
178.218.253.182 fiercecity.outletcontent.com
178.218.253.183 muteclock.outletcontent.com
178.218.253.184 alertarm.outletcontent.com
178.218.253.185 dryapple.outletcontent.com
178.218.253.186 factcontent.com
178.218.253.186 mail.factcontent.com
178.218.253.186 smoothboat.factcontent.com
178.218.253.186 www.factcontent.com
178.218.253.187 oddcellar.factcontent.com
178.218.253.188 slowbean.factcontent.com
178.218.253.189 tophand.factcontent.com
178.218.253.190 fastart.factcontent.com
178.218.253.191 savorywindow.factcontent.com
178.218.253.192 brightsteel.factcontent.com
178.218.253.193 broadsystem.factcontent.com
178.218.253.194 triplebook.factcontent.com
178.218.253.195 earlyfan.factcontent.com
178.218.253.196 tidygarden.factcontent.com
178.218.253.197 cutegrape.factcontent.com
178.218.253.198 lightscarf.factcontent.com
178.218.253.199 flatcopy.factcontent.com
178.218.253.200 richworm.factcontent.com
178.218.253.201 oldbase.factcontent.com
178.218.253.202 icyswing.factcontent.com
178.218.253.203 grayair.factcontent.com
178.218.253.204 quietthrone.factcontent.com
178.218.253.205 pleasantmachine.factcontent.com
178.218.253.206 goodowl.factcontent.com
178.218.253.207 clearatom.factcontent.com
178.218.253.208 roastedbasin.factcontent.com
178.218.253.209 mail.recitecontent.com
178.218.253.209 recitecontent.com
178.218.253.209 widecollar.recitecontent.com
178.218.253.209 www.recitecontent.com
178.218.253.210 heavenlybranch.recitecontent.com
178.218.253.211 greennet.recitecontent.com
178.218.253.212 friedrice.recitecontent.com
178.218.253.213 sadjam.recitecontent.com
178.218.253.214 latecard.recitecontent.com
178.218.253.215 realarea.recitecontent.com
178.218.253.216 steepbox.recitecontent.com
178.218.253.217 twinfeast.recitecontent.com
178.218.253.218 freshtruck.recitecontent.com
178.218.253.219 happyrock.recitecontent.com
178.218.253.220 brownguide.recitecontent.com
178.218.253.221 superwire.recitecontent.com
178.218.253.222 fragileball.recitecontent.com
178.218.253.223 nicemeal.recitecontent.com
178.218.253.224 shrillrabbit.recitecontent.com
178.218.253.225 minidust.recitecontent.com
178.218.253.226 leafycity.recitecontent.com
178.218.253.227 fierceclock.recitecontent.com
178.218.253.228 mutearm.recitecontent.com
178.218.253.229 alertapple.recitecontent.com
178.218.253.230 dryboat.recitecontent.com
178.218.253.231 smoothcellar.recitecontent.com
178.218.253.232 mail.regardcontent.com
178.218.253.232 oddbean.regardcontent.com
178.218.253.232 regardcontent.com
178.218.253.232 www.regardcontent.com
178.218.253.233 slowhand.regardcontent.com
178.218.253.234 topart.regardcontent.com
178.218.253.235 fastwindow.regardcontent.com
178.218.253.236 savorysteel.regardcontent.com
178.218.253.237 brightsystem.regardcontent.com
178.218.253.238 broadbook.regardcontent.com
178.218.253.239 triplefan.regardcontent.com
178.218.253.240 earlygarden.regardcontent.com
178.218.253.241 tidygrape.regardcontent.com
178.218.253.242 cutescarf.regardcontent.com
178.218.253.243 lightcopy.regardcontent.com
178.218.253.244 flatworm.regardcontent.com
178.218.253.245 richbase.regardcontent.com
178.218.253.246 oldswing.regardcontent.com
178.218.253.247 icyair.regardcontent.com
178.218.253.248 graythrone.regardcontent.com
178.218.253.249 quietmachine.regardcontent.com
178.218.253.250 pleasantowl.regardcontent.com
178.218.253.251 goodatom.regardcontent.com
178.218.253.252 clearbasin.regardcontent.com
178.218.253.253 roastedcollar.regardcontent.com
178.218.253.254 widebranch.regardcontent.com
178.218.254.2 fastclock.objectcontent.com
178.218.254.2 mail.objectcontent.com
178.218.254.2 ns1.objectcontent.com
178.218.254.2 objectcontent.com
178.218.254.2 www.objectcontent.com
178.218.254.3 grayapple.objectcontent.com
178.218.254.3 ns2.objectcontent.com
178.218.254.4 cutescarf.objectcontent.com
178.218.254.5 realbean.objectcontent.com
178.218.254.6 broadthrone.objectcontent.com
178.218.254.7 alertbase.objectcontent.com
178.218.254.8 twinbranch.objectcontent.com
178.218.254.9 mutearm.objectcontent.com
178.218.254.10 flatbox.objectcontent.com
178.218.254.11 supermeal.objectcontent.com
178.218.254.12 latemachine.objectcontent.com
178.218.254.13 heavenlyowl.objectcontent.com
178.218.254.14 greenair.objectcontent.com
178.218.254.15 lightboat.objectcontent.com
178.218.254.16 wideworm.objectcontent.com
178.218.254.17 roastedarea.objectcontent.com
178.218.254.18 happycellar.objectcontent.com
178.218.254.19 brightgrape.objectcontent.com
178.218.254.20 fiercehand.objectcontent.com
178.218.254.21 triplegarden.objectcontent.com
178.218.254.22 nicenet.objectcontent.com
178.218.254.23 drywire.objectcontent.com
178.218.254.24 oldfan.objectcontent.com
178.218.254.25 mail.targetcontent.net
178.218.254.25 richcard.targetcontent.net
178.218.254.25 targetcontent.net
178.218.254.25 www.targetcontent.net
178.218.254.26 saddust.targetcontent.net
178.218.254.27 steepatom.targetcontent.net
178.218.254.28 friedsteel.targetcontent.net
178.218.254.29 minisystem.targetcontent.net
178.218.254.30 pleasantwindow.targetcontent.net
178.218.254.31 tidyart.targetcontent.net
178.218.254.32 leafycity.targetcontent.net
178.218.254.33 oddcollar.targetcontent.net
178.218.254.34 freshguide.targetcontent.net
178.218.254.35 savoryfeast.targetcontent.net
178.218.254.36 fragilebasin.targetcontent.net
178.218.254.37 toprock.targetcontent.net
178.218.254.38 shrilltruck.targetcontent.net
178.218.254.39 quietswing.targetcontent.net
178.218.254.40 clearjam.targetcontent.net
178.218.254.41 smoothball.targetcontent.net
178.218.254.42 slowbook.targetcontent.net
178.218.254.43 earlyrice.targetcontent.net
178.218.254.44 goodcopy.targetcontent.net
178.218.254.45 icyrabbit.targetcontent.net
178.218.254.46 brownclock.targetcontent.net
178.218.254.47 fastapple.targetcontent.net
178.218.254.48 grayscarf.portioncontent.com
178.218.254.48 mail.portioncontent.com
178.218.254.48 portioncontent.com
178.218.254.48 www.portioncontent.com
178.218.254.49 cutebean.portioncontent.com
178.218.254.50 realthrone.portioncontent.com
178.218.254.51 broadbase.portioncontent.com
178.218.254.52 alertbranch.portioncontent.com
178.218.254.53 twinarm.portioncontent.com
178.218.254.54 mutebox.portioncontent.com
178.218.254.55 flatmeal.portioncontent.com
178.218.254.56 supermachine.portioncontent.com
178.218.254.57 lateowl.portioncontent.com
178.218.254.58 heavenlyair.portioncontent.com
178.218.254.59 greenboat.portioncontent.com
178.218.254.60 lightworm.portioncontent.com
178.218.254.61 widearea.portioncontent.com
178.218.254.62 roastedcellar.portioncontent.com
178.218.254.63 happygrape.portioncontent.com
178.218.254.64 brighthand.portioncontent.com
178.218.254.65 fiercegarden.portioncontent.com
178.218.254.66 triplenet.portioncontent.com
178.218.254.67 nicewire.portioncontent.com
178.218.254.68 dryfan.portioncontent.com
178.218.254.69 oldcard.portioncontent.com
178.218.254.70 richdust.portioncontent.com
178.218.254.71 mail.positioncontent.net
178.218.254.71 positioncontent.net
178.218.254.71 sadatom.positioncontent.net
178.218.254.71 www.positioncontent.net
178.218.254.72 steepsteel.positioncontent.net
178.218.254.73 friedsystem.positioncontent.net
178.218.254.74 miniwindow.positioncontent.net
178.218.254.75 pleasantart.positioncontent.net
178.218.254.76 tidycity.positioncontent.net
178.218.254.77 leafycollar.positioncontent.net
178.218.254.78 oddguide.positioncontent.net
178.218.254.79 freshfeast.positioncontent.net
178.218.254.80 savorybasin.positioncontent.net
178.218.254.81 fragilerock.positioncontent.net
178.218.254.82 toptruck.positioncontent.net
178.218.254.83 shrillswing.positioncontent.net
178.218.254.84 quietjam.positioncontent.net
178.218.254.85 clearball.positioncontent.net
178.218.254.86 smoothbook.positioncontent.net
178.218.254.87 slowrice.positioncontent.net
178.218.254.88 earlycopy.positioncontent.net
178.218.254.89 goodrabbit.positioncontent.net
178.218.254.90 icyclock.positioncontent.net
178.218.254.91 brownapple.positioncontent.net
178.218.254.92 fastscarf.positioncontent.net
178.218.254.93 graybean.positioncontent.net
178.218.254.94 cutethrone.importcontent.com
178.218.254.94 importcontent.com
178.218.254.94 mail.importcontent.com
178.218.254.94 www.importcontent.com
178.218.254.95 realbase.importcontent.com
178.218.254.96 broadbranch.importcontent.com
178.218.254.97 alertarm.importcontent.com
178.218.254.98 twinbox.importcontent.com
178.218.254.99 mutemeal.importcontent.com
178.218.254.100 flatmachine.importcontent.com
178.218.254.101 superowl.importcontent.com
178.218.254.102 lateair.importcontent.com
178.218.254.103 heavenlyboat.importcontent.com
178.218.254.104 greenworm.importcontent.com
178.218.254.105 lightarea.importcontent.com
178.218.254.106 widecellar.importcontent.com
178.218.254.107 roastedgrape.importcontent.com
178.218.254.108 happyhand.importcontent.com
178.218.254.109 brightgarden.importcontent.com
178.218.254.110 fiercenet.importcontent.com
178.218.254.111 triplewire.importcontent.com
178.218.254.112 nicefan.importcontent.com
178.218.254.113 drycard.importcontent.com
178.218.254.114 olddust.importcontent.com
178.218.254.115 richatom.importcontent.com
178.218.254.116 sadsteel.importcontent.com
178.218.254.117 mail.markcontent.com
178.218.254.117 markcontent.com
178.218.254.117 steepsystem.markcontent.com
178.218.254.117 www.markcontent.com
178.218.254.118 friedwindow.markcontent.com
178.218.254.119 miniart.markcontent.com
178.218.254.120 pleasantcity.markcontent.com
178.218.254.121 tidycollar.markcontent.com
178.218.254.122 leafyguide.markcontent.com
178.218.254.123 oddfeast.markcontent.com
178.218.254.124 freshbasin.markcontent.com
178.218.254.125 savoryrock.markcontent.com
178.218.254.126 fragiletruck.markcontent.com
178.218.254.127 topswing.markcontent.com
178.218.254.128 shrilljam.markcontent.com
178.218.254.129 quietball.markcontent.com
178.218.254.130 clearbook.markcontent.com
178.218.254.131 smoothrice.markcontent.com
178.218.254.132 slowcopy.markcontent.com
178.218.254.133 earlyrabbit.markcontent.com
178.218.254.134 goodclock.markcontent.com
178.218.254.135 icyapple.markcontent.com
178.218.254.136 brownscarf.markcontent.com
178.218.254.137 fastbean.markcontent.com
178.218.254.138 graythrone.markcontent.com
178.218.254.139 cutebase.markcontent.com
178.218.254.140 locationcontent.net
178.218.254.140 mail.locationcontent.net
178.218.254.140 realbranch.locationcontent.net
178.218.254.140 www.locationcontent.net
178.218.254.141 broadarm.locationcontent.net
178.218.254.142 alertbox.locationcontent.net
178.218.254.143 twinmeal.locationcontent.net
178.218.254.144 mutemachine.locationcontent.net
178.218.254.145 flatowl.locationcontent.net
178.218.254.146 superair.locationcontent.net
178.218.254.147 lateboat.locationcontent.net
178.218.254.148 heavenlyworm.locationcontent.net
178.218.254.149 greenarea.locationcontent.net
178.218.254.150 lightcellar.locationcontent.net
178.218.254.151 widegrape.locationcontent.net
178.218.254.152 roastedhand.locationcontent.net
178.218.254.153 happygarden.locationcontent.net
178.218.254.154 brightnet.locationcontent.net
178.218.254.155 fiercewire.locationcontent.net
178.218.254.156 triplefan.locationcontent.net
178.218.254.157 nicecard.locationcontent.net
178.218.254.158 drydust.locationcontent.net
178.218.254.159 oldatom.locationcontent.net
178.218.254.160 richsteel.locationcontent.net
178.218.254.161 sadsystem.locationcontent.net
178.218.254.162 steepwindow.locationcontent.net
178.218.254.163 friedart.rootcontent.com
178.218.254.163 mail.rootcontent.com
178.218.254.163 rootcontent.com
178.218.254.163 www.rootcontent.com
178.218.254.164 minicity.rootcontent.com
178.218.254.165 pleasantcollar.rootcontent.com
178.218.254.166 tidyguide.rootcontent.com
178.218.254.167 leafyfeast.rootcontent.com
178.218.254.168 oddbasin.rootcontent.com
178.218.254.169 freshrock.rootcontent.com
178.218.254.170 savorytruck.rootcontent.com
178.218.254.171 fragileswing.rootcontent.com
178.218.254.172 topjam.rootcontent.com
178.218.254.173 shrillball.rootcontent.com
178.218.254.174 quietbook.rootcontent.com
178.218.254.175 clearrice.rootcontent.com
178.218.254.176 smoothcopy.rootcontent.com
178.218.254.177 slowrabbit.rootcontent.com
178.218.254.178 earlyclock.rootcontent.com
178.218.254.179 goodapple.rootcontent.com
178.218.254.180 icyscarf.rootcontent.com
178.218.254.181 brownbean.rootcontent.com
178.218.254.182 fastthrone.rootcontent.com
178.218.254.183 graybase.rootcontent.com
178.218.254.184 cutebranch.rootcontent.com
178.218.254.185 realarm.rootcontent.com
178.218.254.186 broadbox.sourcecontent.net
178.218.254.186 mail.sourcecontent.net
178.218.254.186 sourcecontent.net
178.218.254.186 www.sourcecontent.net
178.218.254.187 alertmeal.sourcecontent.net
178.218.254.188 twinmachine.sourcecontent.net
178.218.254.189 muteowl.sourcecontent.net
178.218.254.190 flatair.sourcecontent.net
178.218.254.191 superboat.sourcecontent.net
178.218.254.192 lateworm.sourcecontent.net
178.218.254.193 heavenlyarea.sourcecontent.net
178.218.254.194 greencellar.sourcecontent.net
178.218.254.195 lightgrape.sourcecontent.net
178.218.254.196 widehand.sourcecontent.net
178.218.254.197 roastedgarden.sourcecontent.net
178.218.254.198 happynet.sourcecontent.net
178.218.254.199 brightwire.sourcecontent.net
178.218.254.200 fiercefan.sourcecontent.net
178.218.254.201 triplecard.sourcecontent.net
178.218.254.202 nicedust.sourcecontent.net
178.218.254.203 dryatom.sourcecontent.net
178.218.254.204 oldsteel.sourcecontent.net
178.218.254.205 richsystem.sourcecontent.net
178.218.254.206 sadwindow.sourcecontent.net
178.218.254.207 steepart.sourcecontent.net
178.218.254.208 friedcity.sourcecontent.net
178.218.254.209 centercontent.com
178.218.254.209 mail.centercontent.com
178.218.254.209 minicollar.centercontent.com
178.218.254.209 www.centercontent.com
178.218.254.210 pleasantguide.centercontent.com
178.218.254.211 tidyfeast.centercontent.com
178.218.254.212 leafybasin.centercontent.com
178.218.254.213 oddrock.centercontent.com
178.218.254.214 freshtruck.centercontent.com
178.218.254.215 savoryswing.centercontent.com
178.218.254.216 fragilejam.centercontent.com
178.218.254.217 topball.centercontent.com
178.218.254.218 shrillbook.centercontent.com
178.218.254.219 quietrice.centercontent.com
178.218.254.220 clearcopy.centercontent.com
178.218.254.221 smoothrabbit.centercontent.com
178.218.254.222 slowclock.centercontent.com
178.218.254.223 earlyapple.centercontent.com
178.218.254.224 goodscarf.centercontent.com
178.218.254.225 icybean.centercontent.com
178.218.254.226 brownthrone.centercontent.com
178.218.254.227 fastbase.centercontent.com
178.218.254.228 graybranch.centercontent.com
178.218.254.229 cutearm.centercontent.com
178.218.254.230 realbox.centercontent.com
178.218.254.231 broadmeal.centercontent.com
178.218.254.232 alertmachine.cornercontent.net
178.218.254.232 cornercontent.net
178.218.254.232 mail.cornercontent.net
178.218.254.232 www.cornercontent.net
178.218.254.233 twinowl.cornercontent.net
178.218.254.234 muteair.cornercontent.net
178.218.254.235 flatboat.cornercontent.net
178.218.254.236 superworm.cornercontent.net
178.218.254.237 latearea.cornercontent.net
178.218.254.238 heavenlycellar.cornercontent.net
178.218.254.239 greengrape.cornercontent.net
178.218.254.240 lighthand.cornercontent.net
178.218.254.241 widegarden.cornercontent.net
178.218.254.242 roastednet.cornercontent.net
178.218.254.243 happywire.cornercontent.net
178.218.254.244 brightfan.cornercontent.net
178.218.254.245 fiercecard.cornercontent.net
178.218.254.246 tripledust.cornercontent.net
178.218.254.247 niceatom.cornercontent.net
178.218.254.248 drysteel.cornercontent.net
178.218.254.249 oldsystem.cornercontent.net
178.218.254.250 richwindow.cornercontent.net
178.218.254.251 sadart.cornercontent.net
178.218.254.252 steepcity.cornercontent.net
178.218.254.253 friedcollar.cornercontent.net
178.218.254.254 miniguide.cornercontent.net
178.218.255.2 mail.summaryupdate.com
178.218.255.2 ns1.summaryupdate.com
178.218.255.2 oldgarden.summaryupdate.com
178.218.255.2 summaryupdate.com
178.218.255.2 www.summaryupdate.com
178.218.255.3 minimachine.summaryupdate.com
178.218.255.3 ns2.summaryupdate.com
178.218.255.4 topsteel.summaryupdate.com
178.218.255.5 niceball.summaryupdate.com
178.218.255.6 sadrabbit.summaryupdate.com
178.218.255.7 triplerice.summaryupdate.com
178.218.255.8 leafybook.summaryupdate.com
178.218.255.9 quietcopy.summaryupdate.com
178.218.255.10 dryair.summaryupdate.com
178.218.255.11 roasteddust.summaryupdate.com
178.218.255.12 oddjam.summaryupdate.com
178.218.255.13 twinbean.summaryupdate.com
178.218.255.14 broadrock.summaryupdate.com
178.218.255.15 heavenlyarm.summaryupdate.com
178.218.255.16 flatapple.summaryupdate.com
178.218.255.17 alertcity.summaryupdate.com
178.218.255.18 steepfeast.summaryupdate.com
178.218.255.19 icymeal.summaryupdate.com
178.218.255.20 pleasantboat.summaryupdate.com
178.218.255.21 latecellar.summaryupdate.com
178.218.255.22 brightart.summaryupdate.com
178.218.255.23 freshtruck.summaryupdate.com
178.218.255.24 goodowl.summaryupdate.com
178.218.255.25 greenbox.summarynotify.com
178.218.255.25 mail.summarynotify.com
178.218.255.25 summarynotify.com
178.218.255.25 www.summarynotify.com
178.218.255.26 superarea.summarynotify.com
178.218.255.27 brownbase.summarynotify.com
178.218.255.28 fastatom.summarynotify.com
178.218.255.29 friedbranch.summarynotify.com
178.218.255.30 realhand.summarynotify.com
178.218.255.31 fiercesystem.summarynotify.com
178.218.255.32 lightswing.summarynotify.com
178.218.255.33 clearcollar.summarynotify.com
178.218.255.34 slowwire.summarynotify.com
178.218.255.35 tidyclock.summarynotify.com
178.218.255.36 cutethrone.summarynotify.com
178.218.255.37 widefan.summarynotify.com
178.218.255.38 richworm.summarynotify.com
178.218.255.39 smoothgrape.summarynotify.com
178.218.255.40 shrillscarf.summarynotify.com
178.218.255.41 graynet.summarynotify.com
178.218.255.42 mutecard.summarynotify.com
178.218.255.43 happyguide.summarynotify.com
178.218.255.44 savorybasin.summarynotify.com
178.218.255.45 fragilewindow.summarynotify.com
178.218.255.46 earlygarden.summarynotify.com
178.218.255.47 oldmachine.summarynotify.com
178.218.255.48 mail.summarycue.com
178.218.255.48 ministeel.summarycue.com
178.218.255.48 summarycue.com
178.218.255.48 www.summarycue.com
178.218.255.49 topball.summarycue.com
178.218.255.50 nicerabbit.summarycue.com
178.218.255.51 sadrice.summarycue.com
178.218.255.52 triplebook.summarycue.com
178.218.255.53 leafycopy.summarycue.com
178.218.255.54 quietair.summarycue.com
178.218.255.55 drydust.summarycue.com
178.218.255.56 roastedjam.summarycue.com
178.218.255.57 oddbean.summarycue.com
178.218.255.58 twinrock.summarycue.com
178.218.255.59 broadarm.summarycue.com
178.218.255.60 heavenlyapple.summarycue.com
178.218.255.61 flatcity.summarycue.com
178.218.255.62 alertfeast.summarycue.com
178.218.255.63 steepmeal.summarycue.com
178.218.255.64 icyboat.summarycue.com
178.218.255.65 pleasantcellar.summarycue.com
178.218.255.66 lateart.summarycue.com
178.218.255.67 brighttruck.summarycue.com
178.218.255.68 freshowl.summarycue.com
178.218.255.69 goodbox.summarycue.com
178.218.255.70 greenarea.summarycue.com
178.218.255.71 mail.summaryprompt.com
178.218.255.71 summaryprompt.com
178.218.255.71 superbase.summaryprompt.com
178.218.255.71 www.summaryprompt.com
178.218.255.72 brownatom.summaryprompt.com
178.218.255.73 fastbranch.summaryprompt.com
178.218.255.74 friedhand.summaryprompt.com
178.218.255.75 realsystem.summaryprompt.com
178.218.255.76 fierceswing.summaryprompt.com
178.218.255.77 lightcollar.summaryprompt.com
178.218.255.78 clearwire.summaryprompt.com
178.218.255.79 slowclock.summaryprompt.com
178.218.255.80 tidythrone.summaryprompt.com
178.218.255.81 cutefan.summaryprompt.com
178.218.255.82 wideworm.summaryprompt.com
178.218.255.83 richgrape.summaryprompt.com
178.218.255.84 smoothscarf.summaryprompt.com
178.218.255.85 shrillnet.summaryprompt.com
178.218.255.86 graycard.summaryprompt.com
178.218.255.87 muteguide.summaryprompt.com
178.218.255.88 happybasin.summaryprompt.com
178.218.255.89 savorywindow.summaryprompt.com
178.218.255.90 fragilegarden.summaryprompt.com
178.218.255.91 earlymachine.summaryprompt.com
178.218.255.92 oldsteel.summaryprompt.com
178.218.255.93 miniball.summaryprompt.com
178.218.255.94 mail.summarypresent.com
178.218.255.94 summarypresent.com
178.218.255.94 toprabbit.summarypresent.com
178.218.255.94 www.summarypresent.com
178.218.255.95 nicerice.summarypresent.com
178.218.255.96 sadbook.summarypresent.com
178.218.255.97 triplecopy.summarypresent.com
178.218.255.98 leafyair.summarypresent.com
178.218.255.99 quietdust.summarypresent.com
178.218.255.100 dryjam.summarypresent.com
178.218.255.101 roastedbean.summarypresent.com
178.218.255.102 oddrock.summarypresent.com
178.218.255.103 twinarm.summarypresent.com
178.218.255.104 broadapple.summarypresent.com
178.218.255.105 heavenlycity.summarypresent.com
178.218.255.106 flatfeast.summarypresent.com
178.218.255.107 alertmeal.summarypresent.com
178.218.255.108 steepboat.summarypresent.com
178.218.255.109 icycellar.summarypresent.com
178.218.255.110 pleasantart.summarypresent.com
178.218.255.111 latetruck.summarypresent.com
178.218.255.112 brightowl.summarypresent.com
178.218.255.113 freshbox.summarypresent.com
178.218.255.114 goodarea.summarypresent.com
178.218.255.115 greenbase.summarypresent.com
178.218.255.116 superatom.summarypresent.com
178.218.255.117 brownbranch.summarypoint.net
178.218.255.117 mail.summarypoint.net
178.218.255.117 summarypoint.net
178.218.255.117 www.summarypoint.net
178.218.255.118 fasthand.summarypoint.net
178.218.255.119 friedsystem.summarypoint.net
178.218.255.120 realswing.summarypoint.net
178.218.255.121 fiercecollar.summarypoint.net
178.218.255.122 lightwire.summarypoint.net
178.218.255.123 clearclock.summarypoint.net
178.218.255.124 slowthrone.summarypoint.net
178.218.255.125 tidyfan.summarypoint.net
178.218.255.126 cuteworm.summarypoint.net
178.218.255.127 widegrape.summarypoint.net
178.218.255.128 richscarf.summarypoint.net
178.218.255.129 smoothnet.summarypoint.net
178.218.255.130 shrillcard.summarypoint.net
178.218.255.131 grayguide.summarypoint.net
178.218.255.132 mutebasin.summarypoint.net
178.218.255.133 happywindow.summarypoint.net
178.218.255.134 savorygarden.summarypoint.net
178.218.255.135 fragilemachine.summarypoint.net
178.218.255.136 earlysteel.summarypoint.net
178.218.255.137 oldball.summarypoint.net
178.218.255.138 minirabbit.summarypoint.net
178.218.255.139 toprice.summarypoint.net
178.218.255.140 mail.summaryaccount.com
178.218.255.140 nicebook.summaryaccount.com
178.218.255.140 summaryaccount.com
178.218.255.140 www.summaryaccount.com
178.218.255.141 sadcopy.summaryaccount.com
178.218.255.142 tripleair.summaryaccount.com
178.218.255.143 leafydust.summaryaccount.com
178.218.255.144 quietjam.summaryaccount.com
178.218.255.145 drybean.summaryaccount.com
178.218.255.146 roastedrock.summaryaccount.com
178.218.255.147 oddarm.summaryaccount.com
178.218.255.148 twinapple.summaryaccount.com
178.218.255.149 broadcity.summaryaccount.com
178.218.255.150 heavenlyfeast.summaryaccount.com
178.218.255.151 flatmeal.summaryaccount.com
178.218.255.152 alertboat.summaryaccount.com
178.218.255.153 steepcellar.summaryaccount.com
178.218.255.154 icyart.summaryaccount.com
178.218.255.155 pleasanttruck.summaryaccount.com
178.218.255.156 lateowl.summaryaccount.com
178.218.255.157 brightbox.summaryaccount.com
178.218.255.158 fresharea.summaryaccount.com
178.218.255.159 goodbase.summaryaccount.com
178.218.255.160 greenatom.summaryaccount.com
178.218.255.161 superbranch.summaryaccount.com
178.218.255.162 brownhand.summaryaccount.com
178.218.255.163 fastsystem.summaryreport.net
178.218.255.163 mail.summaryreport.net
178.218.255.163 summaryreport.net
178.218.255.163 www.summaryreport.net
178.218.255.164 friedswing.summaryreport.net
178.218.255.165 realcollar.summaryreport.net
178.218.255.166 fiercewire.summaryreport.net
178.218.255.167 lightclock.summaryreport.net
178.218.255.168 clearthrone.summaryreport.net
178.218.255.169 slowfan.summaryreport.net
178.218.255.170 tidyworm.summaryreport.net
178.218.255.171 cutegrape.summaryreport.net
178.218.255.172 widescarf.summaryreport.net
178.218.255.173 richnet.summaryreport.net
178.218.255.174 smoothcard.summaryreport.net
178.218.255.175 shrillguide.summaryreport.net
178.218.255.176 graybasin.summaryreport.net
178.218.255.177 mutewindow.summaryreport.net
178.218.255.178 happygarden.summaryreport.net
178.218.255.179 savorymachine.summaryreport.net
178.218.255.180 fragilesteel.summaryreport.net
178.218.255.181 earlyball.summaryreport.net
178.218.255.182 oldrabbit.summaryreport.net
178.218.255.183 minirice.summaryreport.net
178.218.255.184 topbook.summaryreport.net
178.218.255.185 nicecopy.summaryreport.net
178.218.255.186 mail.summarycover.net
178.218.255.186 sadair.summarycover.net
178.218.255.186 summarycover.net
178.218.255.186 www.summarycover.net
178.218.255.187 tripledust.summarycover.net
178.218.255.188 leafyjam.summarycover.net
178.218.255.189 quietbean.summarycover.net
178.218.255.190 dryrock.summarycover.net
178.218.255.191 roastedarm.summarycover.net
178.218.255.192 oddapple.summarycover.net
178.218.255.193 twincity.summarycover.net
178.218.255.194 broadfeast.summarycover.net
178.218.255.195 heavenlymeal.summarycover.net
178.218.255.196 flatboat.summarycover.net
178.218.255.197 alertcellar.summarycover.net
178.218.255.198 steepart.summarycover.net
178.218.255.199 icytruck.summarycover.net
178.218.255.200 pleasantowl.summarycover.net
178.218.255.201 latebox.summarycover.net
178.218.255.202 brightarea.summarycover.net
178.218.255.203 freshbase.summarycover.net
178.218.255.204 goodatom.summarycover.net
178.218.255.205 greenbranch.summarycover.net
178.218.255.206 superhand.summarycover.net
178.218.255.207 brownsystem.summarycover.net
178.218.255.208 fastswing.summarycover.net
178.218.255.209 friedcollar.identifycontent.com
178.218.255.209 identifycontent.com
178.218.255.209 mail.identifycontent.com
178.218.255.209 www.identifycontent.com
178.218.255.210 realwire.identifycontent.com
178.218.255.211 fierceclock.identifycontent.com
178.218.255.212 lightthrone.identifycontent.com
178.218.255.213 clearfan.identifycontent.com
178.218.255.214 slowworm.identifycontent.com
178.218.255.215 tidygrape.identifycontent.com
178.218.255.216 cutescarf.identifycontent.com
178.218.255.217 widenet.identifycontent.com
178.218.255.218 richcard.identifycontent.com
178.218.255.219 smoothguide.identifycontent.com
178.218.255.220 shrillbasin.identifycontent.com
178.218.255.221 graywindow.identifycontent.com
178.218.255.222 mutegarden.identifycontent.com
178.218.255.223 happymachine.identifycontent.com
178.218.255.224 savorysteel.identifycontent.com
178.218.255.225 fragileball.identifycontent.com
178.218.255.226 earlyrabbit.identifycontent.com
178.218.255.227 oldrice.identifycontent.com
178.218.255.228 minibook.identifycontent.com
178.218.255.229 topcopy.identifycontent.com
178.218.255.230 niceair.identifycontent.com
178.218.255.231 saddust.identifycontent.com
178.218.255.232 mail.pointcontent.net
178.218.255.232 pointcontent.net
178.218.255.232 triplejam.pointcontent.net
178.218.255.232 www.pointcontent.net
178.218.255.233 leafybean.pointcontent.net
178.218.255.234 quietrock.pointcontent.net
178.218.255.235 dryarm.pointcontent.net
178.218.255.236 roastedapple.pointcontent.net
178.218.255.237 oddcity.pointcontent.net
178.218.255.238 twinfeast.pointcontent.net
178.218.255.239 broadmeal.pointcontent.net
178.218.255.240 heavenlyboat.pointcontent.net
178.218.255.241 flatcellar.pointcontent.net
178.218.255.242 alertart.pointcontent.net
178.218.255.243 steeptruck.pointcontent.net
178.218.255.244 icyowl.pointcontent.net
178.218.255.245 pleasantbox.pointcontent.net
178.218.255.246 latearea.pointcontent.net
178.218.255.247 brightbase.pointcontent.net
178.218.255.248 freshatom.pointcontent.net
178.218.255.249 goodbranch.pointcontent.net
178.218.255.250 greenhand.pointcontent.net
178.218.255.251 supersystem.pointcontent.net
178.218.255.252 brownswing.pointcontent.net
178.218.255.253 fastcollar.pointcontent.net
178.218.255.254 friedwire.pointcontent.net

89.248.173.73 topazapple.groovejunks.com
89.248.173.74 greenhop.groovejunks.com
89.248.173.75 goldyucca.groovejunks.com
89.248.173.75 groovejunks.com
89.248.173.76 bluepin.groovejunks.com
89.248.173.77 azurepin.groovejunks.com
89.248.173.78 yellowyucca.groovejunks.com
89.248.173.79 beigehop.groovejunks.com
89.248.173.80 apricotapple.ecmpowder.com
89.248.173.81 burnetaxe.ecmpowder.com
89.248.173.82 argentbean.ecmpowder.com
89.248.173.83 taupeweb.ecmpowder.com
89.248.173.84 silveryucca.ecmpowder.com
89.248.173.85 plumtop.ecmpowder.com
89.248.173.86 orangeyew.ecmpowder.com
89.248.173.87 ecmpowder.com
89.248.173.87 oliveyucca.ecmpowder.com



From shane at time-travellers.org  Tue Mar  8 14:33:31 2011
From: shane at time-travellers.org (Shane Kerr)
Date: Tue, 08 Mar 2011 14:33:31 +0100
Subject: [anti-abuse-wg] RIPE policy
In-Reply-To: <28482.1299584054@tristatelogic.com>
References: <28482.1299584054@tristatelogic.com>
Message-ID: <1299591211.2276.36.camel@shane-desktop>

Ronald,

On Tue, 2011-03-08 at 03:34 -0800, Ronald F. Guilmette wrote:
> I feel compelled to inquire as to how (or whether) it comports with
> RIPE policy for holders of RIPE IPv4 space to be giving over sizable
> chunks of that space for exclusive use by American bulk E-mail marketing
> companies.

As long as that's the purpose the assignments were registered for, I
don't think there is anything in the policies against using IPv4 space
for sending e-mail in any quantity for any purpose.

I imagine it would be quite tricky to create such a policy. If you want
such a thing, I am interested to hear any suggestions as to how it could
be done.

Cheers,

--
Shane



From michele at blacknight.ie  Tue Mar  8 14:36:03 2011
From: michele at blacknight.ie (Michele Neylon :: Blacknight)
Date: Tue, 8 Mar 2011 13:36:03 +0000
Subject: [anti-abuse-wg] RIPE policy
In-Reply-To: <1299591211.2276.36.camel@shane-desktop>
References: <28482.1299584054@tristatelogic.com>
 <1299591211.2276.36.camel@shane-desktop>
Message-ID: <928CEF1B-54FC-4CCA-8BC0-FD336F767F3D@blacknight.ie>

If they're using the space for email and they're not actually causing issues, what difference does it make?


Mr Michele Neylon
Blacknight Solutions
Hosting & Colocation, Brand Protection
ICANN Accredited Registrar
http://www.blacknight.com/
http://blog.blacknight.com/
http://blacknight.mobi/
http://mneylon.tel
Intl. +353 (0) 59  9183072
US: 213-233-1612 
UK: 0844 484 9361
Locall: 1850 929 929
Direct Dial: +353 (0)59 9183090
Twitter: http://twitter.com/mneylon

PS: Check out our latest offers on domains & hosting: http://domainoffers.me/
-------------------------------
Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty
Road,Graiguecullen,Carlow,Ireland  Company No.: 370845





From ops.lists at gmail.com  Tue Mar  8 15:12:04 2011
From: ops.lists at gmail.com (Suresh Ramasubramanian)
Date: Tue, 8 Mar 2011 19:42:04 +0530
Subject: [anti-abuse-wg] RIPE policy
In-Reply-To: <1299591211.2276.36.camel@shane-desktop>
References: <28482.1299584054@tristatelogic.com>
	<1299591211.2276.36.camel@shane-desktop>
Message-ID: <AANLkTikUUWLUJ4NrjhmLTJJPCk1607HYdMuR=5k-=2sK@mail.gmail.com>

How about ensuring accuracy in whois - in the descr: field, say?

Its currently encouraged but not mandatory.

(and do I hear a "we are not the whois police" out there?)

On Tue, Mar 8, 2011 at 7:03 PM, Shane Kerr <shane at time-travellers.org> wrote:
> As long as that's the purpose the assignments were registered for, I
> don't think there is anything in the policies against using IPv4 space
> for sending e-mail in any quantity for any purpose.
>
> I imagine it would be quite tricky to create such a policy. If you want
> such a thing, I am interested to hear any suggestions as to how it could
> be done.



-- 
Suresh Ramasubramanian (ops.lists at gmail.com)



From leo.vegoda at icann.org  Tue Mar  8 16:46:09 2011
From: leo.vegoda at icann.org (Leo Vegoda)
Date: Tue, 8 Mar 2011 07:46:09 -0800
Subject: [anti-abuse-wg] RIPE policy
In-Reply-To: <AANLkTikUUWLUJ4NrjhmLTJJPCk1607HYdMuR=5k-=2sK@mail.gmail.com>
References: <28482.1299584054@tristatelogic.com>
 <1299591211.2276.36.camel@shane-desktop>
 <AANLkTikUUWLUJ4NrjhmLTJJPCk1607HYdMuR=5k-=2sK@mail.gmail.com>
Message-ID: <5578C0CA-2217-4C26-8A95-3F649BBA008A@icann.org>

On Mar 8, 2011, at 6:12 AM, Suresh Ramasubramanian wrote:

> How about ensuring accuracy in whois - in the descr: field, say?
> 
> Its currently encouraged but not mandatory.

At which level?

If the address space is an allocation or a PI assignment from the RIPE NCC there should be an "org:" attribute referring to an "organisation:" object with whatever details are in the contract. If it's an assignment from an LIR's allocation then I'm not sure what value it would have.

"descr:" is free form text and trying to impose a structure on that kind of field after a couple of decades is probably not a route to success.

Regards,

Leo


From ops.lists at gmail.com  Tue Mar  8 16:48:40 2011
From: ops.lists at gmail.com (Suresh Ramasubramanian)
Date: Tue, 8 Mar 2011 21:18:40 +0530
Subject: [anti-abuse-wg] RIPE policy
In-Reply-To: <5578C0CA-2217-4C26-8A95-3F649BBA008A@icann.org>
References: <28482.1299584054@tristatelogic.com>
	<1299591211.2276.36.camel@shane-desktop>
	<AANLkTikUUWLUJ4NrjhmLTJJPCk1607HYdMuR=5k-=2sK@mail.gmail.com>
	<5578C0CA-2217-4C26-8A95-3F649BBA008A@icann.org>
Message-ID: <AANLkTikUp6vLxp7M=W5NoXFK06PsjAfTwUny49DFZn5O@mail.gmail.com>

On Tue, Mar 8, 2011 at 9:16 PM, Leo Vegoda <leo.vegoda at icann.org> wrote:
>
> "descr:" is free form text and trying to impose a structure on that kind of field after a couple of decades is probably not a route to success.
>

Please note, I didn't say "structure".  I said "accuracy".  At least
to the extent of "Broadband IP space" not being equal to "IPs used for
email marketing"

--srs

-- 
Suresh Ramasubramanian (ops.lists at gmail.com)



From leo.vegoda at icann.org  Tue Mar  8 17:33:43 2011
From: leo.vegoda at icann.org (Leo Vegoda)
Date: Tue, 8 Mar 2011 08:33:43 -0800
Subject: [anti-abuse-wg] RIPE policy
In-Reply-To: <AANLkTikUp6vLxp7M=W5NoXFK06PsjAfTwUny49DFZn5O@mail.gmail.com>
References: <28482.1299584054@tristatelogic.com>
 <1299591211.2276.36.camel@shane-desktop>
 <AANLkTikUUWLUJ4NrjhmLTJJPCk1607HYdMuR=5k-=2sK@mail.gmail.com>
 <5578C0CA-2217-4C26-8A95-3F649BBA008A@icann.org>
 <AANLkTikUp6vLxp7M=W5NoXFK06PsjAfTwUny49DFZn5O@mail.gmail.com>
Message-ID: <6B036D3A-2804-40C1-B6A8-C0B66A4C4DED@icann.org>

On Mar 8, 2011, at 7:48 AM, Suresh Ramasubramanian wrote:
> On Tue, Mar 8, 2011 at 9:16 PM, Leo Vegoda <leo.vegoda at icann.org> wrote:
>> 
>> "descr:" is free form text and trying to impose a structure on that kind of field after a couple of decades is probably not a route to success.
> 
> Please note, I didn't say "structure".  I said "accuracy".  At least
> to the extent of "Broadband IP space" not being equal to "IPs used for
> email marketing"

Both could be true, although that would probably be the best choice. However, as we approach the point where obtaining IPv4 address space becomes more difficult I think we will have to accept that individual IPv4 addresses will share role much more frequently. 

Regards,

Leo


From ops.lists at gmail.com  Tue Mar  8 17:38:22 2011
From: ops.lists at gmail.com (Suresh Ramasubramanian)
Date: Tue, 8 Mar 2011 22:08:22 +0530
Subject: [anti-abuse-wg] RIPE policy
In-Reply-To: <6B036D3A-2804-40C1-B6A8-C0B66A4C4DED@icann.org>
References: <28482.1299584054@tristatelogic.com>
	<1299591211.2276.36.camel@shane-desktop>
	<AANLkTikUUWLUJ4NrjhmLTJJPCk1607HYdMuR=5k-=2sK@mail.gmail.com>
	<5578C0CA-2217-4C26-8A95-3F649BBA008A@icann.org>
	<AANLkTikUp6vLxp7M=W5NoXFK06PsjAfTwUny49DFZn5O@mail.gmail.com>
	<6B036D3A-2804-40C1-B6A8-C0B66A4C4DED@icann.org>
Message-ID: <AANLkTi=VKb2M_3Z2tji-Y3h3u=+qECr_=FMmjw-+oivR@mail.gmail.com>

On Tue, Mar 8, 2011 at 10:03 PM, Leo Vegoda <leo.vegoda at icann.org> wrote:
> Both could be true, although that would probably be the best choice. However, as we approach the point where obtaining IPv4 address space becomes more difficult I think we will have to accept that individual IPv4 addresses will share role much more frequently.

I guess.  But the allocation policies, whois requirements etc remain
substantially the same for ipv6.
We might as well forget, for the moment, that we're talking about a
set of IPv4 netblocks in this thread.

-- 
Suresh Ramasubramanian (ops.lists at gmail.com)



From vesely at tana.it  Tue Mar  8 18:54:12 2011
From: vesely at tana.it (Alessandro Vesely)
Date: Tue, 08 Mar 2011 18:54:12 +0100
Subject: [anti-abuse-wg] RIPE policy
In-Reply-To: <AANLkTi=VKb2M_3Z2tji-Y3h3u=+qECr_=FMmjw-+oivR@mail.gmail.com>
References: <28482.1299584054@tristatelogic.com>	<1299591211.2276.36.camel@shane-desktop>	<AANLkTikUUWLUJ4NrjhmLTJJPCk1607HYdMuR=5k-=2sK@mail.gmail.com>	<5578C0CA-2217-4C26-8A95-3F649BBA008A@icann.org>	<AANLkTikUp6vLxp7M=W5NoXFK06PsjAfTwUny49DFZn5O@mail.gmail.com>	<6B036D3A-2804-40C1-B6A8-C0B66A4C4DED@icann.org> <AANLkTi=VKb2M_3Z2tji-Y3h3u=+qECr_=FMmjw-+oivR@mail.gmail.com>
Message-ID: <4D766D44.4040400@tana.it>

On 08/Mar/11 17:38, Suresh Ramasubramanian wrote:
> On Tue, Mar 8, 2011 at 10:03 PM, Leo Vegoda <leo.vegoda at icann.org> wrote:
>> Both [of "Broadband IP space" and "IPs used for email marketing"]
>> could be true, although that would probably be the best choice.
>> However, as we approach the point where obtaining IPv4 address
>> space becomes more difficult I think we will have to accept that
>> individual IPv4 addresses will share role much more frequently.
> 
> I guess.  But the allocation policies, whois requirements etc remain
> substantially the same for ipv6.

This similarity should make less and less sense, as time goes by.
How do users choose between IPv4 and IPv6 in case they have both?  In
particular, DNSBLs are more difficult with IPv6, so it could make
sense to kindly push users to sticking to IPv4 for _and only for_
tasks that may benefit from DNSBLs, typically public MXes and email
marketing.



From peter at hk.ipsec.se  Tue Mar  8 18:59:52 2011
From: peter at hk.ipsec.se (peter h)
Date: Tue, 8 Mar 2011 18:59:52 +0100
Subject: [anti-abuse-wg] RIPE policy
In-Reply-To: <4D766D44.4040400@tana.it>
References: <28482.1299584054@tristatelogic.com> <AANLkTi=VKb2M_3Z2tji-Y3h3u=+qECr_=FMmjw-+oivR@mail.gmail.com> <4D766D44.4040400@tana.it>
Message-ID: <201103081859.53378.peter@hk.ipsec.se>

On Tuesday 08 March 2011 18.54, Alessandro Vesely wrote:
> On 08/Mar/11 17:38, Suresh Ramasubramanian wrote:
> > On Tue, Mar 8, 2011 at 10:03 PM, Leo Vegoda <leo.vegoda at icann.org> wrote:
> >> Both [of "Broadband IP space" and "IPs used for email marketing"]
> >> could be true, although that would probably be the best choice.
> >> However, as we approach the point where obtaining IPv4 address
> >> space becomes more difficult I think we will have to accept that
> >> individual IPv4 addresses will share role much more frequently.
> > 
> > I guess.  But the allocation policies, whois requirements etc remain
> > substantially the same for ipv6.
> 
> This similarity should make less and less sense, as time goes by.
> How do users choose between IPv4 and IPv6 in case they have both?  In
> particular, DNSBLs are more difficult with IPv6, so it could make
> sense to kindly push users to sticking to IPv4 for _and only for_
> tasks that may benefit from DNSBLs, typically public MXes and email
> marketing.

I have no problem with blocklists ipv6. Larger chunks however :-)

I do have problem with abuse, where spam is the dominant factor, often
used as vehicle for other kinds of fraud.


> 
> 

-- 
        Peter H?kanson   

        There's never money to do it right, but always money to do it
        again ... and again ... and again ... and again.
        ( Det ?r billigare att g?ra r?tt. Det ?r dyrt att laga fel. )



From rfg at tristatelogic.com  Wed Mar  9 00:03:48 2011
From: rfg at tristatelogic.com (Ronald F. Guilmette)
Date: Tue, 08 Mar 2011 15:03:48 -0800
Subject: [anti-abuse-wg] RIPE policy 
In-Reply-To: <1299591211.2276.36.camel@shane-desktop> 
Message-ID: <41186.1299625428@tristatelogic.com>

In message <1299591211.2276.36.camel at shane-desktop>, 
Shane Kerr <shane at time-travellers.org> wrote:

>Ronald,
>
>On Tue, 2011-03-08 at 03:34 -0800, Ronald F. Guilmette wrote:
>> I feel compelled to inquire as to how (or whether) it comports with
>> RIPE policy for holders of RIPE IPv4 space to be giving over sizable
>> chunks of that space for exclusive use by American bulk E-mail marketing
>> companies.
>
>As long as that's the purpose the assignments were registered for, I
>don't think there is anything in the policies against using IPv4 space
>for sending e-mail in any quantity for any purpose.
>
>I imagine it would be quite tricky to create such a policy. If you want
>such a thing, I am interested to hear any suggestions as to how it could
>be done.

It wasn't so much the specific use to which the IP space is being put
that I was questioning.  Rather, I was wondering more about the apparent
re-assignment (re-selling?) of RIPE IP space, en mass, to parties outside
of the RIPE geographic jurisdiction.

Of course, I'll freely admit that I only raised the question because of my
personal distaste for the specific activities going on in those blocks.
But again, the question is about the re-selling of (precious?) IPv4 space,
en mass, and not specifically about the business practices of those to whom
such space may be (re-)sold.


Regards,
rfg



From leo.vegoda at icann.org  Wed Mar  9 00:39:22 2011
From: leo.vegoda at icann.org (Leo Vegoda)
Date: Tue, 8 Mar 2011 15:39:22 -0800
Subject: [anti-abuse-wg] RIPE policy 
In-Reply-To: <41186.1299625428@tristatelogic.com>
References: <41186.1299625428@tristatelogic.com>
Message-ID: <9651ABB9-2489-4DDA-808A-36846E334B8B@icann.org>

On Mar 8, 2011, at 3:04 PM, "Ronald F. Guilmette" <rfg at tristatelogic.com> wrote:

[...]

> It wasn't so much the specific use to which the IP space is being put
> that I was questioning.  Rather, I was wondering more about the apparent
> re-assignment (re-selling?) of RIPE IP space, en mass, to parties outside
> of the RIPE geographic jurisdiction.

Do you mean selling IP connectivity to networks outside the region? That is fairly common and not unreasonable. For instance, satellite connectivity providers often have customers in fairly remote locations.

Regards,

Leo


From rfg at tristatelogic.com  Wed Mar  9 00:56:31 2011
From: rfg at tristatelogic.com (Ronald F. Guilmette)
Date: Tue, 08 Mar 2011 15:56:31 -0800
Subject: [anti-abuse-wg] RIPE policy 
In-Reply-To: <9651ABB9-2489-4DDA-808A-36846E334B8B@icann.org> 
Message-ID: <41680.1299628591@tristatelogic.com>

In message <9651ABB9-2489-4DDA-808A-36846E334B8B at icann.org>, 
Leo Vegoda <leo.vegoda at icann.org> wrote:

>On Mar 8, 2011, at 3:04 PM, "Ronald F. Guilmette" <rfg at tristatelogic.com> w=
>rote:
>
>[...]
>
>> It wasn't so much the specific use to which the IP space is being put
>> that I was questioning.  Rather, I was wondering more about the apparent
>> re-assignment (re-selling?) of RIPE IP space, en mass, to parties outside
>> of the RIPE geographic jurisdiction.
>
>Do you mean selling IP connectivity to networks outside the region? That is=
> fairly common and not unreasonable. For instance, satellite connectivity p=
>roviders often have customers in fairly remote locations.

The several cases I posted are _not_ ``satellite connectivity providers'',
and these are _not_ just, like, /28s and /29s we are talking about here.

Apples and oranges are both sort-of round-ish.  That fact does not make
them either equivalent or interchangable.  I don't believe that it takes
an exceptional amount of wisdom to understand that.



From leo.vegoda at icann.org  Wed Mar  9 01:08:55 2011
From: leo.vegoda at icann.org (Leo Vegoda)
Date: Tue, 8 Mar 2011 16:08:55 -0800
Subject: [anti-abuse-wg] RIPE policy 
In-Reply-To: <41680.1299628591@tristatelogic.com>
References: <41680.1299628591@tristatelogic.com>
Message-ID: <EA9DF45F-B584-48C4-A598-0EA671C54011@icann.org>

On Mar 8, 2011, at 3:57 PM, "Ronald F. Guilmette" <rfg at tristatelogic.com> wrote:

[...]

> 
>> 
>>>   Rather, I was wondering more about the apparent
>>> re-assignment (re-selling?) of RIPE IP space, en mass, to parties outside
>>> of the RIPE geographic jurisdiction.
>> 
>> Do you mean selling IP connectivity to networks outside the region? That is=
>> fairly common and not unreasonable. For instance, satellite connectivity p=
>> roviders often have customers in fairly remote locations.
> 
> The several cases I posted are _not_ ``satellite connectivity providers'',
> and these are _not_ just, like, /28s and /29s we are talking about here.

I asked you to clarify what you meant and gave an example of a legitimate situation.

Asking again: do you mean selling connectivity services?

Selling address blocks without connectivity is different from selling them with it.

Regards,

Leo


From ops.lists at gmail.com  Wed Mar  9 02:00:17 2011
From: ops.lists at gmail.com (Suresh Ramasubramanian)
Date: Wed, 9 Mar 2011 06:30:17 +0530
Subject: [anti-abuse-wg] RIPE policy
In-Reply-To: <EA9DF45F-B584-48C4-A598-0EA671C54011@icann.org>
References: <41680.1299628591@tristatelogic.com>
	<EA9DF45F-B584-48C4-A598-0EA671C54011@icann.org>
Message-ID: <AANLkTim89Ca=Tyq2an+w2YPX==7XGBfmTqnjEjM_SLU0@mail.gmail.com>

He isn't talking about any of the legitimate use cases here

Not connectivity providers of any sort
Not anycast
Not multihomed, international corporations

Acquiring extremely large netblocks solely for net abuse is something
that goes on, on a grand scale in the RIPE region, compared to any
other RIR in the world

It is a fact you will have to acknowledge first before you can even
begin to put in place any measures to stop it .. and that does not
seem to be the case as far as I can see.

--srs

On Wed, Mar 9, 2011 at 5:38 AM, Leo Vegoda <leo.vegoda at icann.org> wrote:
>
> I asked you to clarify what you meant and gave an example of a legitimate situation.
>
> Asking again: do you mean selling connectivity services?
>
> Selling address blocks without connectivity is different from selling them with it.
>



-- 
Suresh Ramasubramanian (ops.lists at gmail.com)



From rfg at tristatelogic.com  Wed Mar  9 02:10:22 2011
From: rfg at tristatelogic.com (Ronald F. Guilmette)
Date: Tue, 08 Mar 2011 17:10:22 -0800
Subject: [anti-abuse-wg] RIPE policy 
In-Reply-To: <EA9DF45F-B584-48C4-A598-0EA671C54011@icann.org> 
Message-ID: <42318.1299633022@tristatelogic.com>

In message <EA9DF45F-B584-48C4-A598-0EA671C54011 at icann.org>, 
Leo Vegoda <leo.vegoda at icann.org> wrote:

>On Mar 8, 2011, at 3:57 PM, "Ronald F. Guilmette" <rfg at tristatelogic.com> w
>rote:
>
>[...]
>
>>>>   Rather, I was wondering more about the apparent
>>>> re-assignment (re-selling?) of RIPE IP space, en mass, to parties outsi
>de
>>>> of the RIPE geographic jurisdiction.
>>> Do you mean selling IP connectivity to networks outside the region? That
>> is
>>> fairly common and not unreasonable. For instance, satellite connectivity
> p
>>> roviders often have customers in fairly remote locations.
>>
>> The several cases I posted are _not_ ``satellite connectivity providers''
>,
>> and these are _not_ just, like, /28s and /29s we are talking about here.
>
>I asked you to clarify what you meant and gave an example of a legitimate s
>ituation.

With all due respect, no.  You gave an example of a situation which you
personally believe to be in some sense ``legitimate''.

Is there a document somewhere, either within RIPE or ICANN, that says
explicitly that ``satellite connectivity providers'' may do X, Y, and Z?

Is there a document somewhere, either within RIPE or ICANN, that explicitly
defines the term ``satellite connectivity providers'' in a way so that anyone
with basic familiarity with networking could easily differentiate things
that are ``satellite connectivity providers'' from things that are not?
I mean FORMALLY?

(If you are determined to play lawyer, then you really should approach the
game armed with a suitable set of formal, ratified documents to support
your positions and assertions, I think.)

>Asking again: do you mean selling connectivity services?

I could perhaps attempt to answer your question if it were not so clearly
ambiguous.

Why don't you start by defining your terms with at least the level of rigor
that you are, apparently, demanding of me when I post a simple and reasonable
question about policy?

What EXACTLY do you mean by ``selling connectivity services''.  Please be
precise.  Then I might be able to provide an answer to your question.

When providing your definition, please be sure that it is ``testable'' in
the scientific sense of the word, that is it should be possible for a
person skilled in the art to use your definition to consistantly and
accurately determine what sets of circumstances do or do not constitute
``selling connectivity services''.

>Selling address blocks without connectivity is different from selling them 
>with it.

It is?

Why do you assert that those two things are ``different''?

How precisely do those differ, and how, exactly, could a person skilled in
the art tell them apart?

Is there a formal ratified policy document somwhere that says that they differ?

Or is this merely your own personal view of things?


Regards,
rfg


P.S.  No, I am _not_ asking all of these questions to be annoying, obtuse,
or pin-headed.  I am looking at various sets of facts with respect to the
specific IP blocks I posted about, some of which may conform to policy,
and others of which may not.  You've effectively asked me what I think
is wrong.  In response, I've simply asked you to define your terms, pre-
ferably with reference to actual policy documents and not merely your
intuition about what ``feels'' right or wrong to you personally.



From rfg at tristatelogic.com  Wed Mar  9 02:28:28 2011
From: rfg at tristatelogic.com (Ronald F. Guilmette)
Date: Tue, 08 Mar 2011 17:28:28 -0800
Subject: [anti-abuse-wg] RIPE policy 
In-Reply-To: <AANLkTim89Ca=Tyq2an+w2YPX==7XGBfmTqnjEjM_SLU0@mail.gmail.com> 
Message-ID: <42516.1299634108@tristatelogic.com>

In message <AANLkTim89Ca=Tyq2an+w2YPX==7XGBfmTqnjEjM_SLU0 at mail.gmail.com>,
Suresh Ramasubramanian <ops.lists at gmail.com> wrote:

>Acquiring extremely large netblocks solely for net abuse is something
>that goes on, on a grand scale in the RIPE region, compared to any
>other RIR in the world

For the record (and having some substantial knowledge in this particular
area) let me just say that Suresh is right, but only in so far as he attached
the word "extremely".

Here in the ARIN region, the questionable aqusition of sizable netblocks
"solely for net abuse' is also unfortunately widespread (and one might
even say rampant) but the size of the individual blocks tends to be smaller...
but there are more of them.  Innumerable /24s in ARIN-land have gone over
to the Dark Side, and even the occasional recycled /16.

But I do sort-of recall one particular brand-spankin'-new /15 that got
assigned out of RIPE space... not really that long ago... to some Romanians,
I think, who promptly filled the whole bleedin' thing up with snowshoe spam
domains.  That certainly was eye opening.

But I don't think it is productive to call out any particular RiRs for
doing less than what could be done to fight this sort of thing.  There
is plenty of blame to go around, and blame ain't gonna solve the problem.


Regards,
rfg



From ops.lists at gmail.com  Wed Mar  9 02:32:06 2011
From: ops.lists at gmail.com (Suresh Ramasubramanian)
Date: Wed, 9 Mar 2011 07:02:06 +0530
Subject: [anti-abuse-wg] RIPE policy
In-Reply-To: <42516.1299634108@tristatelogic.com>
References: <AANLkTim89Ca=Tyq2an+w2YPX==7XGBfmTqnjEjM_SLU0@mail.gmail.com>
	<42516.1299634108@tristatelogic.com>
Message-ID: <AANLkTimhqubMOO4JcmeBWMcDkZOpqR6rCguPrb6=GNwS@mail.gmail.com>

On Wed, Mar 9, 2011 at 6:58 AM, Ronald F. Guilmette
<rfg at tristatelogic.com> wrote:
> Here in the ARIN region, the questionable aqusition of sizable netblocks
> "solely for net abuse' is also unfortunately widespread (and one might
> even say rampant) but the size of the individual blocks tends to be smaller...
> but there are more of them. ?Innumerable /24s in ARIN-land have gone over
> to the Dark Side, and even the occasional recycled /16.

These have mostly been acquired by providers who then allocate it
further to customers.

As for the recycled /16s those are cases - well known sometimes, such
as the sfbay packet radio netblock
(http://voices.washingtonpost.com/securityfix/2008/04/a_case_of_network_identity_the_1.html)
of defunct companies being "revived" for the sake of a unused /16
that's in their hands ..

What we see in the RIPE region is a series of assigned PI and PA
netblocks.  Large ones.

-- 
Suresh Ramasubramanian (ops.lists at gmail.com)



From leo.vegoda at icann.org  Wed Mar  9 03:41:49 2011
From: leo.vegoda at icann.org (Leo Vegoda)
Date: Tue, 8 Mar 2011 18:41:49 -0800
Subject: [anti-abuse-wg] RIPE policy
In-Reply-To: <AANLkTim89Ca=Tyq2an+w2YPX==7XGBfmTqnjEjM_SLU0@mail.gmail.com>
References: <41680.1299628591@tristatelogic.com>
 <EA9DF45F-B584-48C4-A598-0EA671C54011@icann.org>
 <AANLkTim89Ca=Tyq2an+w2YPX==7XGBfmTqnjEjM_SLU0@mail.gmail.com>
Message-ID: <2D30BD8C-E07A-46CA-9F07-747796EAC8AE@icann.org>

Suresh,

On Mar 8, 2011, at 5:00 PM, Suresh Ramasubramanian wrote:

[?]

> It is a fact you will have to acknowledge first before you can even
> begin to put in place any measures to stop it .. and that does not
> seem to be the case as far as I can see.

I am sure that if it was not a problem you would not keep complaining about it.

That being said, it is quite sad that those of you who repeatedly return and complain never put forward a formal proposal to change the allocation policy. I personally don't understand why you have not done this. Presumably changing the policy so that the space doesn't get distributed to the people you don't like in the first place would go quite some way to solving your problem.

Regards,

Leo


From leo.vegoda at icann.org  Wed Mar  9 03:42:58 2011
From: leo.vegoda at icann.org (Leo Vegoda)
Date: Tue, 8 Mar 2011 18:42:58 -0800
Subject: [anti-abuse-wg] RIPE policy 
In-Reply-To: <42318.1299633022@tristatelogic.com>
References: <42318.1299633022@tristatelogic.com>
Message-ID: <12A549E2-2EF4-4CA3-BD9D-1541C8B8302A@icann.org>

Ronald,

On Mar 8, 2011, at 5:10 PM, Ronald F. Guilmette wrote:

[?]

>> I asked you to clarify what you meant and gave an example of a legitimate s
>> ituation.
> 
> With all due respect, no.  You gave an example of a situation which you
> personally believe to be in some sense ``legitimate''.
> 
> Is there a document somewhere, either within RIPE or ICANN, that says
> explicitly that ``satellite connectivity providers'' may do X, Y, and Z?

You appear to be taking the approach that only what is explicitly permitted is allowed. However, I am sure that the principle applied is that everything is allowed unless we all, as the RIPE community, agree to restrict it.

>> Asking again: do you mean selling connectivity services?

[?]

> What EXACTLY do you mean by ``selling connectivity services''.  Please be
> precise.  Then I might be able to provide an answer to your question.

The dictionary definition, such as this one from the American Heritage dictionary, is fine. 

"The ability to make and maintain a connection between two or more points in a telecommunications system: a phone company that offers excellent Internet connectivity."

[?]

>> Selling address blocks without connectivity is different from selling them 
>> with it.
> 
> It is?
> 
> Why do you assert that those two things are ``different''?

As I read the current IPv4 policy, address space transfers that are not used for a connection to the provider have to be made according to the transfer policy in section 5.5:

http://www.ripe.net/ripe/docs/ripe-509#----transfers-of-allocations

It is entirely possible that I am wrong and if so, please let me know how.

Regards,

Leo


From ops.lists at gmail.com  Wed Mar  9 03:51:46 2011
From: ops.lists at gmail.com (Suresh Ramasubramanian)
Date: Wed, 9 Mar 2011 08:21:46 +0530
Subject: [anti-abuse-wg] RIPE policy
In-Reply-To: <2D30BD8C-E07A-46CA-9F07-747796EAC8AE@icann.org>
References: <41680.1299628591@tristatelogic.com>
	<EA9DF45F-B584-48C4-A598-0EA671C54011@icann.org>
	<AANLkTim89Ca=Tyq2an+w2YPX==7XGBfmTqnjEjM_SLU0@mail.gmail.com>
	<2D30BD8C-E07A-46CA-9F07-747796EAC8AE@icann.org>
Message-ID: <AANLkTi=z7DrM97R9jFssN8z-R3DW3FV3G=ka6TGo9qa4@mail.gmail.com>

On Wed, Mar 9, 2011 at 8:11 AM, Leo Vegoda <leo.vegoda at icann.org> wrote:
>
> That being said, it is quite sad that those of you who repeatedly return and complain never put forward a formal proposal to change the allocation policy. I personally don't understand why you have not done this. Presumably changing the policy so that the space doesn't get distributed to the people you don't like in the first place would go quite some way to solving your problem.

You will hopefully get a proposal by the time of the next RIPE meeting.

I have not personally submitted a proposal earlier as I don't
participate in RIPE (and thanks to travel restrictions, haven't
participated in APRICOT since 2009 + resigned from the APIA board).
But I do hope to assist someone in contributing to his proposal.

That said, maybe it is high time to close what might be seen as a
process hole in RIPE -

http://www.ripe.net/ripe/groups/wg/anti-abuse/minutes/ripe-58

Filiz Yilmaz (RIPE NCC Policy Development Manager) made a
clarification on the effect of having different mechanisms among the
RIRs and whether they had LIR structures or not. She said the RIPE NCC
membership might understand some terms differently from people in
other RIR regions. She said the assignment window mechanism in the
RIPE NCC service region allowed LIRs some freedom to make assignments
without RIPE NCC approval. She said this means the RIPE NCC doesn?t
see those requests as approval requests. She said AfriNIC has an LIR
system but not that assignment window.

Richard thanked Filiz and made the point that AfriNIC assigned a /20
to an entity that does not exist and it has not revoked the block even
though they have been informed. He said APNIC had previously had
problems with Whois accuracy but he does not see any problems there
now. He said the only RIRs where he saw problems were the RIPE NCC and
LACNIC.

-- 
Suresh Ramasubramanian (ops.lists at gmail.com)



From ops.lists at gmail.com  Wed Mar  9 03:59:12 2011
From: ops.lists at gmail.com (Suresh Ramasubramanian)
Date: Wed, 9 Mar 2011 08:29:12 +0530
Subject: [anti-abuse-wg] RIPE policy
In-Reply-To: <201103081859.53378.peter@hk.ipsec.se>
References: <28482.1299584054@tristatelogic.com>
	<AANLkTi=VKb2M_3Z2tji-Y3h3u=+qECr_=FMmjw-+oivR@mail.gmail.com>
	<4D766D44.4040400@tana.it>
	<201103081859.53378.peter@hk.ipsec.se>
Message-ID: <AANLkTimGGsUsmnKuWY0dTNUs4=7iu_9acOjJdb8SRo2F@mail.gmail.com>

On Tue, Mar 8, 2011 at 11:29 PM, peter h <peter at hk.ipsec.se> wrote:
> I have no problem with blocklists ipv6. Larger chunks however :-)
>
> I do have problem with abuse, where spam is the dominant factor, often
> used as vehicle for other kinds of fraud.

At least some blocklists have moved to support v6 listings ..

Quoting from http://virbl.bit.nl/

15-01-2010:

We've changed Virbl today, which makes it the first fully IPv6 enabled
dnsbl, as far as we can tell. You could already reach Virbl via IPv6
for years, but no IPv6 hosts were served by the nameserver. rbldnsd,
on which we ran Virbl before, does not understand IPv6 in its zones.

We changed some things today:

   1. We implemented a way to list machines with IPv6 and privacy-extensions
   2. We switched from rbldnsd to Bind
   3. We've changed the website so the changes made in '1' are visible
on the website as well


-- 
Suresh Ramasubramanian (ops.lists at gmail.com)



From leo.vegoda at icann.org  Wed Mar  9 04:01:16 2011
From: leo.vegoda at icann.org (Leo Vegoda)
Date: Tue, 8 Mar 2011 19:01:16 -0800
Subject: [anti-abuse-wg] RIPE policy
In-Reply-To: <AANLkTi=z7DrM97R9jFssN8z-R3DW3FV3G=ka6TGo9qa4@mail.gmail.com>
References: <41680.1299628591@tristatelogic.com>
 <EA9DF45F-B584-48C4-A598-0EA671C54011@icann.org>
 <AANLkTim89Ca=Tyq2an+w2YPX==7XGBfmTqnjEjM_SLU0@mail.gmail.com>
 <2D30BD8C-E07A-46CA-9F07-747796EAC8AE@icann.org>
 <AANLkTi=z7DrM97R9jFssN8z-R3DW3FV3G=ka6TGo9qa4@mail.gmail.com>
Message-ID: <10E2F2E1-5795-47B1-99E6-4739EE6AFD02@icann.org>

Hi Suresh,

On Mar 8, 2011, at 6:51 PM, Suresh Ramasubramanian wrote:
> On Wed, Mar 9, 2011 at 8:11 AM, Leo Vegoda <leo.vegoda at icann.org> wrote:

[?]

> I have not personally submitted a proposal earlier as I don't
> participate in RIPE 

You don't need to attend the meeting to participate - just e-mail. If you look at the Policy Development Process you'll see that it doesn't contain the word meeting:

http://www.ripe.net/ripe/docs/ripe-500

[?]

> That said, maybe it is high time to close what might be seen as a
> process hole in RIPE -

Now is probably a reasonable time to review the assignment window policy as it was last revised four years ago and things have changed since then.

Regards,

Leo



From ops.lists at gmail.com  Wed Mar  9 04:06:28 2011
From: ops.lists at gmail.com (Suresh Ramasubramanian)
Date: Wed, 9 Mar 2011 08:36:28 +0530
Subject: [anti-abuse-wg] RIPE policy
In-Reply-To: <10E2F2E1-5795-47B1-99E6-4739EE6AFD02@icann.org>
References: <41680.1299628591@tristatelogic.com>
	<EA9DF45F-B584-48C4-A598-0EA671C54011@icann.org>
	<AANLkTim89Ca=Tyq2an+w2YPX==7XGBfmTqnjEjM_SLU0@mail.gmail.com>
	<2D30BD8C-E07A-46CA-9F07-747796EAC8AE@icann.org>
	<AANLkTi=z7DrM97R9jFssN8z-R3DW3FV3G=ka6TGo9qa4@mail.gmail.com>
	<10E2F2E1-5795-47B1-99E6-4739EE6AFD02@icann.org>
Message-ID: <AANLkTikzSsnt2yZc3fFRneJJNP6HugjPayxCAesTdMoG@mail.gmail.com>

On Wed, Mar 9, 2011 at 8:31 AM, Leo Vegoda <leo.vegoda at icann.org> wrote:
>
> You don't need to attend the meeting to participate - just e-mail. If you look at the Policy Development Process you'll see that it doesn't contain the word meeting:
>
> http://www.ripe.net/ripe/docs/ripe-500

I fully agree.  It is just that remote participation is something I'm
never good at, for all that my current job is with a vendor that also
provides such services.

Just call me old fashioned I guess.

I will see what I can do to submit and/or assist in the submission of
a proposal.

-- 
Suresh Ramasubramanian (ops.lists at gmail.com)



From rfg at tristatelogic.com  Wed Mar  9 05:45:29 2011
From: rfg at tristatelogic.com (Ronald F. Guilmette)
Date: Tue, 08 Mar 2011 20:45:29 -0800
Subject: [anti-abuse-wg] RIPE policy 
In-Reply-To: <12A549E2-2EF4-4CA3-BD9D-1541C8B8302A@icann.org> 
Message-ID: <43977.1299645929@tristatelogic.com>

In message <12A549E2-2EF4-4CA3-BD9D-1541C8B8302A at icann.org>, 
Leo Vegoda <leo.vegoda at icann.org> wrote:

>On Mar 8, 2011, at 5:10 PM, Ronald F. Guilmette wrote:
>> Is there a document somewhere, either within RIPE or ICANN, that says
>> explicitly that ``satellite connectivity providers'' may do X, Y, and Z?
>
>You appear to be taking the approach that only what is explicitly permitted=
>is allowed.

I beg to differ.  I am merely taking the same approach that you are appear
to have taken, formalism as a defense for what rational people with at least
just a tad of the common sense that God gave them would see as being clearly
infensible.

But I don't blame you personally.  There appears to be an awfully widespread
lack of common sense on the Internet these days, and you are certainly far
from alone in falling back on comfortable formalisms as a means of rational-
izing and/or justifying massive unjustifiable waste of precious resources.

>> What EXACTLY do you mean by ``selling connectivity services''.  Please be
>> precise.  Then I might be able to provide an answer to your question.
>
>The dictionary definition, such as this one from the American Heritage dict=
>ionary, is fine.
>
>"The ability to make and maintain a connection between two or more points i=
>n a telecommunications system: a phone company that offers excellent Intern=
>et connectivity."

Reaching into the simplicity of the American Heritage dictionary is neither
helpful nor enlightening in the present highly technical context.

I own a broadband modem/router thingy.  Do I provide connectivity to myself?

Does the ocean provide connectivity between North America and Europe?
Certainly, without it we would have had no place to lay the cables.

Well, nevermind.  Since it appears that you may be a bit reluctant to further
clarify your own question to me in concrete technical terms, I think that
we can perhaps dispense with the need for that, for now anyway, and instead
of trying to wrestle with the terminology of the abstract, we can just deal
with the immediate and the concrete.

I posted lists of IP addresses and domain names within several ``RIPE'' IP
address blocks that I allege have been handed over for use by American
bulk e-mail advertising companies.  (If you no longer have that e-mail or
those lists I will be happy to re-send them to you.)

So to cut to the chase here, I would like to propose something simple.  Why
don't YOU select at random some IP addresses out of the middles of those
IP address blocks, and then do whatever you do... whatever you think is
technically appropriate to do... traceroutes or whatever, as necessary...
and then come back here and then YOU can teach ME, by example, what is
and what is not, in your estimation, ``selling connectivity services''.
I'll be happy to defer to your vastly greater experience in these matters...
as detailed in your online bio... as long as you take the time to explain
whatever conlusions you arrive at with respect to those specific IP blocks.

Yes, I've already done my own paltry and miniscule research with respect to
the ``connectivity'' of those blocks, and I've reached some of my own con-
clusions.  But I will be happy to withold those (naive?) opinions and defer
to your evidently greater expertise, so long as you will do me the courtesy
of explaining the technical basis for your own independent conclusions.

>As I read the current IPv4 policy, address space transfers that are not use=
>d for a connection to the provider have to be made according to the transfe=
>r policy in section 5.5:

OK.  Great.  So now, do any of the blocks that I previously posted about
meet that requirement?  Do any fail to meet it?  If so, which ones and how
did you determine that?

I look forward to being educated by your analysis.


Regards,
rfg



From leo.vegoda at icann.org  Wed Mar  9 06:22:55 2011
From: leo.vegoda at icann.org (Leo Vegoda)
Date: Tue, 8 Mar 2011 21:22:55 -0800
Subject: [anti-abuse-wg] RIPE policy 
In-Reply-To: <43977.1299645929@tristatelogic.com>
References: <43977.1299645929@tristatelogic.com>
Message-ID: <9EACD2CD-15C5-4EBF-8F1A-6CAAEF8B4C36@icann.org>

On Mar 8, 2011, at 8:45 PM, Ronald F. Guilmette wrote:

[?]

> I beg to differ.  I am merely taking the same approach that you are appear
> to have taken, formalism as a defense for what rational people with at least
> just a tad of the common sense that God gave them would see as being clearly
> infensible.
> 
> But I don't blame you personally.  There appears to be an awfully widespread
> lack of common sense on the Internet these days, and you are certainly far
> from alone in falling back on comfortable formalisms as a means of rational-
> izing and/or justifying massive unjustifiable waste of precious resources.

Ah, ad hominem.

*plonk*



From michele at blacknight.ie  Wed Mar  9 09:13:27 2011
From: michele at blacknight.ie (Michele Neylon :: Blacknight)
Date: Wed, 9 Mar 2011 08:13:27 +0000
Subject: [anti-abuse-wg] RIPE policy
In-Reply-To: <AANLkTimGGsUsmnKuWY0dTNUs4=7iu_9acOjJdb8SRo2F@mail.gmail.com>
References: <28482.1299584054@tristatelogic.com>
 <AANLkTi=VKb2M_3Z2tji-Y3h3u=+qECr_=FMmjw-+oivR@mail.gmail.com>
 <4D766D44.4040400@tana.it> <201103081859.53378.peter@hk.ipsec.se>
 <AANLkTimGGsUsmnKuWY0dTNUs4=7iu_9acOjJdb8SRo2F@mail.gmail.com>
Message-ID: <A09C84E7-1F6B-4C04-BA4A-348B8A01184D@blacknight.ie>

On 9 Mar 2011, at 02:59, Suresh Ramasubramanian wrote:

> On Tue, Mar 8, 2011 at 11:29 PM, peter h <peter at hk.ipsec.se> wrote:
>> I have no problem with blocklists ipv6. Larger chunks however :-)
>> 
>> I do have problem with abuse, where spam is the dominant factor, often
>> used as vehicle for other kinds of fraud.
> 
> At least some blocklists have moved to support v6 listings ..
> 
> Quoting from http://virbl.bit.nl/
> 
> 15-01-2010:
> 
> We've changed Virbl today, which makes it the first fully IPv6 enabled
> dnsbl, as far as we can tell. You could already reach Virbl via IPv6
> for years, but no IPv6 hosts were served by the nameserver. rbldnsd,
> on which we ran Virbl before, does not understand IPv6 in its zones.
> 
> We changed some things today:
> 
>   1. We implemented a way to list machines with IPv6 and privacy-extensions
>   2. We switched from rbldnsd to Bind

RBLDNSD will have IPv6 support .. they made an announcement about it having some kind of support for it a few days ago .. 

>   3. We've changed the website so the changes made in '1' are visible
> on the website as well
> 
> 
> -- 
> Suresh Ramasubramanian (ops.lists at gmail.com)
> 

Mr Michele Neylon
Blacknight Solutions
Hosting & Colocation, Brand Protection
ICANN Accredited Registrar
http://www.blacknight.com/
http://blog.blacknight.com/
http://blacknight.mobi/
http://mneylon.tel
Intl. +353 (0) 59  9183072
US: 213-233-1612 
UK: 0844 484 9361
Direct Dial: +353 (0)59 9183090
Fax. +353 (0) 1 4811 763
-------------------------------
Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty
Road,Graiguecullen,Carlow,Ireland  Company No.: 370845



From jorgen at hovland.cx  Wed Mar  9 09:42:24 2011
From: jorgen at hovland.cx (=?ISO-8859-1?Q?J=F8rgen_Hovland?=)
Date: Wed, 09 Mar 2011 09:42:24 +0100
Subject: [anti-abuse-wg] RIPE policy
In-Reply-To: <A09C84E7-1F6B-4C04-BA4A-348B8A01184D@blacknight.ie>
References: <28482.1299584054@tristatelogic.com> <AANLkTi=VKb2M_3Z2tji-Y3h3u=+qECr_=FMmjw-+oivR@mail.gmail.com> <4D766D44.4040400@tana.it> <201103081859.53378.peter@hk.ipsec.se> <AANLkTimGGsUsmnKuWY0dTNUs4=7iu_9acOjJdb8SRo2F@mail.gmail.com> <A09C84E7-1F6B-4C04-BA4A-348B8A01184D@blacknight.ie>
Message-ID: <4D773D70.4010305@hovland.cx>


On 03/09/11 09:13, : Blacknight" <michele at blacknight.ie>" wrote:
>
>> At least some blocklists have moved to support v6 listings ..
>>
>> Quoting from http://virbl.bit.nl/
>>
>> 15-01-2010:
>>
>> We've changed Virbl today, which makes it the first fully IPv6 enabled
>> dnsbl, as far as we can tell.

Probably not very interesting, but the first public fully IPv6-enabled 
dnsbl as far as I can tell was created April 2006 (and private in 2001).





From vesely at tana.it  Wed Mar  9 11:14:14 2011
From: vesely at tana.it (Alessandro Vesely)
Date: Wed, 09 Mar 2011 11:14:14 +0100
Subject: [anti-abuse-wg] RIPE policy
In-Reply-To: <AANLkTimGGsUsmnKuWY0dTNUs4=7iu_9acOjJdb8SRo2F@mail.gmail.com>
References: <28482.1299584054@tristatelogic.com>	<AANLkTi=VKb2M_3Z2tji-Y3h3u=+qECr_=FMmjw-+oivR@mail.gmail.com>	<4D766D44.4040400@tana.it>	<201103081859.53378.peter@hk.ipsec.se> <AANLkTimGGsUsmnKuWY0dTNUs4=7iu_9acOjJdb8SRo2F@mail.gmail.com>
Message-ID: <4D7752F6.1050000@tana.it>

On 09/Mar/11 03:59, Suresh Ramasubramanian wrote:
> On Tue, Mar 8, 2011 at 11:29 PM, peter h <peter at hk.ipsec.se> wrote:
>> I have no problem with blocklists ipv6. Larger chunks however :-)
>>
>> I do have problem with abuse, where spam is the dominant factor, often
>> used as vehicle for other kinds of fraud.
> 
> At least some blocklists have moved to support v6 listings ..

Yes, it is obviously possible.  But discovering the right granularity
and transmitting it to clients is problematic.  For a possible
solution see http://tools.ietf.org/html/draft-levine-iprangepub .

OTOH, IPv4 extensively uses NAT, so that blocking the wrong IP may
affect an entire network behind it.  Traditional DNSBLs would be safer
without such widespread use of NAT, which can be taken down using IPv6.

However we distaste spammers, we are better off if they stick to IPv4
while the rest of the traffic moves to IPv6.  I note that a working
definition for such address classes already exists.  It may be enough
to discourage public IPv6 MXes in order to promote this sort of
compartmentalization.



From shane at time-travellers.org  Wed Mar  9 11:56:33 2011
From: shane at time-travellers.org (Shane Kerr)
Date: Wed, 09 Mar 2011 11:56:33 +0100
Subject: [anti-abuse-wg] Use of RIPE region space by out-of-region users, was RIPE policy
In-Reply-To: <43977.1299645929@tristatelogic.com>
References: <43977.1299645929@tristatelogic.com>
Message-ID: <1299668193.2210.12.camel@shane-desktop>

Ronald,

On Tue, 2011-03-08 at 20:45 -0800, Ronald F. Guilmette wrote:

> I posted lists of IP addresses and domain names within several ``RIPE'' IP
> address blocks that I allege have been handed over for use by American
> bulk e-mail advertising companies.  (If you no longer have that e-mail or
> those lists I will be happy to re-send them to you.)

Looking at the first IP address in your list:

shane at madras:~$ mtr --report --report-wide 109.177.8.2
HOST: madras                              Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. hosted.by.leaseweb.com               0.0%    10    1.4   1.1   0.4   1.5   0.5
  2. te0-3-0-3.crs.tc2.leaseweb.net       0.0%    10    1.5   1.0   0.4   1.5   0.6
  3. ae4-30.RT.TC2.AMS.NL.retn.net        0.0%    10    1.6   2.1   0.4  13.6   4.1
  4. ae1-9.RT.MR.MSK.RU.retn.net          0.0%    10   46.9  46.3  45.7  46.9   0.6
  5. GW-Synterra.retn.net                 0.0%    10   52.3  54.4  51.1  78.3   8.4
  6. msk-d2-hq-ae2.main.synterra.ru       0.0%    10   55.4  58.5  54.3  88.7  10.6
  7. GW-OOO171Enlink187.main.synterra.ru  0.0%    10   55.0  56.7  54.7  67.0   3.7
  8. 94.231.116.62                        0.0%    10   58.2  58.9  58.2  60.0   0.7
  9. ???                                 100.0    10    0.0   0.0   0.0   0.0   0.0
 10. 109.177.8.2                         10.0%    10  212.4 211.9 211.3 212.5   0.5

These addresses appear to be hosted in Russia. Probably a Russian
company is selling hosting service to American advertisers.

AFAIK there have never been rules about who you can provide services to
with the address blocks you have been given. I would object strongly to
a proposal to do so.

--
Shane



From michele at blacknight.ie  Wed Mar  9 12:08:12 2011
From: michele at blacknight.ie (Michele Neylon :: Blacknight)
Date: Wed, 9 Mar 2011 11:08:12 +0000
Subject: [anti-abuse-wg] Use of RIPE region space by out-of-region
 users, was RIPE policy
In-Reply-To: <1299668193.2210.12.camel@shane-desktop>
References: <43977.1299645929@tristatelogic.com>
 <1299668193.2210.12.camel@shane-desktop>
Message-ID: <631B1D4D-5473-4452-90DC-736D013D9136@blacknight.ie>

On 9 Mar 2011, at 10:56, Shane Kerr wrote:
> 
> 
> AFAIK there have never been rules about who you can provide services to
> with the address blocks you have been given. I would object strongly to
> a proposal to do so.


As would I

If network operators are abusing or allowing their networks to be abused then I can understand why some people might get upset, but I don't see why that should impact the rest of us. 

If I want to provide services to a company in Mongolia and we provide an allocation to them and it complies with the RIPE rules then it is none of anybody's business

Regards

Michele


Mr Michele Neylon
Blacknight Solutions
Hosting & Colocation, Brand Protection
ICANN Accredited Registrar
http://www.blacknight.com/
http://blog.blacknight.com/
http://blacknight.mobi/
http://mneylon.tel
Intl. +353 (0) 59  9183072
US: 213-233-1612 
UK: 0844 484 9361
Locall: 1850 929 929
Direct Dial: +353 (0)59 9183090
Twitter: http://twitter.com/mneylon

PS: Check out our latest offers on domains & hosting: http://domainoffers.me/
-------------------------------
Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty
Road,Graiguecullen,Carlow,Ireland  Company No.: 370845





From michele at blacknight.ie  Wed Mar  9 12:16:52 2011
From: michele at blacknight.ie (Michele Neylon :: Blacknight)
Date: Wed, 9 Mar 2011 11:16:52 +0000
Subject: [anti-abuse-wg] Use of RIPE region space by out-of-region
 users, was RIPE policy
In-Reply-To: <631B1D4D-5473-4452-90DC-736D013D9136@blacknight.ie>
References: <43977.1299645929@tristatelogic.com>
 <1299668193.2210.12.camel@shane-desktop>
 <631B1D4D-5473-4452-90DC-736D013D9136@blacknight.ie>
Message-ID: <9AA9525D-1484-49CD-AA87-BAA4F5067F63@blacknight.ie>

On 9 Mar 2011, at 11:08, Michele Neylon :: Blacknight wrote:

> 
> On 9 Mar 2011, at 10:56, Shane Kerr wrote:
>> 
>> 
>> AFAIK there have never been rules about who you can provide services to
>> with the address blocks you have been given. I would object strongly to
>> a proposal to do so.
> 
> 
> As would I
> 
> If network operators are abusing or allowing their networks to be abused then I can understand why some people might get upset, but I don't see why that should impact the rest of us. 
> 
> If I want to provide services to a company in Mongolia and we provide an allocation to them and it complies with the RIPE rules then it is none of anybody's business
> 
> Regards
> 
> Michele
> 


And of course Ronald probably won't even see my emails since he's blacklisted the entire blacknight.ie domain for some reason 

*sigh*


Mr Michele Neylon
Blacknight Solutions
Hosting & Colocation, Brand Protection
ICANN Accredited Registrar
http://www.blacknight.com/
http://blog.blacknight.com/
http://blacknight.mobi/
http://mneylon.tel
Intl. +353 (0) 59  9183072
US: 213-233-1612 
UK: 0844 484 9361
Locall: 1850 929 929
Direct Dial: +353 (0)59 9183090
Twitter: http://twitter.com/mneylon

PS: Check out our latest offers on domains & hosting: http://domainoffers.me/
-------------------------------
Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty
Road,Graiguecullen,Carlow,Ireland  Company No.: 370845





From ops.lists at gmail.com  Wed Mar  9 12:33:40 2011
From: ops.lists at gmail.com (Suresh Ramasubramanian)
Date: Wed, 9 Mar 2011 17:03:40 +0530
Subject: [anti-abuse-wg] RIPE policy
In-Reply-To: <4D7752F6.1050000@tana.it>
References: <28482.1299584054@tristatelogic.com>
	<AANLkTi=VKb2M_3Z2tji-Y3h3u=+qECr_=FMmjw-+oivR@mail.gmail.com>
	<4D766D44.4040400@tana.it>
	<201103081859.53378.peter@hk.ipsec.se>
	<AANLkTimGGsUsmnKuWY0dTNUs4=7iu_9acOjJdb8SRo2F@mail.gmail.com>
	<4D7752F6.1050000@tana.it>
Message-ID: <AANLkTimO-kTTzunKOgKbxsiuo8ynADxNok7-2K6yvH0J@mail.gmail.com>

I am aware of Levine's draft and it makes more sense than most things
I've read on this.  But that's putting the cart a bit before the horse
in this discussion - which is about trying to ensure that spammers
don't get /32 and larger v6 netblocks with the same ease they're
acquiring /15s and /16s.

As for IPs behind carrier grade NAT - just how many of those do you
see operating smtp servers? :)

thanks
--srs

On Wed, Mar 9, 2011 at 3:44 PM, Alessandro Vesely <vesely at tana.it> wrote:
>
> Yes, it is obviously possible. ?But discovering the right granularity
> and transmitting it to clients is problematic. ?For a possible
> solution see http://tools.ietf.org/html/draft-levine-iprangepub .
>
> OTOH, IPv4 extensively uses NAT, so that blocking the wrong IP may
> affect an entire network behind it. ?Traditional DNSBLs would be safer
> without such widespread use of NAT, which can be taken down using IPv6.



-- 
Suresh Ramasubramanian (ops.lists at gmail.com)



From rfg at tristatelogic.com  Wed Mar  9 13:06:04 2011
From: rfg at tristatelogic.com (Ronald F. Guilmette)
Date: Wed, 09 Mar 2011 04:06:04 -0800
Subject: [anti-abuse-wg] Re: Use of RIPE region space by out-of-region users, was RIPE policy
In-Reply-To: <1299668193.2210.12.camel@shane-desktop> 
Message-ID: <48942.1299672364@tristatelogic.com>

In message <1299668193.2210.12.camel at shane-desktop>, you wrote:

>Ronald,
>
>On Tue, 2011-03-08 at 20:45 -0800, Ronald F. Guilmette wrote:
>
>> I posted lists of IP addresses and domain names within several ``RIPE'' IP
>> address blocks that I allege have been handed over for use by American
>> bulk e-mail advertising companies.  (If you no longer have that e-mail or
>> those lists I will be happy to re-send them to you.)
>
>Looking at the first IP address in your list:

So you didn't bother to check any of the other blocks, correct?

What does traceroute  to, e.g., 178.215.176.99 indicate to you?

I'm not an expert in these things, so please do tell me what YOU think.

>AFAIK there have never been rules about who you can provide services to
>with the address blocks you have been given. I would object strongly to
>a proposal to do so.

Someone suggested that there already exists a policy to the effect that
providing IP block without also providing connectivity is a no-no.

Or did I misunderstand that?


Regards,
rfg



From rfg at tristatelogic.com  Wed Mar  9 13:43:34 2011
From: rfg at tristatelogic.com (Ronald F. Guilmette)
Date: Wed, 09 Mar 2011 04:43:34 -0800
Subject: [anti-abuse-wg] Use of RIPE region space by out-of-region users, was RIPE policy 
In-Reply-To: <9AA9525D-1484-49CD-AA87-BAA4F5067F63@blacknight.ie> 
Message-ID: <49174.1299674614@tristatelogic.com>

In message <9AA9525D-1484-49CD-AA87-BAA4F5067F63 at blacknight.ie>, 
"Michele Neylon :: Blacknight" <michele at blacknight.ie> wrote:

>
>On 9 Mar 2011, at 11:08, Michele Neylon :: Blacknight wrote:
>
>>
>> On 9 Mar 2011, at 10:56, Shane Kerr wrote:
>>>
>>>
>>> AFAIK there have never been rules about who you can provide services to
>>> with the address blocks you have been given. I would object strongly to
>>> a proposal to do so.
>>
>>
>> As would I
>>
>> If network operators are abusing or allowing their networks to be abused 
>then I can understand why some people might get upset, but I don't see why 
>that should impact the rest of us.
>>
>> If I want to provide services to a company in Mongolia and we provide an 
>allocation to them and it complies with the RIPE rules then it is none of a
>nybody's business
>>
>> Regards
>>
>> Michele
>>
>
>
>And of course Ronald probably won't even see my emails since he's blacklist
>ed the entire blacknight.ie domain for some reason
>
>*sigh*

Sigh indeed.

OK, let's take these one at a time.

Firstly, I saw what you wrote because you posted it to a mailing list that
I'm on.  (I'm sorry if this concept of an e-mail mailing list confuses you,
but there's really nothing I can do about that.  I'm also sorry that an
awful lot of people, here and elsewhere, seem not to have mastered their
mail clients well enough to avoid sending me a separate and duplicate
copy of whatever messages they post to the list and which I will see
there anyway... but that's also, apparently, not something that I can do
anything about.)

Secondly, regarding the local blacklisting of blacknight.ie, I can assure
you that it's nothing personal.  That happens to all domains that spam me.
If you want to see the spam that triggered that, ask and I'll be happy to
dig it out for you.  (There's a handy contact form on my web site for use
by folks in domains that are in the local blacklist.)

Thirdly, I just want to say that you guys are both a riot.  Really,  It's
rather hilarious how quick some folks are to defend against any perceived
attack on their own selfish interests (and pocketbooks) even when the only
threat is in their own minds.

How you guys got so far off into the weeds, and started talking about things
totally unrelated to the discussion at hand is beyond me.  You guys should
really consider joining the knee-jerk caucus of the Democratic Party here
in the U.S., so that, you know, when I say something simple and innocent
like "Our schools aren't doing a good job teaching kids English" you guys
can come up with an equally off-the-wall reaction, like asserting that I'm
obviously a racist because I demand that children in the U.S. learn English.

In short, get a grip.

If either of you would like to return to _this_ reality for a moment, you
may perhaps notice that (contrary to your bunker-mentality perception) I
actually _didn't_ attack your right to sell service to Mongolia, if that
is your wish.

I did (and do) however wonder out loud about RIPE policies when I see
what appears to be large scale waste and fraud relating to precious and
increasingly scarce number resources, and I did (and do) wonder about
cases where some ``provider'' in the RIPE region somehow manages to get
hold of a nice sized chunk of IPv4 space which is then, apparently, sold
off to an American mass e-mailing company with _no_ apparent connectivity
being associated with that deal... a practice that even the ICANN Political
Scientist fellow with the exceptionally thin skin seemed to indicate was
in fact a violation of *existing* RIPE policies.

OK, that's really all I had to say.  You may now proceed to misinterpret
and misconstrue _this_ message, as you did that last one, in a way that
best fits with your own preconceived and misplaced fears and concerns.


Regards,
rfg



From michele at blacknight.ie  Wed Mar  9 13:53:26 2011
From: michele at blacknight.ie (Michele Neylon :: Blacknight)
Date: Wed, 9 Mar 2011 12:53:26 +0000
Subject: [anti-abuse-wg] Use of RIPE region space by out-of-region
 users, was RIPE policy
In-Reply-To: <49174.1299674614@tristatelogic.com>
References: <49174.1299674614@tristatelogic.com>
Message-ID: <0DF22081-3CA4-4E6A-BC95-118CC8BCDE68@blacknight.ie>

On 9 Mar 2011, at 12:43, Ronald F. Guilmette wrote:
> Secondly, regarding the local blacklisting of blacknight.ie, I can assure
> you that it's nothing personal.  That happens to all domains that spam me.
> If you want to see the spam that triggered that, ask and I'll be happy to
> dig it out for you.  (There's a handy contact form on my web site for use
> by folks in domains that are in the local blacklist.)


Well if the form on your site loaded I would have .. 

It doesn't so I couldn't

If you could send it to me offlist or to abuse at blacknight.ie we will look into it


> 
> Thirdly, I just want to say that you guys are both a riot.  Really,  It's
> rather hilarious how quick some folks are to defend against any perceived
> attack on their own selfish interests (and pocketbooks) even when the only
> threat is in their own minds.
> 
> How you guys got so far off into the weeds, and started talking about things
> totally unrelated to the discussion at hand is beyond me.  You guys should
> really consider joining the knee-jerk caucus of the Democratic Party here
> in the U.S., so that, you know, when I say something simple and innocent
> like "Our schools aren't doing a good job teaching kids English" you guys
> can come up with an equally off-the-wall reaction, like asserting that I'm
> obviously a racist because I demand that children in the U.S. learn English.
> 
> In short, get a grip.
> 
> If either of you would like to return to _this_ reality for a moment, you
> may perhaps notice that (contrary to your bunker-mentality perception) I
> actually _didn't_ attack your right to sell service to Mongolia, if that
> is your wish.

Ok, but you didn't communicate that particularly clearly

> 
> I did (and do) however wonder out loud about RIPE policies when I see
> what appears to be large scale waste and fraud relating to precious and
> increasingly scarce number resources, and I did (and do) wonder about
> cases where some ``provider'' in the RIPE region somehow manages to get
> hold of a nice sized chunk of IPv4 space which is then, apparently, sold
> off to an American mass e-mailing company with _no_ apparent connectivity
> being associated with that deal... a practice that even the ICANN Political
> Scientist fellow with the exceptionally thin skin seemed to indicate was
> in fact a violation of *existing* RIPE policies.

See here you're not making any sense

I know you think you are, but you're actually ignoring reality

We have clients from the US (and elsewhere) that do not have a physical presence in Ireland or anywhere else in Europe.

If they are given an allocation of space it's obviously going to be assigned to them.

For all you know they could be using the space and servers etc., just to serve their EMEA clients ..

Now obviously if they're abusing the space and the policies then I'd love to see that addressed.. but I don't see why where a company is based is relevant

> 
> OK, that's really all I had to say.  You may now proceed to misinterpret
> and misconstrue _this_ message, as you did that last one, in a way that
> best fits with your own preconceived and misplaced fears and concerns.
> 
> 
> Regards,
> rfg
> 

Mr Michele Neylon
Blacknight Solutions
Hosting & Colocation, Brand Protection
ICANN Accredited Registrar
http://www.blacknight.com/
http://blog.blacknight.com/
http://blacknight.mobi/
http://mneylon.tel
Intl. +353 (0) 59  9183072
US: 213-233-1612 
UK: 0844 484 9361
Locall: 1850 929 929
Direct Dial: +353 (0)59 9183090
Twitter: http://twitter.com/mneylon

PS: Check out our latest offers on domains & hosting: http://domainoffers.me/
-------------------------------
Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty
Road,Graiguecullen,Carlow,Ireland  Company No.: 370845





From ops.lists at gmail.com  Wed Mar  9 14:13:43 2011
From: ops.lists at gmail.com (Suresh Ramasubramanian)
Date: Wed, 9 Mar 2011 18:43:43 +0530
Subject: [anti-abuse-wg] RIPE policy
In-Reply-To: <20110309125958.GY30227@Space.Net>
References: <28482.1299584054@tristatelogic.com>
	<AANLkTi=VKb2M_3Z2tji-Y3h3u=+qECr_=FMmjw-+oivR@mail.gmail.com>
	<4D766D44.4040400@tana.it>
	<201103081859.53378.peter@hk.ipsec.se>
	<AANLkTimGGsUsmnKuWY0dTNUs4=7iu_9acOjJdb8SRo2F@mail.gmail.com>
	<4D7752F6.1050000@tana.it>
	<AANLkTimO-kTTzunKOgKbxsiuo8ynADxNok7-2K6yvH0J@mail.gmail.com>
	<20110309125958.GY30227@Space.Net>
Message-ID: <AANLkTi=kxUaFCref2Oz7nhrswt4zDRQ1o54T04hEH9cM@mail.gmail.com>

If it was just spammers with large netblocks, great.  There is no
shortage of PI / PA netblocks which are used to host, for example,
malware c&c.

While what you say is more than probably correct, it is strange that
spammers seem to prefer the RIPE region, and working through some LIRs
in eastern europe, to acquiring large netblocks from any other RIR
region in the world.

On Wed, Mar 9, 2011 at 6:29 PM, Gert Doering <gert at space.net> wrote:
>
> As long as "the spammers" are providing correct corporate documents, and
> operate within their legal framework, I don't see any way to *deny* them
> IPv4/IPv6 addresses. ?"Sending lots of mail" might be a perfectly
> legitimate business in some country in the RIPE NCC service region, and
> as such, "need to use IP addresses for my legitimate business" is
> appropriate for a needs-based allocation system...
>



-- 
Suresh Ramasubramanian (ops.lists at gmail.com)



From shane at time-travellers.org  Wed Mar  9 14:16:02 2011
From: shane at time-travellers.org (Shane Kerr)
Date: Wed, 09 Mar 2011 14:16:02 +0100
Subject: [anti-abuse-wg] Re: Use of RIPE region space by out-of-region
 users, was RIPE policy
In-Reply-To: <48942.1299672364@tristatelogic.com>
References: <48942.1299672364@tristatelogic.com>
Message-ID: <1299676562.2210.43.camel@shane-desktop>

Ronald,

On Wed, 2011-03-09 at 04:06 -0800, Ronald F. Guilmette wrote:
> In message <1299668193.2210.12.camel at shane-desktop>, you wrote:
> 
> >Ronald,
> >
> >On Tue, 2011-03-08 at 20:45 -0800, Ronald F. Guilmette wrote:
> >
> >> I posted lists of IP addresses and domain names within several ``RIPE'' IP
> >> address blocks that I allege have been handed over for use by American
> >> bulk e-mail advertising companies.  (If you no longer have that e-mail or
> >> those lists I will be happy to re-send them to you.)
> >
> >Looking at the first IP address in your list:
> 
> So you didn't bother to check any of the other blocks, correct?

Well, you challenged Leo to pick one, so I did just that. Admittedly I
didn't pick one out of the middle. But you sent a list of over 4000 IP
addresses, surely you didn't think I would check them all?

> What does traceroute  to, e.g., 178.215.176.99 indicate to you?
> 
> I'm not an expert in these things, so please do tell me what YOU think.

Looks like it's going out of New York. If you look at the last couple
hops, we see:

      .
      .
      .
  9. xe-1-1-0.er1.lga5.us.above.n  0.0%    10   84.5  88.1  84.4 114.5   9.3
 10. 209.249.75.160                0.0%    10   85.3  85.1  84.1  86.3   0.8
 11. ???                          100.0    10    0.0   0.0   0.0   0.0   0.0
 12. 178.215.176.99               10.0%    10  153.8 156.3 153.8 158.1   1.4

We see that it seems to be coming from 209.249.75.160. 

That appears in the ARIN database as NET-209-249-75-0-1, which has the
following customer information:

CustName:       UNIVERSAL WEB DESIGN
Address:        320 7th Ave, Suite 134
City:           Brooklyn
StateProv:      NY
PostalCode:     00000
Country:        US
RegDate:        2004-03-23
Updated:        2004-03-23
Ref:            http://whois.arin.net/rest/customer/C00789085

So, my guess would be that the Ukrainian holder of this PI block decided
to have it hosted by an American company. That seems just as legitimate
as a Russian company providing services to an American company.

That's what *I* think.

I realize you're not an expert, but there may be some training available
from someone if you do want to become an expert in these things. I think
most of the RIRs have courses that they give to law enforcement
officials to help figure out the dispositions of various address blocks.
Maybe one of them would be willing to make some slide decks public?

> >AFAIK there have never been rules about who you can provide services to
> >with the address blocks you have been given. I would object strongly to
> >a proposal to do so.
> 
> Someone suggested that there already exists a policy to the effect that
> providing IP block without also providing connectivity is a no-no.
> 
> Or did I misunderstand that?

You did misunderstand that.

As I understand it, you can request IP space if you either are an LIR or
can find an LIR to request a PI block for you, and you have a need for
it. This need might be providing connectivity, but it could also be web
hosting, or video delivery, or download farms, or research networks, or
a million other purposes that may or may not have been invented yet.

What the other poster was suggesting is that the actual usage did not
match the documented usage. That is a "no-no", and I think what Suresh
was trying to make easier to identify with his proposal about making the
"descr:" more explicit.

--
Shane



From ripe-anti-spam-wg at powerweb.de  Wed Mar  9 14:18:18 2011
From: ripe-anti-spam-wg at powerweb.de (Frank Gadegast)
Date: Wed, 09 Mar 2011 14:18:18 +0100
Subject: [anti-abuse-wg] Use of RIPE region space by out-of-region users,
 was RIPE policy
In-Reply-To: <49174.1299674614@tristatelogic.com>
References: <49174.1299674614@tristatelogic.com>
Message-ID: <4D777E1A.2010303@powerweb.de>

Ronald F. Guilmette wrote:

First time its getting funny one this list ;o)

 > Thirdly, I just want to say that you guys are both a riot.  Really,
 > It's rather hilarious how quick some folks are to defend against any
 > perceived attack on their own selfish interests (and pocketbooks)
 > even when the only threat is in their own minds.

Thnx for that.
Its aweful true, that this abuse group does not make it any further,
because a lot of the people on this list fill their pockets with
"services" that really bother others.
Very sad, but true and as we can see here, theres nothing we can do
about this, until the community really introduces a few new concepts.

I just want to remember:
- we have no definition of abuse since this list is running
- the last and very good drafts, all helping to detect spam better,
   did not make it to reach consent

Why ?
Because its a comunity and even the arguments of people with
"filthy" practices count. That might be democratic, but does
not bring us any further.

Maybe RIPE should introduce real votes, where 50% are enough to accept 
drafts.

> Secondly, regarding the local blacklisting of blacknight.ie, I can assure
> you that it's nothing personal.  That happens to all domains that spam me.
> If you want to see the spam that triggered that, ask and I'll be happy to
> dig it out for you.  (There's a handy contact form on my web site for use
> by folks in domains that are in the local blacklist.)

Just want to add my opinion here:
its quite stupid to maintain sender domains in blacklists, because
sender domains are usually faked anyway.

I just hope for yourself, that you will never receive a spam having
your own domain as sender domain, making it quite hard for your
coworkers to write you some mail ;o)

> obviously a racist because I demand that children in the U.S. learn English.

And I recommend that we change the language on this list to German, 
French or any other European language ASAP !
There are less native english speaking people in Europe than a lot of
other languages, probably russian is the most spoken language in the
RIPE region ...

> I did (and do) however wonder out loud about RIPE policies when I see
> what appears to be large scale waste and fraud relating to precious and
> increasingly scarce number resources, and I did (and do) wonder about
> cases where some ``provider'' in the RIPE region somehow manages to get
> hold of a nice sized chunk of IPv4 space which is then, apparently, sold

Here I want to add some points:
- there are probably more stable tools out there to handle spam from
   IPv4 adresses than for IPv6
- we receive a much higher percentage of spam via IPv6 blocks than
   for IPv4, probably because we can filter them much better.
   thnx to all those different blacklists (that are still based on IPv4)
- we decided to block mail traffic from IPv6 completely and will not
   change that for a long time, because many professional spam farms
   already work on IPv6

> off to an American mass e-mailing company with _no_ apparent connectivity
> being associated with that deal... a practice that even the ICANN Political

Maybe they order housing services with them ?
We also have customers not located in Germany, that have servers in our
colocations.

> OK, that's really all I had to say.  You may now proceed to misinterpret
> and misconstrue _this_ message, as you did that last one, in a way that
> best fits with your own preconceived and misplaced fears and concerns.

All the best, Frank

> Regards,
> rfg

--
PHADE Software - PowerWeb                       http://www.powerweb.de
Inh. Dipl.-Inform. Frank Gadegast             mailto:frank at powerweb.de
Schinkelstrasse 17                                fon: +49 33200 52920
14558 Nuthetal OT Rehbruecke, Germany             fax: +49 33200 52921
======================================================================
Public PGP Key available for frank at powerweb.de



From rfg at tristatelogic.com  Wed Mar  9 14:26:18 2011
From: rfg at tristatelogic.com (Ronald F. Guilmette)
Date: Wed, 09 Mar 2011 05:26:18 -0800
Subject: [anti-abuse-wg] Use of RIPE region space by out-of-region users, was RIPE policy 
In-Reply-To: <0DF22081-3CA4-4E6A-BC95-118CC8BCDE68@blacknight.ie> 
Message-ID: <49525.1299677178@tristatelogic.com>

In message <0DF22081-3CA4-4E6A-BC95-118CC8BCDE68 at blacknight.ie>, 
"Michele Neylon :: Blacknight" <michele at blacknight.ie> wrote:

>
>On 9 Mar 2011, at 12:43, Ronald F. Guilmette wrote:
>> Secondly, regarding the local blacklisting of blacknight.ie, I can assure
>> you that it's nothing personal.  That happens to all domains that spam me=
>.
>> If you want to see the spam that triggered that, ask and I'll be happy to
>> dig it out for you.  (There's a handy contact form on my web site for use
>> by folks in domains that are in the local blacklist.)
>
>
>Well if the form on your site loaded I would have

Works for me.

>If you could send it to me offlist or to abuse at blacknight.ie we will look
>into it

Sent, as requested.

Was there some particular reasons why Nigerian fraudsters would have been
allowed to send e-mail through your servers in Jan of '010?  Did you have
a security melt down?

>> If either of you would like to return to _this_ reality for a moment, you
>> may perhaps notice that (contrary to your bunker-mentality perception) I
>> actually _didn't_ attack your right to sell service to Mongolia, if that
>> is your wish.
>
>Ok, but you didn't communicate that particularly clearly

Why do you say that?  Because I pointed out that in addition to eveything
else that made the IP blocks I posted aout fishy, they also just happened
to have been given over to _American_ mass e-mailers?

OK.  Gee.  Sorry.  Please strike the word "American".

>> I did (and do) however wonder out loud about RIPE policies when I see
>> what appears to be large scale waste and fraud relating to precious and
>> increasingly scarce number resources, and I did (and do) wonder about
>> cases where some ``provider'' in the RIPE region somehow manages to get
>> hold of a nice sized chunk of IPv4 space which is then, apparently, sold
>> off to an American mass e-mailing company with _no_ apparent connectivity
>> being associated with that deal... a practice that even the ICANN Politic=
>al
>> Scientist fellow with the exceptionally thin skin seemed to indicate was
>> in fact a violation of *existing* RIPE policies.
>
>See here you're not making any sense
>
>I know you think you are, but you're actually ignoring reality
>
>We have clients from the US (and elsewhere) that do not have a physical pre
>sence in Ireland or anywhere else in Europe.
>
>If they are given an allocation of space it's obviously going to be assigne
>d to them.

Do you have ``customers'' to whom you simply sell IP addresses, and nothing
else?

>For all you know they could be using the space and servers etc., just to se
>rve their EMEA clients ..

I have no idea what that stands for... Emerging Market E-mail Association?

>Now obviously if they're abusing the space and the policies then I'd love t
>o see that addressed..

If??

> but I don't see why where a company is based is relevant

Hey!  I don't make the rules.  I'm just trying to understand what they are

Maybe location _isn't_ actually relevant to anything, ever.  But it has
been my understanding that if a company from your side of the pond came
over and asked ARIN for a hunk of IPv4 space without so much as putting
a single server or router anywhere in North America, then you'd be politely
told to go fish.  (And likewise and conversely for someone on this side
of the pond, coming and asking RIPE for space.)

Did I misunderstand?

If not, then maybe location _does_ matter after all.  No?


Regards,
rfg



From michele at blacknight.ie  Wed Mar  9 14:39:28 2011
From: michele at blacknight.ie (Michele Neylon :: Blacknight)
Date: Wed, 9 Mar 2011 13:39:28 +0000
Subject: [anti-abuse-wg] Use of RIPE region space by out-of-region
 users, was RIPE policy
In-Reply-To: <49525.1299677178@tristatelogic.com>
References: <49525.1299677178@tristatelogic.com>
Message-ID: <6ECF18BD-3F5B-4E9C-917A-087ED01AF626@blacknight.ie>

On 9 Mar 2011, at 13:26, Ronald F. Guilmette wrote:

> 
> In message <0DF22081-3CA4-4E6A-BC95-118CC8BCDE68 at blacknight.ie>, 
> "Michele Neylon :: Blacknight" <michele at blacknight.ie> wrote:
> 
>> 
>> On 9 Mar 2011, at 12:43, Ronald F. Guilmette wrote:
>>> Secondly, regarding the local blacklisting of blacknight.ie, I can assure
>>> you that it's nothing personal.  That happens to all domains that spam me=
>> .
>>> If you want to see the spam that triggered that, ask and I'll be happy to
>>> dig it out for you.  (There's a handy contact form on my web site for use
>>> by folks in domains that are in the local blacklist.)
>> 
>> 
>> Well if the form on your site loaded I would have
> 
> Works for me.
> 
>> If you could send it to me offlist or to abuse at blacknight.ie we will look
>> into it
> 
> Sent, as requested.
> 
> Was there some particular reasons why Nigerian fraudsters would have been
> allowed to send e-mail through your servers in Jan of '010?  Did you have
> a security melt down?

ROFL

We are a hosting company.

Our clients can and do do silly things from time to time

If / when we get reports to our abuse desk about such behaviour we take action 

And blocking our domain name isn't exactly the sanest way of blocking junk from our network .. 


> 
>>> If either of you would like to return to _this_ reality for a moment, you
>>> may perhaps notice that (contrary to your bunker-mentality perception) I
>>> actually _didn't_ attack your right to sell service to Mongolia, if that
>>> is your wish.
>> 
>> Ok, but you didn't communicate that particularly clearly
> 
> Why do you say that?  Because I pointed out that in addition to eveything
> else that made the IP blocks I posted aout fishy, they also just happened
> to have been given over to _American_ mass e-mailers?
> 
> OK.  Gee.  Sorry.  Please strike the word "American".
> 
>>> I did (and do) however wonder out loud about RIPE policies when I see
>>> what appears to be large scale waste and fraud relating to precious and
>>> increasingly scarce number resources, and I did (and do) wonder about
>>> cases where some ``provider'' in the RIPE region somehow manages to get
>>> hold of a nice sized chunk of IPv4 space which is then, apparently, sold
>>> off to an American mass e-mailing company with _no_ apparent connectivity
>>> being associated with that deal... a practice that even the ICANN Politic=
>> al
>>> Scientist fellow with the exceptionally thin skin seemed to indicate was
>>> in fact a violation of *existing* RIPE policies.
>> 
>> See here you're not making any sense
>> 
>> I know you think you are, but you're actually ignoring reality
>> 
>> We have clients from the US (and elsewhere) that do not have a physical pre
>> sence in Ireland or anywhere else in Europe.
>> 
>> If they are given an allocation of space it's obviously going to be assigne
>> d to them.
> 
> Do you have ``customers'' to whom you simply sell IP addresses, and nothing
> else?


We don't sell IP addresses

We sell services which include IP allocations and LIR services

*cough*

We generally would hope that the clients would take bandwidth and other services from us, but we also have clients who pay us just for blocks of IPs and the management of same


> 
>> For all you know they could be using the space and servers etc., just to se
>> rve their EMEA clients ..
> 
> I have no idea what that stands for... Emerging Market E-mail Association?

Google it

If you are going to make silly assumptions based on your ignorance then I'm not going to jump through hoops to educate you

> 
>> Now obviously if they're abusing the space and the policies then I'd love t
>> o see that addressed..
> 
> If??

Yes - "if" it's a part of speech used in the English language in conditionals

http://www.merriam-webster.com/dictionary/conditional


> 
>> but I don't see why where a company is based is relevant
> 
> Hey!  I don't make the rules.  I'm just trying to understand what they are

Well I think you need to take that up with RIPE's policy people.


> 
> Maybe location _isn't_ actually relevant to anything, ever.  But it has
> been my understanding that if a company from your side of the pond came
> over and asked ARIN for a hunk of IPv4 space without so much as putting
> a single server or router anywhere in North America, then you'd be politely
> told to go fish.

Well we would only be doing that if we had kit in the US .. I can't think of any reason why we'd do it otherwise


>  (And likewise and conversely for someone on this side
> of the pond, coming and asking RIPE for space.)
> 
> Did I misunderstand?

I don't think so, but someone else might be able to correct me


> 
> If not, then maybe location _does_ matter after all.  No?

Location of what?

Location of the company isn't relevant. Location of network equipment probably is .. 

Regards

Michele


Mr Michele Neylon
Blacknight Solutions
Hosting & Colocation, Brand Protection
ICANN Accredited Registrar
http://www.blacknight.com/
http://blog.blacknight.com/
http://blacknight.mobi/
http://mneylon.tel
Intl. +353 (0) 59  9183072
US: 213-233-1612 
UK: 0844 484 9361
Locall: 1850 929 929
Direct Dial: +353 (0)59 9183090
Twitter: http://twitter.com/mneylon

PS: Check out our latest offers on domains & hosting: http://domainoffers.me/
-------------------------------
Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty
Road,Graiguecullen,Carlow,Ireland  Company No.: 370845





From gert at space.net  Wed Mar  9 13:59:59 2011
From: gert at space.net (Gert Doering)
Date: Wed, 9 Mar 2011 13:59:59 +0100
Subject: [anti-abuse-wg] RIPE policy
In-Reply-To: <AANLkTimO-kTTzunKOgKbxsiuo8ynADxNok7-2K6yvH0J@mail.gmail.com>
References: <28482.1299584054@tristatelogic.com>
 <AANLkTi=VKb2M_3Z2tji-Y3h3u=+qECr_=FMmjw-+oivR@mail.gmail.com>
 <4D766D44.4040400@tana.it>
 <201103081859.53378.peter@hk.ipsec.se>
 <AANLkTimGGsUsmnKuWY0dTNUs4=7iu_9acOjJdb8SRo2F@mail.gmail.com>
 <4D7752F6.1050000@tana.it>
 <AANLkTimO-kTTzunKOgKbxsiuo8ynADxNok7-2K6yvH0J@mail.gmail.com>
Message-ID: <20110309125958.GY30227@Space.Net>

Hi,

On Wed, Mar 09, 2011 at 05:03:40PM +0530, Suresh Ramasubramanian wrote:
[..]
> in this discussion - which is about trying to ensure that spammers
> don't get /32 and larger v6 netblocks with the same ease they're
> acquiring /15s and /16s.

This is about the gist of the current dispute, I'd say.

As long as "the spammers" are providing correct corporate documents, and
operate within their legal framework, I don't see any way to *deny* them
IPv4/IPv6 addresses.  "Sending lots of mail" might be a perfectly
legitimate business in some country in the RIPE NCC service region, and
as such, "need to use IP addresses for my legitimate business" is 
appropriate for a needs-based allocation system...

"Some people do not like what other people do with their addresses" is not
something the RIPE NCC can operate on - the RIRs (have to) operate on 
documented need, not on reputation.

Now, faked identity data, faked corporate documents, a judge that decides
that a given entity is violating the law - that's sufficient, of course,
as can be seen in the NCC draft document about closures.

Gert Doering
-- 
did you enable IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279



From ops.lists at gmail.com  Wed Mar  9 14:48:29 2011
From: ops.lists at gmail.com (Suresh Ramasubramanian)
Date: Wed, 9 Mar 2011 19:18:29 +0530
Subject: [anti-abuse-wg] Re: Use of RIPE region space by out-of-region
 users, was RIPE policy
In-Reply-To: <1299676562.2210.43.camel@shane-desktop>
References: <48942.1299672364@tristatelogic.com>
	<1299676562.2210.43.camel@shane-desktop>
Message-ID: <AANLkTi=N__1LByaLi_1gaJedJr76o-A8isjn2LOt0BR5@mail.gmail.com>

On Wed, Mar 9, 2011 at 6:46 PM, Shane Kerr <shane at time-travellers.org> wrote:
> Looks like it's going out of New York. If you look at the last couple
> hops, we see:

Yes.

> CustName: ? ? ? UNIVERSAL WEB DESIGN
> Address: ? ? ? ?320 7th Ave, Suite 134
> City: ? ? ? ? ? Brooklyn

Which happens to be a UPS store in Brooklyn ..
http://www.theupsstorelocal.com/3678/

> I realize you're not an expert, but there may be some training available
> from someone if you do want to become an expert in these things. I think
> most of the RIRs have courses that they give to law enforcement
> officials to help figure out the dispositions of various address blocks.
> Maybe one of them would be willing to make some slide decks public?

Let us put it this way, Shane - what Ron dug up does have a certain
piscine odor about it.

There's clearly a process hole that is causing large netblocks to be
allocated - mostly - as "vpn ranges", "dsl pools" etc and then
repurposed for bulk mail.

It could be a lack of accuracy in whois
It could be a window of opportunity that exists in the LIR process
that is vulnerable to abuse
It could be a disconnect between the RIPE anti abuse community and
more  mainstream / large SP antispam
[and all due respect to RFG, he isn't wired into that scene either]

Could be a combination of all those, and more.

1. This needs fixing - either tightening policies or their enforcement
2. This needs people who highlight problems

Ron is doing a decent job at #2, and we're all straying far afield from #1

--srs



From rfg at tristatelogic.com  Wed Mar  9 14:51:45 2011
From: rfg at tristatelogic.com (Ronald F. Guilmette)
Date: Wed, 09 Mar 2011 05:51:45 -0800
Subject: [anti-abuse-wg] Re: Use of RIPE region space by out-of-region users, was RIPE policy 
In-Reply-To: <1299676562.2210.43.camel@shane-desktop> 
Message-ID: <49697.1299678705@tristatelogic.com>

In message <1299676562.2210.43.camel at shane-desktop>, 
Shane Kerr <shane at time-travellers.org> wrote:

>> What does traceroute  to, e.g., 178.215.176.99 indicate to you?
>> 
>> I'm not an expert in these things, so please do tell me what YOU think.
>
>Looks like it's going out of New York.

"Going out of New York"??

Is there any evidence that the traceroute ever LEAVES New York, I mean
once it gets into the city?

If so, it sure isn't apparent to me.

>      .
>  9. xe-1-1-0.er1.lga5.us.above.n  0.0%    10   84.5  88.1  84.4 114.5   9.3
> 10. 209.249.75.160                0.0%    10   85.3  85.1  84.1  86.3   0.8
> 11. ???                          100.0    10    0.0   0.0   0.0   0.0   0.0
> 12. 178.215.176.99               10.0%    10  153.8 156.3 153.8 158.1   1.4
>
>We see that it seems to be coming from 209.249.75.160. 

Yes.  Quite.

>That appears in the ARIN database as NET-209-249-75-0-1, which has the
>following customer information:

Yes.  Some company in Brooklyn, NY.

>So, my guess would be that the Ukrainian holder of this PI block decided
>to have it hosted by an American company.

I wish there were an emoticon for a double-take.

As there isn't, I'll just say "Eh?? Come again??"

So let me see if I get this.  A ``provider'' in the RIPE region can go
to RIPE and ask for a hunk of IP space.  When RIPE gives the organization
in question the space, then that organization can just turn around and give
it to anybody else they damn well please.  They don't have to provide any
connectivity.  They can just take the block and have it ``hosted'' (your
word, not mine) with some totally different ACTUAL connectivity provider
elsewhere?  Is that what you are saying?

Does the organization that first obtained the space from RIPE even have
to be the one announcing routes to the space?

>That seems just as legitimate
>as a Russian company providing services to an American company.

What is the ``service'' that is being provided?  I mean other than being
the front-man who snookers RIPE out of the IP space (so that it can then
just be immediately resold to somebody else who will actually route it
and provide copper or fiber to it).

>> Someone suggested that there already exists a policy to the effect that
>> providing IP block without also providing connectivity is a no-no.
>> 
>> Or did I misunderstand that?
>
>You did misunderstand that.
>
>As I understand it, you can request IP space if you either are an LIR or
>can find an LIR to request a PI block for you, and you have a need for
>it. This need might be providing connectivity, but it could also be web
>hosting, or video delivery, or download farms, or research networks, or
>a million other purposes that may or may not have been invented yet.

Jesus!  Really?

*I* have a real, legitimate, and serious need for... umm... a /14 right now,
because you know, what with the economic crisis of the past couple of years
my retirement account has been seriously diminished, and I need to restore
it to its former glory if I am to have any hope of retiring this century.
So I "need" a /14 from RIPE.   I need it because there are a whole lot of
spammers on this side of the pond who will pay me Big Bucks for even just
a /21, and I can break up the /14 and resell it as a whole lot of of smaller
blocks (to the spammers).

So, um, where exactly does one apply for a RIPE IPv4 allocation?

I'll move to France if I have to.  It will be worth it.


Regards,
rfg


P.S.  I want to thank you for bringing this gold mine of an opportunity to
my attention.



From marcoh at marcoh.net  Wed Mar  9 14:48:31 2011
From: marcoh at marcoh.net (Marco Hogewoning)
Date: Wed, 9 Mar 2011 14:48:31 +0100
Subject: [anti-abuse-wg] RIPE policy
In-Reply-To: <4D7752F6.1050000@tana.it>
References: <28482.1299584054@tristatelogic.com>	<AANLkTi=VKb2M_3Z2tji-Y3h3u=+qECr_=FMmjw-+oivR@mail.gmail.com>	<4D766D44.4040400@tana.it>	<201103081859.53378.peter@hk.ipsec.se> <AANLkTimGGsUsmnKuWY0dTNUs4=7iu_9acOjJdb8SRo2F@mail.gmail.com> <4D7752F6.1050000@tana.it>
Message-ID: <B1439B3B-BDB6-44A9-A63F-2BCB3FF49251@marcoh.net>

> OTOH, IPv4 extensively uses NAT, so that blocking the wrong IP may
> affect an entire network behind it.  Traditional DNSBLs would be safer
> without such widespread use of NAT, which can be taken down using IPv6.

While on this topic, be aware the same could happen with IPv6 very easily. As people will no longer get a single address but a whole range, there will probably be some need to aggregate. As assignments per end site can vary between /64 and /48 you run the risk of blocking 65.000 customers while you intended to block one.

To partially solve these issues there is now a attribute in de RIPE Database called assignment size, indicating the size of assignment to a single end site. If you are working on black- or grey listings you might want to have a look at RIPE-513 which describes the use of this new attribute.

For your information,

MarcoH
(co-author of the document)


From ops.lists at gmail.com  Wed Mar  9 14:58:19 2011
From: ops.lists at gmail.com (Suresh Ramasubramanian)
Date: Wed, 9 Mar 2011 19:28:19 +0530
Subject: [anti-abuse-wg] RIPE policy
In-Reply-To: <B1439B3B-BDB6-44A9-A63F-2BCB3FF49251@marcoh.net>
References: <28482.1299584054@tristatelogic.com>
	<AANLkTi=VKb2M_3Z2tji-Y3h3u=+qECr_=FMmjw-+oivR@mail.gmail.com>
	<4D766D44.4040400@tana.it>
	<201103081859.53378.peter@hk.ipsec.se>
	<AANLkTimGGsUsmnKuWY0dTNUs4=7iu_9acOjJdb8SRo2F@mail.gmail.com>
	<4D7752F6.1050000@tana.it>
	<B1439B3B-BDB6-44A9-A63F-2BCB3FF49251@marcoh.net>
Message-ID: <AANLkTi=-zb8XAQ0cZTOwDLOgMgF4m+pMv2pu6Am3m8Km@mail.gmail.com>

On Wed, Mar 9, 2011 at 7:18 PM, Marco Hogewoning <marcoh at marcoh.net> wrote:
> To partially solve these issues there is now a attribute in de RIPE Database called assignment size, indicating the size of assignment to a single end site. If you are working on black- or grey listings you might want to have a look at RIPE-513 which describes the use of this new attribute.

Standardizing this across RIRs would be an idea.

-- 
Suresh Ramasubramanian (ops.lists at gmail.com)



From rfg at tristatelogic.com  Wed Mar  9 15:02:22 2011
From: rfg at tristatelogic.com (Ronald F. Guilmette)
Date: Wed, 09 Mar 2011 06:02:22 -0800
Subject: [anti-abuse-wg] Use of RIPE region space by out-of-region users, was RIPE policy 
In-Reply-To: <4D777E1A.2010303@powerweb.de> 
Message-ID: <49831.1299679342@tristatelogic.com>

In message <4D777E1A.2010303 at powerweb.de>, 
Frank Gadegast <ripe-anti-spam-wg at powerweb.de> wrote:

>Maybe RIPE should introduce real votes, where 50% are enough to accept 
>drafts.

I was not aware that this is NOT currently the case.

So, um, let me see if a get this... At this point in time, the folks in
Egypt have a more democratic system in place than RIPE does.  Is that
about the size of it?

>Just want to add my opinion here:
>its quite stupid to maintain sender domains in blacklists, because
>sender domains are usually faked anyway.

I can only agree, and that's why I don't ``maintain sender domains in
blacklists''.

If you assumed that I did, then you assumed wrong.

(Sorry.  I don't have time to provide a tutorial about Received: headers,
reverse DNS, and mail filtering just now.  Maybe later.)


Regards,
rfg



From marcoh at marcoh.net  Wed Mar  9 15:14:13 2011
From: marcoh at marcoh.net (Marco Hogewoning)
Date: Wed, 9 Mar 2011 15:14:13 +0100
Subject: [anti-abuse-wg] RIPE policy
In-Reply-To: <AANLkTi=-zb8XAQ0cZTOwDLOgMgF4m+pMv2pu6Am3m8Km@mail.gmail.com>
References: <28482.1299584054@tristatelogic.com> <AANLkTi=VKb2M_3Z2tji-Y3h3u=+qECr_=FMmjw-+oivR@mail.gmail.com> <4D766D44.4040400@tana.it> <201103081859.53378.peter@hk.ipsec.se> <AANLkTimGGsUsmnKuWY0dTNUs4=7iu_9acOjJdb8SRo2F@mail.gmail.com> <4D7752F6.1050000@tana.it> <B1439B3B-BDB6-44A9-A63F-2BCB3FF49251@marcoh.net> <AANLkTi=-zb8XAQ0cZTOwDLOgMgF4m+pMv2pu6Am3m8Km@mail.gmail.com>
Message-ID: <E8293F95-4427-42C9-A920-262A6295F4F1@marcoh.net>

On Mar 9, 2011, at 2:58 PM, Suresh Ramasubramanian wrote:

> On Wed, Mar 9, 2011 at 7:18 PM, Marco Hogewoning <marcoh at marcoh.net> wrote:
>> To partially solve these issues there is now a attribute in de RIPE Database called assignment size, indicating the size of assignment to a single end site. If you are working on black- or grey listings you might want to have a look at RIPE-513 which describes the use of this new attribute.
> 
> Standardizing this across RIRs would be an idea.

It would be a nice idea, in which case somebody needs to copy this, modify it to fit the database model and policy process for a specific region and submit it as a proposal.

My only experience is with RIPE, so it would be hard for me to do. Also some of my other positions make it difficult to submit policy proposals, especially in other regions. But if there are volunteers I'm happy to give some details, well in fact all details are published so feel free to pick from the original proposal (2010-06) and resulting documents.

Maro


From jorgen at hovland.cx  Wed Mar  9 15:14:41 2011
From: jorgen at hovland.cx (=?UTF-8?B?SsO4cmdlbiBIb3ZsYW5k?=)
Date: Wed, 09 Mar 2011 15:14:41 +0100
Subject: [anti-abuse-wg] RIPE policy
In-Reply-To: <AANLkTi=-zb8XAQ0cZTOwDLOgMgF4m+pMv2pu6Am3m8Km@mail.gmail.com>
References: <28482.1299584054@tristatelogic.com>	<AANLkTi=VKb2M_3Z2tji-Y3h3u=+qECr_=FMmjw-+oivR@mail.gmail.com>	<4D766D44.4040400@tana.it>	<201103081859.53378.peter@hk.ipsec.se>	<AANLkTimGGsUsmnKuWY0dTNUs4=7iu_9acOjJdb8SRo2F@mail.gmail.com>	<4D7752F6.1050000@tana.it>	<B1439B3B-BDB6-44A9-A63F-2BCB3FF49251@marcoh.net> <AANLkTi=-zb8XAQ0cZTOwDLOgMgF4m+pMv2pu6Am3m8Km@mail.gmail.com>
Message-ID: <4D778B51.3020301@hovland.cx>


On 03/09/11 14:58, Suresh Ramasubramanian wrote:
> On Wed, Mar 9, 2011 at 7:18 PM, Marco Hogewoning<marcoh at marcoh.net>  wrote:
>> To partially solve these issues there is now a attribute in de RIPE Database called assignment size, indicating the size of assignment to a single end site. If you are working on black- or grey listings you might want to have a look at RIPE-513 which describes the use of this new attribute.
> Standardizing this across RIRs would be an idea.
>

While the attribute may be good for informational and RIPE NCC 
policy-wise use, it is however unusable for any system that partition 
end-users/sites into particular ranges of ip-space such as blacklists 
and other types of restriction sysems.

If I write assignment-size 112 on my /48-block in the ripe db I can 
pretend to come from a billion companies. A system that believed that 
the assignment-size was indeed 112 could be subject to abuse. Therefore 
the problem remains and we still have to treat a /48 as equal to /128. 
This might force anyone to use /48 instead of /64, /96, /112 or whatever 
prefixlength that works for you. Perhaps that is good.

(Please don't reply with "there is enough ipv6-space anyway" :) The 
argument is void.)




From shane at time-travellers.org  Wed Mar  9 15:23:40 2011
From: shane at time-travellers.org (Shane Kerr)
Date: Wed, 09 Mar 2011 15:23:40 +0100
Subject: [anti-abuse-wg] Re: Use of RIPE region space by out-of-region
 users, was RIPE policy
In-Reply-To: <49697.1299678705@tristatelogic.com>
References: <49697.1299678705@tristatelogic.com>
Message-ID: <1299680620.2210.66.camel@shane-desktop>

Ronald,

On Wed, 2011-03-09 at 05:51 -0800, Ronald F. Guilmette wrote:
> >So, my guess would be that the Ukrainian holder of this PI block decided
> >to have it hosted by an American company.
> 
> I wish there were an emoticon for a double-take.
> 
> As there isn't, I'll just say "Eh?? Come again??"
> 
> So let me see if I get this.  A ``provider'' in the RIPE region can go
> to RIPE and ask for a hunk of IP space.  When RIPE gives the organization
> in question the space, then that organization can just turn around and give
> it to anybody else they damn well please.  They don't have to provide any
> connectivity.  They can just take the block and have it ``hosted'' (your
> word, not mine) with some totally different ACTUAL connectivity provider
> elsewhere?  Is that what you are saying?

Yes, that's right.

> Does the organization that first obtained the space from RIPE even have
> to be the one announcing routes to the space?

No, of course not. This is PI space - provider independent. There are
several different models for use of this space. One model is for the
organization to buy its own routers and act as network operators for the
space. Another model is to have someone else manage the space for you.
The important thing for the organization that receives the space is that
if they are unhappy with the service provided, that they can move to
another provider and not have to renumber.

> >> Someone suggested that there already exists a policy to the effect that
> >> providing IP block without also providing connectivity is a no-no.
> >> 
> >> Or did I misunderstand that?
> >
> >You did misunderstand that.
> >
> >As I understand it, you can request IP space if you either are an LIR or
> >can find an LIR to request a PI block for you, and you have a need for
> >it. This need might be providing connectivity, but it could also be web
> >hosting, or video delivery, or download farms, or research networks, or
> >a million other purposes that may or may not have been invented yet.
> 
> Jesus!  Really?
> 
> *I* have a real, legitimate, and serious need for... umm... a /14 right now,
> because you know, what with the economic crisis of the past couple of years
> my retirement account has been seriously diminished, and I need to restore
> it to its former glory if I am to have any hope of retiring this century.
> So I "need" a /14 from RIPE.   I need it because there are a whole lot of
> spammers on this side of the pond who will pay me Big Bucks for even just
> a /21, and I can break up the /14 and resell it as a whole lot of of smaller
> blocks (to the spammers).

I believe you can only get space you are going to use in the next 3
months now, although that may be even smaller. I don't know the exact
criteria, but it generally involves business plans and numbering and
suchlike. You may need to provide a list of your customers - again I
don't really know. In principle I believe that mass mailing meets the
requirements, but you'd probably need to get small blocks and then go
back to the RIPE NCC after you can demonstrate that each one has become
poisoned (probably pointing out the blackhole lists that you're on
should be enough).

> So, um, where exactly does one apply for a RIPE IPv4 allocation?

Either become an LIR:

https://www.ripe.net/lir-services/member-support/become-a-member

Or if you only need PI space, then contact an LIR in your area and ask
it to help you with your PI request:

https://www.ripe.net/membership/indices/

> I'll move to France if I have to.  It will be worth it.

Bon courage, mon ami!

--
Shane



From shane at time-travellers.org  Wed Mar  9 15:29:32 2011
From: shane at time-travellers.org (Shane Kerr)
Date: Wed, 09 Mar 2011 15:29:32 +0100
Subject: [anti-abuse-wg] Policy disallowing spam from RIPE blocks, was Use of RIPE region
 space by out-of-region users
In-Reply-To: <AANLkTi=N__1LByaLi_1gaJedJr76o-A8isjn2LOt0BR5@mail.gmail.com>
References: <48942.1299672364@tristatelogic.com>
	 <1299676562.2210.43.camel@shane-desktop>
	 <AANLkTi=N__1LByaLi_1gaJedJr76o-A8isjn2LOt0BR5@mail.gmail.com>
Message-ID: <1299680973.2210.72.camel@shane-desktop>

Suresh,

On Wed, 2011-03-09 at 19:18 +0530, Suresh Ramasubramanian wrote:
> 
> > CustName:       UNIVERSAL WEB DESIGN
> > Address:        320 7th Ave, Suite 134
> > City:           Brooklyn
> 
> Which happens to be a UPS store in Brooklyn ..
> http://www.theupsstorelocal.com/3678/

I guess ARIN needs to tighten their Whois policies then? ;)

> There's clearly a process hole that is causing large netblocks to be
> allocated - mostly - as "vpn ranges", "dsl pools" etc and then
> repurposed for bulk mail.
> 
> It could be a lack of accuracy in whois
> It could be a window of opportunity that exists in the LIR process
> that is vulnerable to abuse
> It could be a disconnect between the RIPE anti abuse community and
> more  mainstream / large SP antispam
> [and all due respect to RFG, he isn't wired into that scene either]
> 
> Could be a combination of all those, and more.
> 
> 1. This needs fixing - either tightening policies or their enforcement
> 2. This needs people who highlight problems
> 
> Ron is doing a decent job at #2, and we're all straying far afield from #1

As far as I can tell, the desire is to make it against the policies to
send spam from RIPE NCC address space. I find it incredibly frustrating
that nobody will actually just say that. :)

I think it will be very, very difficult to create such a policy. But I
am certainly willing to help anyone willing to make an attempt. What I
have not seen is any attempt, but rather complaints because it has not
been done.

If I'm missing the point and there is actually something else going on,
please someone clue me in!

If I am not missing the point, and the actual request is for an
anti-spam policy, then someone please propose something!

--
Shane



From ops.lists at gmail.com  Wed Mar  9 15:35:50 2011
From: ops.lists at gmail.com (Suresh Ramasubramanian)
Date: Wed, 9 Mar 2011 20:05:50 +0530
Subject: [anti-abuse-wg] Re: Use of RIPE region space by out-of-region
 users, was RIPE policy
In-Reply-To: <1299680620.2210.66.camel@shane-desktop>
References: <49697.1299678705@tristatelogic.com>
	<1299680620.2210.66.camel@shane-desktop>
Message-ID: <AANLkTin50nM9beuEEoiV5cWQAU4dX87-5mzg1AN90ujK@mail.gmail.com>

On Wed, Mar 9, 2011 at 7:53 PM, Shane Kerr <shane at time-travellers.org> wrote:
> In principle I believe that mass mailing meets the
> requirements, but you'd probably need to get small blocks and then go
> back to the RIPE NCC after you can demonstrate that each one has become
> poisoned (probably pointing out the blackhole lists that you're on
> should be enough).

Go through an LIR .. that approval doesn't seem to be needed at all.
Become an LIR yourself, or find yourself a suitable LIR and bob's your uncle.

-- 
Suresh Ramasubramanian (ops.lists at gmail.com)



From marcoh at marcoh.net  Wed Mar  9 15:42:18 2011
From: marcoh at marcoh.net (Marco Hogewoning)
Date: Wed, 9 Mar 2011 15:42:18 +0100
Subject: [anti-abuse-wg] RIPE policy
In-Reply-To: <4D778B51.3020301@hovland.cx>
References: <28482.1299584054@tristatelogic.com>	<AANLkTi=VKb2M_3Z2tji-Y3h3u=+qECr_=FMmjw-+oivR@mail.gmail.com>	<4D766D44.4040400@tana.it>	<201103081859.53378.peter@hk.ipsec.se>	<AANLkTimGGsUsmnKuWY0dTNUs4=7iu_9acOjJdb8SRo2F@mail.gmail.com>	<4D7752F6.1050000@tana.it>	<B1439B3B-BDB6-44A9-A63F-2BCB3FF49251@marcoh.net> <AANLkTi=-zb8XAQ0cZTOwDLOgMgF4m+pMv2pu6Am3m8Km@mail.gmail.com> <4D778B51.3020301@hovland.cx>
Message-ID: <F6E75712-C7A6-471E-A8A8-2542CF8884F5@marcoh.net>

> While the attribute may be good for informational and RIPE NCC policy-wise use, it is however unusable for any system that partition end-users/sites into particular ranges of ip-space such as blacklists and other types of restriction sysems.
> 
> If I write assignment-size 112 on my /48-block in the ripe db I can pretend to come from a billion companies. A system that believed that the assignment-size was indeed 112 could be subject to abuse. Therefore the problem remains and we still have to treat a /48 as equal to /128. This might force anyone to use /48 instead of /64, /96, /112 or whatever prefixlength that works for you. Perhaps that is good.

That's not the way it works, or at least that's not how it's intended to work. Unless we've overlooked some vital part in designing this system, in which case please explain and we'll find a drawing board again.

You can't easily set 'assignment-size: 112' on 'your' /48. The trick here is that it's your provider who sets it and not for individual assignments, but for a whole bunch in one go. Basically what they say is "In this block, any subnet of size X can be considered a single end site".

This won't work for PI assignments as per policy you shouldn't sub-assign those blocks. So although not up to me to decide, I can imagine any PI block with an assignment-size attribute might raise some questions. In fact the database should prohibit the creation of such an object, because it can be considered invalid.

So the only reasonable way to implement the situation you sketched is to ask your provider for a sub-allocation, instead of an assignment. While adding your maintainer to it and allow you to create the appropriate objects and attributes on or under the sub allocation.

I think the quick start manual for this would read something like:

"Do a lookup, if status is set to AGGREGATED-BY-LIR you can trust the assignment size and act accordingly. If status is 'ASSIGNED' use the object itself as an aggregation point. If in any other status you encounter the assignment-size attribute take it as a hint, but feel free to use your own aggregation scheme."

And as a concerned citizen,  one could add:

"Never aggregate above the size of the most specific database object or even never aggregate above the /64 level when in doubt. This will prevent collateral damage to other users and the reputation of your *list".

Now of course this is the way it works in the RIPE region. As I said before any attempt to copy this to another RIR would mean you have to take the 'local' situation into consideration and adjust the proposal where necessary.

Grtx,

Marco




From rfg at tristatelogic.com  Wed Mar  9 15:46:40 2011
From: rfg at tristatelogic.com (Ronald F. Guilmette)
Date: Wed, 09 Mar 2011 06:46:40 -0800
Subject: [anti-abuse-wg] Use of RIPE region space by out-of-region users, was RIPE policy 
In-Reply-To: <6ECF18BD-3F5B-4E9C-917A-087ED01AF626@blacknight.ie> 
Message-ID: <50222.1299682000@tristatelogic.com>

In message <6ECF18BD-3F5B-4E9C-917A-087ED01AF626 at blacknight.ie>, 
"Michele Neylon :: Blacknight" <michele at blacknight.ie> wrote:

>On 9 Mar 2011, at 13:26, Ronald F. Guilmette wrote:
>> Was there some particular reasons why Nigerian fraudsters would have been
>> allowed to send e-mail through your servers in Jan of '010?  Did you have
>> a security melt down?
>
>ROFL
>
>We are a hosting company.

Are you under the impression that this fact gives you some sort of special 
dispensation to send me spam?

If so, allow me to suggest, politely, that you reevaluate your assumptions.

>Our clients can and do do silly things from time to time

The way you say that, so nochalantly, it sounds to me like you have been aware
of this fact of human nature for quite some time now. Assuming so, what, if
anything, has your company done to compensate for it?

(Some other hosting companies who care about their reputations and about
not polluting the Internet have arranged for all outbound port 25 connects
from end-luser frequently-compromosed machines to be either blocked or else
transparently redirected to a machine, or set of machines, where outbound
filtering takes place... you know... in order to fully suppress the inevitable
and easily forseeable Nigerian 419 spam outflow from the inevitable and easily
forseeable compromised end-luser machine.)

>If / when we get reports to our abuse desk about such behaviour we take act
>ion

Right.

I think that's pretty much what the guys in charge of Chernobyl said too...
"Just let us know if there's a problem with these tests and we'll clean up
the mess afterwards."

Call me old-fashioned, but I've always believed that, all things considered,
it's better not to screw up in the first place than it is to apologize after-
wards.

In other words, the time to stop spam is quite certainly NOT after it has
already entered my inbox.  (It never ceases to amaze me how many providers
seem to think that they have earned some sort of accolades or appreciation
for their selfless act of shutting the barn door after the horses have
already bolted.)

>And blocking our domain name isn't exactly the sanest way of blocking junk
>from our network ..

Actually, it has worked with 100% effectivness.

What's insane is for people to accept the ludicrous notion that they should
spend their own time wading through reams of spam e-mail every day, just
because thousands of companies like your's don't much feel like investing
in proper spam outflow control.  (In my case I recognized a long time ago
that life is just too short.)

>>Do you have ``customers'' to whom you simply sell IP addresses, and nothing
>> else?
>
>
>We don't sell IP addresses
>
>We sell services which include IP allocations and LIR services
>
>*cough*
>
>We generally would hope that the clients would take bandwidth and other ser
>vices from us, but we also have clients who pay us just for blocks of IPs a
>nd the management of same

Facinating.  Really.

I really did construe from that other gentleman's remarks that this sort
of thing was entirely verboten, based on existing RIPE rules.

>>> but I don't see why where a company is based is relevant
>>
>> Hey!  I don't make the rules.  I'm just trying to understand what they are
>
>Well I think you need to take that up with RIPE's policy people.

Not necessary, as what you said (below) answers my question and also con-
forms to my existing understanding.

>> Maybe location _isn't_ actually relevant to anything, ever.  But it has
>> been my understanding that if a company from your side of the pond came
>> over and asked ARIN for a hunk of IPv4 space without so much as putting
>> a single server or router anywhere in North America, then you'd be politely
>> told to go fish.
>
>Well we would only be doing that if we had kit in the US .. I can't think o
>f any reason why we'd do it otherwise

OK, so you agree that with respect to IP address allocations, location _does_
nmatter in at least some contextx, e.g. when one is requesting an allocation
directly from an RiR, yes?

>Location of the company isn't relevant. Location of network equipment proba=
>bly is ..

OK.  Now we are getting somewhere.

Can you tell me what is the ``location of the network equipment'' with re-
spect to the RIPE-issued block 178.215.176.0/20?  Where does it seem to be?



From gert at space.net  Wed Mar  9 15:44:38 2011
From: gert at space.net (Gert Doering)
Date: Wed, 9 Mar 2011 15:44:38 +0100
Subject: [anti-abuse-wg] Use of RIPE region space by out-of-region users,
 was RIPE policy
In-Reply-To: <49831.1299679342@tristatelogic.com>
References: <4D777E1A.2010303@powerweb.de>
 <49831.1299679342@tristatelogic.com>
Message-ID: <20110309144438.GB30227@Space.Net>

Hi,

On Wed, Mar 09, 2011 at 06:02:22AM -0800, Ronald F. Guilmette wrote:
> Frank Gadegast <ripe-anti-spam-wg at powerweb.de> wrote:
> 
> >Maybe RIPE should introduce real votes, where 50% are enough to accept 
> >drafts.
> 
> I was not aware that this is NOT currently the case.

To clarify: 

 - the RIPE NCC and the RIPE AGM has voting, and counting of votes
   (this is the legal entity that handles the day to day work, the flow
   of money, serves as point of contact for legal enforcement agencies, 
   etc.)

 - the RIPE *community* (that sets the policy framework for the RIPE NCC) 
   operates on the basis of consensus - there's no voting here, because
   nobody ever figured out how to make voting work for "The Internet
   Community".

Gert Doering
        -- NetMaster
-- 
did you enable IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279



From ops.lists at gmail.com  Wed Mar  9 15:49:02 2011
From: ops.lists at gmail.com (Suresh Ramasubramanian)
Date: Wed, 9 Mar 2011 20:19:02 +0530
Subject: [anti-abuse-wg] Re: Policy disallowing spam from RIPE blocks, was Use of RIPE region
 space by out-of-region users
In-Reply-To: <1299680973.2210.72.camel@shane-desktop>
References: <48942.1299672364@tristatelogic.com>
	<1299676562.2210.43.camel@shane-desktop>
	<AANLkTi=N__1LByaLi_1gaJedJr76o-A8isjn2LOt0BR5@mail.gmail.com>
	<1299680973.2210.72.camel@shane-desktop>
Message-ID: <AANLkTi=9UZ0zxL9cRhGcRBi_LxfrfNgsf8NV10Yeh0Bh@mail.gmail.com>

Shane, nobody at all said what you're saying.  Not even RFG, funnily enough.

And if you want policy proposals, please do let me know what you think
about some concrete proposals that have emerged from all this argument
and ad hominem

1. Closing the allocation window / giving LIRs less leeway in
approvals [so there should be no difference in submitting a request
through a LIR, or through the RIR]

2. Increasing accuracy in whois (including the descr: field) <- note,
I am not saying "structure to a freeform field", just seeing that it
matches the justification paperwork and its use

and maybe a third -

3. Maybe some way to weed out bogus LIRs, tighten the process of new
LIR creation [or simply get rid of the entire LIR concept?]

--srs

On Wed, Mar 9, 2011 at 7:59 PM, Shane Kerr <shane at time-travellers.org> wrote:
> As far as I can tell, the desire is to make it against the policies to
> send spam from RIPE NCC address space. I find it incredibly frustrating
> that nobody will actually just say that. :)
>
> I think it will be very, very difficult to create such a policy. But I
> am certainly willing to help anyone willing to make an attempt. What I
> have not seen is any attempt, but rather complaints because it has not
> been done.
>
> If I'm missing the point and there is actually something else going on,
> please someone clue me in!
>
> If I am not missing the point, and the actual request is for an
> anti-spam policy, then someone please propose something!



-- 
Suresh Ramasubramanian (ops.lists at gmail.com)



From ops.lists at gmail.com  Wed Mar  9 15:53:47 2011
From: ops.lists at gmail.com (Suresh Ramasubramanian)
Date: Wed, 9 Mar 2011 20:23:47 +0530
Subject: [anti-abuse-wg] RIPE policy
In-Reply-To: <20110309145021.GC30227@Space.Net>
References: <28482.1299584054@tristatelogic.com>
	<AANLkTi=VKb2M_3Z2tji-Y3h3u=+qECr_=FMmjw-+oivR@mail.gmail.com>
	<4D766D44.4040400@tana.it>
	<201103081859.53378.peter@hk.ipsec.se>
	<AANLkTimGGsUsmnKuWY0dTNUs4=7iu_9acOjJdb8SRo2F@mail.gmail.com>
	<4D7752F6.1050000@tana.it>
	<AANLkTimO-kTTzunKOgKbxsiuo8ynADxNok7-2K6yvH0J@mail.gmail.com>
	<20110309125958.GY30227@Space.Net>
	<AANLkTi=kxUaFCref2Oz7nhrswt4zDRQ1o54T04hEH9cM@mail.gmail.com>
	<20110309145021.GC30227@Space.Net>
Message-ID: <AANLkTi=xQmy5djtFPU5g4pKJ_QCdQCvffnokuFSviWp7@mail.gmail.com>

On Wed, Mar 9, 2011 at 8:20 PM, Gert Doering <gert at space.net> wrote:
>
> I'm not sure about APNIC, though - I'd expect similar issues there.
>

Funnily enough, not that you'd notice at all.
So again, what makes RIPE unique here?

-- 
Suresh Ramasubramanian (ops.lists at gmail.com)



From ops.lists at gmail.com  Wed Mar  9 16:03:20 2011
From: ops.lists at gmail.com (Suresh Ramasubramanian)
Date: Wed, 9 Mar 2011 20:33:20 +0530
Subject: [anti-abuse-wg] RIPE policy
In-Reply-To: <20110309145514.GE30227@Space.Net>
References: <AANLkTi=VKb2M_3Z2tji-Y3h3u=+qECr_=FMmjw-+oivR@mail.gmail.com>
	<4D766D44.4040400@tana.it>
	<201103081859.53378.peter@hk.ipsec.se>
	<AANLkTimGGsUsmnKuWY0dTNUs4=7iu_9acOjJdb8SRo2F@mail.gmail.com>
	<4D7752F6.1050000@tana.it>
	<AANLkTimO-kTTzunKOgKbxsiuo8ynADxNok7-2K6yvH0J@mail.gmail.com>
	<20110309125958.GY30227@Space.Net>
	<AANLkTi=kxUaFCref2Oz7nhrswt4zDRQ1o54T04hEH9cM@mail.gmail.com>
	<20110309145021.GC30227@Space.Net>
	<AANLkTi=xQmy5djtFPU5g4pKJ_QCdQCvffnokuFSviWp7@mail.gmail.com>
	<20110309145514.GE30227@Space.Net>
Message-ID: <AANLkTimq1hPMSOsz7ypc6S-FYj3EiE6UDK55j8Q=Y6kz@mail.gmail.com>

On Wed, Mar 9, 2011 at 8:25 PM, Gert Doering <gert at space.net> wrote:
>
>> Funnily enough, not that you'd notice at all.
>> So again, what makes RIPE unique here?
>
> Dunno. ?Where's all the chinese-hosted spam coming from?

Large broadband pools infested with pirated windows machines, mainly.
 These are swipped to local chinese ISPs, who get their IP space from
CNNIC (and/or some older netblocks from APNIC)

In other words, what is happening there is a bunch of SPs with an
infested network who could do stuff like walled gardens, port 25
filtering etc.   I haven't seen spammers or malware artists getting
themselves a PI /15 from CNNIC or APNIC

Smaller netblocks direct from the RIR maybe.  Or hijacked IP space
repurposed from defunct companies.

Not one case that I can remember of PI /15s acquired through LIRs.

--srs

-- 
Suresh Ramasubramanian (ops.lists at gmail.com)



From gert at space.net  Wed Mar  9 15:50:21 2011
From: gert at space.net (Gert Doering)
Date: Wed, 9 Mar 2011 15:50:21 +0100
Subject: [anti-abuse-wg] RIPE policy
In-Reply-To: <AANLkTi=kxUaFCref2Oz7nhrswt4zDRQ1o54T04hEH9cM@mail.gmail.com>
References: <28482.1299584054@tristatelogic.com>
 <AANLkTi=VKb2M_3Z2tji-Y3h3u=+qECr_=FMmjw-+oivR@mail.gmail.com>
 <4D766D44.4040400@tana.it>
 <201103081859.53378.peter@hk.ipsec.se>
 <AANLkTimGGsUsmnKuWY0dTNUs4=7iu_9acOjJdb8SRo2F@mail.gmail.com>
 <4D7752F6.1050000@tana.it>
 <AANLkTimO-kTTzunKOgKbxsiuo8ynADxNok7-2K6yvH0J@mail.gmail.com>
 <20110309125958.GY30227@Space.Net>
 <AANLkTi=kxUaFCref2Oz7nhrswt4zDRQ1o54T04hEH9cM@mail.gmail.com>
Message-ID: <20110309145021.GC30227@Space.Net>

Hi,

On Wed, Mar 09, 2011 at 06:43:43PM +0530, Suresh Ramasubramanian wrote:
> If it was just spammers with large netblocks, great.  There is no
> shortage of PI / PA netblocks which are used to host, for example,
> malware c&c.
> 
> While what you say is more than probably correct, it is strange that
> spammers seem to prefer the RIPE region, and working through some LIRs
> in eastern europe, to acquiring large netblocks from any other RIR
> region in the world.

Without any scientific proof, my guess would be that the RIPE region
happens to be right in the middle of "there's a high number of very
different companies with wildly different legal systems and legal
enforcement capabilities" and "the infrastructure in the region is 
good and cheap enough to make it worthwile".

ARIN has the easy side regarding legal system - almost all of it is
"the US and Canada", so it's somewhat easier to verify documents, and
to actually figure out what activity *is* legal or not.  Something which
might be legal in NL can be frowned-upon in DE and punishable with
years of jail in RU - or vice versa.

Afrinic and Lacnic have historically just lacked the infrastructure
to setup a set of well-connected malware servers "quickly and inexpensively".

I'm not sure about APNIC, though - I'd expect similar issues there.

Gert Doering
        -- NetMaster
-- 
did you enable IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 306 bytes
Desc: not available
URL: <https://lists.ripe.net/ripe/mail/archives/anti-abuse-wg/attachments/20110309/37622955/attachment.sig>

From gert at space.net  Wed Mar  9 15:55:14 2011
From: gert at space.net (Gert Doering)
Date: Wed, 9 Mar 2011 15:55:14 +0100
Subject: [anti-abuse-wg] RIPE policy
In-Reply-To: <AANLkTi=xQmy5djtFPU5g4pKJ_QCdQCvffnokuFSviWp7@mail.gmail.com>
References: <AANLkTi=VKb2M_3Z2tji-Y3h3u=+qECr_=FMmjw-+oivR@mail.gmail.com>
 <4D766D44.4040400@tana.it>
 <201103081859.53378.peter@hk.ipsec.se>
 <AANLkTimGGsUsmnKuWY0dTNUs4=7iu_9acOjJdb8SRo2F@mail.gmail.com>
 <4D7752F6.1050000@tana.it>
 <AANLkTimO-kTTzunKOgKbxsiuo8ynADxNok7-2K6yvH0J@mail.gmail.com>
 <20110309125958.GY30227@Space.Net>
 <AANLkTi=kxUaFCref2Oz7nhrswt4zDRQ1o54T04hEH9cM@mail.gmail.com>
 <20110309145021.GC30227@Space.Net>
 <AANLkTi=xQmy5djtFPU5g4pKJ_QCdQCvffnokuFSviWp7@mail.gmail.com>
Message-ID: <20110309145514.GE30227@Space.Net>

Hi,

On Wed, Mar 09, 2011 at 08:23:47PM +0530, Suresh Ramasubramanian wrote:
> On Wed, Mar 9, 2011 at 8:20 PM, Gert Doering <gert at space.net> wrote:
> >
> > I'm not sure about APNIC, though - I'd expect similar issues there.
> 
> Funnily enough, not that you'd notice at all.
> So again, what makes RIPE unique here?

Dunno.  Where's all the chinese-hosted spam coming from?

Gert Doering
        -- NetMaster
-- 
did you enable IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 306 bytes
Desc: not available
URL: <https://lists.ripe.net/ripe/mail/archives/anti-abuse-wg/attachments/20110309/08fcc5a0/attachment.sig>

From brian.nisbet at heanet.ie  Wed Mar  9 16:19:51 2011
From: brian.nisbet at heanet.ie (Brian Nisbet)
Date: Wed, 09 Mar 2011 15:19:51 +0000
Subject: [anti-abuse-wg] Recent Trends in List Discussion & RIPE Policy
Message-ID: <4D779A97.7090707@heanet.ie>

Colleagues,

While much of the conversation on the list today has been informative, I 
would ask you all to refrain from ad hominem attacks and to try to avoid 
a descent into flamewars. There are many mailing lists (especially 
anti-abuse/anti-spam) on the Internet you can post to if you want to 
achieve that end.

This is, as we all know, an emotive issue, it is also one that, despite 
what people may say and think, is not being ignored by the RIPE 
Community nor the NCC. There is more work to be done, lots more, but 
there are limits to what can be done in some situations in the RIPE 
service region. Sending suggestions for policies, perhaps as a follow-up 
to sending a list of 4K IP addresses, is the best way to proceed if that 
is what you wish. Discuss those, go from there, contact 
aa-wg-chairs at ripe.net and we can discuss the Policy Development Process 
etc. But remember, policy, agreed by consensus, is the way to achieve 
things.

As a final note, the recent policies (2010-08, 2010-09 & 2010-10) have 
not gone away, the task force discussed at RIPE 61 has now been formed 
and, at the very least, there will be progress report at the WG session 
in Amsterdam this May.

Thanks,

Brian,
AA-WG Chair



From michele at blacknight.ie  Wed Mar  9 16:27:59 2011
From: michele at blacknight.ie (Michele Neylon :: Blacknight)
Date: Wed, 9 Mar 2011 15:27:59 +0000
Subject: [anti-abuse-wg] Use of RIPE region space by out-of-region
 users, was RIPE policy
In-Reply-To: <50222.1299682000@tristatelogic.com>
References: <50222.1299682000@tristatelogic.com>
Message-ID: <30BAC6E1-AE5C-4BEC-9CA7-8D44B9124647@blacknight.ie>

On 9 Mar 2011, at 14:46, Ronald F. Guilmette wrote:

>> 
>> 
>> We are a hosting company.
> 
> Are you under the impression that this fact gives you some sort of special 
> dispensation to send me spam?


I'm sorry, but I honestly don't know how you have the gall to make that kind of throwaway remark. 

Your manner of communicating is exactly why so few network operators take anti-spam / abuse people seriously.

You are your own worse enemies

It's a pity, but I've noticed this with a lot of American anti-abuse people. (Not as much with Europeans - they generally "get" the concepts of reality and non-parallel universes)


> 
> If so, allow me to suggest, politely, that you reevaluate your assumptions.
> 
>> Our clients can and do do silly things from time to time
> 
> The way you say that, so nochalantly, it sounds to me like you have been aware
> of this fact of human nature for quite some time now.

Yes. Of course. Most people know that other people do silly things 



> Assuming so, what, if
> anything, has your company done to compensate for it?
> 
> (Some other hosting companies who care about their reputations and about
> not polluting the Internet have arranged for all outbound port 25 connects
> from end-luser frequently-compromosed machines to be either blocked or else
> transparently redirected to a machine, or set of machines, where outbound
> filtering takes place... you know... in order to fully suppress the inevitable
> and easily forseeable Nigerian 419 spam outflow from the inevitable and easily
> forseeable compromised end-luser machine.)


Read our terms of service. http://www.blacknight.com/acceptable-usage.html

(And your entire commentary is based on some really odd assumptions.)



> 
> Actually, it has worked with 100% effectivness.

That's only coincidental .. 

Not causal
> 
> 
> I really did construe from that other gentleman's remarks that this sort
> of thing was entirely verboten, based on existing RIPE rules.

Not that I'm aware of

But if we are doing anything that we aren't meant to be doing I'm sure someone will tell us 

Regards

Michele




Mr Michele Neylon
Blacknight Solutions
Hosting & Colocation, Brand Protection
ICANN Accredited Registrar
http://www.blacknight.com/
http://blog.blacknight.com/
http://blacknight.mobi/
http://mneylon.tel
Intl. +353 (0) 59  9183072
US: 213-233-1612 
UK: 0844 484 9361
Locall: 1850 929 929
Direct Dial: +353 (0)59 9183090
Twitter: http://twitter.com/mneylon

PS: Check out our latest offers on domains & hosting: http://domainoffers.me/
-------------------------------
Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty
Road,Graiguecullen,Carlow,Ireland  Company No.: 370845





From ops.lists at gmail.com  Wed Mar  9 16:47:18 2011
From: ops.lists at gmail.com (Suresh Ramasubramanian)
Date: Wed, 9 Mar 2011 21:17:18 +0530
Subject: [anti-abuse-wg] Use of RIPE region space by out-of-region users,
 was RIPE policy
In-Reply-To: <30BAC6E1-AE5C-4BEC-9CA7-8D44B9124647@blacknight.ie>
References: <50222.1299682000@tristatelogic.com>
	<30BAC6E1-AE5C-4BEC-9CA7-8D44B9124647@blacknight.ie>
Message-ID: <AANLkTimE281OkZLF_DHdcF_DDZabnutPHTfK=Ka2xfdd@mail.gmail.com>

On Wed, Mar 9, 2011 at 8:57 PM, Michele Neylon :: Blacknight
<michele at blacknight.ie> wrote:
>
> It's a pity, but I've noticed this with a lot of American anti-abuse people. (Not as much with Europeans - they generally "get" the concepts of reality and non-parallel universes)

Been to many MAAWGs yet?

cheers
--srs (from india, if that matters when we're generalizing)

-- 
Suresh Ramasubramanian (ops.lists at gmail.com)



From ripe-anti-spam-wg at powerweb.de  Wed Mar  9 17:18:58 2011
From: ripe-anti-spam-wg at powerweb.de (Frank Gadegast)
Date: Wed, 09 Mar 2011 17:18:58 +0100
Subject: [anti-abuse-wg] draft policy
In-Reply-To: <20110309144438.GB30227@Space.Net>
References: <4D777E1A.2010303@powerweb.de> <49831.1299679342@tristatelogic.com> <20110309144438.GB30227@Space.Net>
Message-ID: <4D77A872.5010107@powerweb.de>

Gert Doering wrote:
> Hi,
>

Hi,

> On Wed, Mar 09, 2011 at 06:02:22AM -0800, Ronald F. Guilmette wrote:
>> Frank Gadegast<ripe-anti-spam-wg at powerweb.de>  wrote:
>>
>>> Maybe RIPE should introduce real votes, where 50% are enough to accept
>>> drafts.
>>
>> I was not aware that this is NOT currently the case.
>
> To clarify:
>
>   - the RIPE NCC and the RIPE AGM has voting, and counting of votes
>     (this is the legal entity that handles the day to day work, the flow
>     of money, serves as point of contact for legal enforcement agencies,
>     etc.)
>
>   - the RIPE *community* (that sets the policy framework for the RIPE NCC)
>     operates on the basis of consensus - there's no voting here, because
>     nobody ever figured out how to make voting work for "The Internet
>     Community".

And thats really a point to question these days.

RIPE is the only organisation Im a member of, that allows non-members
to tell them what to do.
Its really strange, that any Internetuser worldwide capable of
working an mailclient can contribute to the process of consensus
and can be part of the descisions how RIPe handles their resources.

And it seems to be an important part, that the leader of any group
has to decide if consensus has been reached about a draft, before
the draft can reach the next step.
Its not very democratic if the whole process can be stopped
- either by a bunch of people that are neither RIPE members
   nor even located in the RIPE region
- of by the working group leader (that should defny be his role)

I defny vote for that RIPE drafts should only be discussed
by RIPE members and that a 50% votes of RIPE members are enough
to accept a draft.

Think of the following:
if I would be AT&T and like to fight against German Telekom
as a big competitor in the US market, I would get a thousand
US customers, that like to have cheaper rates, and file
a draft at RIPE that will cost all RIPE members a lot
of money ...


Kind regards, Frank

P.S.: uups, have to go now, several if our POP/IMAP server seems to be
       under attack by a password scanner just in this moment.
       Have to check, if our Anti-DDOS-Tools catch them all right.

       Interesting, this time coming from
       adsl-75-18-71-221.dsl.chcgil.sbcglobal.net
       AT&T is misusing the resources they got from ARIN
       in a very illegal way here :o)
       And they did not even write
       Descr: POP/IMAP password scanner to get hold of user passwords
       Descr: for illegal activities
       in there description field !




> Gert Doering
>          -- NetMaster


-- 

Kind regards, Frank
--
PHADE Software - PowerWeb                       http://www.powerweb.de
Inh. Dipl.-Inform. Frank Gadegast             mailto:frank at powerweb.de
Schinkelstrasse 17                                fon: +49 33200 52920
14558 Nuthetal OT Rehbruecke, Germany             fax: +49 33200 52921
======================================================================



From ops.lists at gmail.com  Wed Mar  9 17:27:04 2011
From: ops.lists at gmail.com (Suresh Ramasubramanian)
Date: Wed, 9 Mar 2011 21:57:04 +0530
Subject: [anti-abuse-wg] draft policy
In-Reply-To: <4D77A872.5010107@powerweb.de>
References: <4D777E1A.2010303@powerweb.de>
	<49831.1299679342@tristatelogic.com>
	<20110309144438.GB30227@Space.Net>
	<4D77A872.5010107@powerweb.de>
Message-ID: <AANLkTikKvMmiymvuCMij=bYhW1Vbs7V5=2oAtsSxemRc@mail.gmail.com>

This, mein herr, is what you'd call missing the forest for the trees.

Or rather looking at a weed in a kitchen garden (a botted IP in a dsl
range somewhere) compared to a large patch of water hyacinth in a lake

On Wed, Mar 9, 2011 at 9:48 PM, Frank Gadegast
<ripe-anti-spam-wg at powerweb.de> wrote:
>
> ? ? ?Interesting, this time coming from
> ? ? ?adsl-75-18-71-221.dsl.chcgil.sbcglobal.net
> ? ? ?AT&T is misusing the resources they got from ARIN
> ? ? ?in a very illegal way here :o)
> ? ? ?And they did not even write
> ? ? ?Descr: POP/IMAP password scanner to get hold of user passwords
> ? ? ?Descr: for illegal activities
> ? ? ?in there description field !



-- 
Suresh Ramasubramanian (ops.lists at gmail.com)



From rhe at nosc.ja.net  Wed Mar  9 17:30:27 2011
From: rhe at nosc.ja.net (Rob Evans)
Date: Wed, 09 Mar 2011 16:30:27 +0000
Subject: [anti-abuse-wg] draft policy
In-Reply-To: <4D77A872.5010107@powerweb.de>
References: <4D777E1A.2010303@powerweb.de> <49831.1299679342@tristatelogic.com> <20110309144438.GB30227@Space.Net> <4D77A872.5010107@powerweb.de>
Message-ID: <4D77AB23.7060806@nosc.ja.net>

> I defny vote for that RIPE drafts should only be discussed
> by RIPE members and that a 50% votes of RIPE members are enough
> to accept a draft.

Therein lies stagnation, but perhaps that is what you're aiming for?

Assuming you mean RIPE NCC members (anybody can be a member of RIPE, it 
is just a community, and your guess as to the number of members of the 
community is as good as anybody's), then when I looked a couple of years 
ago, 2% of RIPE NCC members voted for the members of the NCC's executive 
board.

2%.

How many of the members do you think get actively involved in policy 
discussions?  (Hint: it is much less than 50%.)

All of the RIRs have open policy discussion forums, just as the IETF has 
no members and anybody can contribute to the Internet's standards.  Good 
luck changing that. :)

Rob



From ripe-anti-spam-wg at powerweb.de  Wed Mar  9 18:20:56 2011
From: ripe-anti-spam-wg at powerweb.de (Frank Gadegast)
Date: Wed, 09 Mar 2011 18:20:56 +0100
Subject: [anti-abuse-wg] draft policy
In-Reply-To: <4D77AB23.7060806@nosc.ja.net>
References: <4D777E1A.2010303@powerweb.de> <49831.1299679342@tristatelogic.com> <20110309144438.GB30227@Space.Net> <4D77A872.5010107@powerweb.de> <4D77AB23.7060806@nosc.ja.net>
Message-ID: <4D77B6F8.70507@powerweb.de>

Rob Evans wrote:
>> I defny vote for that RIPE drafts should only be discussed
>> by RIPE members and that a 50% votes of RIPE members are enough
>> to accept a draft.
>
> Therein lies stagnation, but perhaps that is what you're aiming for?
>
> Assuming you mean RIPE NCC members (anybody can be a member of RIPE, it
> is just a community, and your guess as to the number of members of the
> community is as good as anybody's), then when I looked a couple of years
> ago, 2% of RIPE NCC members voted for the members of the NCC's executive
> board.
>
> 2%.

Nobody is talking about members that are NOT voting.
50% of the people that ARE voting should count.
So, according to your numbers: 1% is enough

> How many of the members do you think get actively involved in policy
> discussions? (Hint: it is much less than 50%.)

People that are not going to vote do not care for the results,
like it is for any democratic political vote in the RIPE region.

> All of the RIRs have open policy discussion forums, just as the IETF has
> no members and anybody can contribute to the Internet's standards. Good
> luck changing that. :)

IETF is different.

RIPE is no "community", its more a association of members, that are
paying money to get resources they need.
And non-members still can decide (or at least block) the wishes
of the members, thats really crazy.

Lets compare: DENIC is also an association of members wich pay
for the resources they need.
Do you think anybody can tell DENIC how to deal with .de domainnames or 
decide about the whois or technical procedures and protocols, if they 
are not a member ?
Sure not.

This is not stopping you from becoming a member, anybody can become a 
member according to the current rules, after he is a member, he can
start changing things, but not before.

So: why should the opinions of non-members count at RIPE, when its
going about the consensus about drafts ?



Kind regards, Frank

>
> Rob
>
>


-- 

Mit freundlichen Gruessen,
--
PHADE Software - PowerWeb                       http://www.powerweb.de
Inh. Dipl.-Inform. Frank Gadegast             mailto:frank at powerweb.de
Schinkelstrasse 17                                fon: +49 33200 52920
14558 Nuthetal OT Rehbruecke, Germany             fax: +49 33200 52921
======================================================================



From brian.nisbet at heanet.ie  Wed Mar  9 18:28:03 2011
From: brian.nisbet at heanet.ie (Brian Nisbet)
Date: Wed, 09 Mar 2011 17:28:03 +0000
Subject: [anti-abuse-wg] draft policy
In-Reply-To: <4D77B6F8.70507@powerweb.de>
References: <4D777E1A.2010303@powerweb.de> <49831.1299679342@tristatelogic.com> <20110309144438.GB30227@Space.Net> <4D77A872.5010107@powerweb.de> <4D77AB23.7060806@nosc.ja.net> <4D77B6F8.70507@powerweb.de>
Message-ID: <4D77B8A3.3060207@heanet.ie>

Frank,

"Frank Gadegast" wrote the following on 09/03/2011 17:20:
>
>> How many of the members do you think get actively involved in policy
>> discussions? (Hint: it is much less than 50%.)
>
> People that are not going to vote do not care for the results,
> like it is for any democratic political vote in the RIPE region.

Not always true, but that's philosophy.

>> All of the RIRs have open policy discussion forums, just as the IETF has
>> no members and anybody can contribute to the Internet's standards. Good
>> luck changing that. :)
>
> IETF is different.
>
> RIPE is no "community", its more a association of members, that are
> paying money to get resources they need.
> And non-members still can decide (or at least block) the wishes
> of the members, thats really crazy.

RIPE is a community. The association of members are RIPE NCC members, 
who pay a membership fee. Policy is made by the community, members of 
the NCC vote on motions to do with the NCC.

This distinction really is vital to all of this.

Brian.



From fweimer at bfk.de  Wed Mar  9 18:38:26 2011
From: fweimer at bfk.de (Florian Weimer)
Date: Wed, 09 Mar 2011 17:38:26 +0000
Subject: [anti-abuse-wg] draft policy
In-Reply-To: <4D77B6F8.70507@powerweb.de> (Frank Gadegast's message of "Wed\, 09 Mar 2011 18\:20\:56 +0100")
References: <4D777E1A.2010303@powerweb.de>
	<49831.1299679342@tristatelogic.com>
	<20110309144438.GB30227@Space.Net> <4D77A872.5010107@powerweb.de>
	<4D77AB23.7060806@nosc.ja.net> <4D77B6F8.70507@powerweb.de>
Message-ID: <821v2g8a99.fsf@mid.bfk.de>

* Frank Gadegast:

> Do you think anybody can tell DENIC how to deal with .de domainnames
> or decide about the whois or technical procedures and protocols, if
> they are not a member ?

German citizens surely can, indirectly, through the branches of
representative government.

-- 
Florian Weimer                <fweimer at bfk.de>
BFK edv-consulting GmbH       http://www.bfk.de/
Kriegsstra?e 100              tel: +49-721-96201-1
D-76133 Karlsruhe             fax: +49-721-96201-99



From ripe-anti-spam-wg at powerweb.de  Wed Mar  9 19:27:02 2011
From: ripe-anti-spam-wg at powerweb.de (Frank Gadegast)
Date: Wed, 09 Mar 2011 19:27:02 +0100
Subject: [anti-abuse-wg] draft policy
In-Reply-To: <821v2g8a99.fsf@mid.bfk.de>
References: <4D777E1A.2010303@powerweb.de>	<49831.1299679342@tristatelogic.com>	<20110309144438.GB30227@Space.Net> <4D77A872.5010107@powerweb.de>	<4D77AB23.7060806@nosc.ja.net> <4D77B6F8.70507@powerweb.de> <821v2g8a99.fsf@mid.bfk.de>
Message-ID: <4D77C676.7010305@powerweb.de>

Florian Weimer wrote:
> * Frank Gadegast:
>
>> Do you think anybody can tell DENIC how to deal with .de domainnames
>> or decide about the whois or technical procedures and protocols, if
>> they are not a member ?
>
> German citizens surely can, indirectly, through the branches of
> representative government.
>

Sorry, they cant.

DENIC is a "e.g.", an "eingetragene Gemeinschaft", a "registered 
association".

The only thing German citizens could decide is wich party they like on 
the next German Government vote.

Those parties could then decide to make a law, that the DENIC e.g. is 
not responsible for the .de TLD anymore.

But the German citizens could not at all through whatever government 
could tell DENIC what to do.


-- 

Kind regards, Frank
--
PHADE Software - PowerWeb                       http://www.powerweb.de
Inh. Dipl.-Inform. Frank Gadegast             mailto:frank at powerweb.de
Schinkelstrasse 17                                fon: +49 33200 52920
14558 Nuthetal OT Rehbruecke, Germany             fax: +49 33200 52921
======================================================================



From ripe-anti-spam-wg at powerweb.de  Wed Mar  9 19:40:10 2011
From: ripe-anti-spam-wg at powerweb.de (Frank Gadegast)
Date: Wed, 09 Mar 2011 19:40:10 +0100
Subject: [anti-abuse-wg] draft policy
In-Reply-To: <4D77B8A3.3060207@heanet.ie>
References: <4D777E1A.2010303@powerweb.de> <49831.1299679342@tristatelogic.com> <20110309144438.GB30227@Space.Net> <4D77A872.5010107@powerweb.de> <4D77AB23.7060806@nosc.ja.net> <4D77B6F8.70507@powerweb.de> <4D77B8A3.3060207@heanet.ie>
Message-ID: <4D77C98A.7030504@powerweb.de>

Brian Nisbet wrote:
> Frank,
>
> "Frank Gadegast" wrote the following on 09/03/2011 17:20:
>>
>>> How many of the members do you think get actively involved in policy
>>> discussions? (Hint: it is much less than 50%.)
>>
>> People that are not going to vote do not care for the results,
>> like it is for any democratic political vote in the RIPE region.
>
> Not always true, but that's philosophy.

No, its called democracy.

>>> All of the RIRs have open policy discussion forums, just as the IETF has
>>> no members and anybody can contribute to the Internet's standards. Good
>>> luck changing that. :)
>>
>> IETF is different.
>>
>> RIPE is no "community", its more a association of members, that are
>> paying money to get resources they need.
>> And non-members still can decide (or at least block) the wishes
>> of the members, thats really crazy.
>
> RIPE is a community. The association of members are RIPE NCC members,
> who pay a membership fee. Policy is made by the community, members of
> the NCC vote on motions to do with the NCC.

So the world-wide community tells RIPE NCC (and their members) what the 
members are going to do with their money they pay for RIPE NCCs services ?

Sorry, do you mean, what your saying ?

> This distinction really is vital to all of this.

Not at all, when is going up for decissions.

Sure, comments and input are vital for this process.
the communication with other RIRs and their LIRs is important.

But: but RIPE NCC members should really be able to decide, what
theye are doing with there resources and how they are giving them
to their members.

I just remember Tobias' last drafts, they someehow simply "ended".
I do not remember, that a vote was taking place.
How can that happen at all ?


I have an idea:
I gonna pay about 5000 people worldwide 10$ if they vote for, that
small LIRs do not have to pay for the services anymore and just the big 
ones have to pay.
5000 people worldwide will mean consensus in the RIPE community.
And I will have all the small LIRs on me side too.
And I will save money in a couple of years.

Or think about: spammers paying the community to give them more IPs ...
absolutly legaly.



Kind regards, Frank


>
> Brian.
>
>


-- 

Mit freundlichen Gruessen,
--
PHADE Software - PowerWeb                       http://www.powerweb.de
Inh. Dipl.-Inform. Frank Gadegast             mailto:frank at powerweb.de
Schinkelstrasse 17                                fon: +49 33200 52920
14558 Nuthetal OT Rehbruecke, Germany             fax: +49 33200 52921
======================================================================



From shane at time-travellers.org  Wed Mar  9 20:18:46 2011
From: shane at time-travellers.org (Shane Kerr)
Date: Wed, 09 Mar 2011 20:18:46 +0100
Subject: [anti-abuse-wg] Off-topic: German government involvement with DENIC policy, was
 draft policy
In-Reply-To: <4D77C676.7010305@powerweb.de>
References: <4D777E1A.2010303@powerweb.de>
	 <49831.1299679342@tristatelogic.com>	<20110309144438.GB30227@Space.Net>
	 <4D77A872.5010107@powerweb.de>	<4D77AB23.7060806@nosc.ja.net>
	 <4D77B6F8.70507@powerweb.de> <821v2g8a99.fsf@mid.bfk.de>
	 <4D77C676.7010305@powerweb.de>
Message-ID: <1299698326.2210.91.camel@shane-desktop>

Frank,

On Wed, 2011-03-09 at 19:27 +0100, Frank Gadegast wrote:
> But the German citizens could not at all through whatever government 
> could tell DENIC what to do.

This really is wildly off-topic, but exactly this happened:

http://www.dmueller.com/2009/10/18/domain-names-domains/denic-to-make-million-dollar-domains-available-for-the-first-time/

A reminder that governments are the ones in charge. :)

--
Shane



From michele at blacknight.ie  Wed Mar  9 20:21:06 2011
From: michele at blacknight.ie (Michele Neylon :: Blacknight)
Date: Wed, 9 Mar 2011 19:21:06 +0000
Subject: [anti-abuse-wg] draft policy
In-Reply-To: <4D77C676.7010305@powerweb.de>
References: <4D777E1A.2010303@powerweb.de>
	<49831.1299679342@tristatelogic.com>	<20110309144438.GB30227@Space.Net>
 <4D77A872.5010107@powerweb.de>	<4D77AB23.7060806@nosc.ja.net>
 <4D77B6F8.70507@powerweb.de> <821v2g8a99.fsf@mid.bfk.de>
 <4D77C676.7010305@powerweb.de>
Message-ID: <B78DC8A0-412F-4C76-BDC1-6E229F0360F6@blacknight.ie>

On 9 Mar 2011, at 18:27, Frank Gadegast wrote:

> Florian Weimer wrote:
>> * Frank Gadegast:
>> 
>>> Do you think anybody can tell DENIC how to deal with .de domainnames
>>> or decide about the whois or technical procedures and protocols, if
>>> they are not a member ?
>> 
>> German citizens surely can, indirectly, through the branches of
>> representative government.
>> 
> 
> Sorry, they cant.
> 
> DENIC is a "e.g.", an "eingetragene Gemeinschaft", a "registered association".
> 
> The only thing German citizens could decide is wich party they like on the next German Government vote.
> 
> Those parties could then decide to make a law, that the DENIC e.g. is not responsible for the .de TLD anymore.
> 
> But the German citizens could not at all through whatever government could tell DENIC what to do.

That's not really true either

DENIC is subject to German law.

If German law forbade X then DENIC would not be able to do X

Having said that, the German government does not currently have direct control over DENIC. It can, of course, influence it indirectly

This is pretty much the same with all ccTLDs :)




Mr Michele Neylon
Blacknight Solutions
Hosting & Colocation, Brand Protection
ICANN Accredited Registrar
http://www.blacknight.com/
http://blog.blacknight.com/
http://blacknight.mobi/
http://mneylon.tel
Intl. +353 (0) 59  9183072
US: 213-233-1612 
UK: 0844 484 9361
Direct Dial: +353 (0)59 9183090
Fax. +353 (0) 1 4811 763
-------------------------------
Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty
Road,Graiguecullen,Carlow,Ireland  Company No.: 370845



From ripe-anti-spam-wg at powerweb.de  Wed Mar  9 21:22:39 2011
From: ripe-anti-spam-wg at powerweb.de (Frank Gadegast)
Date: Wed, 09 Mar 2011 21:22:39 +0100
Subject: [anti-abuse-wg] draft policy
In-Reply-To: <B78DC8A0-412F-4C76-BDC1-6E229F0360F6@blacknight.ie>
References: <4D777E1A.2010303@powerweb.de>	<49831.1299679342@tristatelogic.com>	<20110309144438.GB30227@Space.Net> <4D77A872.5010107@powerweb.de>	<4D77AB23.7060806@nosc.ja.net> <4D77B6F8.70507@powerweb.de> <821v2g8a99.fsf@mid.bfk.de> <4D77C676.7010305@powerweb.de> <B78DC8A0-412F-4C76-BDC1-6E229F0360F6@blacknight.ie>
Message-ID: <4D77E18F.1070800@powerweb.de>

Michele Neylon :: Blacknight wrote:
>
>>
>> But the German citizens could not at all through whatever government could tell DENIC what to do.
>
> That's not really true either
>
> DENIC is subject to German law.
>
> If German law forbade X then DENIC would not be able to do X
>
> Having said that, the German government does not currently have direct control over DENIC. It can, of course, influence it indirectly
>
> This is pretty much the same with all ccTLDs :)

Right, because surely an "e.g" has to follow German law.

Ok, to make it even more clearer:
- German citizens cannot take influence of DENIC rules or
   technical procedures until DENIC follows German law
- only DENIC members can modify DENICs technical procedures
   or regulations

- but any person can influence RIPEs regulations that the NCC
   has to fulfill in a more technical way
- NCCs members are paying for resources, but the decissions
   are not made by the members only

And thats simply wrong, stupid and highly risky.

BTW: just read a couple of days ago about a study that
a 10.000 PC botnet costs only about 800$/month.
Write a nifty little program and create 10.000 fake internet user.
And those could block any draft, just because no "consensus"
could be reached.

And I always wondered why there is that much wind-in-your-face, when
someone is having a great idea on this list.
I think its not really a problem for spammers to put a couple
of fake identities on the list, right ?

Just asking another thing:
why is there not one draft finally through resulting from discussions
on this list through all those years ?
why is there not even consensus about what abuse is ?
even when about 100 LIRs on this list liked those things ...

anybody on this list should be ashamed, that there are no results yet.

simply because anybody in the world can say "no, I dont like it" ...


Kind regards, Frank



>
>
>
>
> Mr Michele Neylon
> Blacknight Solutions
> Hosting&  Colocation, Brand Protection
> ICANN Accredited Registrar
> http://www.blacknight.com/
> http://blog.blacknight.com/
> http://blacknight.mobi/
> http://mneylon.tel
> Intl. +353 (0) 59  9183072
> US: 213-233-1612
> UK: 0844 484 9361
> Direct Dial: +353 (0)59 9183090
> Fax. +353 (0) 1 4811 763
> -------------------------------
> Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty
> Road,Graiguecullen,Carlow,Ireland  Company No.: 370845
>
>
>


-- 

Mit freundlichen Gruessen,
--
PHADE Software - PowerWeb                       http://www.powerweb.de
Inh. Dipl.-Inform. Frank Gadegast             mailto:frank at powerweb.de
Schinkelstrasse 17                                fon: +49 33200 52920
14558 Nuthetal OT Rehbruecke, Germany             fax: +49 33200 52921
======================================================================



From ripe-anti-spam-wg at powerweb.de  Wed Mar  9 21:52:19 2011
From: ripe-anti-spam-wg at powerweb.de (Frank Gadegast)
Date: Wed, 09 Mar 2011 21:52:19 +0100
Subject: [anti-abuse-wg] Re: Off-topic: German government involvement with DENIC policy, was
 draft policy
In-Reply-To: <1299698326.2210.91.camel@shane-desktop>
References: <4D777E1A.2010303@powerweb.de>	 <49831.1299679342@tristatelogic.com>	<20110309144438.GB30227@Space.Net>	 <4D77A872.5010107@powerweb.de>	<4D77AB23.7060806@nosc.ja.net>	 <4D77B6F8.70507@powerweb.de> <821v2g8a99.fsf@mid.bfk.de>	 <4D77C676.7010305@powerweb.de> <1299698326.2210.91.camel@shane-desktop>
Message-ID: <4D77E883.9080509@powerweb.de>

Shane Kerr wrote:
> Frank,
>
> On Wed, 2011-03-09 at 19:27 +0100, Frank Gadegast wrote:
>> But the German citizens could not at all through whatever government
>> could tell DENIC what to do.
>
> This really is wildly off-topic, but exactly this happened:
>
> http://www.dmueller.com/2009/10/18/domain-names-domains/denic-to-make-million-dollar-domains-available-for-the-first-time/
>
> A reminder that governments are the ones in charge. :)

Really off-topic now :o(

Its not citizens telling DENIC what to do.
It was a German court, and surely DENIC
has to do something then ...

If Nederland court is telling RIPE NCC to stop forming their internal 
regulations after the comments from non-members, RIPE NCC will also have 
to do something too.

Great idea btw :o)


Anyway: took this from RIPEs homepage
"The RIPE NCC is an independent, not-for-profit membership organisation"

So again (I want an answer now): why should RIPE NCC has to form it 
internal procedures and regulations after the will of the world ?

And from ripe-514
"10.2 The Executive Board may, at its own discretion, consult the 
Members about any decisions it plans to take."

And I do not find any note, that RIPE-NCC has to listen to 
whatever-what-people-say arround the world, its only about members ...

So it would be the most-easy way to ask its members several 
abuse-related things at the next general metting (oh, Im so naive).

So why should I not attend the next GM and ask:
"do we want to have the abuse-mailbox-field to change to be mandatory ?" 
and we just have a vote there at the GM and finish all the discussion of 
the last year ?

> --
> Shane
>
>

Kind regards, Frank
--
PHADE Software - PowerWeb                       http://www.powerweb.de
Inh. Dipl.-Inform. Frank Gadegast             mailto:frank at powerweb.de
Schinkelstrasse 17                                fon: +49 33200 52920
14558 Nuthetal OT Rehbruecke, Germany             fax: +49 33200 52921
======================================================================



From rhe at nosc.ja.net  Wed Mar  9 22:33:16 2011
From: rhe at nosc.ja.net (Rob Evans)
Date: Wed, 09 Mar 2011 21:33:16 +0000
Subject: [anti-abuse-wg] draft policy
In-Reply-To: <4D77C98A.7030504@powerweb.de>
References: <4D777E1A.2010303@powerweb.de> <49831.1299679342@tristatelogic.com> <20110309144438.GB30227@Space.Net> <4D77A872.5010107@powerweb.de> <4D77AB23.7060806@nosc.ja.net> <4D77B6F8.70507@powerweb.de> <4D77B8A3.3060207@heanet.ie> <4D77C98A.7030504@powerweb.de>
Message-ID: <4D77F21C.1040602@nosc.ja.net>

Frank,

> So the world-wide community tells RIPE NCC (and their members) what the
> members are going to do with their money they pay for RIPE NCCs services ?

Not quite, the world-wide community tells the RIRs what they are going
to do with their number resources.  There are some people heavily
involved with policy development in all the regions, but equally, there
are many people involved only with the policy development in their local
region, which is why the RIRs often have divergent policies.

The RIPE NCC members (i.e. the paid-up LIRs) decide, to some extent, how
the RIPE NCC spends the money they pay as membership fees by approving
-- or otherwise -- the charging plan that is presented to them at the
Autumn General Meeting.

> I gonna pay about 5000 people worldwide 10$ if they vote for, that
> small LIRs do not have to pay for the services anymore and just the big
> ones have to pay.
> 5000 people worldwide will mean consensus in the RIPE community.

Sorry, you are confusing the RIPE community with the RIPE NCC again.

The charging plan (who pays what) comes out of the RIPE NCC, and the
RIPE NCC members vote on that at the General Meeting.  The charging plan
is not something the RIPE community has direct influence over.

> Or think about: spammers paying the community to give them more IPs ...
> absolutly legaly.

Consensus != majority.

In theory this could happen, but one of the strong points of an open
policy development process is that anything along those lines should be
caught and should not reach consensus.

All the best,
Rob



From rfg at tristatelogic.com  Thu Mar 10 00:51:20 2011
From: rfg at tristatelogic.com (Ronald F. Guilmette)
Date: Wed, 09 Mar 2011 15:51:20 -0800
Subject: [anti-abuse-wg] Policy disallowing spam from RIPE blocks, was Use of RIPE region space by out-of-region users 
In-Reply-To: <1299680973.2210.72.camel@shane-desktop> 
Message-ID: <54258.1299714680@tristatelogic.com>

In message <1299680973.2210.72.camel at shane-desktop>, 
Shane Kerr <shane at time-travellers.org> wrote:

>As far as I can tell, the desire is to make it against the policies to
>send spam from RIPE NCC address space. I find it incredibly frustrating
>that nobody will actually just say that. :)
>...
>If I'm missing the point and there is actually something else going on,
>please someone clue me in!

Be glad to.  And I appreciate you asking.

OK, here's what's really going on...

As yu may have noticed, there's a LOT of spam on the Internet, and has
been for several years now.  but there are different flavors of it, and
some are harder to combat (and some create some _separate_ and _additional_
problems) more than others.

It is often the case that, for example, "Joe" of "Joe's Pizza Palace"
happens to have an idiot nephew, and the idiot nephew, who believes
everything he reads, believes that the way to instant riches is to
have a web site and then spam *everybody* in the Universe, from Alaska
to Zanzibar, telling them how swell Joe's pizza is.  (This happens
routinely _even though_ Joe's Pizza Palace has only one location, on
the Interstate just outside of Lakewood, New Jersey, and nobody is
likely to travel from Alaska to New jersey just to get a pizza.)

So anyway, Joe, being an ordinary small businessman, has one web site
and it has been assigned one single domain name and one single IP
address.  When Joe's idiot nephew sends out his massive spam run,
that one domain name and that one IP address almost instantly end up
on a whole slew of blacklists.  (In particular, the IP address will
end up very quickly on the Spamcop blacklist.)

The bottom line is that these kinds of one-domain/one-IP spammers are
actually not difficult at all to handle in a very complete and comprehensive
manner, using existing tools (i.e. existing blacklists), and thus they
don't create much in the way of problems for anyone.  The problem of
one-domain/one-IP spammers is virtually a non-problem.

In contrast to this sort of sitiation, these days the net has lots and
lots of what are called professional ``snowshoe'' spammers.  These folks
are astute. They know the score, and they know how existing spam blocking
systems work.  These people are *not* at all the same as Joe's idiot nephew.
They are determined, and they educated, and like he Terminator, they WILL
NOT STOP... at least not until they have managed to defeat all of the
existing technical systems that have been put in place to block spam.

The primary methodology of these folks... the way they get around traditional
anti-spam blacklists, if to ``spread out'' (like a snowshoe) their activities,
across big swaths of the domain name space and also across big swaths of the
IP address space.  Their approach is the same what the Soviets were planning
(hoping?) to be able to use to overcome the U.S's "Star Wars" missle defense
system... just build enough attack vehicles so that you can overwhelm the
defenses with sheer numbers.

In the case of showshoe spammers, their ``attack vehicles'' consist of domain
names and IP addresses, and from their perspective, they can NEVER have too
many of either one.  As we speak, there are snowshoe spammers on the Internet
who have well over 10,000 different second-level domain names and well over
10,000 different IPv4 addresses at their disposal, and they are using them
all to overwhelm traditional spam defenses (like the Spamcop IP blacklist,
and the URIBL and SURBL domain-based blacklists).  The ``spam traps'' that
are used gto drive these blacklists are never likely to see _all_ of the
actual spam sources (IPs & domains) that comprise any given snowshoer's
complete arsenal, so as with the Soviets, 20+ years ago, they can be assured
that at least _some_ of their stuff will always get through.

Is this whole escalation of the spam arms race bad for ``our side''... for
the ``good guys'' who are fighting against spam?  Yes.  Certainly.  But
here, since not everybody on this list is even clearly convinced that spam
itself is a Bad Thing, we can... abnd probably should... ignore that fact
entire.  Instead, just ask yourself if this specific escalation in the
ongoing spam arms is good (or bad) for the Internet generally, and without
even any regard for the acual spam flow which inevitably follows the setting
up of any given snowshoe.

When the issue is looked at even with these blinders on... ignoring totally
the massive annoyance and massive costs that spam on the net creates for
everyone... it can *still* be seen that ``snowshoeing'', at least with
respect to IP address space, is a fundamentally and unequivocally Bad Thing.
The reason is simple... IP address snowshoeing uses up vast quantities of
IP address space... in particular, IPv4 address space... you know... the
stuff that we are supposedly running out of, and that people soon won't
be able to get any more of.  Professional snowshoe spammers are rather like
the all-consuming ``virus'' that was alluded to briefly in the first "Matrix"
movie.  It doesn't matter how much IPv4 space you give them.  They will
always want more and always consume as much as they were given (laying waste
to it as they consume it).

So in order to understand why the issue of snowshoe spammers might have
relevance to RIPE, *even independent from the annoying and costly aspects
of the spam they generate*, you only have to understand that IPv4 (and
also IPv6) are finite resources, that we are rapidly running out of IPv4,
and that snowshoe spam farms are almost certainly the absolutely LEAST
effecient and/or cost effective way to make use of what remains.

Think of it this way... You are among the remaining inhabitants of Easter
Island.  Your tribe has already chopped down and used up all of the trees 
on the island except one.  Your friends are currently making plans to
chop down that one last tree, and they plan to use the wood from it
_not_ to build a canoe to get you and your tribe away from this dying
island, but rather, your friends just want to use the wood from the
last remaining tree to make toothpicks and earrings.  Now they turn to
you and ask you for YOUR opinion.  What are you going to tell them?

Using vast swaths of the remaining IPv4 address space for spammer snowshoe
farms is simply THE most silly and wasteful use of what remains that you
can possibly imagine, bar none.

In summary:

    *  Thwarting spam from single-point sources is easy.  Thwarting it
       when it emmanates from ``snowshoe spam farms'' is exponentially
       harder.

    *  Snowshoe spam farms are THE single most wasteful use of finite and
       limited Internet number resources imaginable.

Some people here don't want RIPE involved in the business of regulating
spam.  OK.  Fine.  I understand that.  But that's not the question before
us.

Rather, the dual questions before us are as follows:

    *  Does RIPE _really_ have to operate under a set of policies (and/or
       lack-of-policies) that, it would seem, may actually be *encouraging*
       and *supporting* the practice of snowshoe spamming, which, as I have
       said, is the most difficult form of spamming to combat with existing
       technical measures?

    *  Does RIPE and the RIPE community _really_ not grasp that fact that
       regardless of what you think of spam and spammers, the creation of
       IP address snowshoe spam farms is an unmitigated and colossal waste
       of the very resources that RIPE was created to be competent shepards
       over?

Yes, I admit it.  Guilty as charged.  I don't like spam.  And I'd love it
if every spammer ever found using RIPE number resources was summarily
shown the door.  But that's clearly not going to happen, so just forget
I even mentioned it, and a please turn your attention instead to the two
bullet points just above.

Just one last comment... I have no doubts whatsoever that some folks here
in the U.S.A., and many folks in the RIPE geographical region, and probably
even a few people on this specific mailing lists own stock in companies
that manufacture and sell networking equipment, in particular, IPv6 gear.
For all such folks, I fully expect my entreaties to fall on deaf ears.
Anybody owning stock in the various network equipment manufacturers would,
I suspect, like nothing better than the utter and final exhaustion of IPv4
at the earliest possible moment, as that event will almost certainly be
the primary trigger for the next big equipment upgrade cycle.  Notwithstanding
these facts, the community as a whole... both stockholders and non-stockholders
alike... would be ill-served, I think, by any deliberate efforts to engineer
the early exhaustion of the IPv4 space, e.g. by using snowshoe spammers
and their infinite appetities for IP space as convenient scapegoats.


Regards,
rfg



From ops.lists at gmail.com  Thu Mar 10 02:39:42 2011
From: ops.lists at gmail.com (Suresh Ramasubramanian)
Date: Thu, 10 Mar 2011 07:09:42 +0530
Subject: [anti-abuse-wg] Off-topic: German government involvement with
 DENIC policy, was draft policy
In-Reply-To: <1299698326.2210.91.camel@shane-desktop>
References: <4D777E1A.2010303@powerweb.de>
	<49831.1299679342@tristatelogic.com>
	<20110309144438.GB30227@Space.Net>
	<4D77A872.5010107@powerweb.de>
	<4D77AB23.7060806@nosc.ja.net>
	<4D77B6F8.70507@powerweb.de>
	<821v2g8a99.fsf@mid.bfk.de>
	<4D77C676.7010305@powerweb.de>
	<1299698326.2210.91.camel@shane-desktop>
Message-ID: <AANLkTinkNDZKL4sVTL2rgw+BrDBikFtUNq8EZdZGg6Ob@mail.gmail.com>

Christ, I wonder how many hares get started off this thread.

Can we all post a few proposals please / agree on some things we could
do, and then turn the energies of this group into helping wordsmith
them?

Say on the LIR assignment window?  Whois accuracy in descr:?  Anything else?

On Thu, Mar 10, 2011 at 12:48 AM, Shane Kerr <shane at time-travellers.org> wrote:
>
> This really is wildly off-topic, but exactly this happened:
>
> http://www.dmueller.com/2009/10/18/domain-names-domains/denic-to-make-million-dollar-domains-available-for-the-first-time/
>
> A reminder that governments are the ones in charge. :)



-- 
Suresh Ramasubramanian (ops.lists at gmail.com)



From rfg at tristatelogic.com  Thu Mar 10 02:42:54 2011
From: rfg at tristatelogic.com (Ronald F. Guilmette)
Date: Wed, 09 Mar 2011 17:42:54 -0800
Subject: [anti-abuse-wg] Use of RIPE region space by out-of-region users, was RIPE policy 
In-Reply-To: <30BAC6E1-AE5C-4BEC-9CA7-8D44B9124647@blacknight.ie> 
Message-ID: <55187.1299721374@tristatelogic.com>

In message <30BAC6E1-AE5C-4BEC-9CA7-8D44B9124647 at blacknight.ie>, 
"Michele Neylon :: Blacknight" <michele at blacknight.ie> wrote:

>On 9 Mar 2011, at 14:46, Ronald F. Guilmette wrote:
>
>>> We are a hosting company.
>>
>> Are you under the impression that this fact gives you some sort of special
>> dispensation to send me spam?
>
>I'm sorry, but I honestly don't know how you have the gall to make that kind
>of throwaway remark.

Sorry.  It was in response to your throw-away remark "We are a hosting company",
as if that had some relevance to, or bearing on the fact that I received spam
from your domain.

(In the context where it appeared, your comment certainly seemed to have been
offered as some sort of excuse or justification for the spam.)

>> (Some other hosting companies who care about their reputations and about
>> not polluting the Internet have arranged for all outbound port 25 connects
>> from end-luser frequently-compromosed machines to be either blocked or else
>> transparently redirected to a machine, or set of machines, where outbound
>> filtering takes place... you know... in order to fully suppress the inevi
>> table
>> and easily forseeable Nigerian 419 spam outflow from the inevitable and
>>>easily
>> forseeable compromised end-luser machine.)
>
>Read our terms of service. http://www.blacknight.com/acceptable-usage.html

OK.  I skimmed it.

That tells me what _legal_ steps you have taken, contract-wise, to try to
minimize spam outflow.  What I had intended to ask (which I admit may not
have been perfectly clear) is "What steps you have taken _technically_
to minimize your spam outflow?"

Of course, your network, your rules.  You can do (or not do) whatever you
want on YOUR network.  Conversely and likewise, I can do what I want on
my network, and on my network the domain name blacknight.ie is in the
local blacklist.  And as I have explained, it did not get there by sheer
random chance.

So I think this horse is dead now, and we can both stop beating it.  Your
network, your rules.  My network my rules.  Nothing more to say really, now
is there?


Regards,
rfg



From rfg at tristatelogic.com  Thu Mar 10 03:19:24 2011
From: rfg at tristatelogic.com (Ronald F. Guilmette)
Date: Wed, 09 Mar 2011 18:19:24 -0800
Subject: [anti-abuse-wg] draft policy 
In-Reply-To: <4D77C98A.7030504@powerweb.de> 
Message-ID: <55588.1299723564@tristatelogic.com>

In message <4D77C98A.7030504 at powerweb.de>, 
Frank Gadegast <ripe-anti-spam-wg at powerweb.de> wrote:

>I have an idea:
>I gonna pay about 5000 people worldwide 10$ if they vote for, that
>small LIRs do not have to pay for the services anymore and just the big 
>ones have to pay.
>5000 people worldwide will mean consensus in the RIPE community.
>And I will have all the small LIRs on me side too.
>And I will save money in a couple of years.


Fyi -

There's no special reason why folks in the RIPE region would already
know this, so for the benefit of those that don't I just thought that
I would mention that what you have just described is prettty much the
was "democracy" works nowadays in these United States, i.e. following the
recent Supreme Court decision in Citizens United v. Federal Election
Commission:

   http://www.nytimes.com/2010/01/22/us/politics/22scotus.html

These days, anybody can "buy" pretty much any political outcome they
want, assuming they have enough money to do it.


Regards,
rfg



From ripe-anti-spam-wg at powerweb.de  Thu Mar 10 08:53:19 2011
From: ripe-anti-spam-wg at powerweb.de (Frank Gadegast)
Date: Thu, 10 Mar 2011 08:53:19 +0100
Subject: [anti-abuse-wg] Policy disallowing spam from RIPE blocks
In-Reply-To: <54258.1299714680@tristatelogic.com>
References: <54258.1299714680@tristatelogic.com>
Message-ID: <4D78836F.8030809@powerweb.de>

Ronald F. Guilmette wrote:
> In message<1299680973.2210.72.camel at shane-desktop>,
> Shane Kerr<shane at time-travellers.org>  wrote:
>
>> As far as I can tell, the desire is to make it against the policies to
>> send spam from RIPE NCC address space. I find it incredibly frustrating
>> that nobody will actually just say that. :)
>> ...
>> If I'm missing the point and there is actually something else going on,
>> please someone clue me in!
>
> Be glad to.  And I appreciate you asking.
>

> The bottom line is that these kinds of one-domain/one-IP spammers are
> actually not difficult at all to handle in a very complete and comprehensive
> manner, using existing tools (i.e. existing blacklists), and thus they
> don't create much in the way of problems for anyone.  The problem of
> one-domain/one-IP spammers is virtually a non-problem.

No, its not.
Spam is illegal in a couple of countries and every spam counts in those.

We have to get away from the perspective to rank spam by the "size" of
the problem its causing.

The only way to define abuse is to describe it as the problems abuse
is causing at the receivers side, not the senders side.

"Abuse" is to my understanding, any harm an activity of a third party
is causing to the resources of an IP owner, that the IP owner did
not intented or wants.
The definition of "abuse" is up to the abused resource owner.

And responsible for any kind of abuse is the resource owner of
the IPs the abuse is originating from.

And RIPE NCC has to improve its concepts and regulations to
prevent abuse caused by their members.
A first step of RIPE NCC should be to improve abuse reporting
by improving whois data by accuracy and ease to retrieve
the responsible person.

> In contrast to this sort of sitiation, these days the net has lots and
> lots of what are called professional ``snowshoe'' spammers.  These folks
> are astute. They know the score, and they know how existing spam blocking
> systems work.  These people are *not* at all the same as Joe's idiot nephew.
> They are determined, and they educated, and like he Terminator, they WILL
> NOT STOP... at least not until they have managed to defeat all of the
> existing technical systems that have been put in place to block spam.

True, RIPE NCC cannot do a lot these days to stop them, but RIPE NCC
can do a lot to make it easier for the victims to protect themselve.

> Is this whole escalation of the spam arms race bad for ``our side''... for
> the ``good guys'' who are fighting against spam?  Yes.  Certainly.  But
> here, since not everybody on this list is even clearly convinced that spam
> itself is a Bad Thing, we can... abnd probably should... ignore that fact

And thats the crazy thing I complain about.
How can RIPE NCC not do anything because the "RIPE community" also
consist of spammers ?

Thats like a goverment saying, that murder or theft isnt eval and wrong
because some murders and thiefs think its ok ...
I really wonder that the current RIPE regulations do not contain
at least some points that are coming close to human rights.

So: any idea how we can bring the RIPE regulations so far, that
abuse IS eval and the RIPE NCC has to improve regulations, protocols
and techniques ?
And stop abuse friendly people in the community from blocking this
process ?

> When the issue is looked at even with these blinders on... ignoring totally
> the massive annoyance and massive costs that spam on the net creates for
> everyone... it can *still* be seen that ``snowshoeing'', at least with

Do not think about abuse only on spam.
There is a lot of other abuse, like password scanning of mail accounts,
DDoS attacks or hacking.
Those things are not even simple abuse, these things are against laws
in the most countries.

As an ISP we had a lot of cases during the last years, where this kind
of abuse was going to be invested by legal authorities (police, court
aso) and they had NO chance to detect the originator, because of
inaccuracy in RIPEs database, highjaked IP space, because the LIR
did not care who announces his old IP space aso ...
So: RIPE NCC IS responsible for the accuracy of the database
and the resources.
And: the LIRs should be forced to improve their techniques
to prevent misuse by regulations, just because its very easy
to detect botted PCs in your own network and its even easier
to block them.
Its also easy to detect misuse of orphaned address space.
And its easy for RIPE NCC to punish LIRs that do not follow
the regulations (f.e. why are LIRs not beeing forced to
announce address space they own ? if they do not need the IPs,
RIPE NCC could revoke them).


BTW: spam farms are usally not a big technical problem, because
its easy to detect ranges with spam outbreaks. More problematic
are all those unprotected PCs out there with daily changing IP.


Kind regards, Frank



>
>
> Regards,
> rfg
>
>
>


-- 

Mit freundlichen Gruessen,
--
PHADE Software - PowerWeb                       http://www.powerweb.de
Inh. Dipl.-Inform. Frank Gadegast             mailto:frank at powerweb.de
Schinkelstrasse 17                                fon: +49 33200 52920
14558 Nuthetal OT Rehbruecke, Germany             fax: +49 33200 52921
======================================================================
Public PGP Key available for frank at powerweb.de



From ops.lists at gmail.com  Thu Mar 10 09:21:07 2011
From: ops.lists at gmail.com (Suresh Ramasubramanian)
Date: Thu, 10 Mar 2011 13:51:07 +0530
Subject: [anti-abuse-wg] Policy disallowing spam from RIPE blocks
In-Reply-To: <4D78836F.8030809@powerweb.de>
References: <54258.1299714680@tristatelogic.com>
	<4D78836F.8030809@powerweb.de>
Message-ID: <AANLkTinRZE2ydcwopudsvsvS2z9mM==SJJ90xDMDzfod@mail.gmail.com>

On Thu, Mar 10, 2011 at 1:23 PM, Frank Gadegast
<ripe-anti-spam-wg at powerweb.de> wrote:
>
> BTW: spam farms are usally not a big technical problem, because
> its easy to detect ranges with spam outbreaks. More problematic
> are all those unprotected PCs out there with daily changing IP.
>

Its not a "technical" problem in that a smtp block or a nullroute
solves it for you

Now picture what happens when the ISP turfs whatever spammer got a /14
from them, or the RIR revokes a /20 that is full of malware C&C .. and
then, months later, its reassigned to someone else.

I would invite you to go explain how easy or difficult a technical
problem it is, to whichever poor SOB gets that netblock.

-- 
Suresh Ramasubramanian (ops.lists at gmail.com)



From ripe-anti-spam-wg at powerweb.de  Thu Mar 10 09:53:44 2011
From: ripe-anti-spam-wg at powerweb.de (Frank Gadegast)
Date: Thu, 10 Mar 2011 09:53:44 +0100
Subject: [anti-abuse-wg] Policy disallowing spam from RIPE blocks
In-Reply-To: <AANLkTinRZE2ydcwopudsvsvS2z9mM==SJJ90xDMDzfod@mail.gmail.com>
References: <54258.1299714680@tristatelogic.com>	<4D78836F.8030809@powerweb.de> <AANLkTinRZE2ydcwopudsvsvS2z9mM==SJJ90xDMDzfod@mail.gmail.com>
Message-ID: <4D789198.7060802@powerweb.de>

Suresh Ramasubramanian wrote:
> On Thu, Mar 10, 2011 at 1:23 PM, Frank Gadegast
> <ripe-anti-spam-wg at powerweb.de>  wrote:
>>
>> BTW: spam farms are usally not a big technical problem, because
>> its easy to detect ranges with spam outbreaks. More problematic
>> are all those unprotected PCs out there with daily changing IP.
>>
>
> Its not a "technical" problem in that a smtp block or a nullroute
> solves it for you
>
> Now picture what happens when the ISP turfs whatever spammer got a /14
> from them, or the RIR revokes a /20 that is full of malware C&C .. and
> then, months later, its reassigned to someone else.
>
> I would invite you to go explain how easy or difficult a technical
> problem it is, to whichever poor SOB gets that netblock.

Thats easy.

We remove blocked IP ranges or addresses automatically on a regular
base. Our statistics show, that spam only "outbreaks" for a couple
of days from specific IPs and that we detect new outbreaks quick enough.
We remove dynamic single IPs after a week automatically, when they were
added automatically.
And we remove manually added bigger blocks after 3 months.

We also offer a webpage anybody can reach to remove IPs from our
blacklist easily without any further "excuse" or "procedure".
With just one simply click.
Even any spammer could remove his IPs also very easily, if he ever
reads an error report or mail reply from us, but thats no problem,
because the IP will end up on the blacklist just with the next spam
received.

And: we never had the problem, that a new owner of a bigger netblock
contacted us for removal, its unlikely, that such a newly used netblock
has to reach our customers, we are small and only a small percentage
of the IPs worldwide really want to communicate with our customers.

Its fuzzy, does not get any case, but works great.


Kind regards, Frank
--
PHADE Software - PowerWeb                       http://www.powerweb.de
Inh. Dipl.-Inform. Frank Gadegast             mailto:frank at powerweb.de
Schinkelstrasse 17                                fon: +49 33200 52920
14558 Nuthetal OT Rehbruecke, Germany             fax: +49 33200 52921
======================================================================
Public PGP Key available for frank at powerweb.de

-- 

Mit freundlichen Gruessen,
--
PHADE Software - PowerWeb                       http://www.powerweb.de
Inh. Dipl.-Inform. Frank Gadegast             mailto:frank at powerweb.de
Schinkelstrasse 17                                fon: +49 33200 52920
14558 Nuthetal OT Rehbruecke, Germany             fax: +49 33200 52921
======================================================================
Public PGP Key available for frank at powerweb.de



From Woeber at CC.UniVie.ac.at  Thu Mar 10 09:59:49 2011
From: Woeber at CC.UniVie.ac.at (Wilfried Woeber, UniVie/ACOnet)
Date: Thu, 10 Mar 2011 08:59:49 +0000
Subject: [anti-abuse-wg] Re: Interaction between the RIPE and anti-abuse
 communities]
In-Reply-To: <AANLkTin=Sk6FUaSeC+XsqGiPKnS+2M-bDJ0P1WkOVvW9@mail.gmail.com>
References: <47332.1296776348@tristatelogic.com>	<4D4BBCEC.3060909@tana.it> <AANLkTin=Sk6FUaSeC+XsqGiPKnS+2M-bDJ0P1WkOVvW9@mail.gmail.com>
Message-ID: <4D789305.4080707@CC.UniVie.ac.at>

Suresh Ramasubramanian wrote:

> That is only useful if the organization doing so has some sort of
> oversight or escalation power over what the receiver of those
> complaints is supposed to do.
> 
> It might actually make sense to involve the dutch CERT in this.

Which one? I presume you are thinking about GOVCERT.nl ?

If I am right, what would be that CERT's role with regard to this
discussion?

> On Fri, Feb 4, 2011 at 2:16 PM, Alessandro Vesely <vesely at tana.it> wrote:
> 
>>Agreed, especially if the procedure provides for handing complaints to
>>external abuse teams, e.g. according to IP allocations.

Wilfried
(wearing my ACOnet-CERT scarf for a moment :-) )



From gert at space.net  Thu Mar 10 10:00:54 2011
From: gert at space.net (Gert Doering)
Date: Thu, 10 Mar 2011 10:00:54 +0100
Subject: [anti-abuse-wg] Policy disallowing spam from RIPE blocks, was
 Use of RIPE region space by out-of-region users
In-Reply-To: <54258.1299714680@tristatelogic.com>
References: <1299680973.2210.72.camel@shane-desktop>
 <54258.1299714680@tristatelogic.com>
Message-ID: <20110310090054.GS30227@Space.Net>

Hi,

On Wed, Mar 09, 2011 at 03:51:20PM -0800, Ronald F. Guilmette wrote:
> you and ask you for YOUR opinion.  What are you going to tell them?

"Stop worrying about that tree, we've built a nice boat from metal in
the mean time".

Whatevery you do to IPv4, it's a lost cause anyway - if you spend enough
time and resources, you might make it last one or two years longer, and
then it's *still* gone, and all you've achieved is "lots of extra resources 
burned".  Get over it.

We should have moved to IPv6 5 years ago, without the pressure of 
impending exhaustion.  Less pain for everybody, and *far* less devices
to touch.

Gert Doering
        -- NetMaster
-- 
did you enable IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279



From ops.lists at gmail.com  Thu Mar 10 10:14:06 2011
From: ops.lists at gmail.com (Suresh Ramasubramanian)
Date: Thu, 10 Mar 2011 14:44:06 +0530
Subject: [anti-abuse-wg] Re: Interaction between the RIPE and anti-abuse communities]
In-Reply-To: <4D789305.4080707@CC.UniVie.ac.at>
References: <47332.1296776348@tristatelogic.com>
	<4D4BBCEC.3060909@tana.it>
	<AANLkTin=Sk6FUaSeC+XsqGiPKnS+2M-bDJ0P1WkOVvW9@mail.gmail.com>
	<4D789305.4080707@CC.UniVie.ac.at>
Message-ID: <AANLkTimj-P0a-rN4==-hm1MQMsp7vSv9_1FF1b3VNV8n@mail.gmail.com>

Purely a coordination role - where regulators and law enforcement may
well have a role to play when there's malware involved.

And yes, I do mean the people at govcert.nl

thanks
--srs

On Thu, Mar 10, 2011 at 2:29 PM, Wilfried Woeber, UniVie/ACOnet
<Woeber at cc.univie.ac.at> wrote:
> Suresh Ramasubramanian wrote:
>
>> That is only useful if the organization doing so has some sort of
>> oversight or escalation power over what the receiver of those
>> complaints is supposed to do.
>>
>> It might actually make sense to involve the dutch CERT in this.
>
> Which one? I presume you are thinking about GOVCERT.nl ?
>
> If I am right, what would be that CERT's role with regard to this
> discussion?
>
>> On Fri, Feb 4, 2011 at 2:16 PM, Alessandro Vesely <vesely at tana.it> wrote:
>>
>>>Agreed, especially if the procedure provides for handing complaints to
>>>external abuse teams, e.g. according to IP allocations.
>
> Wilfried
> (wearing my ACOnet-CERT scarf for a moment :-) )
>
>



-- 
Suresh Ramasubramanian (ops.lists at gmail.com)



From ops.lists at gmail.com  Thu Mar 10 10:16:00 2011
From: ops.lists at gmail.com (Suresh Ramasubramanian)
Date: Thu, 10 Mar 2011 14:46:00 +0530
Subject: [anti-abuse-wg] Policy disallowing spam from RIPE blocks
In-Reply-To: <4D789198.7060802@powerweb.de>
References: <54258.1299714680@tristatelogic.com>
	<4D78836F.8030809@powerweb.de>
	<AANLkTinRZE2ydcwopudsvsvS2z9mM==SJJ90xDMDzfod@mail.gmail.com>
	<4D789198.7060802@powerweb.de>
Message-ID: <AANLkTi=obnmk-52ph_MmGF7a338R5WHcB6x386Cbzr5Y@mail.gmail.com>

You do.  We have something on very similar lines.

I'm willing to bet that several networks (ranging from ISPs to large
corporations) have filters that date back to a decade ago, but were
never removed.

No, that wouldn't be a good bet to make when I know that for a fact.

thanks
-suresh

On Thu, Mar 10, 2011 at 2:23 PM, Frank Gadegast
<ripe-anti-spam-wg at powerweb.de> wrote:
> We remove blocked IP ranges or addresses automatically on a regular
> base. Our statistics show, that spam only "outbreaks" for a couple
> of days from specific IPs and that we detect new outbreaks quick enough.
> We remove dynamic single IPs after a week automatically, when they were
> added automatically.
> And we remove manually added bigger blocks after 3 months.
>
> We also offer a webpage anybody can reach to remove IPs from our
> blacklist easily without any further "excuse" or "procedure".
> With just one simply click.



-- 
Suresh Ramasubramanian (ops.lists at gmail.com)



From shane at time-travellers.org  Thu Mar 10 14:05:31 2011
From: shane at time-travellers.org (Shane Kerr)
Date: Thu, 10 Mar 2011 14:05:31 +0100
Subject: [anti-abuse-wg] Policy proposal: closing allocation/assignment window, was Policy
 disallowing spam from RIPE blocks
In-Reply-To: <AANLkTi=9UZ0zxL9cRhGcRBi_LxfrfNgsf8NV10Yeh0Bh@mail.gmail.com>
References: <48942.1299672364@tristatelogic.com>
	 <1299676562.2210.43.camel@shane-desktop>
	 <AANLkTi=N__1LByaLi_1gaJedJr76o-A8isjn2LOt0BR5@mail.gmail.com>
	 <1299680973.2210.72.camel@shane-desktop>
	 <AANLkTi=9UZ0zxL9cRhGcRBi_LxfrfNgsf8NV10Yeh0Bh@mail.gmail.com>
Message-ID: <1299762331.2251.30.camel@shane-desktop>

Suresh,

On Wed, 2011-03-09 at 20:19 +0530, Suresh Ramasubramanian wrote:
> And if you want policy proposals, please do let me know what you think
> about some concrete proposals that have emerged from all this argument
> and ad hominem

THANK YOU. :)

I'll address these in separate replies to try to remain focused on each
one.

> 1. Closing the allocation window / giving LIRs less leeway in
> approvals [so there should be no difference in submitting a request
> through a LIR, or through the RIR]

Do you mean the "assignment window"?

As I understand it, when you get an allocation from the RIPE NCC you
can't actually use it for anything until you get approval to assign that
space. After a certain amount of time, you have proven yourself
more-or-less trustworthy, then you get an assignment window, and can
make smallish assignments yourself without prior approval. These
assignments are reviewed - both by automated tools and by humans - if
and when you ask for another allocation.

These assignment windows can get raised or lowered depending on how the
LIR behaves. Having an experienced network administrator leave and
replaced by someone without a clue may result in it getting lowered, for
example. :)

I think the assignment window is more-or-less okay as it is today.

-----

If you mean the process by which provider-independent (PI) space is
assigned, then as I understand it this REQUIRES an LIR to make the
request on your behalf. I assume that the RIPE NCC reviews each request,
the same as they would any address request.

To be honest, I don't really understand what the LIR role in this whole
process is, other than maybe companies prefer to work with a local
company that speaks their language, is in their time zone, and
understands their business environment. 

The RIPE NCC is currently finishing implementing a newish requirement
that PI blocks have a contract with either the RIPE NCC or with an LIR.
Based on this is should be possible to revoke misused PI space (where
"misuse" is defined as "not being used for the purpose assigned under",
*not* defined as "being used for things I do not like").

In theory that policy already exists for all RIPE NCC space, I think. Do
you think we should try to push for the RIPE NCC to actually implement
this policy? Do you think there should be further penalties for LIRs
involved with arranging bogus PI assignments?

--
Shane



From shane at time-travellers.org  Thu Mar 10 14:10:15 2011
From: shane at time-travellers.org (Shane Kerr)
Date: Thu, 10 Mar 2011 14:10:15 +0100
Subject: [anti-abuse-wg] Increasing Whois accuracy, was  Policy disallowing spam from RIPE
 blocks
In-Reply-To: <AANLkTi=9UZ0zxL9cRhGcRBi_LxfrfNgsf8NV10Yeh0Bh@mail.gmail.com>
References: <48942.1299672364@tristatelogic.com>
	 <1299676562.2210.43.camel@shane-desktop>
	 <AANLkTi=N__1LByaLi_1gaJedJr76o-A8isjn2LOt0BR5@mail.gmail.com>
	 <1299680973.2210.72.camel@shane-desktop>
	 <AANLkTi=9UZ0zxL9cRhGcRBi_LxfrfNgsf8NV10Yeh0Bh@mail.gmail.com>
Message-ID: <1299762615.2251.35.camel@shane-desktop>

Suresh,

And on to #2...

On Wed, 2011-03-09 at 20:19 +0530, Suresh Ramasubramanian wrote:
> 2. Increasing accuracy in whois (including the descr: field) <- note,
> I am not saying "structure to a freeform field", just seeing that it
> matches the justification paperwork and its use

I think this may make sense. One problem is that right now nobody knows
what the supposed purpose of an assignment was except for the address
holder and the RIPE NCC.

The RIPE database group tends to prefer explicit fields for explicit
purposes. Okay, maybe that is just me. ;)  We could add something as
simple as:

assignment-purpose: [reason]

We could ask the RIPE NCC for guidance for 'reason' labels that cover
the vast majority of all assignments, like 'mobile phones' or 'cable
customers' or 'isp infrastructure'.

That would make it a lot easier for us, as 3rd parties, to know if the
assignment was being used incorrectly.

I suspect we'd get a lot of pushback from LIRs, but I could be wrong.

--
Shane



From shane at time-travellers.org  Thu Mar 10 14:16:00 2011
From: shane at time-travellers.org (Shane Kerr)
Date: Thu, 10 Mar 2011 14:16:00 +0100
Subject: [anti-abuse-wg] LIR membership, was  Policy disallowing spam from RIPE blocks
In-Reply-To: <AANLkTi=9UZ0zxL9cRhGcRBi_LxfrfNgsf8NV10Yeh0Bh@mail.gmail.com>
References: <48942.1299672364@tristatelogic.com>
	 <1299676562.2210.43.camel@shane-desktop>
	 <AANLkTi=N__1LByaLi_1gaJedJr76o-A8isjn2LOt0BR5@mail.gmail.com>
	 <1299680973.2210.72.camel@shane-desktop>
	 <AANLkTi=9UZ0zxL9cRhGcRBi_LxfrfNgsf8NV10Yeh0Bh@mail.gmail.com>
Message-ID: <1299762960.2251.41.camel@shane-desktop>

Suresh,

And finally, #3!

On Wed, 2011-03-09 at 20:19 +0530, Suresh Ramasubramanian wrote:
> 3. Maybe some way to weed out bogus LIRs, tighten the process of new
> LIR creation [or simply get rid of the entire LIR concept?]

Tricky. The RIPE NCC is a membership organization - the LIRs are the
owners. Right now the membership process is really easy, but membership
does not automatically get you an allocation. You still have to justify
your first allocation, and then justify the assignments within your
allocation when you want to use the space.

I don't represent an LIR, so it feels a bit weird to recommend changes
to the process. If it is too easy, some things can be done. Perhaps some
sort of process where you need to be introduced by another LIR before
you can join? It would be a low hurdle, but it might be something.

--
Shane



From gert at space.net  Thu Mar 10 14:17:19 2011
From: gert at space.net (Gert Doering)
Date: Thu, 10 Mar 2011 14:17:19 +0100
Subject: [anti-abuse-wg] Policy proposal: closing allocation/assignment
 window, was Policy disallowing spam from RIPE blocks
In-Reply-To: <1299762331.2251.30.camel@shane-desktop>
References: <48942.1299672364@tristatelogic.com>
 <1299676562.2210.43.camel@shane-desktop>
 <AANLkTi=N__1LByaLi_1gaJedJr76o-A8isjn2LOt0BR5@mail.gmail.com>
 <1299680973.2210.72.camel@shane-desktop>
 <AANLkTi=9UZ0zxL9cRhGcRBi_LxfrfNgsf8NV10Yeh0Bh@mail.gmail.com>
 <1299762331.2251.30.camel@shane-desktop>
Message-ID: <20110310131719.GG30227@Space.Net>

Hi,

On Thu, Mar 10, 2011 at 02:05:31PM +0100, Shane Kerr wrote:
> > 1. Closing the allocation window / giving LIRs less leeway in
> > approvals [so there should be no difference in submitting a request
> > through a LIR, or through the RIR]
> 
> Do you mean the "assignment window"?
> 
> As I understand it, when you get an allocation from the RIPE NCC you
> can't actually use it for anything until you get approval to assign that
> space. After a certain amount of time, you have proven yourself
> more-or-less trustworthy, then you get an assignment window, and can
> make smallish assignments yourself without prior approval. These
> assignments are reviewed - both by automated tools and by humans - if
> and when you ask for another allocation.

Mostly correct, yes.  You still start with an AW=0, and that goes up
after 6 month to /22 if you have done some NCC-approved assignments in
that time.

(It was somewhat more strict in previous times, where you'd only get to
about the size you have assigned - while today, you always get /22 or
bigger)

[..]
> If you mean the process by which provider-independent (PI) space is
> assigned, then as I understand it this REQUIRES an LIR to make the
> request on your behalf. I assume that the RIPE NCC reviews each request,
> the same as they would any address request.
> 
> To be honest, I don't really understand what the LIR role in this whole
> process is, other than maybe companies prefer to work with a local
> company that speaks their language, is in their time zone, and
> understands their business environment. 

This is the whole point.  There might be a business relation with a local
LIR already, and that's way easier for "smallish companies" than to do 
international contracts with Amstedam.

You *can* get the PI space from the RIPE NCC directly (nowadays) by becoming 
a so-called "direct access user" - but this is more expensive, and more
paperwork.

Gert Doering
        -- NetMaster
-- 
did you enable IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279



From fweimer at bfk.de  Thu Mar 10 14:24:45 2011
From: fweimer at bfk.de (Florian Weimer)
Date: Thu, 10 Mar 2011 13:24:45 +0000
Subject: [anti-abuse-wg] Policy proposal: closing allocation/assignment window, was Policy disallowing spam from RIPE blocks
In-Reply-To: <20110310131719.GG30227@Space.Net> (Gert Doering's message of "Thu\, 10 Mar 2011 14\:17\:19 +0100")
References: <48942.1299672364@tristatelogic.com>
	<1299676562.2210.43.camel@shane-desktop>
	<AANLkTi=N__1LByaLi_1gaJedJr76o-A8isjn2LOt0BR5@mail.gmail.com>
	<1299680973.2210.72.camel@shane-desktop>
	<AANLkTi=9UZ0zxL9cRhGcRBi_LxfrfNgsf8NV10Yeh0Bh@mail.gmail.com>
	<1299762331.2251.30.camel@shane-desktop>
	<20110310131719.GG30227@Space.Net>
Message-ID: <82zkp33y76.fsf@mid.bfk.de>

* Gert Doering:

> This is the whole point.  There might be a business relation with a local
> LIR already, and that's way easier for "smallish companies" than to do 
> international contracts with Amstedam.

Some transit providers require LIR status in their contracts
(presumably, they don't want to deal with abuse complaints, RIPE
policy changes, and so on, so this is understandable).  Relying on an
existing LIR is not always an option, even for small companies.

-- 
Florian Weimer                <fweimer at bfk.de>
BFK edv-consulting GmbH       http://www.bfk.de/
Kriegsstra?e 100              tel: +49-721-96201-1
D-76133 Karlsruhe             fax: +49-721-96201-99



From fweimer at bfk.de  Thu Mar 10 14:26:38 2011
From: fweimer at bfk.de (Florian Weimer)
Date: Thu, 10 Mar 2011 13:26:38 +0000
Subject: [anti-abuse-wg] LIR membership, was  Policy disallowing spam from RIPE blocks
In-Reply-To: <1299762960.2251.41.camel@shane-desktop> (Shane Kerr's message of "Thu\, 10 Mar 2011 14\:16\:00 +0100")
References: <48942.1299672364@tristatelogic.com>
	<1299676562.2210.43.camel@shane-desktop>
	<AANLkTi=N__1LByaLi_1gaJedJr76o-A8isjn2LOt0BR5@mail.gmail.com>
	<1299680973.2210.72.camel@shane-desktop>
	<AANLkTi=9UZ0zxL9cRhGcRBi_LxfrfNgsf8NV10Yeh0Bh@mail.gmail.com>
	<1299762960.2251.41.camel@shane-desktop>
Message-ID: <82y64n3y41.fsf@mid.bfk.de>

* Shane Kerr:

> Tricky. The RIPE NCC is a membership organization - the LIRs are the
> owners. Right now the membership process is really easy, but membership
> does not automatically get you an allocation.

I think it basically does, for IPv6.

> You still have to justify your first allocation, and then justify
> the assignments within your allocation when you want to use the
> space.

For creating the route object, allocation is sufficient.

It's difficult to introduce the right level of barriers because we
need to walk a fine line between preventing devaluation of RIPE
address space and forming a cartel which excludes potential
competitors.

-- 
Florian Weimer                <fweimer at bfk.de>
BFK edv-consulting GmbH       http://www.bfk.de/
Kriegsstra?e 100              tel: +49-721-96201-1
D-76133 Karlsruhe             fax: +49-721-96201-99



From gert at space.net  Thu Mar 10 14:38:21 2011
From: gert at space.net (Gert Doering)
Date: Thu, 10 Mar 2011 14:38:21 +0100
Subject: [anti-abuse-wg] Policy proposal: closing allocation/assignment
 window, was Policy disallowing spam from RIPE blocks
In-Reply-To: <20110310131719.GG30227@Space.Net>
References: <48942.1299672364@tristatelogic.com>
 <1299676562.2210.43.camel@shane-desktop>
 <AANLkTi=N__1LByaLi_1gaJedJr76o-A8isjn2LOt0BR5@mail.gmail.com>
 <1299680973.2210.72.camel@shane-desktop>
 <AANLkTi=9UZ0zxL9cRhGcRBi_LxfrfNgsf8NV10Yeh0Bh@mail.gmail.com>
 <1299762331.2251.30.camel@shane-desktop>
 <20110310131719.GG30227@Space.Net>
Message-ID: <20110310133821.GH30227@Space.Net>

Hi,

On Thu, Mar 10, 2011 at 02:17:19PM +0100, Gert Doering wrote:
> Mostly correct, yes.  You still start with an AW=0, and that goes up
> after 6 month to /22 if you have done some NCC-approved assignments in
> that time.
> 
> (It was somewhat more strict in previous times, where you'd only get to
> about the size you have assigned - while today, you always get /22 or
> bigger)

Small correction: the AW goes to a /21, not /22.

One should keep in mind what the AW does: it gives a LIR that wants to
play by the rules(!) some room to handle "common day to day stuff" on
their own, without having to spend some time talking to a NCC IPRA
for every single customer assignment.

A rogue LIR that does *not* want to "play by the rules" will not honour
the AW either, and just use addresses as it wants.

The difference becomes relevant when the RIPE NCC does an audit, or the
LIR comes back for more space - then the NCC will check that all housekeeping
has been done and that the AW rules have been followed.

Gert Doering
        -- NetMaster
-- 
did you enable IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279



From gert at space.net  Thu Mar 10 14:42:16 2011
From: gert at space.net (Gert Doering)
Date: Thu, 10 Mar 2011 14:42:16 +0100
Subject: [anti-abuse-wg] Policy proposal: closing allocation/assignment
 window, was Policy disallowing spam from RIPE blocks
In-Reply-To: <82zkp33y76.fsf@mid.bfk.de>
References: <48942.1299672364@tristatelogic.com>
 <1299676562.2210.43.camel@shane-desktop>
 <AANLkTi=N__1LByaLi_1gaJedJr76o-A8isjn2LOt0BR5@mail.gmail.com>
 <1299680973.2210.72.camel@shane-desktop>
 <AANLkTi=9UZ0zxL9cRhGcRBi_LxfrfNgsf8NV10Yeh0Bh@mail.gmail.com>
 <1299762331.2251.30.camel@shane-desktop>
 <20110310131719.GG30227@Space.Net>
 <82zkp33y76.fsf@mid.bfk.de>
Message-ID: <20110310134215.GI30227@Space.Net>

Hi,

On Thu, Mar 10, 2011 at 01:24:45PM +0000, Florian Weimer wrote:
> * Gert Doering:
> 
> > This is the whole point.  There might be a business relation with a local
> > LIR already, and that's way easier for "smallish companies" than to do 
> > international contracts with Amstedam.
> 
> Some transit providers require LIR status in their contracts
> (presumably, they don't want to deal with abuse complaints, RIPE
> policy changes, and so on, so this is understandable).  Relying on an
> existing LIR is not always an option, even for small companies.

Not that I have ever seen such a contract - but certainly there's good
reason why a large transit ISP might not want to be bothered with 
end customer assignment rules when their business focus is on "move 
packets".

Tacking this to "LIR status" is a somewhat funny thing to do, though, as
that has nothing to do whatsoever with the presumed purpose - a non-LIR
can have PI space acquired through another LIR, and thus not bother the
transit provider with all these "LIR things" but still not be LIR itself.

(But this is straying from the point - Shane was talking about the current
ways to get *PI* space, which, in the typical cases, is not something LIRs
do for themselves)

Gert Doering
        -- NetMaster
-- 
did you enable IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 306 bytes
Desc: not available
URL: <https://lists.ripe.net/ripe/mail/archives/anti-abuse-wg/attachments/20110310/6cda3134/attachment.sig>

From ops.lists at gmail.com  Thu Mar 10 15:25:53 2011
From: ops.lists at gmail.com (Suresh Ramasubramanian)
Date: Thu, 10 Mar 2011 19:55:53 +0530
Subject: [anti-abuse-wg] Re: Policy proposal: closing allocation/assignment window, was Policy
 disallowing spam from RIPE blocks
In-Reply-To: <1299762331.2251.30.camel@shane-desktop>
References: <48942.1299672364@tristatelogic.com>
	<1299676562.2210.43.camel@shane-desktop>
	<AANLkTi=N__1LByaLi_1gaJedJr76o-A8isjn2LOt0BR5@mail.gmail.com>
	<1299680973.2210.72.camel@shane-desktop>
	<AANLkTi=9UZ0zxL9cRhGcRBi_LxfrfNgsf8NV10Yeh0Bh@mail.gmail.com>
	<1299762331.2251.30.camel@shane-desktop>
Message-ID: <AANLkTim9K7Wt_nYg-_jmFoQuE8MuRAn5sYd9+5GsWUPe@mail.gmail.com>

Where there is apparent fraud, it might make sense to penalize the LIR
if they are complicit in this.

I do have my doubts about the *current* need for an LIR, to be frank
(as opposed to an ISP that acquires a large IP block and swips it to
their downstream customers)

On Thu, Mar 10, 2011 at 6:35 PM, Shane Kerr <shane at time-travellers.org> wrote:
> The RIPE NCC is currently finishing implementing a newish requirement
> that PI blocks have a contract with either the RIPE NCC or with an LIR.
> Based on this is should be possible to revoke misused PI space (where
> "misuse" is defined as "not being used for the purpose assigned under",
> *not* defined as "being used for things I do not like").
>
> In theory that policy already exists for all RIPE NCC space, I think. Do
> you think we should try to push for the RIPE NCC to actually implement
> this policy? Do you think there should be further penalties for LIRs
> involved with arranging bogus PI assignments?



-- 
Suresh Ramasubramanian (ops.lists at gmail.com)



From ops.lists at gmail.com  Thu Mar 10 15:27:27 2011
From: ops.lists at gmail.com (Suresh Ramasubramanian)
Date: Thu, 10 Mar 2011 19:57:27 +0530
Subject: [anti-abuse-wg] LIR membership, was Policy disallowing spam from
 RIPE blocks
In-Reply-To: <82y64n3y41.fsf@mid.bfk.de>
References: <48942.1299672364@tristatelogic.com>
	<1299676562.2210.43.camel@shane-desktop>
	<AANLkTi=N__1LByaLi_1gaJedJr76o-A8isjn2LOt0BR5@mail.gmail.com>
	<1299680973.2210.72.camel@shane-desktop>
	<AANLkTi=9UZ0zxL9cRhGcRBi_LxfrfNgsf8NV10Yeh0Bh@mail.gmail.com>
	<1299762960.2251.41.camel@shane-desktop>
	<82y64n3y41.fsf@mid.bfk.de>
Message-ID: <AANLkTi=sWxNge8W6ceocNoX7icUmrwtVZ3+AtD4NvegY@mail.gmail.com>

There's no question of cartelization here - merely a background check
of the sort that any bank carries out when sanctioning a loan.

[which is the closest analogy I can find to an RIR being a custodian
of, and allocating IP addresses to its members]

On Thu, Mar 10, 2011 at 6:56 PM, Florian Weimer <fweimer at bfk.de> wrote:
> It's difficult to introduce the right level of barriers because we
> need to walk a fine line between preventing devaluation of RIPE
> address space and forming a cartel which excludes potential
> competitors.
>



-- 
Suresh Ramasubramanian (ops.lists at gmail.com)



From michele at blacknight.ie  Thu Mar 10 15:29:00 2011
From: michele at blacknight.ie (Michele Neylon :: Blacknight)
Date: Thu, 10 Mar 2011 14:29:00 +0000
Subject: [anti-abuse-wg] Re: Policy proposal: closing
 allocation/assignment window, was Policy disallowing spam from RIPE blocks
In-Reply-To: <AANLkTim9K7Wt_nYg-_jmFoQuE8MuRAn5sYd9+5GsWUPe@mail.gmail.com>
References: <48942.1299672364@tristatelogic.com>
 <1299676562.2210.43.camel@shane-desktop>
 <AANLkTi=N__1LByaLi_1gaJedJr76o-A8isjn2LOt0BR5@mail.gmail.com>
 <1299680973.2210.72.camel@shane-desktop>
 <AANLkTi=9UZ0zxL9cRhGcRBi_LxfrfNgsf8NV10Yeh0Bh@mail.gmail.com>
 <1299762331.2251.30.camel@shane-desktop>
 <AANLkTim9K7Wt_nYg-_jmFoQuE8MuRAn5sYd9+5GsWUPe@mail.gmail.com>
Message-ID: <735749EC-B76C-441D-AEC2-C77BF83F8284@blacknight.ie>

On 10 Mar 2011, at 14:25, Suresh Ramasubramanian wrote:

> Where there is apparent fraud, it might make sense to penalize the LIR
> if they are complicit in this.
> 
> I do have my doubts about the *current* need for an LIR, to be frank
> (as opposed to an ISP that acquires a large IP block and swips it to
> their downstream customers)

It's to avoid membership and associated costs etc

A LIR should have the technical know-how etc., to manage requests etc., in a cost-effective manner
A lot of the organisations that take PI space probably don't .. 


> 
> On Thu, Mar 10, 2011 at 6:35 PM, Shane Kerr <shane at time-travellers.org> wrote:
>> The RIPE NCC is currently finishing implementing a newish requirement
>> that PI blocks have a contract with either the RIPE NCC or with an LIR.
>> Based on this is should be possible to revoke misused PI space (where
>> "misuse" is defined as "not being used for the purpose assigned under",
>> *not* defined as "being used for things I do not like").
>> 
>> In theory that policy already exists for all RIPE NCC space, I think. Do
>> you think we should try to push for the RIPE NCC to actually implement
>> this policy? Do you think there should be further penalties for LIRs
>> involved with arranging bogus PI assignments?
> 
> 
> 
> -- 
> Suresh Ramasubramanian (ops.lists at gmail.com)
> 

Mr Michele Neylon
Blacknight Solutions
Hosting & Colocation, Brand Protection
ICANN Accredited Registrar
http://www.blacknight.com/
http://blog.blacknight.com/
http://blacknight.mobi/
http://mneylon.tel
Intl. +353 (0) 59  9183072
US: 213-233-1612 
UK: 0844 484 9361
Locall: 1850 929 929
Direct Dial: +353 (0)59 9183090
Twitter: http://twitter.com/mneylon

PS: Check out our latest offers on domains & hosting: http://domainoffers.me/
-------------------------------
Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty
Road,Graiguecullen,Carlow,Ireland  Company No.: 370845





From ops.lists at gmail.com  Thu Mar 10 15:31:29 2011
From: ops.lists at gmail.com (Suresh Ramasubramanian)
Date: Thu, 10 Mar 2011 20:01:29 +0530
Subject: [anti-abuse-wg] Re: Policy proposal: closing allocation/assignment
 window, was Policy disallowing spam from RIPE blocks
In-Reply-To: <735749EC-B76C-441D-AEC2-C77BF83F8284@blacknight.ie>
References: <48942.1299672364@tristatelogic.com>
	<1299676562.2210.43.camel@shane-desktop>
	<AANLkTi=N__1LByaLi_1gaJedJr76o-A8isjn2LOt0BR5@mail.gmail.com>
	<1299680973.2210.72.camel@shane-desktop>
	<AANLkTi=9UZ0zxL9cRhGcRBi_LxfrfNgsf8NV10Yeh0Bh@mail.gmail.com>
	<1299762331.2251.30.camel@shane-desktop>
	<AANLkTim9K7Wt_nYg-_jmFoQuE8MuRAn5sYd9+5GsWUPe@mail.gmail.com>
	<735749EC-B76C-441D-AEC2-C77BF83F8284@blacknight.ie>
Message-ID: <AANLkTimrhYtEz3=P6qc-mWb9+Pgf+yp=ti=LNq6cZbm0@mail.gmail.com>

On Thu, Mar 10, 2011 at 7:59 PM, Michele Neylon :: Blacknight
<michele at blacknight.ie> wrote:
> A LIR should have the technical know-how etc., to manage requests etc., in a cost-effective manner
> A lot of the organisations that take PI space probably don't ..

PI space normally argues a specific need such as multihoming, or
portability across ISPs.   Any organization that has the technical
knowhow to do this ...
Any ISP can allocate a /24 to a customer with a T3 or a rack of
servers - but does that space necessarily need to be PI?

-- 
Suresh Ramasubramanian (ops.lists at gmail.com)



From michele at blacknight.ie  Thu Mar 10 16:13:51 2011
From: michele at blacknight.ie (Michele Neylon :: Blacknight)
Date: Thu, 10 Mar 2011 15:13:51 +0000
Subject: [anti-abuse-wg] Re: Policy proposal: closing
 allocation/assignment window, was Policy disallowing spam from RIPE blocks
In-Reply-To: <AANLkTimrhYtEz3=P6qc-mWb9+Pgf+yp=ti=LNq6cZbm0@mail.gmail.com>
References: <48942.1299672364@tristatelogic.com>
 <1299676562.2210.43.camel@shane-desktop>
 <AANLkTi=N__1LByaLi_1gaJedJr76o-A8isjn2LOt0BR5@mail.gmail.com>
 <1299680973.2210.72.camel@shane-desktop>
 <AANLkTi=9UZ0zxL9cRhGcRBi_LxfrfNgsf8NV10Yeh0Bh@mail.gmail.com>
 <1299762331.2251.30.camel@shane-desktop>
 <AANLkTim9K7Wt_nYg-_jmFoQuE8MuRAn5sYd9+5GsWUPe@mail.gmail.com>
 <735749EC-B76C-441D-AEC2-C77BF83F8284@blacknight.ie>
 <AANLkTimrhYtEz3=P6qc-mWb9+Pgf+yp=ti=LNq6cZbm0@mail.gmail.com>
Message-ID: <FE504871-AEE9-46A3-B9D8-88ADFAAC51C4@blacknight.ie>

On 10 Mar 2011, at 14:31, Suresh Ramasubramanian wrote:

> On Thu, Mar 10, 2011 at 7:59 PM, Michele Neylon :: Blacknight
> <michele at blacknight.ie> wrote:
>> A LIR should have the technical know-how etc., to manage requests etc., in a cost-effective manner
>> A lot of the organisations that take PI space probably don't ..
> 
> PI space normally argues a specific need such as multihoming, or
> portability across ISPs.   Any organization that has the technical
> knowhow to do this ...

I disagree

We were in that position a few years ago

It made a lot more sense to get PI space than to become fully fledged members of RIPE 

There's an admin overhead etc


> Any ISP can allocate a /24 to a customer with a T3 or a rack of
> servers - but does that space necessarily need to be PI?

It depends on what you are doing.

And yes PI space makes sense

If you get a bunch of IPs from company X and you then stop using them you'll need to renumber


> 
> -- 
> Suresh Ramasubramanian (ops.lists at gmail.com)

Mr Michele Neylon
Blacknight Solutions
Hosting & Colocation, Brand Protection
ICANN Accredited Registrar
http://www.blacknight.com/
http://blog.blacknight.com/
http://blacknight.mobi/
http://mneylon.tel
Intl. +353 (0) 59  9183072
US: 213-233-1612 
UK: 0844 484 9361
Locall: 1850 929 929
Direct Dial: +353 (0)59 9183090
Twitter: http://twitter.com/mneylon

PS: Check out our latest offers on domains & hosting: http://domainoffers.me/
-------------------------------
Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty
Road,Graiguecullen,Carlow,Ireland  Company No.: 370845





From ops.lists at gmail.com  Thu Mar 10 16:21:04 2011
From: ops.lists at gmail.com (Suresh Ramasubramanian)
Date: Thu, 10 Mar 2011 20:51:04 +0530
Subject: [anti-abuse-wg] Re: Policy proposal: closing allocation/assignment
 window, was Policy disallowing spam from RIPE blocks
In-Reply-To: <FE504871-AEE9-46A3-B9D8-88ADFAAC51C4@blacknight.ie>
References: <48942.1299672364@tristatelogic.com>
	<1299676562.2210.43.camel@shane-desktop>
	<AANLkTi=N__1LByaLi_1gaJedJr76o-A8isjn2LOt0BR5@mail.gmail.com>
	<1299680973.2210.72.camel@shane-desktop>
	<AANLkTi=9UZ0zxL9cRhGcRBi_LxfrfNgsf8NV10Yeh0Bh@mail.gmail.com>
	<1299762331.2251.30.camel@shane-desktop>
	<AANLkTim9K7Wt_nYg-_jmFoQuE8MuRAn5sYd9+5GsWUPe@mail.gmail.com>
	<735749EC-B76C-441D-AEC2-C77BF83F8284@blacknight.ie>
	<AANLkTimrhYtEz3=P6qc-mWb9+Pgf+yp=ti=LNq6cZbm0@mail.gmail.com>
	<FE504871-AEE9-46A3-B9D8-88ADFAAC51C4@blacknight.ie>
Message-ID: <AANLkTik9dV6ahDhNmXWEwi8fmUuwUJ7c2uNuSrTdgyXj@mail.gmail.com>

On Thu, Mar 10, 2011 at 8:43 PM, Michele Neylon :: Blacknight
<michele at blacknight.ie> wrote:
>
> If you get a bunch of IPs from company X and you then stop using them you'll need to renumber
>

Yes, as I said, "portability across ISPs".

-- 
Suresh Ramasubramanian (ops.lists at gmail.com)



From noreply at ripe.net  Thu Mar 10 16:46:57 2011
From: noreply at ripe.net (Axel Pawlik)
Date: Thu, 10 Mar 2011 16:46:57 +0100
Subject: [anti-abuse-wg] Closure of LIR and Deregistration of Internet Number Resources
Message-ID: <4D78F271.6080900@ripe.net>

[Apologies for duplicate emails]

Dear colleagues,

The RIPE NCC, after receiving feedback from the RIPE community on the 
draft version, has published the procedural RIPE Document ripe-517, 
"Closure of LIR and Deregistration of Internet Number Resources". The 
document is available at:
https://www.ripe.net/ripe/docs/ripe-517

This document replaces sections in two RIPE Documents that deal with the 
closure of LIRs and the deregistration of resources:

- Sections 3.0 and 4.0 of ripe-301, "Mergers, Acquisitions, Takeovers 
and Closures of Organisations Operating an LIR". These sections are 
entitled "Closing an LIR" and "When an LIR is Closed by the RIPE NCC", 
respectively.

The updated version of this RIPE Document is available at:
https://www.ripe.net/ripe/docs/ripe-515

- Sections 4.0, 4.1 and 4.2 of ripe-475, "Independent Internet Number 
Resources - Contractual Relationship Changes between sponsoring LIR and 
End User". These sections are entitled ?De-registering of Independent 
Internet Number Resources?, ?Closure of Sponsoring LIR? and "Violation 
of RIPE Policy, Law or Contract", respectively.

The updated version of this RIPE Document is available at:
https://www.ripe.net/ripe/docs/ripe-516

The RIPE NCC would like to thank the RIPE community for its feedback.

An interactive chart that helps to explain the process of closure of 
LIRs and deregistration of Internet number resources will be available 
shortly.

Best regards,

Axel Pawlik
Managing Director
RIPE NCC



From Woeber at CC.UniVie.ac.at  Sun Mar 13 20:31:44 2011
From: Woeber at CC.UniVie.ac.at (Wilfried Woeber, UniVie/ACOnet)
Date: Sun, 13 Mar 2011 19:31:44 +0000
Subject: [anti-abuse-wg] LIR membership
In-Reply-To: <1299762960.2251.41.camel@shane-desktop>
References: <48942.1299672364@tristatelogic.com>	 <1299676562.2210.43.camel@shane-desktop>	 <AANLkTi=N__1LByaLi_1gaJedJr76o-A8isjn2LOt0BR5@mail.gmail.com>	 <1299680973.2210.72.camel@shane-desktop>	 <AANLkTi=9UZ0zxL9cRhGcRBi_LxfrfNgsf8NV10Yeh0Bh@mail.gmail.com> <1299762960.2251.41.camel@shane-desktop>
Message-ID: <4D7D1BA0.3080006@CC.UniVie.ac.at>

Shane Kerr wrote:

[...]
> I don't represent an LIR, so it feels a bit weird to recommend changes
> to the process. If it is too easy, some things can be done. Perhaps some
> sort of process where you need to be introduced by another LIR before
> you can join? It would be a low hurdle, but it might be something.

This would definitely raise some eyebrows, as has been said already.

Moreover, I'd expect serious procedural problems for some regions and/or
types of applicants.

> --
> Shane

I think this approach is neither useful nor feasible - and it wouldn't
achieve the goal, on top of it ;-)

Wilfried.



From Woeber at CC.UniVie.ac.at  Sun Mar 13 20:54:40 2011
From: Woeber at CC.UniVie.ac.at (Wilfried Woeber, UniVie/ACOnet)
Date: Sun, 13 Mar 2011 19:54:40 +0000
Subject: [anti-abuse-wg] Policy proposal: closing allocation/assignment
 window, was Policy disallowing spam from RIPE blocks
In-Reply-To: <20110310131719.GG30227@Space.Net>
References: <48942.1299672364@tristatelogic.com> <1299676562.2210.43.camel@shane-desktop> <AANLkTi=N__1LByaLi_1gaJedJr76o-A8isjn2LOt0BR5@mail.gmail.com> <1299680973.2210.72.camel@shane-desktop> <AANLkTi=9UZ0zxL9cRhGcRBi_LxfrfNgsf8NV10Yeh0Bh@mail.gmail.com> <1299762331.2251.30.camel@shane-desktop> <20110310131719.GG30227@Space.Net>
Message-ID: <4D7D2100.4070301@CC.UniVie.ac.at>

[...]
>>If you mean the process by which provider-independent (PI) space is
>>assigned, then as I understand it this REQUIRES an LIR to make the
>>request on your behalf.

To be more precise: to submit the request on behalf of the applicant.
Presumably the sponsoring LIR has already made sure that the requirements
are met, before forwarding to the NCC.

>> I assume that the RIPE NCC reviews each request, the same as they
>>  would any address request.

Indeed, they do. Very painstakingly, I may add :-)

>>To be honest, I don't really understand what the LIR role in this whole
>>process is, other than maybe companies prefer to work with a local
>>company that speaks their language, is in their time zone, and
>>understands their business environment. 
> 
> 
> This is the whole point.  There might be a business relation with a local
> LIR already,

Which allows everyone involved to keep things local and somewaht simpler,
and to be more cost-efficient. E.g. the LIR may send an invoice to the
customer anyway, so any surcharge may be added to that, instead of having
the NCC issue an invoice and follow up. Local payment is simpler and
cheaper than international money transfer for some regions...

> and that's way easier for "smallish companies" than to do 
> international contracts with Amstedam.
> 
> You *can* get the PI space from the RIPE NCC directly (nowadays) by becoming 
> a so-called "direct access user" - but this is more expensive, and more
> paperwork.

The amount of paperwork is pretty comparable (with the exception of the
direct contract between applicant and the NCC), but the load is spread.
E.g. the applicant still has to provide the (same) documentation about
its existence and the sponsoring LIR has to forward that info to the NCC.
And this info, again, is checked by the NCC. I can vouch for that ;-)

Plus, there is a contractual requirement for the sponsoring LIR to keep
the records for the PI stuff up to date and/or make sure that the holder
of the resource complies.

> Gert Doering
>         -- NetMaster

Wilfried.



From Woeber at CC.UniVie.ac.at  Sun Mar 13 21:07:42 2011
From: Woeber at CC.UniVie.ac.at (Wilfried Woeber, UniVie/ACOnet)
Date: Sun, 13 Mar 2011 20:07:42 +0000
Subject: [anti-abuse-wg] Policy proposal: closing allocation/assignment
 window, was Policy disallowing spam from RIPE blocks
In-Reply-To: <1299762331.2251.30.camel@shane-desktop>
References: <48942.1299672364@tristatelogic.com>	 <1299676562.2210.43.camel@shane-desktop>	 <AANLkTi=N__1LByaLi_1gaJedJr76o-A8isjn2LOt0BR5@mail.gmail.com>	 <1299680973.2210.72.camel@shane-desktop>	 <AANLkTi=9UZ0zxL9cRhGcRBi_LxfrfNgsf8NV10Yeh0Bh@mail.gmail.com> <1299762331.2251.30.camel@shane-desktop>
Message-ID: <4D7D240E.7020307@CC.UniVie.ac.at>

Shane Kerr wrote:

[...]
>>1. Closing the allocation window / giving LIRs less leeway in
>>approvals [so there should be no difference in submitting a request
>>through a LIR, or through the RIR]
> 
> 
> Do you mean the "assignment window"?

On a more fundamental aspect: the assignment window is meant to be an
optimisation for well-behaving LIRs, to prevent every request to be
touched by an IPRA at the NCC.

We have to keep in mind that processing requests by the IPRAs in AMS does
not come for free. The cost is borne by the LIRs, i.e. the members' annual
fee, in the end.

Wearing my hat as an LIR-Manager, I'd object aainst any proposal to
terminate the assignment window mechanism.


Btw, on top of all the stuff that was said already about checking, there
is also the formal LIR-Review Process, done by the NCC.

This is not fun - well, it is "fun", if the LIR *has* its act together.
I have been through that with our LIR a while ago (and quite easily got
the approval stamp :-) ).

The trigger for such a review is either the NCC "rolling the dice" or
receiving complaints about the behaviour of a particular LIR!


So, instead of proposing to make life more difficult, and thus more
expensive, for the vast majority of well-behaving LIRs, I'd suggest to
use the already existing processess and mechanisms to follow up on any
(perceived) abuse.

[...]
> --
> Shane

Regards,
Wilfried (wearing my hat as an LIR manager for a moment)



From ops.lists at gmail.com  Mon Mar 14 02:24:22 2011
From: ops.lists at gmail.com (Suresh Ramasubramanian)
Date: Mon, 14 Mar 2011 06:54:22 +0530
Subject: [anti-abuse-wg] Policy proposal: closing allocation/assignment
 window, was Policy disallowing spam from RIPE blocks
In-Reply-To: <4D7D2100.4070301@CC.UniVie.ac.at>
References: <48942.1299672364@tristatelogic.com>
	<1299676562.2210.43.camel@shane-desktop>
	<AANLkTi=N__1LByaLi_1gaJedJr76o-A8isjn2LOt0BR5@mail.gmail.com>
	<1299680973.2210.72.camel@shane-desktop>
	<AANLkTi=9UZ0zxL9cRhGcRBi_LxfrfNgsf8NV10Yeh0Bh@mail.gmail.com>
	<1299762331.2251.30.camel@shane-desktop>
	<20110310131719.GG30227@Space.Net>
	<4D7D2100.4070301@CC.UniVie.ac.at>
Message-ID: <AANLkTi=yUg4SUGuecsEszfi5fLK6JXBnJpoFvTUa6+mG@mail.gmail.com>

On Mon, Mar 14, 2011 at 1:24 AM, Wilfried Woeber, UniVie/ACOnet
<Woeber at cc.univie.ac.at> wrote:
> To be more precise: to submit the request on behalf of the applicant.
> Presumably the sponsoring LIR has already made sure that the requirements
> are met, before forwarding to the NCC.

Depends on whether or not the LIR is complicit in the matter or not.

> the NCC issue an invoice and follow up. Local payment is simpler and
> cheaper than international money transfer for some regions...

Still?

> Plus, there is a contractual requirement for the sponsoring LIR to keep
> the records for the PI stuff up to date and/or make sure that the holder
> of the resource complies.

Well, I'm on the other hand assured that "we're not the document
police" - which was a quote from someone else one or two abuse-wg
meetings back ..

-- 
Suresh Ramasubramanian (ops.lists at gmail.com)



From brian.nisbet at heanet.ie  Wed Mar 23 14:23:25 2011
From: brian.nisbet at heanet.ie (Brian Nisbet)
Date: Wed, 23 Mar 2011 13:23:25 +0000
Subject: [anti-abuse-wg] Proposed New Working Group Co-Chair
Message-ID: <4D89F44D.9020609@heanet.ie>

Colleagues,

After the events of RIPE 61 I announced that it was my intention to have 
a new co-chair in place at or by RIPE 62 in Amsterdam this coming May. 
After the comments at that meeting and the emails I sent out in the 
interim, one person has put themselves forward. I believe this person to 
be eminently suitable for the position and so I would like to present 
him to the working group for your consideration. As there is one 
position and one candidate it is a matter of simple consensus.

My intention is to give a period of two weeks on the list for any 
comments to be sent (either to the list or to me personally) and then to 
devote a short amount of time to this at our WG session in Amsterdam. 
However assuming there is no notable objection on the mailing list this 
should be a very small amount of time indeed.

Anyway, that's a lot of preamble, the candidate to take up the position 
of Co-Chair of the RIPE Anti-Abuse WG is Tobias Knecht from Abusix. Many 
of you will already know Tobias and I believe that his knowledge of and 
connections to the anti-abuse community will be extremely useful in 
progressing the work of the AA-WG.

If you have any questions for Tobias (or for me, obviously) then, as I 
said, please email them either directly to us or to the list.

Thanks,

Brian.
Chair, RIPE Anti-Abuse WG



From andreas.schulze at datev.de  Wed Mar 23 15:07:34 2011
From: andreas.schulze at datev.de (Andreas Schulze)
Date: Wed, 23 Mar 2011 15:07:34 +0100
Subject: [anti-abuse-wg] Proposed New Working Group Co-Chair
In-Reply-To: <4D89F44D.9020609@heanet.ie>
References: <4D89F44D.9020609@heanet.ie>
Message-ID: <20110323140734.GA31923@spider.services.datevnet.de>

Am 23.03.2011 13:23 schrieb Brian Nisbet:

I do not know in detail, what the position of a co-chair means.
But I know Tobias and share his opinions. It's a Question of trust.

so, yes, +1

Andreas

-- 
Andreas Schulze
Internetdienste | P252

DATEV eG
90329 N?rnberg | Telefon +49 911 319-0 | Telefax +49 911 319-3196
E-Mail info @datev.de | Internet www.datev.de
Sitz: 90429 N?rnberg, Paumgartnerstr. 6-14 | Registergericht N?rnberg, GenReg Nr.70
Vorstand
Prof. Dieter Kempf (Vorsitzender)
Dipl.-Kfm. Wolfgang Stegmann (stellvertretender Vorsitzender)
Dipl.-Kfm. Michael Leistenschneider
J?rg Rabe v. Pappenheim
Dipl.-Vw. Eckhard Schwarzer
Vorsitzender des Aufsichtsrates: Reinhard Verholen



From kzorba at otenet.gr  Wed Mar 23 15:29:45 2011
From: kzorba at otenet.gr (Kostas Zorbadelos)
Date: Wed, 23 Mar 2011 16:29:45 +0200
Subject: [anti-abuse-wg] Proposed New Working Group Co-Chair
In-Reply-To: <4D89F44D.9020609@heanet.ie>
References: <4D89F44D.9020609@heanet.ie>
Message-ID: <4D8A03D9.9080204@otenet.gr>

On 03/23/2011 03:23 PM, Brian Nisbet wrote:

> Anyway, that's a lot of preamble, the candidate to take up the position
> of Co-Chair of the RIPE Anti-Abuse WG is Tobias Knecht from Abusix. Many
> of you will already know Tobias and I believe that his knowledge of and
> connections to the anti-abuse community will be extremely useful in
> progressing the work of the AA-WG.

Tobias' work up to now and his proposals are among the most useful 
things produced in this WG.
Therefore from what I have seen, Tobias seems a very good candidate for 
the position. I can only hope that this will be a new beginning for some 
useful work in this WG.

Regards,

Kostas Zorbadelos



From sascha.wilms at eco.de  Wed Mar 23 15:32:51 2011
From: sascha.wilms at eco.de (Sascha Wilms)
Date: Wed, 23 Mar 2011 15:32:51 +0100
Subject: AW: [anti-abuse-wg] Proposed New Working Group Co-Chair
In-Reply-To: <4D89F44D.9020609@heanet.ie>
References: <4D89F44D.9020609@heanet.ie>
Message-ID: <E37851F1DBC78442A2F7956FCF9F038B079C38BE454F@DPA-EXCHANGE01.dc.dom>

 
Hi all,

I would like to express our full support of Tobias' recommendation as co-chair. 
He can certainly make a great contribution to the success of the wg.

Regards
Sascha 

> -----Urspr?ngliche Nachricht-----
> Von: anti-abuse-wg-admin at ripe.net 
> [mailto:anti-abuse-wg-admin at ripe.net] Im Auftrag von Brian Nisbet
> Gesendet: Mittwoch, 23. M?rz 2011 14:23
> An: anti-abuse-wg at ripe.net
> Betreff: [anti-abuse-wg] Proposed New Working Group Co-Chair
> 
> Colleagues,
> 
> After the events of RIPE 61 I announced that it was my 
> intention to have a new co-chair in place at or by RIPE 62 in 
> Amsterdam this coming May. 
> After the comments at that meeting and the emails I sent out 
> in the interim, one person has put themselves forward. I 
> believe this person to be eminently suitable for the position 
> and so I would like to present him to the working group for 
> your consideration. As there is one position and one 
> candidate it is a matter of simple consensus.
> 
> My intention is to give a period of two weeks on the list for 
> any comments to be sent (either to the list or to me 
> personally) and then to devote a short amount of time to this 
> at our WG session in Amsterdam. 
> However assuming there is no notable objection on the mailing 
> list this should be a very small amount of time indeed.
> 
> Anyway, that's a lot of preamble, the candidate to take up 
> the position of Co-Chair of the RIPE Anti-Abuse WG is Tobias 
> Knecht from Abusix. Many of you will already know Tobias and 
> I believe that his knowledge of and connections to the 
> anti-abuse community will be extremely useful in progressing 
> the work of the AA-WG.
> 
> If you have any questions for Tobias (or for me, obviously) 
> then, as I said, please email them either directly to us or 
> to the list.
> 
> Thanks,
> 
> Brian.
> Chair, RIPE Anti-Abuse WG
> 
> 


From james.davis at ja.net  Wed Mar 23 15:32:56 2011
From: james.davis at ja.net (James Davis)
Date: Wed, 23 Mar 2011 14:32:56 +0000
Subject: [anti-abuse-wg] Proposed New Working Group Co-Chair
In-Reply-To: <20110323140734.GA31923@spider.services.datevnet.de>
References: <4D89F44D.9020609@heanet.ie> <20110323140734.GA31923@spider.services.datevnet.de>
Message-ID: <4D8A0498.4090500@ja.net>

On 23/03/2011 14:07, Andreas Schulze wrote:

> I do not know in detail, what the position of a co-chair means.
> But I know Tobias and share his opinions. It's a Question of trust.

I don't know Tobias but at JANET CSIRT we value the work and effort that 
Abusix have done in this field, and his contributions to this group have 
been most useful.

I think that he'd be a great asset to this group as co-chair.

James

-- 
James Davis                0300 999 2340 (+44 1235 822340)
Senior CSIRT Member	
Lumen House, Library Avenue, Didcot, Oxfordshire, OX11 0SG

JANET(UK) is a trading name of The JNT Association, a company limited
by guarantee which is registered in England under No. 2881024 
and whose Registered Office is at Lumen House, Library Avenue,
Harwell Oxford, Didcot, Oxfordshire. OX11 0SG



From vesely at tana.it  Wed Mar 23 17:49:41 2011
From: vesely at tana.it (Alessandro Vesely)
Date: Wed, 23 Mar 2011 17:49:41 +0100
Subject: [anti-abuse-wg] Proposed New Working Group Co-Chair
In-Reply-To: <4D89F44D.9020609@heanet.ie>
References: <4D89F44D.9020609@heanet.ie>
Message-ID: <4D8A24A5.6040705@tana.it>

On 23.03.2011 14:23, Brian Nisbet wrote:
> Many of you will already know Tobias and I believe that his knowledge of
> and connections to the anti-abuse community will be extremely useful in
> progressing the work of the AA-WG.

+1, and thanks to Tobias for this further commitment of his.



From michele at blacknight.ie  Wed Mar 23 17:55:59 2011
From: michele at blacknight.ie (Michele Neylon :: Blacknight)
Date: Wed, 23 Mar 2011 16:55:59 +0000
Subject: [anti-abuse-wg] Proposed New Working Group Co-Chair
In-Reply-To: <4D8A24A5.6040705@tana.it>
References: <4D89F44D.9020609@heanet.ie>,<4D8A24A5.6040705@tana.it>
Message-ID: <4F2538C315ACAC42AD334C533C247C471C35643C@bkexchmbx02.blacknight.local>

Glad to see that somebody stepped up to the plate :)


PS: rss.me is now in beta - signup using invite code: "gambit" (no quotes)
--
Mr Michele Neylon
Blacknight Solutions
Hosting & Colocation, Brand Protection
http://www.blacknight.com/
http://blog.blacknight.com/
http://mneylon.tel/
Intl. +353 (0) 59  9183072
Locall: 1850 929 929
Direct Dial: +353 (0)59 9183090
Fax. +353 (0) 1 4811 763
Twitter: http://twitter.com/mneylon
-------------------------------
Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty
Road,Graiguecullen,Carlow,Ireland  Company No.: 370845


From aftab.siddiqui at gmail.com  Wed Mar 23 20:04:57 2011
From: aftab.siddiqui at gmail.com (Aftab Siddiqui)
Date: Thu, 24 Mar 2011 00:04:57 +0500
Subject: [anti-abuse-wg] Proposed New Working Group Co-Chair
In-Reply-To: <4F2538C315ACAC42AD334C533C247C471C35643C@bkexchmbx02.blacknight.local>
References: <4D89F44D.9020609@heanet.ie>
	<4D8A24A5.6040705@tana.it>
	<4F2538C315ACAC42AD334C533C247C471C35643C@bkexchmbx02.blacknight.local>
Message-ID: <AANLkTinFL8JUagW5fPA6m3=KDdu6CQXfj-sq9q7bGYUy@mail.gmail.com>

I don't fall in the RIPE region but I can share one thing with the WG that
its because of Tobias that today APNIC has a mandatory abuse contact info.
Will be Glad to see him on the co-chair post.


Regards,

Aftab A. Siddiqui


On Wed, Mar 23, 2011 at 9:55 PM, Michele Neylon :: Blacknight <
michele at blacknight.ie> wrote:

> Glad to see that somebody stepped up to the plate :)
>
>
> PS: rss.me is now in beta - signup using invite code: "gambit" (no quotes)
> --
> Mr Michele Neylon
> Blacknight Solutions
> Hosting & Colocation, Brand Protection
> http://www.blacknight.com/
> http://blog.blacknight.com/
> http://mneylon.tel/
> Intl. +353 (0) 59 9183072 <%2B353%20%280%29%2059%20%209183072>
> Locall: 1850 929 929
> Direct Dial: +353 (0)59 9183090
> Fax. +353 (0) 1 4811 763
> Twitter: http://twitter.com/mneylon
> -------------------------------
> Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty
> Road,Graiguecullen,Carlow,Ireland  Company No.: 370845
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ripe.net/ripe/mail/archives/anti-abuse-wg/attachments/20110324/671644be/attachment.html>

From ops.lists at gmail.com  Thu Mar 24 02:18:43 2011
From: ops.lists at gmail.com (Suresh Ramasubramanian)
Date: Thu, 24 Mar 2011 06:48:43 +0530
Subject: [anti-abuse-wg] Proposed New Working Group Co-Chair
In-Reply-To: <4D89F44D.9020609@heanet.ie>
References: <4D89F44D.9020609@heanet.ie>
Message-ID: <AANLkTi=vSUMr6imhuP95CwD+AuLHUdS+XswbVjzwZGEt@mail.gmail.com>

On Wed, Mar 23, 2011 at 6:53 PM, Brian Nisbet <brian.nisbet at heanet.ie> wrote:
> Anyway, that's a lot of preamble, the candidate to take up the position of
> Co-Chair of the RIPE Anti-Abuse WG is Tobias Knecht from Abusix.

I support.

-- 
Suresh Ramasubramanian (ops.lists at gmail.com)



From tk at abusix.com  Thu Mar 24 10:42:00 2011
From: tk at abusix.com (Tobias Knecht)
Date: Thu, 24 Mar 2011 10:42:00 +0100
Subject: [anti-abuse-wg] Thanks for the support!  was: Proposed New Working Group Co-Chair
In-Reply-To: <4D89F44D.9020609@heanet.ie>
References: <4D89F44D.9020609@heanet.ie>
Message-ID: <4D8B11E8.7070700@abusix.com>

Thanks to Brian for his great work as a chair and for accepting me as a
possible future colleague ;-) And of course thanks to everybody for the
support. :-)

As Brian already mentioned, if there are any questions please let me
know. I hope that I can meet as much people from this and other RIR
lists as possible in May in Amsterdam . See you there. :-)

Thanks,

Tobias

-- 
abusix.org



Am 23.03.11 14:23, schrieb Brian Nisbet:
> Colleagues,
> 
> After the events of RIPE 61 I announced that it was my intention to have
> a new co-chair in place at or by RIPE 62 in Amsterdam this coming May.
> After the comments at that meeting and the emails I sent out in the
> interim, one person has put themselves forward. I believe this person to
> be eminently suitable for the position and so I would like to present
> him to the working group for your consideration. As there is one
> position and one candidate it is a matter of simple consensus.
> 
> My intention is to give a period of two weeks on the list for any
> comments to be sent (either to the list or to me personally) and then to
> devote a short amount of time to this at our WG session in Amsterdam.
> However assuming there is no notable objection on the mailing list this
> should be a very small amount of time indeed.
> 
> Anyway, that's a lot of preamble, the candidate to take up the position
> of Co-Chair of the RIPE Anti-Abuse WG is Tobias Knecht from Abusix. Many
> of you will already know Tobias and I believe that his knowledge of and
> connections to the anti-abuse community will be extremely useful in
> progressing the work of the AA-WG.
> 
> If you have any questions for Tobias (or for me, obviously) then, as I
> said, please email them either directly to us or to the list.
> 
> Thanks,
> 
> Brian.
> Chair, RIPE Anti-Abuse WG
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 267 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ripe.net/ripe/mail/archives/anti-abuse-wg/attachments/20110324/179ccea3/attachment.sig>

From Piotr.Strzyzewski at polsl.pl  Thu Mar 24 10:32:37 2011
From: Piotr.Strzyzewski at polsl.pl (Piotr Strzyzewski)
Date: Thu, 24 Mar 2011 10:32:37 +0100
Subject: [anti-abuse-wg] Proposed New Working Group Co-Chair
In-Reply-To: <AANLkTi=vSUMr6imhuP95CwD+AuLHUdS+XswbVjzwZGEt@mail.gmail.com>
References: <4D89F44D.9020609@heanet.ie> <AANLkTi=vSUMr6imhuP95CwD+AuLHUdS+XswbVjzwZGEt@mail.gmail.com>
Message-ID: <20110324093237.GB25874@hydra.ck.polsl.pl>

On Thu, Mar 24, 2011 at 06:48:43AM +0530, Suresh Ramasubramanian wrote:
> On Wed, Mar 23, 2011 at 6:53 PM, Brian Nisbet <brian.nisbet at heanet.ie> wrote:
> > Anyway, that's a lot of preamble, the candidate to take up the position of
> > Co-Chair of the RIPE Anti-Abuse WG is Tobias Knecht from Abusix.
> 
> I support.

+1

Piotr

-- 
gucio -> Piotr Strzy?ewski
E-mail: Piotr.Strzyzewski at polsl.pl