Web Cookies Scanner
All-in-one free web application security tool. Web application vulnerability and privacy scanner with support for HTTP cookies, Flash, HTML5 localStorage, sessionStorage, CANVAS, Supercookies, Evercookies. Includes a free SSL/TLS, HTML and HTTP vulnerability scanner and URL malware scanner.
Title: "Anasayfa - Metin Kaleli"
Category: Marketing
Keywords: blog daha icin imaj neye veya womm medya metin nedir reklam sosyal dijital kisisel yapmali yatirim yonetimi marketing pazarlama yontemleri
Privacy Impact Score is a score reflecting overall cookie-related impact of the website relative to other websites, primarily taking into account the number of third-party domains it reports to and number of persistent cookies it sets. See Privacy Impact Score article for more details.
Third-party domains is the count of organisations allowed by the webmaster to trace your across the site. These cookies may be set for various purposes, like tracking ads displayed on the website, collection of statistics, targeted advertising etc. This website allows 0 other websites to track your activity.
Persistent cookies are the cookies that are preserved through browser shutdowns. This means, even if you close this page today and ever return there in future, the website will know you're a returning visitor. This may be used for "remember me" features, as well as persistent user tracking. These cookies, especially if set by third party organisations, are powerful tool for monitoring your activities across all the websites you visit. This website sets 4 persistent cookies with average life-time of 274 days and longest 730 days.
Session cookies are cleared when you close your browser and allow the website to identify user's state — such as logged-in users. They are mostly considered harmless because they cannot be used for long-term user tracking. This site sets 4 session cookies.
Last fetched: 2020-09-01T04:30:14.131695+00:00
HTTP status: 200 200
HTML5 LocalStorage is client-side storage introduced by HTML5 and supported by all major
browsers.
Data stored there is not sent automatically by the browser (unlike HTTP cookies) but is accessible
to
JavaScript code permanently, until deleted by the application or cleaned manually by the user.
These object can be thus compared to first-party persistent cookies from privacy point of
view.
LocalStorage cookieLocalStorage cookieAdvanced user tracking and fingerprinting techniques are used by websites to bypass privacy protection in web browsers and increase tracking persistence.
b'GIF8' … b'\x01\x00\x01\x00'
b'GIF8' … b'\x01\x00\x01\x00'
b'GIF8' … b'\x01\x00\x01\x00'
b'GIF8' … b'\x01\x00\x01\x00'
b'GIF8' … b'\x01\x00\x01\x00'
b'GIF8' … b'\x01\x00\x01\x00'
b'GIF8' … b'\x01\x00\x01\x00'
b'GIF8' … b'\x01\x00\x01\x00'
b'script.hotjar.com'
Server: nginx
Announces web server software and optionally version details.
Read more...Referrer-Policy: no-referrer-when-downgrade
The Referrer-Policy HTTP header governs which referrer information, sent in the Referer header, should be included with requests made.
Read more...
Referrer-Policy enabled
+1Access-Control-Allow-Origin: *
Controls origins (websites) that are allowed to load data from this web service over JavaScript-based APIs as part of Cross-Origin Resource Sharing (CORS) standard. By default, a web browser will refuse to load data over XmlHttpRequest from a website that is not in the same origin, which is a precaution against various types of data stealing attacks. The target server has to explicitly allow the origin domain using the Access-Control-Allow-Origin (ACAO) header, or it may allow all origins to access it using a wildcard *. The latter however creates a potential security issue if the website in question is transactional and processing sensitive data, so the wildcard should be only used on websites consciously offering public APIs.
The header sets permissive AJAX access by using wildcard origin *. It may be OK if the website is a publicly accessible REST API but otherwise it should be not present at all
Link: </wp-content/cache/minify/c7035.js>; rel=preload; as=script
Indicates location of sub-resources for the given page, in machine-readable format. It may come in a number of types, for example next page, previous page, index page, preloading resources etc.
Read more...
The HTML5 preload is a relatively new web performance feature that instructs the browser to start fetching specified resources before page rendering has been even finished as it will be most likely needed next.
0Link: </wp-content/cache/minify/9cc9c.js>; rel=preload; as=script
Indicates location of sub-resources for the given page, in machine-readable format. It may come in a number of types, for example next page, previous page, index page, preloading resources etc.
Read more...
The HTML5 preload is a relatively new web performance feature that instructs the browser to start fetching specified resources before page rendering has been even finished as it will be most likely needed next.
0Link: </wp-content/cache/minify/a82a7.js>; rel=preload; as=script
Indicates location of sub-resources for the given page, in machine-readable format. It may come in a number of types, for example next page, previous page, index page, preloading resources etc.
Read more...
The HTML5 preload is a relatively new web performance feature that instructs the browser to start fetching specified resources before page rendering has been even finished as it will be most likely needed next.
0X-Powered-By: PleskLin
A non-standard and purely informational, but still very widespread header, whose only purpose is to advertise the name and optionally version of the software used to run the web server.
Read more...Transport Layer Security (TLS) is enabled
+2X-Frame-Options header is missing
X-XSS-Protection header is missing
X-Content-Type-Options header is missing
The website uses the following advertisement publisher ids:
Most web pages load a number of sub-resources such as images, style sheets (CSS), JavaScript files, web fonts, audio or video files and other web pages in frames. Each of these sub-resources may be loaded from the same server (first-party resource) or servers belonging to other parties (third-party resources). In the latter case, the third-party will see a request coming from your browser with the information on the originating page and it can set its own cookies, both of which are frequently used for user tracking. Note that the cookies set by these sub-resources are already recorded in our cookie statistics for this page.
The page loads 10 third-party JavaScript files and 17 CSS but does not employ Sub-Resource Integrity to prevent breach if a third-party CDN is compromised
