usercheck.com valid

UserCheck

UserCheck is a domain intelligence API. Given an email address or a domain, it returns the signals to block fake signups: disposable email detection, relay and forwarding detection, MX validation, domain age and reputation, and more.

For agents: Domain intelligence API that flags disposable, relay and forwarding emails, MX validity and domain reputation to block fake signups. Docs include quickstart and

disposable email detectionemail validation apifake signup preventionmx validationdomain reputation

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-20T19:03:06.071Z. Cached copy · Source on usercheck.com

# UserCheck

> UserCheck is a domain intelligence API. Given an email address or a domain, it returns the signals to block fake signups: disposable email detection, relay and forwarding detection, MX validation, domain age and reputation, and more.

Key features:
- Disposable email detection with an always up-to-date database
- Email forwarding and relay domain detection
- MX records validation and mail provider identification (mx_providers)
- Public email provider detection (Gmail, Yahoo, etc.)
- Spam domain flagging
- Domain authority scoring (0–100)
- TLD trust scoring (1–5)
- SPF and DMARC posture
- Email normalization (normalized_email) to catch aliases of the same mailbox
- Smart typo suggestions (did_you_mean)
- Role account detection (hello@, support@, etc.)
- Custom blocklists for blocking specific domains
- Gates: A rule-based decision engine for signup fraud prevention, with a REST Management API for gates, rules, and decision logs
- Webhooks for real-time notifications
- Integrations with WordPress, Laravel, Zapier, and Make

## Docs

- [Overview](https://www.usercheck.com/docs/get-started/overview.md): What the API returns and how the documentation is organized
- [Quickstart](https://www.usercheck.com/docs/get-started/quickstart.md): Make your first request, read the response, and block a disposable signup
- [Environments](https://www.usercheck.com/docs/get-started/environments.md): How production, staging, and development environments separate keys, blocklists, and webhooks
- [Credits](https://www.usercheck.com/docs/get-started/credits.md): How credits work, what each request costs, and how usage is tracked

### API Reference

- [Introduction](https://www.usercheck.com/docs/api/introduction.md): Base URL, endpoints, authentication, and error format
- [Authentication](https://www.usercheck.com/docs/api/authentication.md): How to authenticate API requests
- [Domain Endpoint](https://www.usercheck.com/docs/api/domain-endpoint.md): Check if a domain is used for disposable email addresses
- [Email Endpoint](https://www.usercheck.com/docs/api/email-endpoint.md): Check if an email address is disposable
- [Blocklist Endpoint](https://www.usercheck.com/docs/api/blocklist-endpoint.md): Manage your account's blocklist of domains
- [Status Endpoint](https://www.usercheck.com/docs/api/status-endpoint.md): Check your account details, plan information, and current API usage
- [Rate Limits](https://www.usercheck.com/docs/api/rate-limits.md): Requests per second allowed on each plan and what happens when you exceed it

### Gates

- [Gates](https://www.usercheck.com/docs/gates/overview.md): Rule-based access control to allow, block, or challenge user actions
- [Quickstart](https://www.usercheck.com/docs/gates/quickstart.md): Create your first gate, review its rules, and call it from your application
- [Rules & Conditions](https://www.usercheck.com/docs/gates/rules-conditions.md): How a gate evaluates its rules, and the fields a condition can check
-
…

Related sites

Other listed sites in Cybersecurity. See the whole category →

Machine-readable: GET /v1/resolve?q=usercheck.com · GET /v1/domain/usercheck.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for usercheck.com:
1. POST https://agentwebmap.com/v1/sites/usercheck.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://usercheck.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/usercheck.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/usercheck.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.