tldts - Blazing Fast URL Parsing
tldts
is a JavaScript library to extract hostnames, domains, public suffixes, top-level domains and subdomains from URLs.
Features:
- Tuned for performance (order of 0.1 to 1 μs per input)
- Handles both URLs and hostnames
- Full Unicode/IDNA support
- Support parsing email addresses
- Detect IPv4 and IPv6 addresses
- Continuously updated version of the public suffix list
- TypeScript, ships with
umd
, esm
, cjs
bundles and type definitions - Small bundles and small memory footprint
- Battle tested: full test coverage and production use
Install
npm install --save tldts
Usage
Using the command-line interface:
$ npx tldts 'http://www.writethedocs.org/conf/eu/2017/'
{
"domain": "writethedocs.org",
"hostname": "www.writethedocs.org",
"isIcann": true,
"isIp": false,
"isPrivate": false,
"publicSuffix": "org",
"subdomain": "www"
}
Programmatically:
const { parse } = require('tldts');
parse('http://www.writethedocs.org/conf/eu/2017/');
Modern ES6 modules import is also supported:
import { parse } from 'tldts';
API
tldts.parse(url | hostname, options)
tldts.getHostname(url | hostname, options)
tldts.getDomain(url | hostname, options)
tldts.getPublicSuffix(url | hostname, options)
tldts.getSubdomain(url, | hostname, options)
The behavior of tldts
can be customized using an options
argument for all
the functions exposed as part of the public API. This is useful to both change
the behavior of the library as well as fine-tune the performance depending on
your inputs.
{
allowIcannDomains: boolean;
allowPrivateDomains: boolean;
extractHostname: boolean;
validateHostname: boolean;
detectIp: boolean;
mixedInputs: boolean;
validHosts: string[] | null;
}
The parse
method returns handy properties about a URL or a hostname.
const tldts = require('tldts');
tldts.parse('https://spark-public.s3.amazonaws.com/dataanalysis/loansData.csv');
tldts.parse('https://spark-public.s3.amazonaws.com/dataanalysis/loansData.csv', { allowPrivateDomains: true })
tldts.parse('gopher://domain.unknown/');
tldts.parse('https://192.168.0.0')
tldts.parse('https://[::1]')
tldts.parse('tldts@emailprovider.co.uk')
Property Name | Type | Description |
---|
hostname | str | hostname of the input extracted automatically |
domain | str | Domain (tld + sld) |
subdomain | str | Sub domain (what comes after domain ) |
publicSuffix | str | Public Suffix (tld) of hostname |
isIcann | bool | Does TLD come from ICANN part of the list |
isPrivate | bool | Does TLD come from Private part of the list |
isIP | bool | Is hostname an IP address? |
Single purpose methods
These methods are shorthands if you want to retrieve only a single value (and
will perform better than parse
because less work will be needed).
getHostname(url | hostname, options?)
Returns the hostname from a given string.
const { getHostname } = require('tldts');
getHostname('google.com');
getHostname('fr.google.com');
getHostname('fr.google.google');
getHostname('foo.google.co.uk');
getHostname('t.co');
getHostname('fr.t.co');
getHostname('https://user:password@example.co.uk:8080/some/path?and&query#hash');
getDomain(url | hostname, options?)
Returns the fully qualified domain from a given string.
const { getDomain } = require('tldts');
getDomain('google.com');
getDomain('fr.google.com');
getDomain('fr.google.google');
getDomain('foo.google.co.uk');
getDomain('t.co');
getDomain('fr.t.co');
getDomain('https://user:password@example.co.uk:8080/some/path?and&query#hash');
getSubdomain(url | hostname, options?)
Returns the complete subdomain for a given string.
const { getSubdomain } = require('tldts');
getSubdomain('google.com');
getSubdomain('fr.google.com');
getSubdomain('google.co.uk');
getSubdomain('foo.google.co.uk');
getSubdomain('moar.foo.google.co.uk');
getSubdomain('t.co');
getSubdomain('fr.t.co');
getSubdomain('https://user:password@secure.example.co.uk:443/some/path?and&query#hash');
getPublicSuffix(url | hostname, options?)
Returns the public suffix for a given string.
const { getPublicSuffix } = require('tldts');
getPublicSuffix('google.com');
getPublicSuffix('fr.google.com');
getPublicSuffix('google.co.uk');
getPublicSuffix('s3.amazonaws.com');
getPublicSuffix('s3.amazonaws.com', { allowPrivateDomains: true });
getPublicSuffix('tld.is.unknown');
Troubleshooting
Retrieving subdomain of localhost
and custom hostnames
tldts
methods getDomain
and getSubdomain
are designed to work only with known and valid TLDs.
This way, you can trust what a domain is.
localhost
is a valid hostname but not a TLD. You can pass additional options to each method exposed by tldts
:
const tldts = require('tldts');
tldts.getDomain('localhost');
tldts.getSubdomain('vhost.localhost');
tldts.getDomain('localhost', { validHosts: ['localhost'] });
tldts.getSubdomain('vhost.localhost', { validHosts: ['localhost'] });
Updating the TLDs List
tldts
made the opinionated choice of shipping with a list of suffixes directly
in its bundle. There is currently no mechanism to update the lists yourself, but
we make sure that the version shipped is always up-to-date.
If you keep tldts
updated, the lists should be up-to-date as well!
Performance
tldts
is the fastest JavaScript library available for parsing hostnames. It is able to parse millions of inputs per second (typically 2-3M depending on your hardware and inputs). It also offers granular options to fine-tune the behavior and performance of the library depending on the kind of inputs you are dealing with (e.g.: if you know you only manipulate valid hostnames you can disable the hostname extraction step with { extractHostname: false }
).
Please see this detailed comparison with other available libraries.
Experimental Bundle
tldts
ships with two bundles, the default one is what you should use and what
is imported out of the box. It makes use of an optimized DAWG (direct acyclic
word graph) data-structure and delivers very good performances. If that is not
enough, you can try the tldts-experimental
bundle which implements a
probabilistic data-structure. It is:
- Must smaller (in terms of bundle size and memory footprint)
- Loads instantly (no data loading or parsing required)
- Much faster (lookups are up to 1.5-2x faster)
The drawback is that there might be some unlikely false positive (think bloom filters).
For more details, check the documentation from the following files:
Contributors
tldts
is based upon the excellent tld.js
library and would not exist without
the many contributors who worked on the project:
This project would not be possible without the amazing Mozilla's
public suffix list. Thank you for your hard work!
License
MIT License.