Jump to content

Abuse address for E*Trade


turetzsr

Recommended Posts

Hi, all,

...Would someone please post this abuse contact information for us.etrade.com to news.spamcop.routing? I don't have access to it. Thanks!

postmaster[at]etrade.com (for etrade.com)

abuse[at]etrade.com (for etrade.com)

The SpamCop parser finds "bhyder[at]etrade.com" but that address refuses reports so it gets bit-bucketed to bhyder#etrade.com[at]devnull.spamcop.net.
Link to comment
Share on other sites

Wow, this is a rough one ... re-ran your spam, did the refresh a couple of times to tickle the parser into handling the URL ... then did a Refresh on the first data results (that matched your bhyder thing) ... However, whil doing that the DNS results changed ... this is the resulting parser output when I last parsed it ... vastly different results ...

Removing old cache entries.

Tracking details

Display data:

"whois 12.153.224.132[at]whois.arin.net" (Getting contact from whois.arin.net )

checking NET-12-153-224-0-1

Display data:

"whois NET-12-153-224-0-1[at]whois.arin.net" (Getting contact from whois.arin.net )

12.153.224.0 - 12.153.224.255:bhyder[at]etrade.com

whois.arin.net contact: bhyder[at]etrade.com

checking NET-12-0-0-0-1

Display data:

"whois NET-12-0-0-0-1[at]whois.arin.net" (Getting contact from whois.arin.net )

Found AbuseEmail in whois abuse[at]att.net

12.0.0.0 - 12.255.255.255:abuse[at]att.net

Routing details for 12.153.224.132

Using abuse net on abuse[at]att.net

abuse net att.net = abuse[at]att.net

Using best contacts abuse[at]att.net

Resolving link obfuscation

https://hk.etrade.com/hk/index.html

https://us.etrade.com/e/t/home

Tracking link: https://us.etrade.com/e/t/home

[report history]

Resolves to 12.153.224.21

Routing details for 12.153.224.21

[refresh/show] Cached whois for 12.153.224.21 : bhyder[at]etrade.com abuse[at]att.net

Using abuse net on abuse[at]att.net

abuse net att.net = abuse[at]att.net

Using best contacts abuse[at]att.net

Tracking link: https://hk.etrade.com/hk/index.html

[report history]

Resolves to 12.153.224.132

Routing details for 12.153.224.132

[refresh/show] Cached whois for 12.153.224.132 : bhyder[at]etrade.com abuse[at]att.net

Using abuse net on abuse[at]att.net

abuse net att.net = abuse[at]att.net

Using best contacts abuse[at]att.net

and interestingly enough, yet another attempt at a re-parse gets me this;

http://www.spamcop.net/sc?id=z772911264zd6...793c780e11e27cz

Resolving link obfuscation

https://us.etrade.com/e/t/home

https://hk.etrade.com/hk/index.html

Tracking link: https://hk.etrade.com/hk/index.html

[report history]

Resolves to 12.153.224.132

Routing details for 12.153.224.132

[refresh/show] Cached whois for 12.153.224.132 : bhyder[at]etrade.com

Using last resort contacts bhyder[at]etrade.com

bhyder[at]etrade.com bounces (119 sent : 60 bounces)

Using bhyder#etrade.com[at]devnull.spamcop.net for statistical tracking.

Tracking link: https://us.etrade.com/e/t/home

[report history]

Resolves to 198.93.34.50

Routing details for 198.93.34.50

[refresh/show] Cached whois for 198.93.34.50 : bhyder[at]etrade.com

Using last resort contacts bhyder[at]etrade.com

bhyder[at]etrade.com bounces (119 sent : 60 bounces)

Using bhyder#etrade.com[at]devnull.spamcop.net for statistical tracking.

Routing details for 198.93.34.50

Third party interested in reports abuse[at]savvis.net

There is some weird stuff going on with this .... unfortuntely, have to hit the road for a bit ... out the door for now ...

Link to comment
Share on other sites

<snip>

Wow, this is a rough one ... re-ran your spam, did the refresh a couple of times to tickle the parser into handling the URL ... then did a Refresh on the first data results (that matched your bhyder thing)

<snip>

29033[/snapback]

...That first result was a bit odd but the second looks quite a bit like what I got, including the "Using bhyder#etrade.com[at]devnull.spamcop.net for statistical tracking."
unfortuntely, have to hit the road for a bit ... out the door for now ...

29033[/snapback]

...No problem; no hurry (I'll be out the door for the day pretty soon, as well); appreciate your help, as always! :) <g>
Link to comment
Share on other sites

I think part of the answer is different code running on different servers in the farm. Please try to post the Parser Version (one is currently "SpamCop v 1.456") when you get different results from the Parser.

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...