{"id":211,"date":"2017-02-11T22:49:23","date_gmt":"2017-02-11T22:49:23","guid":{"rendered":"http:\/\/www.publiconsulting.com\/wordpress\/webliteracy\/chapter\/finding-out-who-owns-a-server\/"},"modified":"2018-01-19T11:38:52","modified_gmt":"2018-01-19T11:38:52","slug":"finding-out-who-owns-a-server","status":"publish","type":"chapter","link":"https:\/\/www.publiconsulting.com\/wordpress\/webliteracy\/chapter\/finding-out-who-owns-a-server\/","title":{"rendered":"Finding Out Who Owns a Domain"},"content":{"raw":"\n

Many times you'll want to know who is behind a domain. This used to be relatively easy to find out in the past: when a person bought a domain, their name was put into a \"registry\" -- which is sort of like the \"phonebook of domains\".  (Yes, I know: many of you are probably now asking what a \"phonebook\" is...)<\/p>\n

Back then, to find out who owned a domain, you'd just go and look it up, using a service called WHOIS.<\/p>\n

Unfortunately, things got more complicated. People who had their email addresses and names in the \"domain phonebook\" would get spam email, or the information displayed on the record would be used to try and hack their site. And many people -- for example, political dissidents -- had good reason to not reveal their names. And so a lot of the \"registrars\" (the people who you by your domain name from) started offering masking services, which hide the owner of the domain.<\/p>\n

Nowadays, if you want to find out who owns a domain, whois-type services are a good first stop, even though they will usually fail for smaller sites.<\/p>\n

To look up domain ownership, we recommend a tool called Domain Dossier<\/a>. Go to the site and type in your root URL and check all the checkboxes:<\/p>\n

\"\"<\/p>\n

When the identity is not masked, you'll be able to see the owner of the domain. The first place to look is \"Registrant Name\" and \"Registrant Organization\":<\/p>\n

\"\"<\/p>\n

Occasionally, you may not get a useful name from the record, but the address might be telling.<\/p>\n

If the name is masked in Domain Dossier, you'll get a record that looks like this:<\/p>\n

\"\"<\/p>\n

You may also see the name of a masking service, such as \"Domains by Proxy\":<\/p>\n

\"\"<\/p>\n

In this case, the registrant is not from Arizona, and not named \"Domains by Proxy\" -- that is just the masking service.<\/p>\n

Again, it's important to note that masking is common enough these days that it shouldn't cause suspicion.<\/p>\n

While domain owners can hide their names, they cannot hide the date the domain was registered. As we'll discuss in another chapter, this is often useful information. By looking at the domain registration date you can often get a sense of whether a site has a long history behind it, or has been spun up for a specific purpose.<\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n\n","rendered":"

Many times you’ll want to know who is behind a domain. This used to be relatively easy to find out in the past: when a person bought a domain, their name was put into a “registry” — which is sort of like the “phonebook of domains”.  (Yes, I know: many of you are probably now asking what a “phonebook” is…)<\/p>\n

Back then, to find out who owned a domain, you’d just go and look it up, using a service called WHOIS.<\/p>\n

Unfortunately, things got more complicated. People who had their email addresses and names in the “domain phonebook” would get spam email, or the information displayed on the record would be used to try and hack their site. And many people — for example, political dissidents — had good reason to not reveal their names. And so a lot of the “registrars” (the people who you by your domain name from) started offering masking services, which hide the owner of the domain.<\/p>\n

Nowadays, if you want to find out who owns a domain, whois-type services are a good first stop, even though they will usually fail for smaller sites.<\/p>\n

To look up domain ownership, we recommend a tool called Domain Dossier<\/a>. Go to the site and type in your root URL and check all the checkboxes:<\/p>\n

\"\"<\/p>\n

When the identity is not masked, you’ll be able to see the owner of the domain. The first place to look is “Registrant Name” and “Registrant Organization”:<\/p>\n

\"\"<\/p>\n

Occasionally, you may not get a useful name from the record, but the address might be telling.<\/p>\n

If the name is masked in Domain Dossier, you’ll get a record that looks like this:<\/p>\n

\"\"<\/p>\n

You may also see the name of a masking service, such as “Domains by Proxy”:<\/p>\n

\"\"<\/p>\n

In this case, the registrant is not from Arizona, and not named “Domains by Proxy” — that is just the masking service.<\/p>\n

Again, it’s important to note that masking is common enough these days that it shouldn’t cause suspicion.<\/p>\n

While domain owners can hide their names, they cannot hide the date the domain was registered. As we’ll discuss in another chapter, this is often useful information. By looking at the domain registration date you can often get a sense of whether a site has a long history behind it, or has been spun up for a specific purpose.<\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n","protected":false},"author":1,"menu_order":1,"template":"","meta":{"pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":[],"pb_section_license":""},"chapter-type":[],"contributor":[],"license":[],"class_list":["post-211","chapter","type-chapter","status-publish","hentry"],"part":152,"_links":{"self":[{"href":"https:\/\/www.publiconsulting.com\/wordpress\/webliteracy\/wp-json\/pressbooks\/v2\/chapters\/211","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.publiconsulting.com\/wordpress\/webliteracy\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/www.publiconsulting.com\/wordpress\/webliteracy\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/www.publiconsulting.com\/wordpress\/webliteracy\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":1,"href":"https:\/\/www.publiconsulting.com\/wordpress\/webliteracy\/wp-json\/pressbooks\/v2\/chapters\/211\/revisions"}],"predecessor-version":[{"id":212,"href":"https:\/\/www.publiconsulting.com\/wordpress\/webliteracy\/wp-json\/pressbooks\/v2\/chapters\/211\/revisions\/212"}],"part":[{"href":"https:\/\/www.publiconsulting.com\/wordpress\/webliteracy\/wp-json\/pressbooks\/v2\/parts\/152"}],"metadata":[{"href":"https:\/\/www.publiconsulting.com\/wordpress\/webliteracy\/wp-json\/pressbooks\/v2\/chapters\/211\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/www.publiconsulting.com\/wordpress\/webliteracy\/wp-json\/wp\/v2\/media?parent=211"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/www.publiconsulting.com\/wordpress\/webliteracy\/wp-json\/pressbooks\/v2\/chapter-type?post=211"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/www.publiconsulting.com\/wordpress\/webliteracy\/wp-json\/wp\/v2\/contributor?post=211"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/www.publiconsulting.com\/wordpress\/webliteracy\/wp-json\/wp\/v2\/license?post=211"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}