Imzy
  • Discover communities
  • Log In
  • Sign up
  • Home
  • Discover communities
  • Log In
  • Sign up
  • About
  • Learn More
  • Contact
  • Community Policy
  • FAQ
  • Sitemap
  • Terms
  • Privacy Policy
  • Available on the App Store
  • Available on Google Play
Copyright © 2017 Saurus, Inc. All rights reserved.
InfoSec

InfoSec

Information Security, securing the digital world. Blogs, talks, videos, discussions, and tips on digital security.

2591 members
Posted byoherralain/infosec-Nov 03, 2016 at 12:36 PM

URI:teller & a Call for the Curious - HowNetWorks

URI:teller & a Call for the Curious - HowNetWorks

Last friday we quietly rolled out a new service called URI:teller. When I say "quietly" I don't count our friends whom we immediately spammed with links to uriteller.io. Sorry about that, friends! #notsorry We built URI:teller to scratch a specific itch: Verifying that end-to-end encrypted messaging apps don't leak links we exchange via chats.

medium.com
Comments3
  • phyzomeNov 15, 2016 at 9:20 PM

    One could also use requestb.in, no?

    • oherralaNov 16, 2016 at 2:50 AM

      Yes! uriteller and requestb.in basically do the same thing: show user who visited a given URL.

      However, the representation is different. requestb.in focuses on the HTTP request content while uriteller focuses on who made the request.

      Pick the one which is better tool for particular need :)

      • phyzomeNov 16, 2016 at 7:44 AM

        Ah, got it!

InfoSec

InfoSec

Information Security, securing the digital world. Blogs, talks, videos, discussions, and tips on digital security.

2591 members
  • About
  • Sitemap
  • Terms and Conditions
  • Privacy Policy
  • Copyright © 2017 Saurus, Inc. All rights reserved.