https://vgate.sago.gov.sa/css/bootstrap-rtl?v=ImhGvjfwSxCAouKW6HdFKg_yZJUImbM_gc_712HumD81


Last fetched: 2019-06-12T09:16:17.585300+00:00

HTTP status: 5 Sub-resource URL


Security-related HTTP headers

  • 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...

  • X-Permitted-Cross-Domain-Policies: none

    Header used by Adobe Flash engine to control cross-site access for Flash applications. Most websites not using Flash would prefer to set it with the value of none as an additional precaution against using them in advanced Flash-based XSS vectors. Flash-serving websites can use them to declare the scope of detailed Flash cross-site policies per Adobe specification.

    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...

  • Referrer-Policy: strict-origin

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

    Read more...

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

    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-Frame-Options: 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...

  • Server: Denied

    Announces web server software and optionally version details.

    Read more...

Content Security Policy

  • default-src 'none'; connect-src *; font-src *; frame-src *; img-src * data:; media-src *; base-uri 'self';form-action 'self';frame-ancestors 'self';object-src 'none'; script-src * 'unsafe-inline' 'unsafe-eval'; style-src * 'unsafe-inline';

Pages loading this URL

Fully automated RESTful API is now available. Subscribe for your free trial today!