Hunter vs TotalShiftLeft Sandbox

Same instrument, two spec sheets — measured, not claimed.

Uptime · 30d
Uptime · 90d100%98.9%
Uptime · 30d100%98.3%
P50 · ms111417
P95 · ms9461171
AuthapiKeynone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree — open sandbox, auth optional
Rate limitUnpublished100 req/window · 99 remaining · resets 60
In directory since2026-07-052026-07-05
operationalpartialdownno data

Hunter vs TotalShiftLeft Sandbox: common questions

Which is more reliable, Hunter or TotalShiftLeft Sandbox?

On our scheduled checks, Hunter leads on measured uptime — Hunter at 100% versus TotalShiftLeft Sandbox at 98.9% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, Hunter or TotalShiftLeft Sandbox?

Hunter has the lower median latency in our checks — Hunter responds in 111 ms versus TotalShiftLeft Sandbox at 417 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do Hunter and TotalShiftLeft Sandbox need an API key?

TotalShiftLeft Sandbox needs no key, while Hunter requires a free API key. If you want to start calling without signup, reach for TotalShiftLeft Sandbox first.

Can I call Hunter and TotalShiftLeft Sandbox from the browser?

Neither sends browser-friendly CORS headers reliably, so call Hunter and TotalShiftLeft Sandbox from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are Hunter and TotalShiftLeft Sandbox free for commercial use?

Hunter has unclear commercial terms, and TotalShiftLeft Sandbox has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.