HTTP Endpoint

An HTTP endpoint in Overmind represents any publicly-addressable URL that responds to the Hypertext Transfer Protocol (HTTP or HTTPS). When an endpoint is added to your catalogue, Overmind performs a lightweight HEAD request to collect metadata such as status code, response headers, redirect targets and (for HTTPS) the x509 certificate chain. This information helps you understand availability, encryption posture and potential dependency risks before you ship a change.
For a detailed description of the HTTP protocol itself, see the IETF specification: https://www.rfc-editor.org/rfc/rfc9110

Supported Methods

• GET: A HTTP endpoint to run a HEAD request against
• LIST
• SEARCH

Possible Links

ip

The endpoint’s hostname ultimately resolves to one or more IP addresses. Overmind links these addresses so you can trace connectivity issues, firewall rules or network ACLs that might affect reachability.

dns

The fully-qualified domain name extracted from the URL is represented as a DNS record. Linking the endpoint to its DNS records lets you spot misconfigured zones, impending record changes or expired domains that could break the service.

certificate

For HTTPS endpoints, the TLS handshake exposes the server’s leaf and intermediate certificates. Overmind creates a link to the corresponding certificate resource so you can monitor expiry dates, key sizes and issuing CAs.

http

If the initial HEAD request returns redirects (3xx responses) or contains absolute links in headers such as Location, Overmind follows them and establishes relationships between the original and the target HTTP endpoints, revealing chained dependencies and potential circular redirects.