![]() ![]() So timestamp+u're 3rd octet+the id of the specific anycast local CF server they picked for u and u're query+queryname=not that hard to identify u in those 25hrs unless u're isp actually is class c, meanwhile if they mask the 3rd octet, the only thing they'd know in my case is just the isp I'm using since my isp is class b, The chance of 2 users with the same v4 3rd octet visiting a website within a day is unlikelyīut that's irrelevant cause they store a timestamp of u're query as part of their 'debug' that too is kept for a day, and I don't think they vowed that they will not tie u're ip and the debugs together With my isp it's the last 2 octets that are tied to me(the 1st 2 octets are used extremely broadly/shared with many other users of my isp, and switch between just the same 4 sets of numbers, in the yrs I've been with them), changing just the last octet offers 0 privacy(especially if the ip is asked for by the gov/u're isp) and they are basically still temp logging u for a day u just like google Cloudflare will delete the truncated IP address within 25 hours. Except for randomly sampled network packets captured from at most 0.05% of all traffic sent to Cloudflare’s network infrastructure, Cloudflare will not retain the source IP from DNS queries to the Public Resolver in non-volatile storageĬloudflare will anonymize source IP addresses via IP truncation methods ( last octet for IPv4).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |