Webhook signing is a mechanism where the sender adds an HMAC signature of the payload to an HTTP header, and the receiver verifies the signature with a shared secret. Without signing, anyone who knows the webhook URL can send fake events. Standard pattern: HMAC-SHA256(secret, timestamp + body) → header X-Hub-Signature-256. Used by Stripe, GitHub, Telegram, YooKassa, Slack.
Below: details, example, related terms, FAQ.
hash_equals() in PHP, crypto.timingSafeEqual() in Node// PHP verification
$expected = hash_hmac("sha256", $body, $secret);
$actual = $_SERVER["HTTP_X_SIGNATURE_256"];
if (!hash_equals($expected, $actual)) return 401;The tool checks HTTP security headers, SSL/TLS configuration, server info leaks, and protection against common attacks (XSS, clickjacking, MIME sniffing). A grade fromA to F shows overall security level.
Checking Content-Security-Policy, HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and more.
TLS version, certificate expiry, chain of trust, HSTS support.
Finding exposed server versions, debug modes, open configs, and directories.
Detailed report explaining each issue with specific steps to fix it.
HTTP header audit
config verification
CSP & HSTS setup
compliance checks
Strict-Transport-Security.Server: Apache/2.4.52 helps attackers find exploits. Hide the version.DENY or SAMEORIGIN.nosniff, browsers may misinterpret file types (MIME sniffing).Content-Security-Policy-Report-Only, monitor violations, then enforce.Server, X-Powered-By, X-AspNet-Version from responses.Security check history and HTTP security header monitoring.
Sign up freeA secret in a header travels in plain. HMAC signs the body; the secret is never transmitted.
Timestamp + nonce in payload. Receiver confirms fresh timestamp (5 min window) and unused nonce.
Stripe (Stripe-Signature), GitHub (X-Hub-Signature-256), Slack (X-Slack-Signature), Telegram (X-Telegram-Bot-Api-Secret-Token), YooKassa.