| 4:59 pm on Jul 16, 2013 (gmt 0)|
It sounds like wildcard DNS [en.wikipedia.org] is configured against your domain name so anything.example.com is serving up your site - that would be the first thing to check / fix...
| 2:52 pm on Jul 17, 2013 (gmt 0)|
That's not it. I'm already set to not accept URL's with wildcards before the domain.
I've searched using every phrase I can think of to find something on putting letters or words before the "www", but can't find anything. I don't know what the person(s) using these URL's are trying to accomplish, but it's annoying my advertiser.
| 9:04 pm on Jul 17, 2013 (gmt 0)|
|I can't find anything in my stats on these, so I don't know how they're originating or from whom. |
Never mind stats: look at raw logs.
Either the visitors are coming from your site or they're not. If they're not, it is not your problem and the advertiser can do whatever they normally do with a forged referer. If they ARE coming from your site, you can then research more deeply-- but don't bother about this part until you're sure they started out with you.
| 10:36 pm on Jul 17, 2013 (gmt 0)|
the only way i can see to verify anything is for your advertiser to provide the date/time and IP address of the referral and then for you to verify in your server access log that you had a preceding request for the referring page at that date and approximate time from that IP address.
otherwise, as lucy24 suggested, it's probably a faked request with a forged Referer: header.
| 3:55 am on Jul 18, 2013 (gmt 0)|
Thank you so much. I'll ask my advertiser to provide the information. I hope it's something on his end, as my hosting company has said they don't deal with such issues.