HTTP Status Testerhttp .dev HTTP Status Codes HTTP Headers HTTP Methods HTTP Testing Tools HTTP Status Tester HTTP Status Tester Check from different countries around the world the HTTP status code, HTTP response, HTTP headers, redirect chains and applicable robots.txt rules for multiple URLs. 0 / 100 URLs Test URLs Select a User Agent This is only used to apply robots.txt directives.defaultGooglebotGooglebot-ImageGooglebot-NewsGooglebot-VideoMediapartners-GoogleAdsBot-GoogleAdsBot-Google-MobileStoreBot-GoogleBingbotAdIdxBotBingPreviewBaiduspiderBaiduspider MobileBaiduspider-imageYandexBotYandexAdNetYandexBlogsYandexForDomainYandexImagesYandexImageResizerYandexMediaYandexNewsYandexOntoDBYandexPagecheckerYandexSearchShopYandexSitelinksYandexSpravBotYandexTurboYandexVertisYandexVerticalsYandexVideoYandexWebmasterExabotfacebookexternalhitia_archiverApplebotDuckDuckBotLinkedInBotCocCocBotCocCocBot-ImageSeznamBotSlurpSogouSogou MobilePetalBotTwitterbotYeti (Naver) From countryUnited StatesAustraliaCanadaFinlandFranceGermanyIndiaNetherlandsPolandSingaporeUnited Kingdom Include random UUID?The test will include an unique identifier in the HTTP headers for debug purposes. Follow redirects?Follows redirects when accessing the URLs. Security options: Optional Validate SSL?If enabled, the requests will fail if the SSL certificates are invalid. Optional request headers: Up to three additional valid HTTP headers (or starting with X-) can be added to the request. Disable robots.txt rules?Disable the default robots.txt rules check. Not recommended. Reset settings Test URLs What makes the HTTP Status Tester different from other similar tools? First, the HTTP Status Tester has bookmarkable and shareable public reports. Each report, as well as each HTTP response using the share link at the bottom of each response, can be shared with any other person. This assists with the debugging process when reporting issues to developers and system administrators. Although reports are publicly accessible, for privacy purposes reports are not publicly listed anywhere on this website. Second, with the HTTP Status Tester it is possible to access URLs from different locations in the world. This is beneficial to test what different users in different countries may see with regards to CDN responses and/or HTTP limitations, e.g. 451 Unavailable For Legal Reasons. Third, the HTTP Status Tester by default adheres to robots.txt directives and will inform about the crawlability of a URL. Fourth, because the HTTP Status Tester by default obeys robots.txt directives, it also informs which robots.txt file applies and what its HTTP response is. Fifth, the HTTP Status Tester also reports on all the HTTP Requests Headers and HTTP Response Headers encountered, e.g. HTTP sniffing or HTTP sniffer, during its journey, including those for the robots.txt URLs visited. Finally, the HTTP Status Tester includes by default a random identifier with each HTTP request, making it possible to trace and debug HTTP responses on the server side. Caveats The HTTP Status Tester checks for robots.txt always follow redirects to its final destination. The HTTP Status Tester adheres to robots.txt rules for filibot and uses rules for Googlebot as a fallback. The robots.txt check in the HTTP Status Tester can be disabled for debugging purposes but that is not recommended as it may lead to incorrect results. URLs entered without schema default to HTTPS. Parallel GET requests with the HTTP Status Tester are limited to two per hostname to prevent overloading servers. URLs submitted in the HTTP Status Tester are automatically encoded when containing characters outside the ASCII set. The HTTP Status Tester only supports the standard ports 80 (HTTP) and 443 (HTTPS). The HTTP Status Tester only checks the initial HTTP response and does not render the HTTP response. Any dependencies on JavaScript and/or meta data is not executed and/or used in the final HTTP response. HTTP requests by the HTTP Status Tester are primarily performed over HTTP/1.1. This may change in the future. The HTTP Status Tester currently supports only GET requests. For privacy and security purposes all public HTTP Status Tester reports expire and become inaccessible after 90 days. The HTTP Status Tester utilizes proxies to access the URLs from different geographic locations. As a consequence, some URLs may be blocked by the proxies and/or by the website's firewalls. In this case a 403 status code or 503 status codeis often returned and there is no way to access the URL until the block is removed. If you control the website in question, check the server/CDN log files if the blocked HTTP request is present. Optionally search for the unique identifier attached to the HTTP request. Once identified, remove the block to continue. The HTTP Status Tester accepts a maximum of 100 URLs per submission. When a lot of URLs are submitted, it may take some time (minutes) to load and render the report page as this includes per URL, in addition to the HTTP response headers, also snippets of the raw HTML code and/or robots.txt files/responses. For example, if 20 URLs submitted, the report potentially loads 20 robots.txt files and/or 20 HTML samples in addition to the report itself, all in one page request. To speed up the reports, submit smaller batches of URLs. Changelog March 10th, 2026: (experimental) Added indexability signals to reports, showing whether a page is indexable based on x-robots-tag, meta robots, meta googlebot, and canonical URL checks. March 10th, 2026: Fixed a bug related to status code reporting on robots.txt URLs. March 9th, 2026: Added wider support for HTTP status codes and HTTP headers. Feb 17th, 2026: Limited the maximum number of URLs per submission to 100. Added captcha to prevent abuse. Jan 17th, 2025: Significantly improved error messaging and reporting. However, reports for larger batches of URLs will now take more time to render the report. May 16th, 2024: Fixed a bug regarding the user-agent field which caused failed HTTP tests. May 9th, 2024: Fixed a few minor bugs and implemented some anti-abuse features. May 8th, 2024: Fixed a bug regarding the user-agent field. April 9th, 2024: Changed the proxies and enforcing filibot as the user-agent for live testing. Going forward, the user-agent dropdown is only used to check and apply robots.txt directives. May 9th, 2023: A few small bug fixes. Jan 11th, 2023: A number of small bug fixes, clarified blocks from firewalls and/or proxies, and restricted ports to 80 and 443. Jan 6th, 2023: Moved HTTP Status Tester to its own domain, from http.dev. Improve your SEO rankings! With SEO Audits by ex-Google Search Engineers searchbrothers.com Status HTTP Status Codes overview 100 Continue 101 Switching Protocols 102 Processing 103 Early Hints 200 OK 201 Created 202 Accepted 203 Non-Authoritative Information 204 No Content 205 Reset Content 206 Partial Content 207 Multi-Status 208 Already Reported 218 This is fine 226 IM Used 300 Multiple Choices 301 Moved Permanently 302 Found 303 See Other 304 Not Modified 305 Use Proxy 306 Switch Proxy 307 Temporary Redirect 308 Permanent Redirect 400 Bad Request 401 Unauthorized 402 Payment Required 403 Forbidden 404 Not Found 405 Method Not Allowed 406 Not Acceptable 407 Proxy Authentication Required 408 Request Timeout 409 Conflict 410 Gone 411 Length Required 412 Precondition Failed 413 Content Too Large 414 URI Too Long 415 Unsupported Media Type 416 Range Not Satisfiable 417 Expectation Failed 418 I'm a teapot 419 Page Expired 420 Method Failure or Enhance your calm 421 Misdirected Request 422 Unprocessable Content 423 Locked 424 Failed Dependency 425 Too Early 426 Upgrade Required 428 Precondition Required 429 Too Many Requests 430 Security Rejection 431 Request Header Fields Too Large 440 Login Time-out 444 No Response 449 Retry With 450 Blocked by Windows Parental Controls 451 Unavailable For Legal Reasons 460 Client closed connection prematurely 463 Too many forwarded IP addresses 464 Incompatible protocol 470 Request Denied 492 User Access Forbidden 493 Unsupported Browser 494 Request header too large 495 SSL Certificate Error 496 SSL Certificate Required 497 HTTP Request Sent to HTTPS Port 498 Invalid Token 499 Token Required or Client Closed Request 500 Internal Server Error 501 Not Implemented 502 Bad Gateway 503 Service Unavailable 504 Gateway Timeout 505 HTTP Version Not Supported 506 Variant Also Negotiates 507 Insufficient Storage 508 Loop Detected 509 Bandwidth Limit Exceeded 510 Not Extended 511 Network Authentication Required 520 Web Server Is Returning an Unknown Error 521 Web Server Is Down 522 Connection Timed Out 523 Origin Is Unreachable 524 A Timeout Occurred 525 SSL Handshake Failed 526 Invalid SSL Certificate 527 Railgun Listener to Origin 529 The Service Is Overloaded 530 Site Frozen 531 Upstream Connection Error 532 Response Too Large 533 Upstream TLS Error 534 Application Error 535 Unknown Application 536 HTTP Response Timeout 537 DNS Resolution Error 538 Request Loop 539 Serverless Timeout 540 Temporarily Disabled 541 Out of Workers 542 Database Error / Header Overflow 543 Communication Error / Upstream Timeout 544 Management Error / Invalid Host Header 545 Authentication Error / Component Not Ready 546 Unknown Application / TLS Error 547 No HTTP Response 548 Invalid Response / DNS Resolution Error 549 Authentication Gateway Error / Application Crash 552 Application Unreachable 553 Directory Service Error 554 Authentication Token Error 555 Application Does Not Support Kerberos 556 Unexpected Authentication Challenge 557 KDC Unreachable 558 Connection Limit Stop 559 Connection Limit Stop 561 Unauthorized 562 Credential Error 598 Network Read Timeout Error 599 Network Connect Timeout Error 600 Invalid Headers 893 Load Balancing Overflow 999 Request Denied Headers HTTP Headers overview A-IM Accept Accept-CH Accept-CH-Lifetime Accept-Charset Accept-Datetime Accept-Encoding Accept-Language Accept-Patch Accept-Post Accept-Ranges Accept-Signature Access-Control-Allow-Credentials Access-Control-Allow-Headers Access-Control-Allow-Methods Access-Control-Allow-Origin Access-Control-Expose-Headers Access-Control-Max-Age Access-Control-Request-Headers Access-Control-Request-Method Age Akamai-GRN Allow Alt-Svc Alt-Used Authentication-Info Authorization Available-Dictionary Cache-Control Cache-Group-Invalidation Cache-Groups Cache-Status Capsule-Protocol CDN-Cache-Control CDN-Loop Cf-Cache-Status Cf-Edge-Cache Cf-Mitigated Cf-Ray Clear-Site-Data Client-Cert Client-Cert-Chain Connection Content-Digest Content-Disposition Content-Encoding Content-Language Content-Length Content-Location Content-MD5 Content-Range Content-Security-Policy Content-Security-Policy-Report-Only Content-Type Cookie Critical-CH Cross-Origin-Embedder-Policy Cross-Origin-Embedder-Policy-Report-Only Cross-Origin-Opener-Policy Cross-Origin-Opener-Policy-Report-Only Cross-Origin-Resource-Policy Date Delta-Base Deprecation Device-Memory Dictionary-ID Digest DNT Document-Isolation-Policy Document-Isolation-Policy-Report-Only Document-Policy Downlink DPoP DPoP-Nonce Early-Data ECT Edge-Control ETag Expect Expect-CT Expires Feature-Policy Forwarded From GLB-X-Seen-By Host Host-Header HTTP2-Settings If-Match If-Modified-Since If-None-Match If-Range If-Unmodified-Since IM Incremental Keep-Alive Last-Event-ID Last-Modified Link Link-Template Location Max-Forwards Memento-Datetime MIME-Version NEL No-Vary-Search Onion-Location Origin Origin-Agent-Cluster Origin-Trial P3P Panel Permissions-Policy Ping-From Ping-To Platform Powered-By Pragma Prefer Preference-Applied Priority Proxy-Authenticate Proxy-Authentication-Info Proxy-Authorization Proxy-Status Public-Key-Pins Public-Key-Pins-Report-Only Purpose Range RateLimit RateLimit-Limit RateLimit-Policy RateLimit-Remaining RateLimit-Reset Referer Referrer-Policy Refresh Replay-Nonce Report-To Reporting-Endpoints Repr-Digest Request-Context Retry-After RTT Save-Data Sec-CH…