Tag Info

You probably logged into your Facebook account over Tor. Facebook sees you exiting the Tor network in Portugal, or what it thinks is Portugal and so it flagged up your own login attempt as suspicious....

The way to check to see if a website is or is not a phishing attempt is the exact same way regardless of the browser. Click on the information link: Click on the arrow for the certificate on the ...

The question is basically saying that Facebook started with this onion address, then set out to generate the corresponding private key. This premise is incorrect, as pointed out by Steve’s answer: in ...

Facebook's onion domain has only 8 custom characters, not 15. Since they generated multiple names with those 8 characters, they chose the one that looked best. It is still out of reach of modern ...

Tor doesn't support v2 addresses and only v3 onion addresses can be surfed through the tor browser. Using a deprecated version of tor doesn't work because v2 domain resolution for Hidden Services has ...

You're trying to reach an obsoleted V2 hidden service - they're not working any more

What would be the issue? Logically, there are three possible answers: Facebook incorrectly recorded your logins. This seems unlikely; I am not aware of any reports of this. Facebook detected one of ...

It seems to be a NoScript bug. When I disable 'Sanitize cross-site suspicious requests' in NoScript Options\Advanced\XSS then Facebook comments come back. So, it is the first solution to disable '...