Fajita only checks public destinations. This protects both your network and Fajita's infrastructure from being used to reach internal systems.
Blocked destinations
- Private IP ranges and loopback addresses.
- Link-local and cloud metadata endpoints.
- Reserved networks.
- Unsupported protocols and restricted ports.
- Redirects that resolve to any of the above.
Make an endpoint monitorable
- Expose a public HTTPS health endpoint.
- Remove redirects that point to private destinations.
- Use an authentication header instead of a private network path.
- Return minimal health data and keep secrets out of query parameters.