Consider to use https://github.com/jeremykendall/php-domain-parser as maintained alternative.
TLDExtract
accurately separates the gTLD or ccTLD (generic or country code top-level domain) from the registered domain and subdomains of a URL, e.g. domain parser. For example, say you want just the 'google' part of 'http://www.google.com'.
Everybody gets this wrong. Splitting on the '.' and taking the last 2 elements goes a long way only if you're thinking of simple e.g. .com domains. Think parsing http://forums.bbc.co.uk for example: the naive splitting method above will give you 'co' as the domain and 'uk' as the TLD, instead of 'bbc' and 'co.uk' respectively.
TLDExtract
on the other hand knows what all gTLDs and ccTLDs look like by looking up the currently living ones according to the Public Suffix List. So, given a URL, it knows its subdomain from its domain, and its domain from its country code.
$result = tld_extract('http://forums.news.cnn.com/');
var_dump($result);
object(LayerShifterTLDExtractResult)#34 (3) {
["subdomain":"LayerShifterTLDExtractResult":private]=>
string(11) "forums.news"
["hostname":"LayerShifterTLDExtractResult":private]=>
string(3) "cnn"
["suffix":"LayerShifterTLDExtractResult":private]=>
string(3) "com"
}
Result
implements ArrayAccess interface, so you simple can access to its result.
var_dump($result['subdomain']);
string(11) "forums.news"
var_dump($result['hostname']);
string(3) "cnn"
var_dump($result['suffix']);
string(3) "com"
Also you can simply convert result to JSON.
var_dump($result->toJson());
string(54) "{"subdomain":"forums.news","hostname":"cnn","suffix":"com"}"
This package is compliant with PSR-1, PSR-2, PSR-4. If you notice compliance oversights, please send a patch via pull request.
No. TLDExtract
uses database from TLDDatabase that generated from Public Suffix List and updated regularly. It does not make any HTTP requests to parse or validate a domain.
The following versions of PHP are supported.
Via Composer
$ composer require layershifter/tld-extract
Class LayerShifterTLDExtractResult
has some usable methods:
$extract = new LayerShifterTLDExtractExtract();
# For domain 'shop.github.com'
$result = $extract->parse('shop.github.com');
$result->getFullHost(); // will return (string) 'shop.github.com'
$result->getRegistrableDomain(); // will return (string) 'github.com'
$result->isValidDomain(); // will return (bool) true
$result->isIp(); // will return (bool) false
# For IP '192.168.0.1'
$result = $extract->parse('192.168.0.1');
$result->getFullHost(); // will return (string) '192.168.0.1'
$result->getRegistrableDomain(); // will return null
$result->isValidDomain(); // will return (bool) false
$result->isIp(); // will return (bool) true
By default package is using database from TLDDatabase package, but you can override this behaviour simply:
new LayerShifterTLDExtractExtract(__DIR__ . '/cache/mydatabase.php');
For more details and how keep database updated TLDDatabase.
By default after parse you will receive object of LayerShifterTLDExtractResult
class, but sometime you need own methods or additional functionality.
You can create own class that implements LayerShifterTLDExtractResultInterface
and use it as parse result.
class CustomResult implements LayerShifterTLDExtractResultInterface {}
new LayerShifterTLDExtractExtract(null, CustomResult::class);
Package has three modes of parsing:
For keeping compatibility with Public Suffix List ideas package runs in all these modes by default, but you can easily change this behavior:
use LayerShifterTLDExtractExtract;
new Extract(null, null, Extract::MODE_ALLOW_ICANN);
new Extract(null, null, Extract::MODE_ALLOW_PRIVATE);
new Extract(null, null, Extract::MODE_ALLOW_NOT_EXISTING_SUFFIXES);
new Extract(null, null, Extract::MODE_ALLOW_ICANN | Extract::MODE_ALLOW_PRIVATE);
Please see CHANGELOG for more information what has changed recently.
$ composer test
Please see CONTRIBUTING and CONDUCT for details.
This library is released under the Apache 2.0 license. Please see License File for more information.