Robot | Path | Permission |
GoogleBot | / | ✔ |
BingBot | / | ✔ |
BaiduSpider | / | ✔ |
YandexBot | / | ✔ |
Title | www.stefanproell.at |
Description | Idea and On this page I collect knowledge and information about databases, software development, containers, Linux and other areas of |
Keywords | N/A |
WebSite | stefanproell.at |
Host IP | 104.198.14.52 |
Location | United States |
Site | Rank |
stefan-naszay.de | 0 |
stefanfrey.ch | 40,341,303 |
stefaneberhardag.ch | 0 |
stefanwallmann.de | 0 |
stefanzwicky.ch | 0 |
Euro€3,306
Zuletzt aktualisiert: 2022-07-03 13:56:24
stefanproell.at hat Semrush globalen Rang von 9,053,639. stefanproell.at hat einen geschätzten Wert von € 3,306, basierend auf seinen geschätzten Werbeeinnahmen. stefanproell.at empfängt jeden Tag ungefähr 551 einzelne Besucher. Sein Webserver befindet sich in United States mit der IP-Adresse 104.198.14.52. Laut SiteAdvisor ist stefanproell.at sicher zu besuchen. |
Kauf-/Verkaufswert | Euro€3,306 |
Tägliche Werbeeinnahmen | Euro€87,609 |
Monatlicher Anzeigenumsatz | Euro€29,203 |
Jährliche Werbeeinnahmen | Euro€2,204 |
Tägliche eindeutige Besucher | 551 |
Hinweis: Alle Traffic- und Einnahmenwerte sind Schätzungen. |
Host | Type | TTL | Data |
stefanproell.at. | A | 3599 | IP: 104.198.14.52 |
stefanproell.at. | NS | 3600 | NS Record: ns13.domaincontrol.com. |
stefanproell.at. | NS | 3600 | NS Record: ns14.domaincontrol.com. |
stefanproell.at. | MX | 3600 | MX Record: 5 alt1.aspmx.l.google.com. |
stefanproell.at. | MX | 3600 | MX Record: 1 aspmx.l.google.com. |
stefanproell.at. | MX | 3600 | MX Record: 10 alt4.aspmx.l.google.com. |
stefanproell.at. | MX | 3600 | MX Record: 10 alt3.aspmx.l.google.com. |
stefanproell.at. | MX | 3600 | MX Record: 5 alt2.aspmx.l.google.com. |
stefanproell.at. | TXT | 3600 | TXT Record: google-site-verification=ZEyBWgsN_hr2iiEGt3T2jJbZgOzf0MWXaC6J2wvqmoI |
www.stefanproell.at A personal blog about technology, data and ideas. Menu Home About me Das MySQL – Buch Impressum Using Balena and Nginx Proxy Manager to secure a Webcam November 18, 2021 (Last Modified: November 20, 2021) IoT , Balena , Security I have an old Web cam which does not support HTTPS and where the dynamic IP resolver service of the manufacturer stopped working some years ago. The camera uses an UMTS hotspot to connect to the Internet and gets a new IP address every now and then. Graciously the camera would send out an email with it’s new IP address after every reboot, however I then would have to update this address manually in the surveilance app each time. Since the camera is working fine, I wanted to put it behind a HTTPS proxy and use DuckDNS to have a domain pointing to it. An old Raspberry Pi 3 serves as the hardware basis for this project. Idea and Requirements I want to have a secure conection using HTTPS to the Web interface of the webcam. Since the camera has |
HTTP/1.1 301 Moved Permanently cache-control: public, max-age=0, must-revalidate content-length: 39 content-type: text/plain date: Thu, 28 Oct 2021 04:53:15 GMT x-nf-request-id: 01FK309PTFNGZWCC3BYYKQB33M location: https://stefanproell.at/ server: Netlify age: 12984 HTTP/2 301 cache-control: public, max-age=0, must-revalidate content-length: 43 content-type: text/plain date: Wed, 27 Oct 2021 12:20:06 GMT strict-transport-security: max-age=31536000 server: Netlify location: https://www.stefanproell.at/ x-nf-request-id: 01FK309Q9SWJB1XPXB3CQPVP8D age: 72574 HTTP/2 200 cache-control: public, max-age=0, must-revalidate content-type: text/html; charset=UTF-8 date: Wed, 27 Oct 2021 15:57:15 GMT etag: "afd427cdae77a2c6f80c33f016faada9-ssl" strict-transport-security: max-age=31536000 content-length: 134026 age: 59545 server: Netlify x-nf-request-id: 01FK309QPCQBGJP5F3RGYSGYFD |