About Privatelyregistered

An independent publication about the part of owning a website that stays invisible until something goes wrong.

Why this site exists

Every website sits on a domain, and every domain sits on a registration record and a registrar account. Most owners never look at either. Then a lookup shows something they didn't expect, a renewal lapses, a transfer request arrives that they didn't make, or a customer asks why a copy of their site is taking payments. Privatelyregistered exists to explain that layer before those moments, in plain language.

Our position is simple. Privacy should cut unnecessary exposure without making accountability disappear. A domain owner shouldn't have to publish a home address to the whole internet. But privacy settings don't replace a secured account, a working contact email or lawful processes for abuse and disputes.

Who it's for

Small businesses, bloggers, developers and agencies managing client names, nonprofits, online retailers, professional-service firms and security teams. Also anyone about to buy a domain, or trying to work out whether the website in front of them belongs to who it says it does. We write for readers in the United States, Canada, the United Kingdom, Australia and Europe, and note where country-code rules differ.

What we cover

Six sections: domain privacy, WHOIS, RDDS, privacy services, proxy services, domain registration. Across them we also report on registrar security, DNS and DNSSEC, registry locks, account recovery, domain hijacking, phishing and lookalike domains, and website verification. Articles are published in Behind The Domain.

How articles are written and checked

  • Claims about policy are checked against primary sources: ICANN policy pages, registry documentation and registrar terms of service.
  • We don't invent statistics, quotes or credentials. When we're not sure a fact is true, it doesn't run.
  • Opinion is labeled as opinion and written in the author's voice.
  • Corrections are made in the article, with the updated date shown. Send them through the contact form.
  • We never publish instructions for evading lawful investigations, impersonating businesses, taking over domains, bypassing registrar security, getting at nonpublic registration data without authorization, or exposing private individuals.
  • Advertising is kept separate from editorial decisions. See the disclaimer for how ads and links work.

Who writes it

Articles carry the byline Nathan Cole, a disclosed editorial pen name used by our content team. We use one consistent byline so readers know which voice and standards they're getting.

Nathan Cole

Domain Privacy and Internet Identity Writer

Covers WHOIS and RDDS, registrars, privacy and proxy services, DNS, domain hijacking, account security, phishing and domain ownership. A disclosed editorial pen name used by the Privatelyregistered content team.

Follow on Google News