Domain and Website Research: WHOIS, DNS and Certificate Records
Fake shops, phishing sites and paper companies usually try to earn trust with a website. But behind every site there are records showing when it was registered, where it is hosted and which sites share its infrastructure. This guide shows how to read those records passively, that is, without interacting with the site in any way.
WHOIS and RDAP: the domain’s identity
A domain’s WHOIS record (or RDAP, the newer standard) shows its registration date, expiry date, registrar and name servers. Since the EU General Data Protection Regulation (GDPR) took effect on 25 May 2018, the registrant’s name, e-mail and phone number are hidden in most records.
- Registration date: if a company that claims “20 years in business” registered its domain last month, that is a strong signal.
- Historical WHOIS: records from before 2018 may still show the owner’s name and e-mail. Some services offer this history with a limited number of free lookups.
- .tr domains: managed and looked up through the TRABIS system.
DNS records: where is the site, where is the e-mail?
- A / AAAA: the site’s IP address.
- MX: which service handles the e-mail (a business mail service or a free one?).
- TXT: verification codes (for example
google-site-verification) and e-mail sending permissions. They reveal which services are in use. - NS and CNAME: what infrastructure the site runs on (for example a ready-made e-commerce platform).
SSL certificate records
SSL certificates issued for a site are written to public logs called Certificate Transparency. Searching those logs with a tool such as crt.sh shows you:
- The domain’s subdomains:
mail.,admin.,test.,panel.and so on. - The date of the first certificate, a good hint of when the site went live.
- Several domains on the same certificate, which most likely belong to the same person or organisation.
Reverse IP and shared infrastructure
A reverse IP lookup lists other sites on the same IP address. Careful: at large hosting companies and services such as Cloudflare, thousands of unrelated sites share one IP. The result only means something if the site uses a dedicated server.
Shared tracking codes
Google Analytics, Google Tag Manager, AdSense or ad pixel IDs in a site’s source code can link sites run by the same person. If the same Analytics ID appears on two supposedly independent sites, the same person is very likely behind both. Look for IDs starting with G-, UA-, GTM- and pub- in the source; some services list the sites that share them.
History and safe inspection
- Web archives: the site’s first version and old “About” and “Team” pages (web archives guide).
- urlscan.io: shows a screenshot of a suspicious site, the domains it contacts and earlier scans, without opening it on your own computer.
Step by step
- From WHOIS/RDAP, note the registration date, registrar and name servers.
- Check historical WHOIS for the owner’s name or e-mail.
- Pull the DNS records: IP, e-mail service, verification codes.
- Search the domain on crt.sh: subdomains and the first certificate date.
- Find tracking codes in the source and look for other sites using the same code.
- Check the site’s history in a web archive and compare your findings with the company’s claims (company register guide).
To find a site’s forgotten pages with search engines, see our Google dorking guide too.
Practise this in a mission
Frequently asked questions
Why can’t I see the owner’s name in WHOIS?
Since GDPR took effect on 25 May 2018, personal data is hidden in most records. Older historical WHOIS records sometimes still show it.
How can I tell when a website was set up?
Look at the domain’s registration date (WHOIS/RDAP), the date of its first SSL certificate (crt.sh) and its first capture in a web archive together.
Do sites on the same IP belong to the same person?
Not always. With shared hosting and services such as Cloudflare, thousands of unrelated sites share one IP; it only means something on dedicated servers.