tldts

n8n community node for parsing URLs and domains using tldts

Package Information

Downloads: 3 weekly / 130 monthly
Latest Version: 1.0.0
Author: erent

Documentation

n8n-nodes-tldts

n8n-nodes-tldts is an n8n community node that exposes the tldts URL/domain parsing library inside n8n workflows.

Use it to extract hostname, public suffix, domain, subdomain, and related parsing information from URLs and hostnames.

n8n is a fair-code licensed workflow automation platform.

Installation

Install the package into your n8n instance according to the community node installation guide.

For a local n8n instance, add the node package and then restart n8n.

Operations

This node supports the following operations:

  • Parse — parse a URL or hostname and return full tldts result data
  • Get Hostname — retrieve only the hostname from a URL or hostname string
  • Get Public Suffix — retrieve the public suffix (effective TLD)
  • Get Domain — retrieve the domain portion of the hostname
  • Get Subdomain — retrieve the subdomain portion of the hostname
  • Get Domain Without Suffix — retrieve domain without its public suffix

Credentials

This node does not require credentials.

Compatibility

This node is compatible with n8n community nodes and depends on the installed tldts package.

Usage

  1. Add the TLDTS node to your workflow.
  2. Choose an operation from the dropdown.
  3. Provide the input URL or hostname.
  4. Adjust optional parsing settings if needed.

Example

Use the Parse operation to extract structured fields from a URL.

{
  "tldts": {
    "hostname": "www.example.com",
    "isIp": false,
    "subdomain": "www",
    "domain": "example.com",
    "publicSuffix": "com",
    "domainWithoutSuffix": "example",
    "isIcann": true,
    "isPrivate": false
  }
}

Recommended workflow

  • Use TLDTS to normalize inputs before performing routing, validation, or domain-based filtering.
  • Use Allow Private Domains when you need support for private/public suffixes such as github.io or blogspot.com.

Resources

Version history

  • 0.1.0 — initial TLDTS community node implementation

Discussion