Yesterday, a customer tried out his new web site using an iPhone. We were trying to discover why he could not access it but that is not the story.
I directed him to one of my web pages which reported the IP and User-Agent, with odd results. The User-Agent he reported back from there was most unlikely...
Phone (Mobile Mode)
So I looked at the log for that access and got three results for it, all at the same time to the nearest second.
apple-touch-icon-precomposed.png (not available so returned 404)
UA: User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/601.2.4 (KHTML, like Gecko) Version/9.0.1 Safari/601.2.4 facebookexternalhit/1.1 Facebot Twitterbot/1.0
browserinfo.php (the required page)
UA: User-Agent:Mozilla/5.0 (iPhone; CPU iPhone OS 15_3 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.3 Mobile/15E148 DuckDuckGo/7 Safari/605.1.15
index.php (no idea why; not requested by customer)
UA: User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/601.2.4 (KHTML, like Gecko) Version/9.0.1 Safari/601.2.4 facebookexternalhit/1.1 Facebot Twitterbot/1.0
These were the only hits, all to the same second. It seems as though the actual page hit (browserinfo.php) was accompanied by the icon request and this was followed by an automatic hit on the home page, which the customer was unaware of.
I can accept the middle UA as being Safari including DDG as its default SE and advertising that fact. If it were MY web browser I would be worried by the first and third UAs. The customer has no facebook or twitter account, access or activity so it's not an expected action. It appears from this that Safari is reporting back to twitter and facebook at least some information about web page visits. This does not happen from a desktop Mac, which has a UA of...
User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/11.1.2 Safari/605.1.15
Since this is a development site with a private domain name, this is not acceptable. yes, I know a domain cannot be completely private but to sneek information in this way is unexpected.