Robot | Path | Permission |
GoogleBot | / | ✔ |
BingBot | / | ✔ |
BaiduSpider | / | ✔ |
YandexBot | / | ✔ |
Title | Latest Posts – Steffen |
Description | The personal blog of Steffen |
Keywords | N/A |
WebSite | st-g.de |
Host IP | 104.21.84.138 |
Location | United States |
Site | Rank |
altenheim-stgeorg.de | 0 |
Euro€2,204
Zuletzt aktualisiert: 2022-07-01 15:46:04
st-g.de hat Semrush globalen Rang von 12,217,301. st-g.de hat einen geschätzten Wert von € 2,204, basierend auf seinen geschätzten Werbeeinnahmen. st-g.de empfängt jeden Tag ungefähr 551 einzelne Besucher. Sein Webserver befindet sich in United States mit der IP-Adresse 104.21.84.138. Laut SiteAdvisor ist st-g.de sicher zu besuchen. |
Kauf-/Verkaufswert | Euro€2,204 |
Tägliche Werbeeinnahmen | Euro€65,018 |
Monatlicher Anzeigenumsatz | Euro€22,040 |
Jährliche Werbeeinnahmen | Euro€1,653 |
Tägliche eindeutige Besucher | 551 |
Hinweis: Alle Traffic- und Einnahmenwerte sind Schätzungen. |
Host | Type | TTL | Data |
st-g.de. | A | 299 | IP: 104.21.84.138 |
st-g.de. | A | 299 | IP: 172.67.193.203 |
st-g.de. | AAAA | 299 | IPV6: 2606:4700:3037::6815:548a |
st-g.de. | AAAA | 299 | IPV6: 2606:4700:3037::ac43:c1cb |
st-g.de. | NS | 86400 | NS Record: mona.ns.cloudflare.com. |
st-g.de. | NS | 86400 | NS Record: mark.ns.cloudflare.com. |
st-g.de. | MX | 300 | MX Record: 100 www6.stg-design.net. |
st-g.de. | TXT | 300 | TXT Record: v=spf1 mx a:www4.stg-design.net a:www5.stg-design.net a:www5.stg-design.net -all |
MENU Home About Speaking Tags Imprint Feed Steffen Gebert My Blog/Website Interview in the EMnify Blog 11 Dec 2020 in Less than 1 minute read As I recently gave two talks at the AWS Community Day - Bay Area as well as DENOG12, where I explained how we implemented two of our recent projects at EMnify, I was interviewed in the EMnify blog. If you are interested in my other talks, see the Speaking page. Happy watching! … read more... Be careful with AWS Private API Gateway Endpoints 24 Jul 2019 in 3.345 minutes read As many shops out there, we (at EMnify) are using AWS Lambda for an increasing number of applications to make our life easier. The prerequisite to trigger Lambda functions via REST API calls is to deploy an API Gateway into an AWS account. Historically, API Gateway offered deployment types: regional: what I would consider expected - the API is reachable directly via a DNS host name including the AWS region where it is deployed edge-optimized: what feels weird and almost |
HTTP/1.1 301 Moved Permanently Date: Wed, 27 Oct 2021 13:33:56 GMT Connection: keep-alive Cache-Control: max-age=3600 Expires: Wed, 27 Oct 2021 14:33:56 GMT Location: https://st-g.de/ Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=4KPlmH7xZaub%2Bz2YhU5%2BqVTpHQvgGM3YJe6TKD0G6CT9alTw2FTZAtqRtRA%2Fn9gTx8OO4sjAgnQHNvTFGBB4O%2BuirooDdvEeTK1%2FStPir1YSIk7QFgevdLT6"}],"group":"cf-nel","max_age":604800} NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800} Server: cloudflare CF-RAY: 6a4c4c8d1b23638a-ORD alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400, h3-28=":443"; ma=86400, h3-27=":443"; ma=86400 HTTP/2 200 date: Wed, 27 Oct 2021 13:33:57 GMT content-type: text/html; charset=utf-8 last-modified: Sun, 10 Oct 2021 18:47:28 GMT vary: Accept-Encoding access-control-allow-origin: * expires: Wed, 27 Oct 2021 13:43:57 GMT cache-control: max-age=600 x-proxy-cache: MISS x-github-request-id: 2620:3B15:35B757:64E7CB:61795545 cf-cache-status: DYNAMIC expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct" report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=lVOn3ZBfpPl8f0rYIIDAuMO477cLOiY4lFWWJwkihl2D4a7OP3JXtuIoZ%2ByLAio6bnsPfqI0eKNdtI0JK3j3IA6OIpTgIUaLWFuV3ETWEgMwtJ2OpQHUT82%2B"}],"group":"cf-nel","max_age":604800} nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800} server: cloudflare cf-ray: 6a4c4c8ef9c761b6-ORD alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400, h3-28=":443"; ma=86400, h3-27=":443"; ma=86400 |