Naked domain will not forward to WWW and site flagged as phishing?

Website, Application, Performance DNS & Network
1

I am not sure if these issues are related at all, but they are both happening on the same domain. I would very much appreciate some guidance.

The raw domain has no origin IP or A record to go to. The www is cnamed to the site it needs to be attached to. My forwarding rule is set up exactly as “domain.com/* > https://www.domain.com”

The entirety of the DNS comprises of a cname for www, a cname for *, and a Google verification txt record.

On the other end, the www site does connect but now has been flagged as phishing by at least Avast and Microsoft defender. I am very confident that this is not site content related, as this site has existed for a long time and only recently underwent a domain change. Is it possible that something is wrong with the DNS?

Thank you all-

2

If you’re using a wildcard for the non-www CNAME, then it’s not proxied and Page Rules will not apply.

I’d advise against using a wildcard, as it makes for an unlimited number of hosts to attract unwanted traffic to your server.

3

Thanks. So my first step should be to change the forwarding url purely to domain.com/ > https://www.domain.com/?

Should there even be a / ?

Thank you very much.

4

Nevermind, I reread that. I have removed the cname for *

1 Like
5

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.