Discussion about this post

User's avatar
Ian Anderson's avatar

Good tip. Thank you.. One can only wonder at substack lack of interest. ?? Being a domain name owner with IP I would act like you suggest. Maybe substack is part of the "Cabal DS" ?

Expand full comment
VJ's avatar

Just recently I get a reminder from Amazon to be aware of phishing emails and similarly from my banks. It's a stark contrast in business approach.

Also in dealing with these emails, I've had good luck ignoring all emails in the headers and looking at the originating or source sending IP, doing a whois lookup and reporting the raw email to the abuse address provided. Sometimes though the hosting provider of the sending IP isn't the mail provider and when it's separate, the mail provider will almost always include extra custom headers with their own contacts or info. E.g. Mailgun uses other hosters but will have X-Mailgun... etc headers.

For phishing urls I do nslookup on the domain name to get the IP, then whois on the IP for the hoster and report it to them.

For me at least, the effort in doing both of these for serious scam and phishing emails have been fruitful. I don't bother on the regular spammy marketing emails though.

Expand full comment
20 more comments...

No posts