Skip to main content

ExtraHop® Closes Enterprise Data Center Blind Spots with new 400 Gbps sensor

Search
  • Solutionschevron right
  • Industrieschevron right
  • Platformchevron right
  • Resourceschevron right
  • Customerschevron right
  • Companychevron right

DETECTION OVERVIEW

HTTP 400 Status Codes

Category

Web Application
Detection diagram
Next in Web Application: HTTP Bad Requests

Description

An application or device had an excessive number of responses with an HTTP 400-level status code, which indicates that a client issued a valid command to the device that was not successful.

Background

HTTP is a communication protocol that enables users to deliver data over the internet. An unusual increase in HTTP 400-level (Client Error) responses indicates that a server is receiving a high volume of invalid or malformed HTTP requests that cannot be processed. A spike in errors might be caused by broken deployments, outdated API clients, or web scanning attempts.

Mitigation Options

Check for client misconfigurations, applications, scripts, or user agents that are sending malformed HTTP requests.

Check for identity provider issues or recent changes to Access Control Lists (ACLs) to avoid 401 (Unauthorized) or 403 (Forbidden) errors.

Validate load balancer and proxy rules to ensure requests are not being incorrectly dropped or rejected before reaching the web server.


Associated content

Announcing The Forrester Wave™: Network Analysis And Visibility Solutions, Q4 2025

Network analysis and visibility solutions remain underrepresented in enterprises. Find out why in this preview of a new Wave report.

Report

ExtraHop® Named a Leader in First-Ever Gartner® Magic Quadrant™ for Network Detection and Response — ExtraHop

ExtraHop® Named a Leader in First-Ever Gartner® Magic Quadrant™ for Network Detection and Response

News

Detections

Visit this resource for more information.

Documentation
Periodic Table of Use Cases

What else can RevealX do for you?