https://xalqbank.az/site/templates/style/img/s_ic.png

Category: Financial

Keywords: gnc str 200m baki baku bank dist kndi saat ucun visa xalq hliyev nizami petrol rayonu sabina filiali azpetrol magazasi


Last fetched: 2020-02-20T18:15:43.173951+00:00

HTTP status: 5 Sub-resource URL


Security-related HTTP headers

  • Server: Apache

    Announces web server software and optionally version details.

    Read more...

  • X-Frame-Options: SAMEORIGIN, SAMEORIGIN

    Instructs the browser if the current website can be embedded in HTML frame by another website. Since this allows the parent website to control the framed page, this creates a potential for data theft attacks ("clickjacking") and most sensitive websites won't allow them to be framed at all (deny) or just allow parts of them to be embedded in frames created by themselves only (samesite).

    Read more...

  • Strict-Transport-Security: max-age=31536000; includeSubDomains; preload

    HTTP Strict Transport Security (HSTS) is an opt-in security enhancement that is specified by a web application through the use of a special response header.

    Read more...

  • X-XSS-Protection: 1; mode=block

    Controls an Cross-Site Scripting (XSS) filters built into the majority of web browsers. The filter is usually turned on by default anyway, but requirement to set the header to 1 became part of canonical set of "secure" HTTP headers. Over time, vulnerabilities in the "sanitizing" mode filter were found, so 1; mode=block became the recommended value. Some companies decided that they don't really need a browser-side XSS filter to mess with their web services which are XSS-free anyway and they became consciously disabling the XSS filter by setting the header to 0.

    Read more...

  • X-Content-Type-Options: nosniff

    A non-standard but widely accepted header introduced originally by Microsoft to disable "content sniffing" or heuristic content type discovery in absence or mismatch of a proper HTTP Content-Type declaration, which led to a number of web attacks. In general, presence of the header with its only defined value of nosniff is considered as part of a properly secured HTTP response.

    Read more...

  • Referrer-Policy: same-origin

    The Referrer-Policy HTTP header governs which referrer information, sent in the Referer header, should be included with requests made.

    Read more...

  • Feature-Policy: accelerometer 'none'; camera 'none'; geolocation 'none'; gyroscope 'none'; magnetometer 'none'; microphone 'none'; payment 'none'; usb 'none'

    Allows web developers selectively enable and disable specific web technologies, especially those that enable two-way communication between the user and web application. For example, the header may inform the user mobile device that the website is not using camera or location tracking by design.

    Read more...

  • Public-Key-Pins: pin-sha256="brv29mkNjXj9ulIMcRDP980MZlakfmG18jl3HAD12BI="; max-age=5184000

    Announces a list of X.509 certificate hashes that are allowed to appear in the website's TLS certification path (HTTP Public Key Pinning or HPKP). This prevents malicious proxy servers from transparently replacing the public certificates with their own and wiretapping the TLS connection of the unsuspecting user. This header sets HPKP in enforcement mode.

    Read more...

Content Security Policy

  • upgrade-insecure-requests;
  • upgrade-insecure-requests;
  • upgrade-insecure-requests;

Want second opinion? Try Google CSP Evaluator.

Sub-resources

Parent pages

Parent pages loading this resource.