Jump to content

dtz

Members
  • Content Count

    23
  • Joined

  • Last visited

Community Reputation

0 Neutral

About dtz

  • Rank
    Member
  1. Abuse contact for '91.235.64.0 - 91.235.64.255' is 'it[at]euromsg.com'
  2. Abuse contact for '141.101.186.0 - 141.101.186.255' is 'info[at]leadertelecom.ru'
  3. SpamCop whois mirror seems to be outdated, has only generic response for inetnum: 103.0.0.0 - 103.255.255.255 % [whois.apnic.net] % Whois data copyright terms http://www.apnic.net/db/dbcopyright.html % Information related to '103.41.176.0 - 103.41.176.255' inetnum: 103.41.176.0 - 103.41.176.255 netname: RedSwitchesNetherlands descr: Hosting Solutions country: NL admin-c: RPLA7-AP tech-c: RPLA7-AP status: ALLOCATED NON-PORTABLE mnt-by: MAINT-RSL-AU mnt-irt: IRT-RSL-AU changed: abuse[at]redswitches.com 20141217 source: APNIC irt: IRT-RSL-AU address: Level 3, 480 Collins Street, Melbourne Victoria 3000 e-mail: abuse[at]redswitches.com abuse-mailbox: abuse[at]redswitches.com
  4. I have nearly the same problem as http://forum.spamcop.net/forums/topic/14874-resolved189212017-should-go-to-axtelipmasteratgmailcom-not-abuseatgmailcom/: Would it be possible to blacklist gmail.com (and maybe other free email providers) for lookups on abuse.net to prevent misdirections like this? I cannot see any case, where lookups for these domains could give useful results. In nearly every case, it will prevent reporting or even worse, cause misdirected reports. Just adding static routes is probably not the best solution.Also, I cannot see, why rvenegas[at]uttecam.edu.mx is properly resolved from whois, but then gets discarded.
  5. Abuse contact for '91.235.108.0 - 91.235.111.255' is 'facturacion[at]adjenet.net'
  6. Abuse contact for '89.106.26.64 - 89.106.26.79' is 'lir[at]grid.com.tr'
  7. Abuse contact for '62.168.39.32 - 62.168.39.39' is 'nic[at]t-mobile.cz'
  8. Abuse contact for '95.107.0.0 - 95.107.15.255' is 'ripe[at]rt.ru'
  9. Abuse contact for '178.211.32.0 - 178.211.63.255' is 'abuse[at]as42926.net' SpamCop only wants to use the other address abuse[at]radore.com, but says it was bouncing.
  10. % Abuse contact for '185.8.164.0 - 185.8.164.255' is 'pavel.snajdr[at]vpsfree.cz'
  11. % Abuse contact for '87.236.232.0 - 87.236.233.255' is 'mayyad[at]junet.edu.jo'
  12. SpamCop fails to detect redirect from ARIN to APNIC % Whois data copyright terms http://www.apnic.net/db/dbcopyright.html % Information related to '153.121.32.0 - 153.121.95.255' inetnum: 153.121.32.0 - 153.121.95.255 netname: SAKURA descr: SAKURA Internet Inc. descr: 1-8-14, Minami Honmachi, Chuo-ku, Osaka 541-0054, Japan country: JP admin-c: JNIC1-AP tech-c: JNIC1-AP status: ALLOCATED PORTABLE remarks: Email address for spam or abuse complaints : abuse[at]sakura.ad.jp
  13. Abuse contact for '195.238.74.0 - 195.238.75.255' is 'm.fritz[at]totaaldomein.nl' but looking further at whois data: inetnum: 195.238.74.0 - 195.238.75.255 netname: TOTAALDOMEIN-CLOUD descr: Totaaldomein BV country: NL [...] person: Mark Fritz address: VOCweg 49 phone: +31320711333 e-mail: abuse[at]totaaldomein.nl nic-hdl: MF10189-RIPE mnt-by: totaaldomein changed: abuse[at]totaaldomein.nl 20110317 source: RIPE So abuse[at]totaaldomein.nl is probably the best reporting address.
  14. Abuse contact for '89.106.26.64 - 89.106.26.79' is 'lir[at]grid.com.tr'
  15. Abuse contact for '212.166.64.0 - 212.166.86.255' is 'sysops[at]ibercom.com'
×