AI-powered
Cyberintelligence.
Real-time fraud risk analysis for every request — powered by IP, email, domain, and device signals.
Trusted by 500+ engineering teams
Signal Check
Blocklist Reputation
Checking blocklists…
Threat Score
Low Risk—/100
Scanning…
Edge response time
< 50ms
Global P95
Email domains blocked
100k+
Continuously updated
API uptime SLA
99.9%
Last 90 days
Three tools, one bill
1 SDK
IP · Email · CAPTCHA
Share links bots can't follow.
RequestGuard Go keeps the destination URL server-side until a visitor passes browser checks and CAPTCHA. Real humans see the destination hostname, then continue through a server-side redirect.
Protected redirect
go.requestguard.com/a1c2d3rs
Visitor opens protected link
Destination URL stays private
Browser checks and CAPTCHA run
Bots stop before the target
Human sees destination hostname
Server-side continue redirect
Live intelligence
Browse checks people actually run.
Public examples for domains, IP addresses, email addresses, and npm packages. Filter the lists, then open the check that matches the thing you are reviewing.
Recent domain checks
Popular and rising domains that are useful starting points for reputation, DNS, and infrastructure review.
google.com
Search Engines
googleapis.com
Infrastructure
cloudflare.com
Infrastructure
gstatic.com
Infrastructure
apple.com
Technology
microsoft.com
Business Software
amazon.com
Commerce
facebook.com
Social Media
Recent IP checks
Inspectable public IP examples for resolvers, cloud ranges, datacenter traffic, and Tor-style risk review.
1.1.1.1
Cloudflare anycast resolver; useful for checking clean infrastructure handling.
8.8.8.8
Google public DNS address used as a low-risk infrastructure reference.
185.220.101.1
Known Tor-style exit address used to preview high-risk IP report behavior.
37.27.1.1
Hetzner cloud range example for hosting and datacenter review.
52.94.236.248
AWS-style cloud address for reviewing infrastructure traffic.
20.42.65.84
Microsoft cloud range example for signup or checkout review.
Recent email checks
Full role-based email addresses for signup, checkout, support, and abuse-review examples without adding emails to URLs.
abuse@cloudflare.com
Public role-style mailbox on a major infrastructure domain.
security@github.com
Security contact pattern on a developer platform domain.
support@shopify.com
Commerce support address pattern for order-context checks.
support@stripe.com
Payments support address pattern for checkout review.
security@microsoft.com
Enterprise security mailbox pattern on a large software domain.
abuse@amazonaws.com
Cloud abuse mailbox pattern often seen in infrastructure investigations.
npm vulnerability checks
High-impact npm packages with public package metadata, download context, and OSV advisory detail pages.
semver
Open package metadata, downloads, and known advisories.
ansi-styles
Open package metadata, downloads, and known advisories.
debug
Open package metadata, downloads, and known advisories.
chalk
Open package metadata, downloads, and known advisories.
minimatch
Open package metadata, downloads, and known advisories.
supports-color
Open package metadata, downloads, and known advisories.
strip-ansi
Open package metadata, downloads, and known advisories.
ms
Open package metadata, downloads, and known advisories.
ansi-regex
Open package metadata, downloads, and known advisories.
string-width
Open package metadata, downloads, and known advisories.
tslib
Open package metadata, downloads, and known advisories.
brace-expansion
Open package metadata, downloads, and known advisories.
Next step
Turn a checked signal into a full fraud report.
Save the email, IP, domain, package, or order context, then review the reasons behind a Trust, Review, or Block recommendation.