How to Check If a URL Is Available

Before you build a website, launch a product, or register a domain, one question comes first: is that URL actually available? The answer isn't always straightforward — "available" can mean different things depending on whether you're asking about a domain name, a specific webpage, or a URL path within an existing project. Here's how to think through each scenario clearly.

What "URL Available" Actually Means

The word "available" does a lot of heavy lifting here. It typically refers to one of two distinct situations:

• Domain availability — Is the domain name (like example.com) unregistered and free to purchase?
• URL reachability — Is a specific web address (like example.com/page) currently live, returning a valid response, and not returning a 404 or redirect?

These are separate questions requiring different tools and methods. Mixing them up leads to wasted time.

Checking Domain Name Availability

A domain name is the human-readable address registered through a domain registrar (like Namecheap, GoDaddy, Google Domains, or Cloudflare Registrar). Before you can use a domain, someone has to own it — and if someone else already does, it's unavailable to register.

How to Check Domain Availability

WHOIS lookup is the foundational method. WHOIS is a public protocol that stores registration records for domain names. You can query it through:

• Registrar websites (most have a search bar on their homepage)
• Dedicated WHOIS tools like whois.domaintools.com or lookup.icann.org
• Command-line tools: typing whois example.com in a terminal on macOS or Linux returns raw registration data

A WHOIS result tells you whether a domain is registered, when it was registered, when it expires, and sometimes who owns it (though privacy protection masks many owner details today).

Domain Status Codes to Know

WHOIS results include EPP status codes that indicate a domain's current state:

If a domain shows no WHOIS record at all, it's generally unregistered and available to purchase — though you should still confirm through a registrar's checkout process before assuming.

TLD Variations Matter 🌐

A domain being taken on .com doesn't mean .net, .org, .io, or newer TLDs like .dev or .co are unavailable. Different TLDs are entirely separate registrations. Bulk availability checkers let you search one name across dozens of TLDs simultaneously, which is useful when your preferred .com is gone.

Checking Whether a Specific URL Is Live or Accessible

This is a different task. You're not asking who owns a domain — you're asking whether a particular URL returns a usable response right now.

HTTP Status Codes Are the Core Signal

Every time a browser or server requests a URL, the server returns an HTTP status code. The most relevant ones:

A 200 confirms the URL is live. A 404 means it's not returning content — but it still tells you the domain is reachable.

Tools for Checking URL Status

• Browser address bar — simplest method; the page either loads or it doesn't
• curl (command line):curl -I https://example.com/page returns just the HTTP headers, including the status code — fast and scriptable ⚡
• HTTP status checker tools — web-based tools like httpstatus.io let you paste a URL and see the response code without loading the full page
• Browser developer tools — open the Network tab (F12 in most browsers), load the URL, and inspect the response code directly
• Postman or Insomnia — useful for developers checking API endpoints or URLs requiring headers/authentication

Bulk URL Checking

If you need to check dozens or hundreds of URLs — common in SEO audits, site migrations, or broken link detection — dedicated crawlers like Screaming Frog, Sitebulb, or Ahrefs Site Audit can crawl entire domains and report status codes at scale. This is far more practical than manual checking when dealing with large sites.

Variables That Change How You Approach This

The right method depends heavily on your situation:

• Your technical comfort level — command-line tools like curl or whois are faster and more precise but require familiarity with terminal environments; web-based tools are accessible to anyone
• Scale — checking one URL manually is trivial; checking thousands requires automation or a crawler
• Purpose — buying a domain requires registrar confirmation; auditing a live site for broken links requires HTTP status checking; building a web app may require checking URL path conflicts within your own codebase
• Access requirements — some URLs are behind authentication, paywalls, or geographic restrictions, which means standard availability checks may return misleading results (a 403 doesn't mean the URL doesn't exist)
• Domain expiry monitoring — if you're watching a domain you want to acquire when it drops, tools like expireddomains.net track domains in pendingDelete status

When Results Are Ambiguous

Not every check gives a clean answer. A domain might show as registered but have an expired renewal — meaning it could become available soon. A URL might return 200 but serve a parked page with no real content. A 403 might mean the page exists but is restricted, not that the path is free to use. 🔍

Reading the result in context — who owns the domain, what the page actually returns, whether the site is parked or active — matters as much as the raw status code.

The method that works best comes down to what exactly you're checking, at what scale, and what you plan to do with the result once you have it.