Unlike other similar (and often suspicious) websites:
- you do not enter your phone number (or email). You just search yourself (or your close ones) by name, the same way you would Google or Facebook yourself or your friends.
- even if that shouldn't be the only trust signal, we (the folks at NextDNS) work around security and privacy every day for the benefits of the users. And while we are still a startup, we are used by many, including experts in the security industry.
Following the release of the 533 million phone numbers (acquired through the 2019 Facebook vulnerability), we wanted to bring awareness to the security & privacy implications of a public worldwide mobile phonebook.
You can check yourself, your family, friends and colleagues and inform them.
Disclaimer: we do not display (or even store) the phone numbers, we only show the last 2 digits so you can confirm it's yours.
Happy to answer related security and privacy questions.
It would be useful to have a search results when names aren't unique. I share my name with a famous author (not a sci-fi author, but somehow he went back in time to steal my name before I was born), but I'm not going to click through all of them to see which one is me.
On the plus side, I'm liking my good choice of having a non-unique name right about now.
Without being able to search by my unique identifier (i.e. my profile is facebook.com/IDENTIFER) because there are more than ten people with my name this tool is useless. Shame.
I've gotten somewhat hit or miss with finding my profile_id via the inspect element in FireFox, and then just appending it onto the end of the url.
However, I'm not sure if it's because my account was created at end of June 2019 that it didn't return anything, or if it didn't work. (it worked when I pulled up a couple of the big name user's id's and compared to the breach.
We made an online generator for (signed) Apple Configuration Profiles that let you use the new system Encrypted DNS feature of iOS 14/iPadOS 14/tvOS 14 and macOS Big Sur, without the need for an app.
The Configuration ID field is entirely optional and if left blank, you will be using our no-logs non-blocking DNS resolver (the one included in Firefox and soon Google Chrome). For reference, here is a map of our anycast network: https://i.imgur.com/doL6nkr.png
On my desktop systems I can configure it in the network options and never think about it again. On Android I always close it if I don't think about it when closing all apps, then I forget to restart it.
Google Chrome (and some Chromium forks) will also be supporting custom DNS-over-HTTPS providers very soon (it's already being rolled out to some users).
Looks like a case of bad anycast routing, as we have a PoP in Toronto! It happens and is usually easily fixable, can you talk to us via the chat on our website (or at support@nextdns.io)?
I figured I'd activate it again and test it first... and of course it's way better now! Consistently getting around 40ms now so I'll keep it enabled and try again :)
I literally (not figuratively) setup NextDNS yesterday and so far it's been great. The documentation is awesome, and love the features available. The only mild feedback I have is that the "Setup Guide" doesn't provide enough context about what's going on, and the implications of setting up on my PC vs mobile device vs router. It says:
"Follow the instructions below to set up NextDNS on your device, browser or router."
A couple more sentences there would be super helpful..
The Windows setup doesn't like Windows 10 on ARM, it couldn't install the TAL driver. Very edge case I guess, I'm going to install on x86 when I get home :)
This is a v1 of our analyzer, but it's already doing a lot of things to mimic a real user (like using a real browser, moving the mouse, scrolling, etc.).
We try to shine a light on the implications of this on the website itself (you may need to scroll down a bit).
Short term, just being aware of it should make things better, as there is going to be a massive surge in phishing and other types of attacks.