bengan

Members
  • Content count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About bengan

  • Rank
    Newbie
  1. $ whois -h whois.ripe.net -b 194.14.207.238 inetnum: 194.14.207.0 - 194.14.207.255 abuse-mailbox: abuse@inleed.se
  2. Shouldn't addresses like IPv4 Link-Local be handled in same way as RFC1918? Sort of: "move on to next received line".
  3. Hi, The first one has a "Recieved" with an IP-number 157.5.64.20 that don't have a route in the routing table (BGP). It's also an early registration prefix. The prefix doesn't have a registration in APNIC that is responsible for the whois-db of 157.0.0.0/8. The last "Received" is an RFC-1918-address. The only "real" IP-number in the Received headers is the outlook address 216.32.180.50. If this is a real email it's Microsoft that is responsible for this weirdness.
  4. Abuse contact for '205.201.128.0 - 205.201.143.255' is 'abuse@mailchimp.com'
  5. Hi, Since several years ago the ripe-whois has a flag, -b, that lists the abuse contact if there is one. Three out of 5 RIR whois servers support this. RIPE NCC, APNIC and AFRINIC while LACNIC and ARIN don't. man whois | grep \\-b -b Return brief IP address ranges with abuse contact. An example that lead me here was this. Spamcop don't find abuse contact for 217.28.197.226 But whois -h whois.ripe.net -b 217.28.197.226 gets you inetnum: 217.28.197.224 - 217.28.197.239 abuse-mailbox: registry@tripnet.se