lauritz-holtmann.de bewertung und analyse
Robots.txt Information
| Robot | Path | Permission |
| GoogleBot | / | ✔ |
| BingBot | / | ✔ |
| BaiduSpider | / | ✔ |
| YandexBot | / | ✔ |
User-agent: * # robotstxt.org - if ENV production variable is false robots will be disallowed. Disallow: | ||
Meta Tags
| Title | (Web-)Insecurity |
| Description | (Web-)Insecurity Blog Advisories Posts Tools (Web-)Insecurity Blog Recent Posts Insufficient Redirect URI validation: The risk of allowing to dynamically |
| Keywords | N/A |
Server Information
| WebSite | |
| Host IP | 78.46.181.2 |
| Location | Germany |
Verwandte Websites
| Site | Rank |
| lausitz-tv.de | 40,455,554 |
Mehr zu entdecken
lauritz-holtmann.de bewertung
|
Euro€3,306
Zuletzt aktualisiert: 2022-07-20
lauritz-holtmann.de hat Semrush globalen Rang von 8,770,055. lauritz-holtmann.de hat einen geschätzten Wert von € 3,306, basierend auf seinen geschätzten Werbeeinnahmen. lauritz-holtmann.de empfängt jeden Tag ungefähr 551 einzelne Besucher. Sein Webserver befindet sich in Germany mit der IP-Adresse 78.46.181.2. Laut SiteAdvisor ist lauritz-holtmann.de sicher zu besuchen. |
Verkehr & Wertschätzungen
| Kauf-/Verkaufswert | Euro€3,306 |
| Tägliche Werbeeinnahmen | Euro€90,364 |
| Monatlicher Anzeigenumsatz | Euro€30,305 |
| Jährliche Werbeeinnahmen | Euro€2,204 |
| Tägliche eindeutige Besucher | 551 |
| Hinweis: Alle Traffic- und Einnahmenwerte sind Schätzungen. | |
DNS Records
| Host | Type | TTL | Data |
| lauritz-holtmann.de. | A | 7199 | IP: 78.46.181.2 |
| lauritz-holtmann.de. | AAAA | 7199 | IPV6: 2a01:4f8:d0a:11ea::2 |
| lauritz-holtmann.de. | NS | 7200 | NS Record: ns.second-ns.com. |
| lauritz-holtmann.de. | NS | 7200 | NS Record: ns1.your-server.de. |
| lauritz-holtmann.de. | NS | 7200 | NS Record: ns3.second-ns.de. |
| lauritz-holtmann.de. | MX | 7200 | MX Record: 10 mail.lauritz-holtmann.de. |
| lauritz-holtmann.de. | TXT | 7200 | TXT Record: v=spf1 +a +mx ?all |
HtmlToTextCheckTime:2022-07-20
| (Web-)Insecurity Blog Advisories Posts Tools (Web-)Insecurity Blog Recent Posts Insufficient Redirect URI validation: The risk of allowing to dynamically add arbitrary query parameters and fragments to the redirect_uri In this post, I will discuss an OAuth 2.0 and OpenID Connect 1.0 implementation flaw pattern that was or is present even in well-known implementations from Github , Stackoverflow and Microsoft . read more XSS in Large Messenger and Payment App - a Shout Out to Parameter Guessing This is a post about a Cross-Site-Scripting (XSS) vulnerability that was identified within the web version of a large Chinese messenger and payment platform. The vulnerability could have been missed easily, as the vulnerable parameter was manually guessed. read more Real-life OIDC Security (VII): Responsible Disclosure This is the final post of a series on Single Sign-On and OpenID Connect 1.0 security. In this post, Responsible Disclosure processes with five vendors and maintainers of popular |
Ads.txtCheckTime:2022-05-07 05:31:07
# There are no authorised digital sellers, go ahead :-) |
HTTP Headers
HTTP/1.1 302 Found Date: Wed, 03 Nov 2021 19:23:07 GMT Server: Apache Location: https://security.lauritz-holtmann.de/ Content-Type: text/html; charset=iso-8859-1 HTTP/2 200 date: Wed, 03 Nov 2021 19:23:07 GMT server: Apache last-modified: Fri, 02 Apr 2021 17:22:44 GMT etag: "47fa-5bf00989a7564" accept-ranges: bytes content-length: 18426 cache-control: no-cache x-xss-protection: 1; mode=block x-frame-options: SAMEORIGIN x-content-type-options: nosniff referrer-policy: no-referrer strict-transport-security: max-age=2592000 content-security-policy: script-src 'self' x-permitted-cross-domain-policies: none content-type: text/html |