Directory / Webhooks
Webhooks 8
Adyen Webhooks
VerifiableAdyen · Webhooks
Adyen's payment-event webhook delivery service. Not a crawler; POSTs notifications to merchant endpoints. Adyen documents its egress domain for DNS-based allowlisting rather than a static IP list, since its outbound IPs change over time.
GitHub Webhooks
Fully verifiableGitHub · Webhooks
GitHub's webhook delivery service. Not a crawler; sends repository and organization event notifications to configured endpoints from IP ranges published in GitHub's meta API.
APIs-Google
Fully verifiableGoogle · Webhooks
Google's agent that delivers push notification messages sent through Google APIs (such as Pub/Sub and WebSub push subscriptions) to subscriber endpoints.
PayPal IPN
VerifiablePayPal · Webhooks
PayPal's Instant Payment Notification service. Not a crawler; POSTs payment-event notifications to merchant listener endpoints from a documented, static set of server CIDR ranges (shared with other PayPal server traffic).
Stripe Webhooks
Fully verifiableStripe · Webhooks
Stripe's webhook delivery service. Not a crawler; sends event notifications (payments, subscriptions) to merchant endpoints from published IPs.
Svix Webhooks
VerifiableSvix · Webhooks
Webhook-sending infrastructure used by Svix's customers to deliver events. Not a crawler; Pro/Enterprise plans get a documented, static set of per-region source IPs, and requests include a Svix sender identifier in the User-Agent.
Telegram Bot Webhooks
VerifiableTelegram · Webhooks
Telegram's webhook delivery to bot servers. Not a crawler; POSTs update events to a bot's registered HTTPS endpoint from two documented, static CIDR ranges. Telegram documents no User-Agent for these POSTs; the UA listed here is Telegram's documented fetcher token and is unconfirmed for webhook traffic — verify by source IP, not UA.
Twilio Webhooks
Listed onlyTwilio · Webhooks
Twilio's webhook delivery service, which POSTs event callbacks (incoming messages and calls, status updates) to customer-configured endpoints. Not a crawler. Twilio states there is no fixed range of source IPs — requests come from a dynamic pool — so recipients are told to validate the X-Twilio-Signature request signature instead.