Home > HTTP Server Header Checker > Test results
-
Server IP : 45.60.14.114
HTTP/1.1 200 OK
Content-Length: 6982
Content-Type: text/html
Date: Sat, 27 Apr 2024 01:37:32 GMT
Server: Windows-Azure-Web/1.0 Microsoft-HTTPAPI/2.0
Accept-Ranges: bytes
Access-Control-Allow-Origin: *
Access-Control-Expose-Headers: Accept-Ranges,Content-Length,Content-MD5,Content-Type,Date,ETag,Last-Modified,Server,x-ms-request-id,x-ms-version
Access-Control-Expose-Headers: Request-Context
Cache-Control: public, max-age=86400, s-maxage=86400
Content-MD5: JWg+rGVZUf9vqWQ05mK6Gg==
ETag: "0x8DC6417ED28AB7E"
Expires: 86400
Last-Modified: Wed, 24 Apr 2024 04:35:10 GMT
Pragma: cache
x-ms-request-id: 71463de4-a01e-008d-1b43-9886c8000000
x-ms-version: 2018-03-28
X-Powered-By: ARR/3.0
X-Powered-By: ASP.NET
Request-Context: appId=cid-v1:8a08ff00-801a-4f31-9a6b-6293d69cea3a
Content-Security-Policy: frame-ancestors 'self'
Set-Cookie: nlbi_1392985=SF07ER+DRi/91R0S4WYXUwAAAAAWnvmRNMzYsZ7KyPLrfOm6; path=/; Domain=.cemexgo.com; Secure; SameSite=None
Set-Cookie: incap_ses_108_1392985=Yfl9LMQurXC3YFTVfbF/AdxWLGYAAAAAvNvvpnMNPeBkSsxIbEmF3A==; path=/; Domain=.cemexgo.com; Secure; SameSite=None
X-CDN: Imperva
Content-Security-Policy-Report-Only: default-src 'self' 'unsafe-eval' 'unsafe-hashes' 'unsafe-inline' data: blob: www.google.com.mx *.googleapis.com customer.experience.cemex.com *.hotjar.com *.bluekai.com *.doubleclick.net cdn.personyze.com ec.walkme.com tags.bkrtx.com cdn.agentbot.net jqtmdiy716.execute-api.us-east-1.amazonaws.com www.google.com.do dc.services.visualstudio.com *.facebook.com *.facebook.net www.google.com.eg *.dynatrace.com *.qualtrics.com statestore.rollout.io www.google.com.co www.googletagmanager.com www.google.co.uk www.google-analytics.com www.google.com api.cobrowse.io *.linkedin.com sentry.aivo.co www.google.com.ph metrics.hotjar.io www.google.pl *.gstatic.com img04.en25.com adapter.aivo.co region1.analytics.google.com cemex.count.ly analytics.google.com conversation-user.aivo.co vc.hotjar.io csxd.contentsquare.net www.google.fr content.hotjar.io cdn.walkme.com analytic.rollout.io c.contentsquare.net cdn.jsdelivr.net counter.personyze.com wss://api.cobrowse.io *.eloqua.com conf.rollout.io t.contentsquare.net js.cobrowse.io counter2.personyze.com ec-playback.walkme.com agentcore.s3.amazonaws.com *.licdn.com playerserver.walkme.com papi.walkme.com s3.amazonaws.com service.maxymiser.net count.personyze.com push.rollout.io ; form-action 'none' ; frame-ancestors 'self' ; report-uri /csp_report
X-Iinfo: 10-26653331-26653343 NNNN CT(35 43 0) RT(1714181852026 50) q(0 0 1 1) r(1 1) U6
HTTP Header Checker
When you have a website, you’re responsible for making sure it is working properly. If your site is laggy or simply not loading, you could miss out on a ton of potential customers. If the URL and site aren’t working properly, you’ll need to test it to find out why.
But how do you get this information?
One of the best ways to view and check the status of a website or server is to check the HTTP headers.
How to Check HTTP Headers
When running a campaign or working on your SEO, it is imperative that your links are not only accurate, but functional. Having a dead link or a server/request problem can be a huge roadblock to successful progress.
Solution? Make our HTTP server header checker part of your toolkit.
Our free header checker tool makes it incredibly quick and easy to check the server response for any URL. Simply paste your accurate URL into the blank field and click “Check Now”. Our HTTP status checker will instantly provide you with information including the status code, server, content type, requested page, keep-alive, caching headers, and any other headers being used. It’s our favorite tool for viewing your HTTP headers.
Using this information, you will be able to learn much more about a URL than you could with the naked eye. The right combination of headers can boost site performance, increase load times, and more. Our clean and simple interface was designed to make the process of viewing and checking headers quick and easy. Whether your site and its content are developed by PHP or another language, our headers checker tool will make sure you always know what’s going on behind the scenes.
What Are HTTP Headers?
HTTP headers are part of a website response that are normally hidden and can only be seen by a browser. They are a bit of code that informs the browser what it should do when viewing and/or opening the website. Essentially, they transfer data from a browser to the server and vice versa. These headers carry important information about the browser, the webpage, and the server itself.
In general, there are two different types of HTTP headers: the HTTP request header and the HTTP response header. The request header is sent to a server, which then sends back a response header.
HTTP Status Codes
While HTTP headers can help you see important information like software versions, content types, and cookie strings, the status codes are arguably the most important. An HTTP status code will quickly and easily tell you the status of a given website. A good and functional URL should always return with a response of 200 to show a successful request has been made.
In addition to 200, a few other common status codes include:
200
– The request has succeeded
301
– The requested resource has been assigned a new permanent URI and any future references to this resource SHOULD use one of the returned URIs.
302 – The requested resource resides temporarily under a different URI.
401
– The request requires user authentication.
404
– Not Found, he server has not found anything matching the Request-URI.
500
– Internal Server Error
503
– Service Unavailable,he server is currently unable to handle the request due to a temporary overloading or maintenance of the server.