Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
This repository was archived by the owner on Nov 20, 2019. It is now read-only.

[DEPRECATED] Library for extraction of domain parts e.g. TLD. Domain parser that uses Public Suffix List

License

NotificationsYou must be signed in to change notification settings

layershifter/TLDExtract

Repository files navigation

Consider to usehttps://github.com/jeremykendall/php-domain-parser as maintained alternative.

TLDExtract

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'.

Latest Version on PackagistSoftware LicenseBuild StatusCoverage StatusTotal Downloads


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 parsinghttp://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 tothe 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(LayerShifter\TLDExtract\Result)#34 (3) {  ["subdomain":"LayerShifter\TLDExtract\Result":private]=>  string(11)"forums.news"  ["hostname":"LayerShifter\TLDExtract\Result":private]=>  string(3)"cnn"  ["suffix":"LayerShifter\TLDExtract\Result":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 withPSR-1,PSR-2,PSR-4. If you notice compliance oversights, please send a patch via pull request.

Does TLDExtract make requests to Public Suffix List website?

No.TLDExtract uses database fromTLDDatabase that generated from Public Suffix List and updated regularly. It does not make any HTTP requests to parse or validate a domain.

Requirements

The following versions of PHP are supported.

  • PHP 5.5
  • PHP 5.6
  • PHP 7.0
  • PHP 7.1
  • PHP 7.2
  • PHP 7.3
  • HHVM

Install

Via Composer

$ composer require layershifter/tld-extract

Additional result methods

ClassLayerShifter\TLDExtract\Result has some usable methods:

$extract =newLayerShifter\TLDExtract\Extract();# 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

Custom database

By default package is using database fromTLDDatabase package, but you can override this behaviour simply:

newLayerShifter\TLDExtract\Extract(__DIR__ .'/cache/mydatabase.php');

For more details and how keep database updatedTLDDatabase.

Implement own result

By default after parse you will receive object ofLayerShifter\TLDExtract\Result class, but sometime you need own methods or additional functionality.

You can create own class that implementsLayerShifter\TLDExtract\ResultInterface and use it as parse result.

class CustomResultimplementsLayerShifter\TLDExtract\ResultInterface {}newLayerShifter\TLDExtract\Extract(null, CustomResult::class);

Parsing modes

Package has three modes of parsing:

  • allow ICANN suffixes (domains are those delegated by ICANN or part of the IANA root zone database);
  • allow private domains (domains are amendments submitted to Public Suffix List by the domain holder, as an expression of how they operate their domain security policy);
  • allow custom (domains that are not in list, but can be usable, for example: example, mycompany, etc).

For keeping compatibility with Public Suffix List ideas package runs in all these modes by default, but you can easily change this behavior:

useLayerShifter\TLDExtract\Extract;newExtract(null,null, Extract::MODE_ALLOW_ICANN);newExtract(null,null, Extract::MODE_ALLOW_PRIVATE);newExtract(null,null, Extract::MODE_ALLOW_NOT_EXISTING_SUFFIXES);newExtract(null,null, Extract::MODE_ALLOW_ICANN | Extract::MODE_ALLOW_PRIVATE);

Change log

Please seeCHANGELOG for more information what has changed recently.

Testing

$ composertest

Contributing

Please seeCONTRIBUTING andCONDUCT for details.

License

This library is released under the Apache 2.0 license. Please seeLicense File for more information.

About

[DEPRECATED] Library for extraction of domain parts e.g. TLD. Domain parser that uses Public Suffix List

Topics

Resources

License

Stars

Watchers

Forks

Packages

No packages published

[8]ページ先頭

©2009-2025 Movatter.jp