Connect to Wireless Teckin Click Webcam using a Web Browser?

I’ve just purchased a wireless Teckin Click webcam that connects to our home network but requires a smartphone app to view the output. We’ve set that up with no problem. However, with our other webcams we can view the images in a browser using the appropriate assigned local IP address, but apparently this is not possible with the Teckin for some unspecified reason, according to the vendor.

I’m using Chrome in Leap 15.3.

I’m not sure in which forum to ask the question that I could not find the answer to searching the web or forums here: How does one access the realtime image from a wireless Teckin webcam using a browser on a computer on the same local network.

Any assistance would be most appreciated.


Is this not possible for some unexpected reason according to the vendor? Does this mean that the vendor thinks it should be possible? And what is in the manual of the device?

I would return the device (and by one of the type you know that it works). When you bought it with the specification that you could connect to it with a web browser (maybe to a specific port different from 80 or 443) then the vendor can not hide himself behind the barrier that there is some unspecified reason for which he is not responsible.

Thanks for your questions. I bought the product thinking that it would be accessible from a browser, although neither the specs nor the manual indicate so.

My understanding is that the vendor is limiting access through the app and has stated in response to my inquiry “[FONT=arial]viewing videos on a computer is not supported”. So [/FONT]I just want to challenge that and find a way to access it as I can other webcams. If, for example, the vendor uses an unspecified port, how would I discover which one?

You could try nmap. See

man nmap

Something like

nmap <Ip-address of he device>

Example here scanning my router:

henk@boven:~> nmap
Starting Nmap 7.92 ( ) at 2022-09-12 20:47 CEST
Nmap scan report for (
Host is up (0.0093s latency).
Not shown: 995 closed tcp ports (conn-refused)
53/tcp   open  domain
80/tcp   open  http
443/tcp  open  https
5060/tcp open  sip
8089/tcp open  unknown

Nmap done: 1 IP address (1 host up) scanned in 0.39 seconds

This URI used to work on some Teckins, don’t know if it would work with your model, you may need to change the IP address it may well differ from model to model.


I do not think the URI is hard-coded, most probably set using DHCP.

I’ve tried your suggestion whilst connected to the app and the result is disappointing…

-> nmap -Pn
Starting Nmap 7.70 ( ) at 2022-09-12 15:58 ADT
Nmap scan report for TC100F37 (
Host is up (0.021s latency).
All 1000 scanned ports on TC100F37 ( are closed

Seems you bought the wrong sort of webcam. :frowning:

BTW, in the future please use CODE tags instead of QUOTE tags around copied/pasted computer text. It is the button with the #, one to the right of the QUOTE tag button.

Thanks Henk. I’ll remember to use the correct notation.

Thanks Paul. I’ve tried your suggestion and escaped the special characters in the URL but with no success.

What puzzles me is that with our two Edimax wifi webcams I can access both from an app and from a computer browser yet with the Teckin it only allows access through the app. What is stopping access from the browser?

It could be using a proprietary protocol. You would need to use wireshark to gain a better understanding.

Great suggestion! I’ll have a look at using that and see what I can find. Thanks.

You need to look at all the ports to see if can pick up at rtsp stream, maybe port 1050, normally 554, else it could be in the 9000+ range…

I am a bit curious about this subject. Partly because of lack of knowledge.

When another device (the haldheld computer aka “smart” phone) can show the images from the camera, is that really connecting to the camera, or does it connect to the vendors cloud where everything is send to from the camera (I maybe a bit paranoid here).

When it really connects to the camera and it uses Wifi and thus TCP/IP, there should be a TCP port open on the camera, independent of the used protocol over TCP.

Only when another technique then TCP is used port scanning would not reveal an open port for that.

Is my strain of thoughts correct, or am I missing something that is clear to anybody who is up-to-date with what those devices do and how?

I appreciate your suggestion. nmap showed no ports open, so should I find the rtsp stream port another way? Or am I asking the wrong question! Thanks.

As others indicated, sounds like some proprietary format… :frowning:

According to their website this cheap (chinese) plastic-trash-camera is sending all data to their (chinese) cloud. With your smartphone app you contact the cloud. I would throw away this plastic-trash. In my opinion this is a big security issue. For 21€ you don’t get an up to date product with proper security standards (up to date firmware, data protection standards, …). It is a big risk for your privacy and security as such cheap plastic boxes have no safety standards, are easily hackable and don’t get any updates firmware/securitywise. So your friendly hacker in the neighborhood can already see everything from your camera…

I appreciate this assessment of the device and I’ll take the appropriate measures to secure it as best I can, but like Henk, I would still like to learn how it operates given it needs a local IP network address, there are no ports open and yet the images are delivered through the app whether its using the same local wifi network or another external network?

Wireshark will give you a better idea about what is going on, but an easy test would be to disconnect your router from the internet and check if the camera and app are still able to communicate. Consumer cloud-based devices scare me.