Jun 4
Failed scans no longer cost credits. If
/analyze (or any of /check, /lookup, /dns, /vulnerability, /history, /stats, /changes, /certificate/check, /security) returns a 4xx or 5xx because the target domain didn’t resolve, the TLS handshake failed, the fetch timed out, or the site was unreachable, the credit it consumed is now refunded automatically. The X-RateLimit-Used header reflects the refund. Customers whose monthly counter was charged for failed scans in early June were credited retroactively. The /site, /analyze/batch, and /compare endpoints have separate refund handling on the roadmap.