Home > Paid Traffic Sources > Mobile

Help please! Domaing marked as phishing by Monetizer (10)

04-11-2017 02:02 PM #1 jrenzi (Member)
Help please! Domaing marked as phishing by Monetizer

Hi guys, hopefully someone can help me with this on a short time, since I have campaigns running.

Today I've received the following email from Monetizer:

Click image for larger version.  Name: phishing-alert.gif  Views: 110  Size: 97.8 KB  ID: 14907

This is my current setup. I'm running some campaigns in Zeropark, direct linking to afflow links. No landing page in the middle, and I'm using Amazon Route 53 as per STM recommendation.

I have no idea why this is happening, so if someone can advice how to get this solved and more important, how to prevent this from happening again it would be really great, since I have a couple of campaigns running. I guess I could just create another subdomaing, but it's not a long term solution.

Thanks!

04-11-2017 02:21 PM #2 manu_adefy (Veteran Member)

Domains are tough to really solve, they will all get flagged at some point. In your case, it could be because of where you buy traffic from, it could also be because of the offers you send traffic to.

Your only realistic solution is to replace it and then hope the next one lasts longer. You should try to blacklist bot placements so you don't get too much bot traffic in the future - I noticed a lot of such ZoneIDs/placements create issues with our domains.

It's certainly not the only factor and doesn't guarantee anything, just keep that in mind...

04-11-2017 04:49 PM #3 jrenzi (Member)

Thanks for the tip manu_adefy. They got back to me and recommended to set up a new domain as well. The bad news is that I was using this domain to host my landers for other campaigns, so I'll have to move them too.

According to what happened, I guess the best option is to register a new domain just for my landers and keep registering new domains just to use for afflow each time this happens.

Do you guys use a similar strategy?

And what would be the cheapest domain extension to register, having in mind this could be an ongoing issue with Monetizer?

04-11-2017 05:39 PM #4 chris_climbs (Member)

Domains getting flagged seems to generally just be part of pops. Of course, some verticals are much more likely to lead to a flag, and maybe fairly quick (AV for example). Buy cheap domains (you can find some for $0.99, just make sure you turn auto-renew off ), keep a few "on hand", set up and ready to go with your hosting, so you can quickly replace them when stuff like this happens.

I'm already starting to envision a tool using Amazon AWS SDK + registrar, that can roll out fresh domains, fully set up with a few clicks...

04-11-2017 05:56 PM #5 jrenzi (Member)

Quote Originally Posted by chris_climbs View Post
I'm already starting to envision a tool using Amazon AWS SDK + registrar, that can roll out fresh domains, fully set up with a few clicks...
I'm in if you deploy it

04-11-2017 06:36 PM #6 servandosilva (Member)

Just change it.
It's probably the offers being promoted from monetizer.

You might want to have several domains not only for your landers, but also per offer/geo in case disaster happens to reduce your risks.

04-11-2017 06:40 PM #7 jrenzi (Member)

Agree. Just registered a couple of .bid domains ($0.88 with whoisguard protection at Namecheap).

BTW, is it necessary to set up the domains with route 53 for afflow or an A record at namecheap will work the same?

04-12-2017 12:14 PM #8 manu_adefy (Veteran Member)

.club and .website also used to be cheap. The others have already answered your other questions.

04-20-2017 11:57 PM #9 jrenzi (Member)

Quote Originally Posted by jrenzi View Post
BTW, is it necessary to set up the domains with route 53 for afflow or an A record at namecheap will work the same?
Hey guys, just quoting myself for this question. For afflow, is it better to use route 53 or directly an A record at namecheap? Since I read in Amy's thread about afflow + ZP that using a CDN with afflow might me detrimental, although I'm not sure if she was referring to route 53 as well.

I'm using route 53 an getting (few) conversions, don't know if it might be related to this.

04-21-2017 05:23 PM #10 chris_climbs (Member)

Quote Originally Posted by jrenzi View Post
Hey guys, just quoting myself for this question. For afflow, is it better to use route 53 or directly an A record at namecheap? Since I read in Amy's thread about afflow + ZP that using a CDN with afflow might me detrimental, although I'm not sure if she was referring to route 53 as well.

I'm using route 53 an getting (few) conversions, don't know if it might be related to this.
Route 53 can only speed things up, when compared to using namecheap's DNS server, so yes keep using it. It's worth the $0.50 per hosted zone to shave those milliseconds, especially for high volume traffic like pops.

The reason CDN's are not 'compatible' with smartlinks, is because they cache STATIC pages for you, whereas a smartlink is extremely dynamic by nature.

Home > Paid Traffic Sources > Mobile