npmpackage.info

Gathering detailed insights and metrics for tld-extract

Other packages similar to tld-extract

@geek/tld

2.0.1-1

Extract the TLD/domain/subdomain parts of an URL/hostname against mozilla TLDs 'official' listing .

extract-tld

1.1.2

Extract the TLD from a URL against the [public suffix list](https://publicsuffix.org/).

qnton-tld-extract

2.0.2

`qnton-tld-extract` is a simple npm package that allows you to extract the top-level domain (TLD), domain, and subdomain from a given URL.

jsdomain-parser

1.0.8

Parse URLs to extract TLDs, domain, protocols and more

Gathering detailed insights and metrics for tld-extract

tld-extract - 2.1.0 | npmpackage.info

tld-extract

Nodejs TLD extract

2.1.0

MIT

JavaScript

212.55 kB

3.4

Installations

npm install tld-extract

Developer Guide

BETA

Typescript

No

Module System

CommonJS

Node Version

8.17.0

NPM Version

6.13.4 Pull Requests

Open

0

Total

6

Closed

5

Merged

1

Issues

Open

1

Total

11

Closed

10

Releases

Unable to fetch releases

Languages

JavaScript

TypeScript

JavaScript (74.55%)

TypeScript (25.45%)

Developer

131 Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

MIT License

46 Stars

40 Commits

15 Forks

2 Watchers

1 Branches

3 Contributors

Updated on Jul 01, 2025

Maintainers

View All 3 Contributors

Package Meta Information

Latest Version

2.1.0

Package Id

tld-extract@2.1.0

Unpacked Size

212.55 kB

Size

47.21 kB

File Count

NPM Version

6.13.4

Node Version

8.17.0

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dev Dependencies

eslint-plugin-ivs expect.js mocha nyc

Motivation

Extract the TLD/domain/subdomain parts of an URL/hostname against mozilla TLDs official listing.

API

var parser = require('tld-extract');

console.log( parser("http://www.google.com") );
console.log( parser("http://google.co.uk") );
/**
* >> { tld: 'com', domain: 'google.com', sub: 'www' }
* >> { tld: 'co.uk', domain: 'google.co.uk', sub: '' }
*/

Private TLDs

Private TLDs are supported, see chromium source code for specs

console.log( parser("http://jeanlebon.cloudfront.net"));
/**
* >> { tld : 'net', domain : 'cloudfront.net', sub : 'jeanlebon' };
*/


console.log( parser("http://jeanlebon.cloudfront.net", {allowPrivateTLD : true}));
/**
* >> { tld : 'cloudfront.net', domain : 'jeanlebon.cloudfront.net', sub : '' };
*/

Unknown TLDs (level0)

By default, unknown TLD throw an exception, you can allow them and use tld-extract as a parser using the allowUnknownTLD option

  parse("http://nowhere.local")
    >> throws /Invalid TLD/

  parse("http://nowhere.local", {allowUnknownTLD : true}))
    >> { tld : 'local', domain : 'nowhere.local', sub : '' }

DotLess domain

Using a tld as a direct domain name, or dotless domain is highly not recommended (ICANN and IAB have spoken out against the practice, classifying it as a security risk among other concerns.[34] ICANN's Security and Stability Advisory Committee (SSAC) additionally claims that SMTP "requires at least two labels in the FQDN of a mail address" and, as such, mail servers would reject emails to addresses with dotless domains), and will throw an error in tld-extract. You can override this behavior using the allowDotlessTLD option.

  parse("http://notaires.fr")
    >> throws /Invalid TLD/

  parse("http://notaires.fr", {allowDotlessTLD : true}))
    >> { tld : 'notaires.fr', domain : 'notaires.fr', sub : '' }

Why

no dependencies
really fast
full code coverage
easy to read (10 lines)
easily updatable vs mozilla TLDs source list

Maintenance

You can update the remote hash table using npm run update

Not Invented Here

A port of a yks/PHP library
tldextract => bad API, (no need for async, "domain" property is wrong), no need for dependencies
tld => (nothing bad, a bit outdated )
tld.js => no sane way to prove/trust/update TLD listing

Credits

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

License

Determines if the project has defined a license.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

0

Maintained

Determines if the project is "actively maintained".

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Fuzzing

Determines if the project uses fuzzing.

0

Security-Policy

Determines if the project has published a security policy.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

Score

3.4

/10

Last Scanned on 2025-07-07

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More