Jump to content

Coping with abuse addresses in RIPE that are images?


Recommended Posts


Return-Path: <RalphLauren@wolved.info>
X-Original-To: x
Delivered-To: x
X-Greylist: delayed 00:06:28 by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.jhmg.net 937B2403AA
Authentication-Results: smtp.jhmg.net;
	dkim=pass (1024-bit key) header.d=wolved.info header.i=@wolved.info header.b="DpuNugtc"
Received: from smoking.wolved.info (smoking.wolved.info [])
	by smtp.jhmg.net (Postfix) with ESMTP id 937B2403AA
	for <x>; Tue,  8 Aug 2017 13:08:43 -0400 (EDT)

Here's the SC interpretation...

Tracking message source:


Display data:
"whois" (Getting contact from whois.arin.net )
   Redirect to ripe
   Display data:
   "whois" (Getting contact from whois.ripe.net)
   Lookup fdl258-ripe@whois.ripe.net
      Display data:
      "whois fdl258-ripe@whois.ripe.net" (Getting contact from whois.ripe.net)
      fdl258-ripe =
   whois.ripe.net (nothing found)
No reporting addresses found for, using devnull for tracking.
HOWEVER... see the attached image. The issue is that the reporting address is an image and not text.
Are there any solutions?  It would be really helpful if we could add an ad-hoc destination on the analysis results screen to cope with this issue.



Link to comment
Share on other sites

I'm guessing that RIPE has achieved their objective by making the "Abuse contact" a  CAPTCHA. 

I would suggest when you find situations like this during your research that you make an entry in "Reporting Help" -> "Routing/ Report address issues" forum.

Link to comment
Share on other sites

  • 2 weeks later...


This topic is now archived and is closed to further replies.

  • Create New...