I built DevicePrint after running into problems with duplicate accounts and unreliable cookies in my own projects.
DevicePrint is a lightweight device fingerprinting tool designed for developers. It helps identify devices across sessions without relying on cookies.
Use cases include fraud detection, preventing duplicate signups, and security-sensitive workflows.
I'd really appreciate feedback — especially around privacy concerns or edge cases you’ve run into.
Link: https://deviceprint.io
Jokes aside, it’s cool but it’s not useful if it’s the first time I visit and I see I have 10+ past visits from all around the world… obviously this is not reliable and I wouldn’t use it for anything, much less anything serious.
Anecdotally speaking, this is the case for most new Show HNs now :^)
https://amiunique.org/fingerprint
What’s even more impressive is I’ve made all of those visits from all of those cities in the last few minutes.
You may have a bug.
I think the 'unique' part of fingerprinting here isn't working unfortunately.
It's a red flag if you hide behind a contact form with no reachability beyond that whatsoever.
And as other said: 99.5% accuracy means you should have millions of working fingerprints, since mine and others are faulty as hell.
You have to be able to understand your core technology/IP/logic - I feel that must have been significantly overlooked here.
This helps you see how your browser tries to block or deflect fingerprint and trackers. I miss their "You are one of x,000 users" from the old site but it still gives a nice summary of bits of info your browser leaks and how fingerprinting basically works.
Visited for the first time and it said I already visited 800+ times with a 99.5% accurancy - not very promising. From the code this also looks like very simple client-side fingerprinting + IP information?
It's a 99.5% declared confidence and says it used 30+ signals.
Assuming you've a list of VPN IP addresses, and travel times between countries, I reckon you should be able to rule out some false positives.
Would be interested to know what the "signals" were that produced the match.
I'm on domestic broadband in the UK (IPv4), according to dnschecker they're on a mainstream mobile provider in Germany. Could be a private tunnel, but those would be rare. Which raises the question of how the confidence rating is made.
I like the general page presentation, a good landing page except that you'll tend to put off everyone who gets a bad result for the example. That might be turned around with something showing "if this isn't you, well done on your browser security" and maybe some compelling stats on confirmed matches from testing?
But as others mentioned, it is far from being accurate. I got the same as others, multiple visits from multiple countries.
I'd love to use a reliable system like this to detect returning fake, banned, and bot users on my services.
Works great! Thank you for fighting for users anonymity
edit: not only that, under past visits I can now see the ip address of other visitors, together with their rough location and browser setup. You may want to remove the "gdpr compliant" from the website :)
It shows I've visited all around the world, lots of times.
Nope. Just once, and from one location.