Is Buying a Domain Through Saw.com Secure?

Updated

Saw.com states that it prioritizes security above all else, partners with a globally renowned payment processor, and has developed a dedicated transfer process — and it says it has helped thousands of buyers acquire domains. Those are the security-relevant claims the site makes for JAZZ.CO.NZ. What the page does not provide is equally important: it names no specific payment processor, no escrow provider, no dispute policy, and no price. So the honest answer is that the listed safeguards are credible in shape but unverified in detail, and you should confirm the specifics before sending money.

What the JAZZ.CO.NZ page actually says

The page is a single-purpose sale listing. Its evidence is limited to a few statements:

Claim on the page What it tells you
"THIS DOMAIN NAME IS FOR SALE" The domain is being offered, not operated as a live site
"Saw.com has successfully helped thousands of buyers acquire the perfect domain name" Track record claim, self-reported
"Make an Offer" Pricing is negotiated, not fixed or published
"Powered by Secure Exchange" A branded transaction/transfer process
"partnership with a globally renowned payment processor" Third-party payment handling, unnamed
"state-of-the-art process for seamless transfers" Transfer workflow exists, details unspecified

Nothing on the page states a price, a payment method, a refund term, or a login requirement. Treat all of those as open questions rather than assumptions.

The security question, broken into parts

"Secure" in a domain purchase usually means three separate things. Judge each one separately.

1. Payment security

The relevant risk is sending funds to a seller before you control the domain. The page's answer is that payment runs through a partner processor rather than directly to an individual. That is the right structure — but the page does not name the processor, so you cannot independently check its reputation, buyer protection, or chargeback rules. Ask which processor handles the payment and whether funds are held until transfer completes.

2. Transfer security

A .co.nz domain is transferred through the .nz registry framework, which is separate from whatever marketplace you buy through. The page claims a "seamless" transfer process but describes no steps. In practice you want to know: who initiates the registrant change, what authorisation code or confirmation is required, and what happens if the transfer stalls after payment. The registry's own transfer rules govern the mechanics; the marketplace governs the money. Confirm both.

3. Counterparty and dispute security

"Thousands of buyers" is a marketing figure with no supporting detail on the page. There is no stated escrow guarantee, no dispute resolution path, and no refund policy. If something goes wrong, the page gives you no documented remedy to point to.

A practical way to check before you commit

Use the "Make an Offer" flow to open a conversation, then get answers in writing before paying:

  1. Ask who processes the payment and whether it is an escrow-style arrangement where the seller is paid only after the domain is in your control.
  2. Ask for the transfer sequence — who submits what, to which registrar or registry, and the expected timeline.
  3. Ask what happens if the transfer fails after payment: refund, re-attempt, or something else.
  4. Confirm the total cost, including any marketplace or transfer fees, since no price is published.
  5. Verify the domain's current status independently through a .nz registrar lookup so you know it is transferable and not locked or expiring.

If any of these answers is vague, that is your signal to slow down — not proof of a problem, but an absence of the guarantees the page implies.

Who this suits, and who should look elsewhere

  • Reasonable fit: a buyer who wants the exact name jazz.co.nz, is comfortable negotiating a price, and is willing to verify payment and transfer terms directly with the seller before committing.
  • Poor fit: anyone who needs a published price, a documented refund policy, or a named escrow provider visible up front. None of that is on the page, and you would be relying on answers you obtain yourself.

The page's security language is a starting point, not a guarantee. The structure it describes — third-party payment plus a defined transfer process — is the correct shape for a safe domain purchase. Whether it holds up depends on details the page leaves out, so get them confirmed before you make an offer.