https://cmharyanacell.nic.in/images/refresh1.gif

Category: Uncategorized

Keywords: cell file form slip enter query track number status window gallery haryana redress grievance haryanacm government grievances redressalcm registration cmharyanagrievancescellhow


Last fetched: 2020-03-30T18:29:12.387395+00:00

HTTP status: 5 Sub-resource URL


TLS/SSL configuration report

TLS score
C

See full SSL/TLS security report for cmharyanacell.nic.in

Security-related HTTP headers

  • Server: Apache

    Announces web server software and optionally version details.

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

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

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

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

  • Public-Key-Pins: pin-sha256="d6qzRu9zOECb90Uez27xWltNsj0e1Md7GkYYkVoZWmM="; pin-sha256="E9CZ9INDbd+2eRQozYqqbQ2yXLVKB9+xcprMF+44U1g="; max-age=604800; report-uri="https://example.net/pkp-report"

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

  • Referrer-Policy: origin-when-cross-origin

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

    Read more...

  • Expect-CT: max-age=7776000, enforce

    The Expect-CT header allows sites to opt in to reporting and/or enforcement of Certificate Transparency requirements, which prevents the use of misissued certificates for that site from going unnoticed. When a site enables the Expect-CT header, they are requesting that the browser check that any certificate for that site appears in public CT logs.

    Read more...

Sub-resources

Parent pages

Parent pages loading this resource.
Fully automated RESTful API is now available. Subscribe for your free trial today!