Laravel Rdap Laravel Package

Product Decisions This Supports

• Domain/IP Intelligence Features: Enables building domain/IP lookup tools (e.g., WHOIS alternatives, security monitoring, or compliance checks) without reinventing RDAP integration.
• Roadmap Expansion: Accelerates development of domain availability validation, threat intelligence feeds, or registration analytics for SaaS products targeting registrars, cybersecurity firms, or legal teams.
• Build vs. Buy: Buy—avoids maintaining custom RDAP clients, caching logic, and retry mechanisms. Build only if needing deep customization (e.g., private RDAP endpoints, non-standard responses).
• Use Cases:
  • Security: Flag suspicious domains/IPs (e.g., "clientTransferProhibited" status).
  • Operations: Automate domain expiration alerts or IP blocklist checks.
  • Compliance: Audit domain registrations for GDPR/legal requirements (e.g., expiration dates).
  • UX: Pre-fill forms with RDAP data (e.g., registrant contact info).

When to Consider This Package

• Adopt if:
  • Your Laravel app needs structured domain/IP data (JSON > WHOIS text).
  • You require reliable retries/caching (handles RDAP’s unreliability out-of-the-box).
  • Your use case aligns with supported TLDs/IP ranges (check supportedTlds()).
  • You’re time-constrained—avoids 3rd-party API costs (e.g., no need for WhoisXML or similar services).
• Look Elsewhere if:
  • You need unsupported TLDs/IP ranges (e.g., .be, .io may lack RDAP).
  • You require real-time WHOIS data (RDAP is often delayed; consider hybrid approaches).
  • Your stack isn’t Laravel/PHP (e.g., Node.js/Python alternatives exist).
  • You need historical WHOIS snapshots (RDAP is present-tense only).

How to Pitch It (Stakeholders)

For Executives: "This package lets us integrate structured domain/IP data into [Product X] with minimal dev effort—no API costs, no custom infrastructure. For example, we could auto-detect expired domains in our portfolio (reducing churn) or flag high-risk IPs in our network (improving security). It’s battle-tested by Spatie (used in 70+ projects) and supports caching/retry logic to handle RDAP’s quirks."

For Engineering: *"Leverage Rdap::domain('example.com') to fetch JSON-structured data (registration dates, statuses, contacts) with built-in:

• Caching: TLD server URLs cached for 1 week; domain responses cached per request.
• Retries: 3 attempts with configurable timeouts (5s default).
• Extensibility: Override defaults (e.g., custom RDAP servers for testing). Tradeoff: Limited to supported TLDs/IPs (verify with Rdap::domainIsSupported()).* Example Use Case:

// Check if a domain is transfer-locked (e.g., for compliance)
if (Rdap::domain('example.com')->hasStatus(DomainStatus::ClientTransferProhibited)) {
    notifyAdmin("Domain locked: $domain");
}
```*
**Risk**: RDAP coverage gaps (e.g., `.be` domains return `null`). Mitigate by validating `supportedTlds()` early."*