Skip to content
SBMM Cloud
Sign inGet started free

Free Bulk URL Parser

Paste a list of addresses. Get protocol, host, root domain, subdomain, suffix, port, path, query, parameter count and fragment, one row each.

What a run costs
One free run a day, no account needed
How it runs
Straight away
Who it is for
Free: 3 a day. Every paid plan: unlimited.

A free account raises the daily allowance and keeps your results. Create one — no card needed.

Loading…

Overview

Almost every job that starts with a list of addresses starts with parsing them: grouping server-log traffic by root domain, classifying backlinks by suffix, filtering a sitemap extract down to one subdomain, counting the parameters on a campaign's landing pages. This parser does that for a whole list at once and returns a row per address.

Where The Root Domain Comes From

Splitting on dots gets the root domain wrong on every country domain: it turns example.co.uk into co.uk. This tool reads the suffix from an embedded list that covers the common country second-level domains and the common hosting suffixes, so example.co.uk, example.com.pk and example.com.au all come out right. It is not the full Public Suffix List, so every row says whether the suffix was recognised or assumed. A measured answer and a guess do not look the same here.

What Each Column Is

The host is the full server name, blog.example.co.uk. The root domain is the registered part, example.co.uk. The subdomain is what sits on top, blog. The suffix is co.uk. Parameters are counted from the query string, and the fragment is the part after the # that never reaches the server at all. A public run takes the first 200 lines; signed in, the limit is 5,000.

About the tool

What Is The SBMM Domain Separator?

The SBMM Domain Separator is a bulk URL parser. Paste any list of addresses and it returns a row per address split into protocol, full host, root domain, subdomain, public suffix, port, path, query string, query parameter count and fragment.

Parsing is the first step in most work that starts with a list of addresses. Grouping server-log traffic by root domain, classifying backlinks by suffix, slicing a competitor's sitemap down to one subdomain, counting the parameters on a campaign's landing pages, building an internal-link map by folder: every one of them needs the address split before anything else can happen.

The column that is hardest to get right is the root domain. Splitting a host on dots turns example.co.uk into co.uk, and that single error runs through everything downstream. This tool reads the suffix from an embedded list of the common country second-level domains and hosting suffixes, and it marks every row where it fell back to assuming the last label. A measured answer and a guess do not look the same here.

Step by step

How To Use This Tool In 3 Steps

  1. Paste Your Addresses

    One per line, from a backlink export, a server log, a sitemap extract or a scrape. An address written without its protocol is accepted and read as https.

  2. Every Address Is Split

    Protocol, host, root domain, subdomain, suffix, port, path, query, parameter count and fragment, using the suffix list rather than a split on dots, so a country domain comes out with the right root.

  3. Read The Table

    A row per address, plus the count of unique root domains across the whole list and the lines that were not addresses at all. Rows with an assumed suffix are marked.

Why this tool

Why Use This Tool

  • Ten Columns From Every Address

    Protocol, host, root domain, subdomain, suffix, port, path, query string, parameter count and fragment, each in its own column so you can group or filter on any of them.

  • Country Suffixes Read, Not Guessed

    example.co.uk, example.com.pk, example.com.au and example.co.in all return the right root domain, because the suffix is read from a list. This is the case a split on dots gets wrong every time.

  • It Says When It Assumed

    The embedded list covers the common suffixes, not all nine thousand entries of the Public Suffix List. Any row where the suffix was assumed rather than recognised is marked, so nobody reads a guess as a fact.

  • Multi-Label Subdomains Kept Whole

    analytics.a.b.example.com comes back with the subdomain analytics.a.b and the root domain example.com. The subdomain column keeps every label rather than only the first.

  • Lines That Are Not Addresses Are Listed

    They appear on their own, not as an empty row in the middle of the table, so a bad paste is visible rather than quietly dropped.

  • One Free Run A Day

    One run a day without an account, on the first 200 lines. A free account gives three runs a day of this tool and raises the list to 5,000 lines.

FAQ

Frequently Asked Questions

What is the difference between the host and the root domain?

The host is the whole server name in the address: blog.example.co.uk. The root domain is the registered part: example.co.uk. The subdomain is what sits on top of it: blog. The split is only hard because of the suffix, which is co.uk here rather than uk.

What is a public suffix?

The part of a host that anybody can register under, but nobody owns as a whole. com is one, co.uk is one, and so is github.io. The registrable domain is the suffix plus one label, which is why knowing the suffix is what decides the root domain.

Which suffixes does it know?

The common country second-level domains (co.uk, com.pk, com.au, co.in, co.jp and the rest) and the common hosting suffixes (github.io, pages.dev, vercel.app, myshopify.com and others). It is not the full Public Suffix List, which runs to thousands of rules and changes monthly, so a row that fell outside the list is marked as assumed rather than presented as known.

Why use a bulk parser instead of a formula?

Because the formula is the thing that gets the country domains wrong. Grouping traffic by root domain, classifying links by suffix and filtering a sitemap extract by subdomain all depend on the same split, and one wrong rule runs through the whole analysis. Clean the list first with the URL Editor and parse it here.

Does it handle subdomains with several labels?

Yes. analytics.a.b.example.com is parsed with analytics.a.b as the subdomain and example.com as the root domain. Nested subdomains are common on large sites, and the whole prefix is kept.

What about an address with an IP or a port?

Both are read. An IPv4 or IPv6 host is reported as the host, and a non-standard port appears in its own column rather than being folded into the host.

What is a fragment?

The part after the # character. It points at a place inside the page and is never sent to the server, so it has no effect on ranking, but it matters for analytics and for deep links. It gets its own column.

How are query parameters counted?

The query string is read as name and value pairs and each one counts as a parameter, including a bare flag with no value. The count is its own column so an address with an unusually long parameter train stands out at a glance.