Anti-Phishing Filters and the Legitimate Sender
Recently I have had several discussions about Anti-phishing measures being deployed by ISPs and the type of things that Legitimate Marketers need to be aware of. It appears that several ISPs are deploying a anti-spam and anti-phishing service that evaluate the URLs embedded in your HTML code against those links in the readable text.
While this is not really anything new, some of these behaviours have been modified recently at a number of ISPs and are causing changes in the way bounces are being generated.
** Note: For all examples round brackets have replaced > or
Normal HTML links look like this :
(a href=”http://www.example.com/”)http://www.example.com (/a)
The view of a managed deployment tools ends with your links looking like this:
ISPs see links like this all the time, except they are usually from some spammer sending you a notice about your Bank account or your PayPal being compromised and asking you to login to verify the status of your account. These services are comparing the two URLs being used and finding that example 2 above looks a lot like the phishing
message I just described… Consisting of two different URLs, potentially redirecting at two different websites that do not match.
What do I ensure I’m not getting caught in this manor?
When building links in your message use words, or other visual queues, as your Human readable text and not a URL. This will hyperlink the word, button, image etc… instead of another miss-matched domain from your html.
(a href=”http://links.for.stats.com/S0meKind0fHashC0d3″)My Best Link Idea(/a)
As an added benefit, I personally believe, it will improve the aesthetics of your email messaging.