Jump to content
Sign in to follow this  
cwg

84.246.227.0 - 84.246.230.255 is email masked ripe lookup requiring -B

Recommended Posts

Parse:

http://www.spamcop.net/sc?id=z4224378412z0...958273849b5aafz

-----

Tracking message source: 84.246.229.67:
Display data:
"whois 84.246.229.67[at]whois.ripe.net" (Getting contact from whois.ripe.net)
Lookup bh1182-ripe[at]whois.ripe.net
   Display data:
   "whois bh1182-ripe[at]whois.ripe.net" (Getting contact from whois.ripe.net)
   bh1182-ripe =
whois.ripe.net 84.246.229.67 (nothing found)
No reporting addresses found for 84.246.229.67, using devnull for tracking.

whois.ripe.net 84.246.229.67 -B

% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See http://www.ripe.net/db/support/db-terms-conditions.pdf

% Information related to '84.246.227.0 - 84.246.230.255'

inetnum:		 84.246.227.0 - 84.246.230.255
netname:		 ELBMULTIMEDIA2
descr:		   netissime
country:		 FR
admin-c:		 BH1182-RIPE
tech-c:		  BH1182-RIPE
status:		  ASSIGNED PA
mnt-by:		  ELB-MNT
mnt-lower:	   ELB-MNT
mnt-routes:	  ELB-MNT
changed:		 ws[at]comalis.com 20081113
source:		  RIPE

person:		  Boulahbel  hichem
address:		 17 rue jean bourgey Villeurbanne 69100
phone:		   +33437430037
nic-hdl:		 Bh1182-RIPE
changed:		 bh[at]netissime.com 20041027
source:		  RIPE

% Information related to '84.246.224.0/21AS34274'

route:		   84.246.224.0/21
descr:		   Routage ELB MULTIMEDIA HOSTING
origin:		  AS34274
mnt-by:		  elb-mnt
changed:		 bh[at]netissime.com 20050311
source:		  RIPE

Share this post


Link to post
Share on other sites

If you would provide a working abuse address in your posts, we would have something. As it is, they're just wasted posts.

- Don D'Minion - SpamCop Admin -

Share this post


Link to post
Share on other sites

As is, unless I find out otherwise, I'd use bh[at]netissime.com as the sole address available from the lookup for reporting abuse to?

Share this post


Link to post
Share on other sites

As would I, but after some digging around at RIPE┬╣, I can see why SpamCop is reluctant:

http://www.ripe.net/info/faq/abuse/using_whois.html

Do not use the email address in the "changed" line of the RIPE Database object. Look for abuse email addresses in the "remarks" field, or use the email address from the "tech-c" or "admin-c".
(they also refer to an optional 'abusemailbox' field here)

The only e-mail address listed for BH1182-RIPE is in a "changed" line. :rolleyes:

┬╣ I wanted to know what is the purpose of the -B flag (why hide details if you can show them with a switch) - didn't find anything.

Edited by Snowbat

Share this post


Link to post
Share on other sites

There was a proposal in 2006 to add the following to a RIPE policy document:

Registration data (range, contact information, status etc.) must be correct at all times (i.e. they have to be maintained). Every organisation controlling an IP address should provide at least one working contact e-mail address where notifications of abuse emanating from that IP address can be sent.
It was withdrawn as not enough consensus was reached.

Also some discussion in 2008 but no action.

Edited by Snowbat

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×