Buying a domain on the secondary market — meaning a name someone already owns — feels different from registering an available one at a registrar. Here’s the path, end to end.
\nUse the marketplace search to look for keywords + TLDs that match your project. Filter by max price and length to surface what’s actually in your budget. Save the ones you like with the heart button — saved domains trigger a price-drop alert if the seller lowers their asking price later, plus an auction-start alert if the name moves to auction.
\nThe biggest negotiation mistake first-time buyers make is starting a conversation without knowing their walk-away number. A clear ceiling protects you from creeping upward in $500 increments over a week of polite back-and-forth.
\nLook at the seller’s min_offer_usd — that’s the floor they’ve published. A reasonable opening offer is typically 30-60% of asking, depending on how priced-up the listing looks. Lowballs (under 20%) tend to be ignored.
Three paths, and they’re not interchangeable:
\nOnce a price is agreed, the marketplace mints a one-time escrow.com checkout link. Pay through that link. Don’t send funds directly to the seller, don’t accept a private payment instruction in chat — both bypass the protection you’re paying the marketplace to provide.
\nEscrow holds the money until the seller actually transfers the domain into your registrar account. If the seller doesn’t deliver, you get refunded in full.
\nTwo paths, and the marketplace usually picks the faster one automatically:
\nOnce the domain shows up in your account, accept the delivery in escrow. Funds release to the seller, and the name is yours.
\nIf the seller stops responding mid-transfer, escrow has a defined delivery window — open a dispute and you get the refund. If chat communication breaks down on a contested issue (which TLD pricing tier? who pays push fees?), marketplace support can intervene. Don’t go off-platform to resolve disputes — once you do, you’ve lost the audit trail you’d need to defend your position.
", "date_published": "2026-05-06T15:53:12.830594+00:00", "date_modified": "2026-05-06T15:53:12.863504+00:00", "authors": [{"name": "The Deepnom Desk"}], "tags": ["Buying Guides"]}, {"id": "https://deepnom.com/blog/buying-a-domain-via-escrow-what-to-expect/", "url": "https://deepnom.com/blog/buying-a-domain-via-escrow-what-to-expect/", "title": "Buying a domain via escrow: what to expect from start to finish", "summary": "Escrow is the backbone of safe domain purchases. Here's the full timeline, the fees, and the failure modes — so nothing surprises you.", "content_html": "Every meaningful domain transaction goes through escrow. If you’ve never used it, here’s what actually happens.
\nDomains are intangible. There’s no truck delivering them, no warehouse to inspect. Without escrow, one party always takes risk: the buyer wires money first (and the seller could vanish), or the seller transfers first (and the buyer could vanish).
\nEscrow inverts that. The buyer pays into the escrow’s account; the seller transfers the domain; the buyer verifies receipt; only then are funds released.
\nDay 0 — Agreement. Buyer accepts the seller’s price (or the seller accepts the buyer’s offer). The marketplace mints an escrow.com checkout link with the agreed amount + fee split.
\nDay 0-5 — Buyer payment. The buyer logs in to escrow, picks a payment method, and funds the transaction. Credit card clears in minutes; wire transfer takes 1-3 business days; PayPal varies.
\nDay 1-7 — Domain transfer. With funds confirmed, escrow notifies the seller to begin the transfer. A push transfer between accounts at the same registrar takes minutes; an inter-registrar transfer takes 5-7 days because of ICANN’s mandatory wait.
\nDay +1 — Buyer inspection. Once the domain shows up in the buyer’s registrar account, escrow notifies the buyer to verify. Default inspection windows are typically 1-3 business days. The buyer either accepts or disputes.
\nSame day — Funds release. If accepted (or if the inspection window passes silently), escrow releases funds to the seller minus fees.
\nEscrow charges a percentage that scales down with transaction size. As a rough guide for 2026:
\nThe marketplace itself adds a separate commission. Both are deducted from the buyer’s payment before the seller’s net hits their bank — you’ll see the full split on the offer breakdown before you click pay.
\nBuyer doesn’t fund. Common in auctions when the winner regrets the bid. Seller waits a few days, escrow times out, the listing reopens. Some marketplaces (including Deepnom) issue strikes against repeat non-paying bidders.
\nSeller doesn’t transfer. Buyer disputes inside the delivery window; escrow refunds in full. The seller’s marketplace reputation takes a hit.
\nBuyer doesn’t accept. The buyer goes silent after delivery. Inspection window expires; escrow auto-releases to the seller.
\nGenuine dispute. Rare, but happens — usually around exactly what was being sold (a domain plus a website? plus social handles?). Escrow has a documented dispute process with concierge involvement.
\nIf you’re sitting on a domain you don’t use anymore — or one you registered with selling in mind — here’s how to actually move it.
\nBefore a marketplace will list your domain, it needs proof you control it. Two paths:
\nPick TXT if you’re listing one or two; nameserver if you’re running a portfolio and want every name to show a sales landing page automatically.
\nThree pricing modes:
\nmin_offer_usd floor; buyers submit; you accept, counter, or reject. Best for one-of-a-kind names where comp data is thin.Don’t overthink the first listing. A make-offer with a reasonable floor will tell you within a few weeks whether your asking price was anywhere near reality.
\nThe SEO description (1-2 sentences explaining what the domain is good for) is load-bearing for two reasons. AI search engines + Google index it for discovery. And buyers scanning the marketplace card decide in 2-3 seconds whether to click through.
\nBad: “Premium domain available for serious buyers.”\nGood: “Short, brandable .com for fintech or crypto wallet products. 8 letters, dictionary-word readable, no hyphens.”
\nBe specific. Say what kind of business would want it. Ambiguity makes buyers drop off.
\nWhen a sale closes, you get a notification. The buyer pays into escrow.com. You initiate the transfer:
\nOnce the buyer confirms receipt, escrow releases your funds (minus the marketplace + escrow fees). Standard payout windows are 24-72 hours after release.
\nSellers often default to whatever pricing mode the marketplace presents first. That’s a mistake — the right mode depends on the domain’s category, your timeline, and your tolerance for negotiation.
\nFixed price. Pay it, get the domain, no conversation.
\nUse BIN when:
\nDon’t use BIN when:
\nNo published price. Buyers submit; you respond. The marketplace enforces a min_offer_usd floor so trash lowballs are auto-rejected.
Use make-offer when:
\nDon’t use make-offer when:
\nTimed bidding with anti-snipe extension. Public bid history visible to all bidders.
\nUse auction when:
\nDon’t use auction when:
\nAsk yourself, in order:
\nMost portfolios end up with a mix — BIN on the well-comped names, make-offer on the long tail, occasional auctions for the showpieces.
", "date_published": "2026-05-06T12:53:12.830594+00:00", "date_modified": "2026-05-06T15:53:12.892317+00:00", "authors": [{"name": "The Deepnom Desk"}], "tags": ["Selling & Listing"]}, {"id": "https://deepnom.com/blog/how-much-is-a-domain-worth/", "url": "https://deepnom.com/blog/how-much-is-a-domain-worth/", "title": "How much is a domain worth? A practical valuation framework", "summary": "Domain pricing isn't mystery — it's a few measurable variables plus brand fit. Here's a working framework.", "content_html": "Every week someone asks: “how much is my domain worth?” The honest answer is “the most a real buyer will actually pay” — but that’s not useful for pricing. Here’s a framework that actually is.
\nLength. Shorter is more valuable. The market values single-character domains in seven figures, 2-letter at $50K-$1M+, 3-letter at $5K-$50K, 4-letter at $500-$10K. Past 6-7 characters, length stops mattering and brand becomes the driver.
\nTLD. .com still anchors valuation — the rest of the world prices off of it. .ai commands premium for AI-fit names. .io for developer/infra. ccTLDs (.de, .fr, .co.uk) trade at significant discounts to the matching .com but carry strong local-SEO value in their target country.
\nBrandability. A made-up word that sounds plausible (“Strapi”, “Notion”) prices higher than a typo of an existing word. A dictionary word in a clear commercial category (“insurance”, “hotels”) prices higher than the same word in a niche category (“baking”, “weaving”).
\nSearch demand. Google Keyword Planner, Ahrefs, Semrush — if a meaningful number of people search the domain name as a query, that’s measurable demand. Names with built-in search traffic price 2-5× similar names without it.
\nAll four base variables get multiplied (sometimes by 10×, sometimes by 0.1×) by buyer fit.
\nA 4-letter .com appraised at $3K from comps can sell to the right buyer for $30K — if the buyer’s brand exactly matches the letters. The same domain sells to a generic buyer for $3K.
\nThis is why marketplace appraisals are statistical: they predict the median sale, not the right-buyer sale. The spread between the two can be 10×.
\nNameBio is the public industry archive — every reported domain sale, searchable by length / TLD / pattern. Filter by recent dates (last 24 months) and matching characteristics. Two-thirds of NameBio’s data comes from wholesale (investor-to-investor) sales, so those numbers are floors, not ceilings.
\nDNJournal publishes a weekly verified-sales list with prices that skew higher (more end-user retail). Deepnom’s intel module ingests both.
\nRecent end-user sales in your category matter most. A $5,000 SaaS-named .com sale six months ago is more predictive for your similar SaaS-named .com than a $50,000 e-commerce sale a year ago.
\nmin_offer_usd set at your floor and BIN at the high end of your retail range.NameBio has logged hundreds of thousands of domain sales. It’s the closest thing the industry has to objective comparable-sales data — but raw NameBio numbers, used naively, will mislead you. Here’s how to filter them.
\nEvery reported public sale: domain, price, date, marketplace. Going back to 2003. Filterable by length, TLD, characters, sale price band, year.
\nWhat’s NOT in the data: private off-market sales, broker-mediated transactions where the buyer requested confidentiality (most $100K+ deals), and sales reported later than the original transaction date.
\nThis is the single most important filter to apply.
\nWholesale sales happen on auction platforms (GoDaddy auctions, NameJet, SnapNames, DropCatch) and are mostly investor-to-investor. They reflect what the trade values a name at as a portfolio holding, not what an end-user would pay.
\nRetail sales happen on premium-listing marketplaces (Sedo, Afternic, brokered deals) and are mostly end-user purchases. The same name typically sells for 5-25× wholesale at retail.
\nWhen pricing a name to sell to an end-user, filter NameBio to retail sources only — otherwise you’ll anchor your asking price 10× too low.
\nA 4-letter .com sale from 2014 tells you nothing about 2026 prices. The .com market has shifted multiple times in the past decade. Filter to the last 24-36 months for any active pricing decision.
\nOlder sales matter for pattern analysis (“is the 4L .com market trending up or down?”) but not for setting your ask.
\nYou’re looking for comps that match your domain on at least two of: length, TLD, semantic category, and letter pattern.
\nA pure length+TLD match (any 5L .com) is a weak comp. A length+TLD+pattern match (any 5L .com starting with a vowel and ending in a consonant cluster) is stronger. A length+TLD+category match (any 5L .com in fintech branding) is strongest of all because it’s predicting the same buyer pool you’re selling into.
\nDrop the top 10% and bottom 10% of your comp set before computing a median. The top 10% are usually buyer-fit outliers (the company that needed exactly that name); the bottom 10% are usually distress sales or misreported amounts. The middle 80% reflects the actual market.
\nYou own flux.io. You want to price it.
Step 1: Filter NameBio to .io sales, 4 characters, last 24 months. You get ~80 results.
\nStep 2: Filter further to retail sources (drop wholesale auctions). You’re down to ~25.
\nStep 3: Drop the top 3 and bottom 3 (outliers). 19 comps remain.
\nStep 4: Median of the 19. Let’s say it’s $4,200.
\nStep 5: That’s your retail floor. End-user asking should be 2-3× ($8K-$12K). Make-offer with min_offer_usd at $3,500-$4,000.
Step 6: If the buyer is clearly using the name as their primary brand (clear buyer fit), the upper range can stretch to $25-$50K. That’s the right-buyer multiplier — but you can’t price based on a buyer you don’t have yet.
", "date_published": "2026-05-06T10:53:12.830594+00:00", "date_modified": "2026-05-06T15:53:12.916554+00:00", "authors": [{"name": "The Deepnom Desk"}], "tags": ["Valuation & Appraisal"]}, {"id": "https://deepnom.com/blog/why-ai-domains-command-premium-prices/", "url": "https://deepnom.com/blog/why-ai-domains-command-premium-prices/", "title": "Why .ai domains command premium prices in 2026", "summary": "The .ai TLD has gone from obscure ccTLD to the default extension for AI startups. Here's what's driving the prices and where they're heading.", "content_html": ".ai is technically the country-code TLD for Anguilla, a tiny British Overseas Territory in the Caribbean. In 2024 the registry generated more revenue from .ai sales than the entire rest of Anguilla’s economy. Here’s how that happened and what it means for prices.
\n.ai went from $80-$100/year retail in 2022 to a clear premium tier in 2024-2025. After-market prices for category-defining .ai names rose 5-20× in the same window.
\nThree drivers:
\nThe AI hype cycle made the TLD obviously thematic. Every funded AI startup in 2023-2024 wanted the matching .ai. When dictionary words like wisdom.ai or thread.ai entered the after-market, bidding wars followed.
Supply is genuinely constrained. Unlike new gTLDs with millions of unregistered combinations, .ai has been actively used since 1995. The good short names were taken long before the hype.
\nEnd-user buyers have AI-scale budgets. A funded AI company with a $30M Series A treats a $200K domain purchase the way a 2010 SaaS company treated a $20K purchase — material but not survival-defining.
\nRough 2026 ranges:
\nchat.ai, agent.ai, learn.ai — names a major AI product would build around.The Anguilla nexus question. Some buyers worry about registry policy stability — Anguilla’s political situation is being watched. The registry transitioned operators in 2024-2025 with policy questions still open. Most investors are pricing this as background risk, not active concern.
\nRenewal costs are higher. Standard .ai retail is $60-$100/year (vs ~$10 for .com). Premium tiers can renew at thousands per year. Investors pricing inventory factor annual carry into multi-year hold strategies.
\nPredictions are guesses, but the structural picture is this: as long as the AI sector keeps generating funded startups with brand-name budgets, the .ai after-market stays elevated. A pullback in AI funding would compress the right-buyer multipliers significantly — base wholesale would survive but the spectacular end-user sales would thin out.
\nIf you’re buying .ai today as an investor: stick to names with multiple plausible end-users. A name that only fits one specific company is bet-the-house concentration. A name that 5-10 different AI companies could brand around is diversified buyer pool.
\nIf you’re buying .ai today as an end-user: it’s not too late. The premium is real but the alternative ($150K+ for a comparable .com) is also real. Run the math against what your brand is worth.
", "date_published": "2026-05-06T09:53:12.830594+00:00", "date_modified": "2026-05-06T15:53:12.923723+00:00", "authors": [{"name": "The Deepnom Desk"}], "tags": ["Market Analysis"]}, {"id": "https://deepnom.com/blog/aged-domains-what-aged-authority-means/", "url": "https://deepnom.com/blog/aged-domains-what-aged-authority-means/", "title": "Aged domains: what 'aged authority' actually means and when it matters", "summary": "\"Aged\" domains carry a real premium — but the value depends on what kind of age, what's been on the domain, and what you plan to use it for.", "content_html": "An “aged” domain — registered 10, 15, 20+ years ago — trades at a real premium over a freshly-registered name in the same category. The premium is justified, but only for specific use cases. Here’s how to evaluate it.
\nSearch engine trust signal. Google’s algorithm treats older domains as more established. Newly-registered domains face a mild “sandbox” effect — fresh content on a fresh domain ranks more slowly than the same content on an aged one.
\nBacklink history. A 15-year-old domain has typically accumulated inbound links over its life. Even broken or abandoned, those links retain SEO weight when redirected or repurposed.
\nBrand legitimacy by association. A B2B sales call lands differently when the prospect sees a 1998-registered domain vs a 2024 one. Age is shorthand for “this is a real business.”
\nThree patterns degrade an aged domain’s value:
\nSpam history. If the domain hosted aggressive SEO spam, PBN content, or malware at some point, search engines may have penalized it. Wayback Machine + Ahrefs/Majestic history checks reveal this. Aged-but-penalized domains are worth less than fresh names.
\nOwnership churn. A domain that changed hands every 2-3 years carries less SEO weight than one with stable ownership. WHOIS history (DomainTools, etc.) shows the transitions.
\nOff-topic prior content. A domain that hosted a fitness blog for 10 years and now redirects to a fintech product gets little SEO credit for the age — the topical drift dilutes accumulated authority.
\nThree free tools, in order:
\nWayback Machine (web.archive.org). Look at snapshots every 2 years. What was on the domain? Stable topic or topic drift? Spam-era pages? Ad-farm parking?
\nWHOIS history (DomainTools or similar paid). How many ownership changes? Dates? Registrars used?
\nBacklink check (Ahrefs, Majestic, or free domain rating tools). Domain Rating + referring domain count + spam score. A 20-year-old domain with DR 0 and 5 referring domains has had no real activity — the age premium for that one is small.
\nPay it when:
\nDon’t pay it when:
\nOn Deepnom, domains 15+ years old are auto-flagged with the Elite badge — the same tier as 1-4 letter premiums. Filter the marketplace by Elite to see verified-aged inventory.
", "date_published": "2026-05-06T08:53:12.830594+00:00", "date_modified": "2026-05-06T15:53:12.931697+00:00", "authors": [{"name": "The Deepnom Desk"}], "tags": ["Market Analysis"]}, {"id": "https://deepnom.com/blog/how-gdpr-changed-whois-forever/", "url": "https://deepnom.com/blog/how-gdpr-changed-whois-forever/", "title": "How GDPR changed WHOIS forever (and why it still matters)", "summary": "Since 2018, public WHOIS records hide registrant details by default. Here's what changed, what's still public, and how to access redacted data legitimately.", "content_html": "Before 2018, WHOIS lookups returned every domain registrant’s name, address, email, and phone number publicly. After GDPR, that became illegal in Europe. ICANN responded with a global redaction policy that still shapes domain due diligence today.
\nICANN’s Temporary Specification (later codified) required registrars worldwide to:
\nThe redaction is global, not just for EU registrants. The compliance cost of running two parallel systems would have been enormous, so registrars defaulted everyone to redacted.
\nThese five give you enough to verify the domain is genuinely registered, see how long it’s been around, and know which registrar to contact for transfer.
\nICANN runs the Registration Data Request Service (RDRS) — a centralized portal for legitimate disclosure requests. You submit your request explaining the basis (IP infringement, fraud investigation, legal process) and the registrar reviews + decides.
\nApproval rates vary widely by registrar. Cloudflare and the privacy-focused providers approve sparingly; the larger commercial registrars (GoDaddy, Network Solutions) tend to be more responsive.
\nBuying due diligence is harder. You can’t directly see who owns a domain you’re considering buying. Reverse-WHOIS tools (the kind that find every domain a person owns) have lost most of their utility.
\nTrademark enforcement is slower. UDRP filings are still possible, but identifying the right respondent now requires going through the registrar — adding days to every dispute.
\nPrivacy services have collapsed in importance. Before 2018, paid WHOIS privacy was a $5-15/year add-on at most registrars. Today it’s redundant for most use cases — the default is already private.
\nSome TLDs and registrars still expose more data:
\nWhen something happens to your domain — a transfer blocked, a price hike, a policy change — knowing which layer of the DNS hierarchy is responsible saves you from calling the wrong support line. Here’s the structure.
\nInternet Corporation for Assigned Names and Numbers — a California nonprofit that coordinates global DNS.
\nWhat ICANN does:
\nWhat ICANN doesn’t do:
\nYou almost never interact with ICANN directly. Their policies cascade down to the registries and registrars who do the actual work.
\nA registry operates a single TLD’s authoritative database. Verisign runs .com and .net. Public Interest Registry runs .org. Identity Digital runs .io plus a portfolio of new gTLDs. Google Registry runs .dev and .app. And so on.
\nWhat registries do:
\nRegistries are wholesale, not retail. You can’t register a domain directly at Verisign — you have to go through a registrar.
\nRegistry policies override registrar policies. If Identity Digital’s .ai registry refuses a transfer pending a compliance review, no registrar can override that. Push for the registrar’s help, but understand the ceiling.
\nA registrar is the customer-facing storefront. Cloudflare, Porkbun, Namecheap, GoDaddy, Hover. There are thousands of them — anyone with an ICANN accreditation + registry contracts.
\nWhat registrars do:
\nThis is where you have the most leverage. Bad customer service? Move registrars. Pricing creep? Move registrars. The transfer process is standardized exactly to make registrar competition possible.
\nDomain expired and is in redemption? Registrar can recover it (for a fee). Registry can’t help — they follow the policy ICANN set.
\nRegistry hiked premium tier renewal prices? Registrar can’t override — they pass through what the registry charges them. Talk to the registry through whatever advocacy channel exists (often: a long uphill fight).
\nTrademark dispute filed against your domain? ICANN’s UDRP process plus the chosen arbitration provider (WIPO, Forum). Registrar implements the result; doesn’t decide it.
\nWHOIS shows wrong info? Update at your registrar. Changes propagate to the registry within hours.
\nIf something is wrong with your domain, ask first which layer the problem lives at. You’ll save yourself hours of polite-but-helpless conversation with the wrong support team.
", "date_published": "2026-05-06T06:53:12.830594+00:00", "date_modified": "2026-05-06T15:53:12.950372+00:00", "authors": [{"name": "The Deepnom Desk"}], "tags": ["Industry News"]}, {"id": "https://deepnom.com/blog/domain-anatomy-101-tlds-subdomains-dns/", "url": "https://deepnom.com/blog/domain-anatomy-101-tlds-subdomains-dns/", "title": "Domain anatomy 101: TLDs, subdomains, DNS, and what each piece does", "summary": "Every domain has the same architecture — TLD, second level, optional subdomain, DNS records — and understanding the parts makes everything else easier.", "content_html": "If you’ve registered a domain but never thought through what each piece is actually called, this is for you. Knowing the vocabulary makes every other domain decision much easier.
\nTake mail.example.com and read it right to left:
com is the top-level domain (TLD). The rightmost component, after the final dot.example is the second-level domain (SLD). What you actually “own” — what you registered at the registrar.mail is a subdomain (also called a third-level domain). Created by you in your DNS settings; the registry has nothing to do with subdomains.The full string mail.example.com is the fully qualified domain name (FQDN).
Generic TLDs (gTLDs): .com, .net, .org from 1985, plus the hundreds of new gTLDs added since 2014 (.app, .dev, .xyz, .blog, .shop, etc.).
\nSponsored TLDs (sTLDs): .edu, .gov, .mil, .museum — restricted to specific communities with eligibility verification.
\nCountry-code TLDs (ccTLDs): .us, .uk, .de, .fr — tied to a specific country. Some require local presence (.ca, .br); others are open globally (.io, .me, .tv) and get used as quasi-gTLDs.
\nWhen you “register a domain” you’re buying the right to use a specific second-level domain (SLD) under a specific TLD for a specific term (1-10 years).
\nYou’re not buying it forever. You’re paying an annual fee (or 10-year prepay) for exclusive registration. Stop paying and the domain returns to the public pool.
\nSubdomains are unlimited and free — you can create as many as you want under your registered SLD without paying more.
\nWhen someone types example.com into a browser, the Domain Name System resolves the name into the IP address of the server that should respond.
That happens through DNS records you configure at your registrar (or at a separate DNS provider like Cloudflare, AWS Route 53, or DNSimple). The most common record types:
\nThese get confused constantly.
\nNameservers are the servers that hold your DNS records. Specified at the registrar level (“this domain is managed by ns1.cloudflare.com and ns2.cloudflare.com”).
DNS records are the actual entries that live on those nameservers (“the A record for example.com points at 192.0.2.10”).
\nChange the nameservers and you switch which provider manages your DNS — but your records have to be re-created on the new provider.
\nMost domain confusion comes from not knowing which layer owns the problem. If your website is unreachable, you need to figure out: is the registration current? Are the nameservers correct? Are the DNS records correct? Is the server actually running?
\nKnowing the vocabulary lets you check each layer in order and find the failure fast.
", "date_published": "2026-05-06T05:53:12.830594+00:00", "date_modified": "2026-05-06T15:53:12.959908+00:00", "authors": [{"name": "The Deepnom Desk"}], "tags": ["Domain Education"]}, {"id": "https://deepnom.com/blog/avoiding-trademark-trouble-domain-investor-checklist/", "url": "https://deepnom.com/blog/avoiding-trademark-trouble-domain-investor-checklist/", "title": "Avoiding trademark trouble: a domain investor's defensive checklist", "summary": "UDRP losses cost time, money, and reputation. A few minutes of trademark checking before you register saves all three.", "content_html": "Most experienced domain investors lose at least one UDRP case in their career. Most of those losses are avoidable. Here’s the discipline that keeps you out of the cases you shouldn’t lose.
\nUnder ICANN’s Uniform Domain-Name Dispute-Resolution Policy:
\nAll three. A domain that matches a trademark but was registered years before the trademark existed isn’t bad faith. A trademark match where you have a legitimate use (your own product, fan site, criticism site) satisfies the second prong.
\nBut: registering microsoft-cloud.com to sell to Microsoft, with no legitimate use, fails all three.
Before you register a name with any commercial value:
\n1. USPTO + EUIPO trademark search. Free, fast. Search for the domain’s text. If a registered trademark exists in a category that overlaps with how you’d use the domain, slow down.
\n2. WIPO Global Brand Database. Catches international trademarks the USPTO won’t show. Same drill.
\n3. Plain Google search. Forget databases — what comes up when someone Googles the name? If it’s an obvious existing brand (even an unregistered one), the UDRP panel will know that.
\n4. UDRP precedent. Search WIPO’s UDRP decisions database for the trademark. If it’s litigious (constantly filing UDRPs), you’re a probable next target.
\nPharma + medical. Brand owners are aggressive UDRP filers. “Sounds-like” matches lose constantly.
\nMajor tech. Microsoft, Apple, Google, Amazon, Meta all run dedicated brand-protection programs. Match anything close and expect a UDRP within months.
\nBanks + insurance. Regulators care + brand owners have lawyers.
\nSports + entertainment IP. “Olympics”, “FIFA”, Disney characters — protected aggressively.
\nIf you get a UDRP complaint or a cease-and-desist:
\n1. Document your prior use. When did you register? What did you do with the domain? Wayback Machine snapshots, sale-listing dates, any plausible business plan.
\n2. Show the trademark didn’t exist (or wasn’t well-known) when you registered. Trademark filing dates are public. If you registered in 2010 and the trademark was filed in 2018, that’s a strong defense.
\n3. Show legitimate non-competing use. A fan site, a fictional product, a parody — any of these can satisfy the legitimate-interest prong.
\n4. Consider settling. If you have no real use for the domain and you’ll lose UDRP anyway, sometimes a polite transfer for cost is faster + cheaper than fighting. UDRP defense costs are rarely zero.
\nSometimes trademark holders file UDRP complaints knowing their case has no merit, hoping the registrant will give up. The panel can declare reverse domain hijacking (RDNH) in the decision text — putting the complainant on record as having abused the process.
\nRDNH findings hurt the complainant’s reputation and can be cited in future disputes. If you’re confident your registration is legitimate, fight.
", "date_published": "2026-05-06T04:53:12.830594+00:00", "date_modified": "2026-05-06T15:53:12.970929+00:00", "authors": [{"name": "The Deepnom Desk"}], "tags": ["Domain Education"]}, {"id": "https://deepnom.com/blog/domain-transfer-after-offer-accepted/", "url": "https://deepnom.com/blog/domain-transfer-after-offer-accepted/", "title": "What happens after you accept an offer: the domain transfer playbook", "summary": "A clear walkthrough of the post-acceptance transfer — auth codes, registrar pushes, escrow inspection periods, and the small mistakes that delay a clean handover by days.", "content_html": "The offer is accepted. The number is final. Now what?
\nFor most buyers and sellers, the window between “we agreed” and “the domain is in its new account” is the part of the deal they understand least. It’s also the part where deals go sideways most often — not through bad faith, but through small mistakes in a process neither side does very often.
\nThis is a plain-English walkthrough of what happens, who does what, and how to avoid the common snags.
\nFrom the moment both parties say yes, a normal domain transfer follows the same five-stage structure:
\nTotal elapsed time for a smooth deal: 2-5 business days. Deals that hit snags can drag to 2-3 weeks.
\nThere are two mechanically different ways to move a domain between accounts, and they have very different characteristics.
\nRegistrar push (same-registrar). If buyer and seller both have accounts at the same registrar (both at GoDaddy, both at Namecheap, both at Dynadot, etc.), the seller can “push” the domain directly to the buyer’s account. The domain never leaves the registrar; it just changes ownership within their system. This is fast — often minutes — and has very few failure points.
\nRegistrar-to-registrar transfer. If the two parties are at different registrars, the seller unlocks the domain and releases an authorization code (sometimes called an EPP code, transfer code, or auth key). The buyer initiates a transfer at their registrar using the code; their registrar contacts the losing registrar; the losing registrar confirms with the seller. The whole dance takes 5-7 days by ICANN rules, though it can be sped up in some cases.
\nWhen practical, a push is the preferred route. If the seller is at, say, GoDaddy and the buyer isn’t, it’s often worth the buyer opening a GoDaddy account specifically to receive the push, then initiating a transfer to their preferred registrar a few weeks later. A same-registrar push eliminates most of the common transfer failures.
\nOne surprise for many first-time domain buyers: ICANN rules lock a domain from outbound transfer for 60 days after any change of registrant (owner). If a seller recently acquired the domain, or recently updated the WHOIS, the domain may not be transferable for up to 60 days.
\nThis lock doesn’t prevent a same-registrar push — those still work. But it does prevent a registrar-to-registrar transfer. If the buyer wants the domain at a specific registrar and the seller is at a different one, the 60-day lock can force either:
\nAsk about this early. A seller who recently acquired the name or changed WHOIS should flag it during negotiation, not during the transfer. It’s not a dealbreaker, but it’s a scheduling constraint worth knowing about.
\nFor registrar-to-registrar transfers, the auth code is the key that unlocks the domain at its current registrar so it can move. It’s a 12-32 character string, sometimes containing special characters.
\nThe discipline around the auth code:
\nOnce the transfer completes, the buyer has a window — typically 1-3 days on domain escrow — to verify that what they got matches what was promised. In practice, this means:
\nIf everything checks out, the buyer accepts the milestone and escrow releases funds. If they don’t, this is the window to raise it. Silence during inspection typically counts as acceptance — the funds release automatically when the timer runs out.
\nA short catalog of what goes wrong in transfers, ranked by how often I see them:
\nAuth code rejected. Usually a copy-paste issue with special characters. Ask the seller to resend the code in a plain-text format, not inside a formatted email.
\nDomain not unlocked. Sellers sometimes forget to disable the transfer lock before releasing the auth code. The buyer’s transfer attempt will fail with a generic error until the seller toggles the lock off.
\nWHOIS privacy blocking confirmations. Some registrars send the transfer confirmation to the email on the WHOIS record, not the registrar account. If the domain has WHOIS privacy enabled, the confirmation email bounces off a forwarding service that may be slow or broken. Disabling WHOIS privacy for the duration of the transfer is the fix.
\nBuyer account not verified. Some registrars require email or phone verification before they’ll accept a transfer. Buyers who open a new account specifically to receive a domain sometimes miss this step and stall the inbound transfer.
\nThe 60-day lock surprise. Covered above. Easy to miss if the seller doesn’t mention it.
\nRegistrar of record dispute. Rare, but occasionally two parties think they have authority to approve a transfer (e.g., an agency that managed a domain on behalf of a client and still has admin access). Sort this out before escrow, not during.
\nFor a clean transfer, the sequence from both sides:
\nBuyer:\n1. Confirms the price and agrees to terms.\n2. Opens escrow (usually the marketplace does this automatically).\n3. Wires funds to escrow. Confirms receipt.\n4. If same-registrar push: provides their account identifier (username, account number) to the seller.\n5. If registrar-to-registrar transfer: receives auth code via escrow, initiates transfer at their registrar, approves confirmation emails.\n6. Verifies ownership of the domain.\n7. Accepts the inspection milestone.
\nSeller:\n1. Confirms the price.\n2. Waits for escrow funding confirmation.\n3. If same-registrar push: executes the push to the buyer’s account.\n4. If transfer: disables transfer lock, retrieves auth code, shares via escrow.\n5. Responds to any registrar confirmation requests.\n6. Waits for escrow release.
\nThat’s really the whole thing. Clean transfers are boring. The pattern is the same every time; the mistakes are always one of a small handful.
\nWhen an offer is accepted on Deepnom, the system automatically opens an escrow transaction at Escrow.com with the agreed price, both email addresses, and the domain name. From there, Escrow.com runs the milestones — funding, transfer, inspection, release — and notifies both parties at each stage.
\nThe chat room stays open throughout. If either party has a question mid-transfer (“which auth code format does your registrar want,” “did you get the verification email”), the conversation continues in one place instead of spawning new email threads.
\nIf something stalls, Deepnom support can see the escrow status and help unstick it. But the money and the domain never pass through us — the funds live at Escrow.com, the domain lives at the registrars, and Deepnom coordinates the messages and the paperwork.
\nA domain transfer is not a complicated process, but it’s an unfamiliar one, and unfamiliarity is what creates the small mistakes that turn a 3-day handover into a 2-week slog. Knowing the shape of the thing — push vs transfer, auth code discipline, the 60-day lock, the inspection period — is 80% of what makes it go smoothly.
\nIf you’re buying or selling for the first time, read this once before the deal starts. You’ll recognize the moves as they happen, spot the snags early, and close on schedule.
", "date_published": "2026-04-18T09:20:30.504349+00:00", "date_modified": "2026-04-20T05:27:32.678904+00:00", "authors": [{"name": "The Deepnom Desk"}], "tags": ["Domain Education"], "image": "https://deepnom.com/media/blog/1000061416.jpg"}, {"id": "https://deepnom.com/blog/how-to-negotiate-a-domain-purchase/", "url": "https://deepnom.com/blog/how-to-negotiate-a-domain-purchase/", "title": "Negotiating a domain purchase: an offer-strategy guide for buyers", "summary": "How to price your opening offer, read a seller's pushback, and decide when to walk away — with the specific moves that tend to close deals and the ones that blow them up.", "content_html": "Most domain negotiations fail the same way: a buyer sees a listing priced at $15,000, fires in an opening offer of $500, and never hears back. The seller doesn’t counter, doesn’t engage, and the conversation dies in one round.
\nThat’s not because the seller is being difficult. It’s because the opening move signaled to the seller that the buyer isn’t serious — or doesn’t understand the market. A thoughtful opener keeps the door open; a reflexive lowball closes it.
\nThis guide covers the moves that actually move deals forward, and the common mistakes that stall them.
\nA domain listing price is rarely what the seller will accept. It’s also rarely pure fiction. Most experienced sellers price their names 20-50% above their walk-away number. If you can estimate the walk-away number, you can negotiate against a reasonable target instead of against a wall.
\nThree signals that move the estimate:
\nThe most common mistake in domain negotiation is opening with 10-20% of the ask. Sellers have seen that move a thousand times and most won’t respond. The second most common mistake is opening at 90% of the ask, which leaves you no room to move and signals you’ll pay whatever the seller insists on.
\nA reasonable opening offer is usually in the range of 30-50% of the listing price, with two critical modifiers:
\nModifier one: what the comparable sales say. If NameBio shows similar names trading at $3,000-$5,000 and the listing is $15,000, an opening offer of $3,500 is defensible even though it’s 23% of the ask. The number is grounded in data the seller can look up too.
\nModifier two: a real reason. An offer accompanied by “here’s what comparable sales support, and here’s what I can actually pay” closes at twice the rate of a number with no context. Sellers don’t need your life story — they need a signal that you’ve done the work.
\nWhen a seller counters, they’re communicating a lot more than a new number. Read the move carefully:
\nCounter barely lower than the ask (e.g., $15,000 → $13,500). The seller is signaling that the listed price is their target and they won’t move much. Your options: meet them close to their counter, walk, or wait 3-6 months and try again with a stronger comp case.
\nCounter meaningfully lower (e.g., $15,000 → $9,000). The seller is engaging. They’ve revealed a ceiling above their walk-away number. Now you have a negotiating window.
\nCounter with a question. “Is this for a project or a brand you’re launching?” is a seller sizing up your budget. Answer honestly — professional buyers work with other professional buyers. “I’m a bootstrapped founder” is legitimate context; “I’m a VC-backed startup” is too, and both will be priced accordingly.
\nNo counter, flat no. The seller either isn’t serious or you moved too far from their target. Don’t chase. Either sharpen your offer with new context or walk.
\nA few tactics that consistently work:
\nAcknowledge the asymmetry. “I understand your list is $15,000. Based on comps I’ve pulled, my realistic top is around $6,500. I’d rather open honestly than waste your time.” This is disarming. It also flushes out whether the seller wants to engage.
\nOffer a clean close. “I can fund escrow within 48 hours.” For most sellers, speed and certainty are worth 5-10% on the price. Nobody wants to negotiate for two weeks and then watch the deal die at the funding stage.
\nBundle when it helps. If the seller owns multiple domains you might want, ask about the bundle. It’s often cheaper per name and sellers like moving inventory.
\nShare the use case when safe. If you’re buying for a clear, non-speculative use (a product launching next month, rebranding an existing company), saying so builds trust. Don’t share this if you think it will push the price up — but for most buyers, a legitimate use case is a green flag for the seller, not a red one.
\nIn the same spirit, mistakes to avoid:
\nThe surprise change. Agreeing to $7,500, then coming back with “actually I can only do $5,500” is the fastest way to end a negotiation. If you need to move the number, be direct about why — budget changed, partner vetoed, whatever — and expect the seller to be annoyed.
\nThe slow response. Four-day gaps between messages signal you’re not serious. Sellers have other conversations. Respond within 24 hours during active negotiation or explicitly say when you’ll be back.
\nThe fake urgency. “This offer expires in 48 hours” is a tactic that works on inexperienced sellers and irritates experienced ones. Real urgency comes from real constraints; manufactured urgency reads as amateur.
\nThe pressure sale. “I’m talking to three other sellers of similar names” is rarely believable and always grating. If you’re genuinely comparison-shopping, the seller will feel it in your tone without you having to announce it.
\nAsking for payment terms outside escrow. “Can we just wire directly?” from a buyer is the single clearest signal a seller needs to be cautious. The answer should almost always be no.
\nWalking is a negotiating move. Done cleanly, it can unstick a stalled conversation — a seller who was 80% committed may come back a week later with a better counter. Done cleanly means:
\nIf a seller genuinely can’t budge and comps support their price, the right move is to pay it or buy a different name. The domain market is large enough that reasonable substitutes exist for almost every brief.
\nPut together, the disciplined flow is:
\nWhen you make an offer on Deepnom, you land in a secure chat room with the seller — or their broker, on Pro listings. Every counter, accept, reject, and message is logged in one place so you’re not chasing an email thread across three inboxes. The offer cards surface the full history: what you offered, what they countered, what’s pending, what’s resolved.
\nThat transparency helps. A negotiation where both sides can see the same state at the same time tends to close cleaner than one mediated through text messages and Slack screenshots.
\nKeep the negotiation professional and grounded. The numbers matter, but the tone is often what decides whether the deal happens at all.
", "date_published": "2026-04-18T09:20:30.489508+00:00", "date_modified": "2026-04-20T05:29:17.349916+00:00", "authors": [{"name": "The Deepnom Desk"}], "tags": ["Buying Guides"], "image": "https://deepnom.com/media/blog/1000061417.jpg"}, {"id": "https://deepnom.com/blog/how-domain-escrow-works/", "url": "https://deepnom.com/blog/how-domain-escrow-works/", "title": "Domain escrow, explained: why a middleman makes transfers safer", "summary": "A plain-English walkthrough of how domain escrow protects buyers and sellers, what the fees cover, and why wire transfers direct between strangers almost always end badly.", "content_html": "Here’s the awkward truth about buying a domain name from a stranger on the internet: neither of you has any reason to trust the other. The buyer is being asked to wire thousands of dollars to someone they’ve never met, on the promise that a domain name will be handed over afterwards. The seller is being asked to hand over the domain — an asset that, once transferred, is essentially gone — on the promise that the money will follow.
\nThat’s not a comfortable trade for either side. Escrow exists so neither party has to take that leap of faith.
\nA domain escrow service is a neutral third party that holds the money while the transfer happens. The choreography is always the same:
\nIf anything goes wrong — the seller never transfers, the buyer never funds, the domain doesn’t match what was advertised — the escrow service is the arbiter. Funds don’t move until both conditions are met: money in, domain out.
\nThis is a structurally different trust model than “send me the money and I’ll send you the domain.” The escrow service doesn’t need to trust either of you. You don’t need to trust each other. You both trust a known, licensed entity whose whole business model depends on being trustworthy.
\nPeople ask this a lot, especially for smaller deals where the escrow fee starts to feel meaningful. The honest answer is: wire transfers work fine if you know and trust the counterparty. They fail catastrophically when one party is acting in bad faith.
\nA short list of failure modes a wire transfer exposes you to:
\nEscrow defuses all of these. It’s not a hypothetical safety net — the fee is the insurance premium, and the service is the insurance.
\nEscrow.com is the dominant provider for domain transactions and most marketplaces route through them. Their fee schedule is tiered, typically running 0.89% to 3.25% depending on transaction size and payment method. A $5,000 deal costs roughly $50-$150 in escrow fees.
\nThat’s not free. But consider what the fee buys you:
\nMost serious buyers of $1,000+ domains pay the escrow fee without negotiating it. The cost of an unescrowed deal going wrong at that price point is an order of magnitude larger than the fee itself.
\nBefore funding the escrow, a disciplined buyer checks a few things:
\nOn the seller side, the discipline is simpler but still matters:
\nEvery transaction on Deepnom that moves money routes through Escrow.com. We don’t hold funds ourselves, we don’t process card details, and we don’t take custody of domains. What we do is coordinate the negotiation — offers, counters, messaging, signatures — and then hand the closed deal off to escrow for settlement.
\nThat separation matters. A marketplace that holds your money is a marketplace that can fail, get acquired, change policies, or freeze an account without warning. A marketplace that only handles the conversation can’t take your money because it never touches it. Your funds live at Escrow.com during the transfer; your domain lives at your registrar until the moment of handover. Deepnom is the connective tissue.
\nMilestone. A stage of the escrow process — agreement, payment, inspection, transfer, release. Each milestone has a status and a deadline.
\nInspection period. The time after transfer during which the buyer can verify they have what was promised. Usually 1-2 days for domains. If the buyer accepts or the period expires silently, funds release.
\nChargeback. A reversed payment initiated by the buyer’s bank. The reason escrow exists — once funds are released to the seller, a later chargeback is the escrow service’s problem, not the seller’s.
\nKYC. “Know Your Customer” — identity verification that legitimate financial intermediaries are legally required to perform on both sides of a transaction.
\nEscrow isn’t a nice-to-have for stranger-to-stranger deals; it’s the mechanism that makes those deals possible. The fee buys trust, compliance, dispute resolution, and a legal paper trail — and the math works out heavily in your favor on anything over a few hundred dollars.
\nIf you’re buying a domain and the seller pushes back on using escrow, that pushback is the story. Listen to it, ask why, and decide accordingly. Most of the time, the honest answer is “I’m comfortable wiring directly.” Sometimes it isn’t.
", "date_published": "2026-04-18T09:20:30.449782+00:00", "date_modified": "2026-04-20T05:31:13.702518+00:00", "authors": [{"name": "The Deepnom Desk"}], "tags": ["Domain Education"], "image": "https://deepnom.com/media/blog/1000061418.png"}, {"id": "https://deepnom.com/blog/why-com-still-wins/", "url": "https://deepnom.com/blog/why-com-still-wins/", "title": "Why .com still wins — a look at what the numbers actually say", "summary": "New TLDs launched every year, dictionary words in .com kept selling for six figures, and the 'death of .com' keeps being predicted. An honest look at what the sales data shows.", "content_html": "Every year for the last decade, someone has written an article predicting the decline of .com. The argument is always plausible: new TLDs are shorter, cheaper, and often more descriptive. Why would anyone keep paying a premium for an arbitrary three-letter suffix from 1985?
\nThe answer, persistently, is “because the buyers do.” Whatever the theoretical case against .com, the practical data points the other way. This article looks at what that data shows and what it doesn’t.
\nEvery major public sales report — NameBio year-end, Sedo quarterly, DNJournal weekly — breaks sales down by TLD. The pattern is consistent year over year:
\nThese numbers don’t tell you what will happen in the next decade. They tell you that the shift toward alternative TLDs predicted in 2015, 2018, and 2022 didn’t happen in 2016, 2019, or 2023.
\nA few structural reasons the .com premium persists:
\nRecall under load. Under cognitive pressure — in a conversation, on a phone call, from a podcast — people default to .com. If a listener hears “the URL is brand.co,” roughly 30-40% of them will type brand.com anyway. This is well-documented in usability testing and hasn’t changed as alternative TLDs have grown.
\nTrust assumptions. Users assume .com is more legitimate than newer TLDs. This assumption is wrong — a scammer can register either — but user behavior is shaped by the assumption, not by the reality.
\nExisting inventory. Most valuable three, four, and five-letter .com names were registered decades ago. When a company names a new product, the alternatives that come up are “invent a word and get the .com” or “take the exact match in a newer TLD.” Funded founders nearly always choose the former.
\nHabit is a feature, not a bug. When a platform has decades of habit behind it, the habit itself becomes a moat. SMS didn’t go away because iMessage launched. Email didn’t go away because Slack launched. The fact that .com is old is the source of its staying power.
\nThis isn’t to say alternative TLDs are dead. Specific categories have matured into genuine buyer pools:
\nEach of these has a real market. The difference is that buyers in these markets self-identify with the TLD — a founder picking .io isn’t settling, they’re signaling. .com buyers, by contrast, often don’t want to signal anything.
\nPublic sales data has limits worth acknowledging:
\nWhat the data does show is durable: when an acquirer is making a decision that costs them real money, they default to .com at a rate that hasn’t moved in a decade.
\nFor sellers:
\nFor buyers:
\n.com isn’t going anywhere near-term. The data is clear and the structural reasons are stable. That’s an unglamorous observation but a practical one.
", "date_published": "2026-04-17T01:37:43.278738+00:00", "date_modified": "2026-04-20T05:32:58.353853+00:00", "authors": [{"name": "The Deepnom Desk"}], "tags": ["Market Analysis"], "image": "https://deepnom.com/media/blog/1000061419.png"}, {"id": "https://deepnom.com/blog/registrars-registries-and-icann/", "url": "https://deepnom.com/blog/registrars-registries-and-icann/", "title": "Registrars, registries, and ICANN — who actually controls a domain name", "summary": "A clear map of the three layers of the domain system — why your name is managed by a registrar, tracked by a registry, and governed by ICANN — and what that means when something goes wrong.", "content_html": "When you buy a domain, you’re interacting with a chain of organizations whose roles are easy to confuse. Knowing which layer handles what saves time when transfers stall, prices change, or a dispute arises. This is the short version.
\nThree groups sit between you and your domain name.
\nRegistrars are the companies you buy domains from — GoDaddy, Namecheap, Cloudflare Registrar, Porkbun, and hundreds of smaller resellers. A registrar’s job is to sell you domains, manage your DNS, bill you, and act as your interface to the registries above them.
\nRegistries sit one level up. Each top-level domain (.com, .net, .io, .xyz) has exactly one registry that operates its database. Verisign operates .com and .net. Identity Digital operates dozens of newer TLDs. Afilias runs .info. The registry is the authoritative source of truth for which domain names exist under its TLD and who currently holds them.
\nICANN (the Internet Corporation for Assigned Names and Numbers) is the non-profit at the top. It doesn’t run any specific TLD — it sets the rules, accredits registrars, delegates TLDs to registries, and handles disputes. When people say “ICANN charges $0.18 per domain,” they mean ICANN collects a small fee from registries and registrars that ultimately lands in your annual renewal cost.
\nThe transaction looks like this:
\nexample.com at Namecheap.The domain is yours but it lives in three databases simultaneously: ICANN’s accreditation records, Verisign’s zone file, and Namecheap’s customer records.
\nA few real-world consequences:
\nTransferring your domain moves it between registrars, not between registries. Moving example.com from GoDaddy to Porkbun changes the registrar of record but the domain stays in Verisign’s .com zone. This is why transfers are fast and cheap — nothing fundamental changes, only the billing relationship.
Losing access to your registrar does not lose the domain. If your Namecheap account is compromised, the domain still exists at Verisign. You can work with Namecheap’s support (or escalate to ICANN if needed) to regain control. This is your safety net.
\nPricing floors are set at the registry. Verisign sets the wholesale price of .com; registrars add their margin. When Verisign raises wholesale .com prices, every registrar’s retail price rises too. Shopping between registrars optimizes the margin, not the underlying cost.
\nTLD-specific quirks come from the registry. Some TLDs have premium pricing tiers (a dictionary-word .xyz can cost $500/year). Some have trademark-based restrictions. Some require a physical address in a specific country. These rules are set by the registry, not the registrar.
\nSmall issues — renewal billing, DNS not propagating, support unresponsiveness — are registrar problems. Start there.
\nMedium issues — transfer disputes, ownership challenges, bad-faith registrations — can escalate to the registry or to ICANN’s accredited-registrar rules. ICANN has a formal dispute process (UDRP) for trademark-based claims.
\nExtreme issues — TLD going under, court-ordered seizures, national-level takedowns — involve ICANN and sometimes governments. You will likely never deal with these unless you hold a domain in a legally contested space.
\nThe three-layer system looks complicated on paper but is mostly invisible in daily use. You interact with your registrar, your registrar interacts with everything else. When something breaks, knowing which layer owns the problem tells you where to send the support ticket.
", "date_published": "2026-04-17T01:37:43.270177+00:00", "date_modified": "2026-04-20T05:35:07.865541+00:00", "authors": [{"name": "The Deepnom Desk"}], "tags": ["Domain Education"], "image": "https://deepnom.com/media/blog/1000061420.png"}, {"id": "https://deepnom.com/blog/pricing-your-first-domain/", "url": "https://deepnom.com/blog/pricing-your-first-domain/", "title": "Pricing your first domain: a checklist for owners new to listing", "summary": "A practical walk-through of what to consider before putting a price tag on a domain you own — covering comparable sales, negotiation room, and the honest question of whether to list at all.", "content_html": "Most first-time sellers start with the same wrong move: they pick a number that reflects how much the domain is worth to them, then list it. The number that matters is what someone else is willing to pay — and that number is usually more reachable than new sellers assume.
\nThis guide covers the few decisions that actually matter when you’re pricing a domain for the first time.
\nNot every domain you own belongs on the market. A few honest questions:
\nitalianshoerepair.com has a narrow buyer pool — probably one or two people on earth actively want it. You can still list it, but patience will be required.If you’ve decided to list, move on to pricing.
\nThe single most grounded input is historical comparable sales. Pull up NameBio, search for comparable names — same length, same TLD, similar word pattern. Skip the top 5% of outlier sales; look at the median.
\nTwo caveats:
\nUse comparables to anchor your expectations, not to set a floor.
\nA common beginner mistake: listing at the price you’d actually accept, then being surprised when offers come in 40% below.
\nThe convention is simple: list 20-40% above the number you’d genuinely accept. Buyers expect to negotiate. If the listing sits at your honest floor, the negotiation still happens — you just end up selling below it.
\nReports from the aftermarket suggest the average accepted-to-listed ratio sits somewhere around 45-55%. That’s the mid-point of the negotiation band, not a rule for any specific domain.
\nA domain priced at $50,000 might genuinely be worth $50,000 in the sense that one right buyer would pay it. But if the pipeline of matching buyers is two or three per year, you’re looking at a long hold.
\nA domain priced at $3,000 with a pipeline of ten matching buyers a month will likely transact within a quarter.
\nIf you have a portfolio, it’s worth asking which names you’d accept a liquidity discount on. A $5,000 sale in ninety days is often worth more — in compounding opportunity — than a theoretical $20,000 sale in three years.
\nOverselling (“PREMIUM ONE-WORD .COM, AUTHORITY DOMAIN, MILLION-DOLLAR POTENTIAL”) reads as amateur to experienced buyers and erodes trust. A short, factual description performs better:
\nThat’s enough. Don’t promise traffic you can’t prove, and don’t quote a guru saying the name is worth more than it is.
\nIf you really can’t decide, try this:
\nThis won’t maximize your outcome, but it will get the domain moving. The best thing a new seller can do is close a deal, learn what buyers actually paid, and use that data to price the next one better.
", "date_published": "2026-04-17T01:37:43.260105+00:00", "date_modified": "2026-04-20T05:47:41.618193+00:00", "authors": [{"name": "The Deepnom Desk"}], "tags": ["Selling & Listing"], "image": "https://deepnom.com/media/blog/1000061421.jpg"}, {"id": "https://deepnom.com/blog/crypto-domain-naming-2026/", "url": "https://deepnom.com/blog/crypto-domain-naming-2026/", "title": "Crypto domain naming in 2026: what still works, what doesn't", "summary": "A look at what buyers in the Web3 space are actually paying for now — and which naming patterns from the 2021 cycle have quietly lost their market.", "content_html": "The crypto domain market went through a significant bubble and then a significant cooling between 2020 and 2024. Some of the naming patterns that commanded six-figure prices at the peak have lost most of their value; others held up or even grew. If you’re naming a new Web3 project or investing in crypto-adjacent domains, it’s worth looking at what’s actually moving.
\nProtocol-style names. Short, made-up, pronounceable names that don’t explain themselves — aave, yearn, curve, paradigm. This naming style remains dominant for DeFi primitives and infrastructure plays. The bar for a new entry is high because the best examples are taken, but the category is healthy.
\nPrefix/suffix compounds built around trusted roots. “Safe”, “vault”, “pool”, “lend” — these words still signal category clearly. Names like safemint, vaultline, lendnode still find buyers when the underlying word pair is clean and the .com is available.
\nAged exact-match domains. A fifteen-year-old chain.com or swap.com carries a premium that didn’t deflate with the market. These are essentially real estate and their prices reflect that.
\nChain-specific names for the top five chains. Ethereum, Solana, Bitcoin, Base, Polygon — anything that clearly maps to one of these still has a buyer pool. Anything tied to a smaller chain (or one that has since deprecated) struggles.
\n“NFT” in the name. Names containing “nft” have lost most of their premium. The market hasn’t disappeared, but the category isn’t commanding the attention it did in 2021-2022, and buyers no longer assume a name with “nft” in it is worth a brand-aligning premium. Public sales data shows the median “nft” name sale price in 2025 is roughly a tenth of what it was in 2022.
\n“Metaverse” anything. This one has collapsed further than NFT. Outside of a narrow slice of VR/AR infrastructure work, the term is essentially commercial dead weight at this point.
\n“DAO” generic names. Names like xdao.com or anydao.com were briefly interesting when every other project wanted governance-first branding. They’re not worthless, but the premium has gone. Specific narrow-use DAO names (governance tooling, treasury management) still transact.
\nToken ticker variants. Registering $SOMETHING.com for a ticker that had a good week in 2021 was a speculative play. Most of those tickers are now dormant. The domains mostly sit unsold.
\nA few patterns from the current cycle are worth noting:
\nAI-crypto overlap is the most active subcategory. Names that plausibly fit an AI-infrastructure or AI-crypto hybrid play are trading at meaningful prices. Expect this to continue as long as capital flows into that intersection.
\nRestaking and LSTs. The restaking ecosystem has produced a new wave of specific naming — anything plausibly related to lst, restake, eigen derivatives, points. Premium for these names is short-window: they correlate tightly with narrative cycles.
\nNames that don’t signal crypto at all are increasingly common for applications that happen to be crypto underneath. Founders have learned that marketing a consumer product with an aggressively crypto-native name narrows the addressable audience. If you’re building a payments app, payd beats payd.crypto by a margin.
\nThe crypto domain market is calmer and more readable than it was three years ago. Most of the noise has cleared. That makes it easier to spot fundamentals and harder to find bargains.
", "date_published": "2026-04-17T00:45:14.213975+00:00", "date_modified": "2026-04-20T05:50:49.268170+00:00", "authors": [{"name": "The Deepnom Desk"}], "tags": ["Market Analysis"], "image": "https://deepnom.com/media/blog/1000061422.jpg"}, {"id": "https://deepnom.com/blog/buying-a-domain-on-deepnom/", "url": "https://deepnom.com/blog/buying-a-domain-on-deepnom/", "title": "A 5-minute guide to buying a domain on Deepnom", "summary": "The step-by-step of getting from 'I want that name' to 'I own that name' — covering search, offers, escrow, and the actual transfer.", "content_html": "This walkthrough covers what happens when you find a domain on Deepnom and decide to buy it. If you’ve bought a domain through an aftermarket marketplace before, a lot of this will be familiar. If you haven’t, the main thing to know is that the process is mostly waiting — not because it’s slow, but because there are a few handoffs that have to happen in order.
\nThe marketplace supports three ways in: the search bar (semantic, so “lounge bar” finds moody-vibe names, not just names containing the word “bar”), the curated collections by category, and the AI broker modal in the nav — which is useful for vague briefs like “something for a fintech product launching in Europe.”
\nEvery listing page shows the asking price, a short description, and the history where available — how old the domain is, when it was listed, how many views it’s had. If you’re comparing two names, those signals are usually more informative than the description copy.
\nThree options, depending on how the listing is configured:
\nThere’s no obligation at this stage. You can message three or four listings and see which sellers respond. Most do within 24-48 hours.
\nDomain pricing is negotiable in practice even when the listing says BIN. Sellers list high because they know some buyers will accept the asking price — but most deals close below the sticker. A rough rule of thumb: opening offers land 30-60% of ask on longer-tail names, 60-80% on names with clear commercial fit. Lowballs below that get ignored.
\nDon’t overthink it. Ask the seller what they’re actually willing to accept; they’ll usually tell you within a round or two.
\nOnce both parties agree on a price, the transaction is held in escrow. Deepnom uses Escrow.com, which is the industry-standard third-party service for this. The flow is:
\nNeither side trusts the other directly — both trust escrow. There’s an escrow fee (flat rate, typically $20-50 depending on deal size) that’s usually split, though negotiable.
\nThis is where most of the waiting happens. Domain transfers between registrars can take anywhere from 1 to 7 days depending on the TLD, the registrars involved, and whether the domain has a transfer lock or authcode requirements. A .com between two mainstream registrars is usually done in 24-48 hours.
\nYou’ll get email notifications from your registrar at each step: transfer initiated, approval requested, completed. If a transfer stalls for more than 48 hours, contact your new registrar’s support — there’s almost always a small issue (an unacknowledged email, a stray authcode mismatch) that they can resolve in minutes once flagged.
\nOnce the domain is in your account, escrow releases funds and the transaction closes. At this point the name is yours to point wherever you want — a landing page, a redirect, DNS for an app, sitting parked for later.
\nMost new buyers are surprised how little the marketplace is involved in the actual transfer — that’s by design. The marketplace matches you with the seller and holds the agreement together through escrow; the registrars handle the technical hand-off.
\nIf anything genuinely doesn’t work — the seller goes quiet mid-transfer, the escrow gets confused, the name doesn’t match what was listed — Deepnom support is the fallback. Most buyers never need to contact us.
", "date_published": "2026-04-17T00:45:14.203699+00:00", "date_modified": "2026-04-20T05:52:55.521136+00:00", "authors": [{"name": "The Deepnom Desk"}], "tags": ["Buying Guides"], "image": "https://deepnom.com/media/blog/1000061423.jpg"}]}