Weave Code
Php Epp2 Laravel Package
africc/php-epp2
A PHP client library for the Extensible Provisioning Protocol (EPP), the standard used by domain registrars. It builds and parses EPP XML requests over TLS, with support for domain, contact, and host commands plus common registry extensions.
africc/php-epp2 is a PHP client for the Extensible Provisioning Protocol (EPP), designed to integrate with registrar and registry EPP servers for domain lifecycle automation. It provides structured handling of TLS connections, EPP frames, XML commands, and responses, making it easier to build reliable registrar integrations.
- Domain, contact, and host management commands
- Secure EPP login, greeting, and TLS connection handling
- XML request builders and response parsing
- Framework-agnostic PHP API
- Extensible command structure for custom EPP operations
Frequently asked questions about Php Epp2
- What is africc/php-epp2 and what does it do?
- africc/php-epp2 is a Composer-installable PHP client for the Extensible Provisioning Protocol (EPP). It builds RFC 5730-compliant XML command frames, sends them over a TCP/TLS socket to a registry, and parses the response into PHP objects. It is intended for registrar, reseller, and domain-portfolio back ends that need to register, renew, transfer, and manage domains and contacts.
- How do I install africc/php-epp2 in a Laravel application?
- Install it with Composer using composer require africc/php-epp2. In Laravel you would typically wrap the client in a small service class bound in a service provider, with registry credentials and endpoints supplied from config/epp.php and environment variables. A companion Symfony bundle exists, but you do not need it in Laravel.
- Does africc/php-epp2 support Laravel 11 and PHP 8.2, 8.3, and 8.4?
- The last tagged release was 2022-10-15, which is roughly three PHP minor versions of drift from current runtimes. Before adopting it you should verify PHP 8.2, 8.3, and 8.4 compatibility, check its symfony/* and psr/* constraints, and run a deprecation sweep under your target Laravel version. Treat a stale dependency graph as a real source of Composer update friction.
- Can I call africc/php-epp2 directly inside a Laravel controller?
- Technically yes, but it is a synchronous, blocking client and a single TLS round trip to a registry typically costs 150–500ms. In a normal request cycle, and especially under Octane or Swoole, that will tie up workers and hurt p99 latency. Put EPP commands behind a queued job with a small per-registry worker pool, and use a cached or strictly timed-out path for any user-facing availability checks.
- Does africc/php-epp2 support EPP extensions such as fee:0.12, secDNS:1.1, launch:1.0, RGP, and IDN?
- Base EPP covers create, check, info, update, transfer, renew, and delete, but real registries require extension namespaces for pricing, sunrise and claims, DNSSEC, restore, and IDN variants. The library's extension coverage is the highest-uncertainty item in the evaluation and must be confirmed against your target registry list. Build a registry-by-extension matrix first, because gaps mean you will hand-roll XML anyway.
- What license does africc/php-epp2 use, and can I use it in a commercial SaaS product?
- The package is GPL-3.0, which is a copyleft license. It is usually acceptable for internal or SaaS use where you do not distribute the binary, but it becomes problematic in an on-prem appliance, SDK, or distributed agent. Get legal sign-off before adoption, or architecturally contain the GPL code behind a separate service boundary.
- How do I connect africc/php-epp2 to a registry like Verisign, Nominet, Identity Digital, or PIR?
- Each registry has its own endpoint hostname, port, TLS requirements, credentials, and XML quirks, so you should model them as a config-driven credential and endpoint registry rather than hard-coding one connection. Use the library's standard OpenSSL transport and pass the correct host and port per registry. Expect registry-specific behavior differences and test each connection against that registry's OT&E environment.
- How do I test africc/php-epp2 against a registry OT&E or sandbox environment?
- Most registries provide an OT&E test bed with separate credentials and endpoints, and you should point your config at those during CI or staging runs. The evaluation notes do not confirm whether integration tests ship with the package, so plan to write your own harness covering login, greeting, check, create, and logout. Also verify session lifecycle handling, including greeting parsing, idle-timeout detection, and server-initiated close.
- Is africc/php-epp2 actively maintained and safe for production use?
- The project shows 54 stars and follows a single-maintainer pattern, with no visible security policy or CVE process and no tagged release since October 2022. That means you should assume a fork-and-own posture, track an active fork, and review the XML parsing configuration for LIBXML_NONET and entity-loading behavior. It can be used in production if you accept the maintenance burden and add idempotency and reconciliation around provisioning.
- What are the alternatives to africc/php-epp2 for EPP in PHP and Laravel?
- Alternatives include other Composer-installable PHP EPP clients, such as metaregistrar/php-epp-client, and writing a thin XML client tailored to your exact registry and extension set. Given the extension-coverage and maintenance uncertainty here, a small in-house client that only implements the commands and namespaces you actually need is a legitimate option. Compare licensing, PHP 8.x support, and OT&E test coverage before choosing.
Weaver
How can I help you explore Laravel packages today?