thispersondoesnotexist.com is a live website, registered in 2019, served from Toronto, Canada. It has a valid HTTPS certificate, 0 of 6 common security headers.
Does thispersondoesnotexist.com publish the usual trust pages?
None of about, contact, privacy or terms could be found at their usual addresses.
That is common for small or single-purpose sites, and it is also what a disposable
site looks like, so it is worth noting rather than concluding from.
These were checked at conventional paths only, so a site using different URLs may
publish them elsewhere.
How does thispersondoesnotexist.com compare with other domains analysed here?
Measured against the 81 domains in this index. This is a
small, self-selected sample — the domains people happened to look up — not a
representative sample of the web.
| Response time | Faster than 80% of them (median 491ms) |
|---|---|
| Security headers | More than 0% of them |
| Domain age | Older than 29% of them |
Related domains in this index
Analysed domains sharing the same network (AS13335 Cloudflare, Inc.):
Sharing a network means sharing a host or CDN. It implies nothing about a
relationship between the sites themselves.
Analysed domains built on a similar stack:
Other analysed domains served from the same country:
When was thispersondoesnotexist.com registered?
thispersondoesnotexist.com was registered on 9 February 2019, which makes it about 7 years old.
The registrar of record is Squarespace Domains II LLC.
Registration runs until 9 February 2027.
The domain carries 2 registry locks, which blocks unauthorised transfer or deletion.
| Registered | 9 February 2019 |
|---|---|
| Expires | 9 February 2027 |
| Registrar | Squarespace Domains II LLC |
| Registry status | client delete prohibited, client transfer prohibited |
Where is thispersondoesnotexist.com hosted?
The first address resolves to infrastructure in Toronto, Canada.
The network is operated by Cloudflare, Inc. (AS13335 Cloudflare, Inc.).
Hosting location describes where the responding server sits, not where the business is. A CDN will report its nearest edge rather than the origin.
What is thispersondoesnotexist.com running on?
thispersondoesnotexist.com exposes 1 identifiable technology: Cloudflare.
Cloudflare sits in front of the origin, so the server header, IP addresses and response timing describe the edge rather than the machine actually running the site.
- Cloudflare
How does the homepage respond?
The server answered with HTTP 200 over
HTTPS.
At 156ms to first byte this response is fast for a homepage measured from a single European location.
At 4KB the HTML is unusually small, which typically means the page builds itself client-side after load.
The HTML is compressed with gzip.
| Server header | cloudflare |
|---|---|
| Compression | gzip |
| Page size | 4,532 bytes |
| Declared language | en |
| Mobile viewport | declared |
What does the homepage say about itself?
The title is 26 characters, inside the range that displays without truncation.
There is no meta description, so the snippet shown in search results is assembled by the search engine from whatever text it considers relevant.
All 1 images on the homepage have alt attributes.
| Title | This Person Does Not Exist (26 chars) |
|---|---|
| Meta description | — none — (0 chars) |
| H1 | "thispersondoesnotexist"Domain For Sale (1 on the page) |
| Canonical | not set |
| Open Graph title | not set |
| Headings / images | 0 H2s, 1 images (0 without alt text) |
Is thispersondoesnotexist.com served over a valid certificate?
The HTTPS certificate is issued by Google Trust Services and is
valid until 2026-12-17, which is 73 days from the date of this check. It covers
2 hostnames.
- thispersondoesnotexist.com
- *.thispersondoesnotexist.com
The certificate has 73 days left to run.
It covers 2 hostnames, so it was issued for this site specifically.
Which security headers does it set?
None of the 6 headers checked are set. That is the default state of most servers rather than evidence of a problem, but it means the browser is given no instructions it could otherwise act on.
Without HSTS, a browser that has never visited before will try HTTP first, which is the window a network attacker needs.
With no Content Security Policy, any script that reaches the page — including one injected through a compromised third-party dependency — runs with full access to it.
| Header | Set | Value |
|---|---|---|
| HSTS | no | — |
| Content Security Policy | no | — |
| X-Content-Type-Options | no | — |
| X-Frame-Options | no | — |
| Referrer-Policy | no | — |
| Permissions-Policy | no | — |
How is DNS configured for thispersondoesnotexist.com?
| IP addresses | 172.67.130.241, 104.21.3.164, 2606:4700:3033::6815:3a4, 2606:4700:3033::ac43:82f1 |
|---|---|
| Reverse DNS | 172.67.130.241, 104.21.3.164 |
| Name servers | roxy.ns.cloudflare.com, max.ns.cloudflare.com |
| Mail (MX) | _dc-mx.0287d668c2bf.thispersondoesnotexist.com (pri 10) |
| SPF | not published |
| TXT records | 0 |
thispersondoesnotexist.com resolves to 4 addresses, which indicates load balancing or a CDN rather than a single origin server.
Mail is handled by 1 exchanger.
No SPF record is published. Receiving servers therefore have no published rule for who may send mail as this domain, which makes spoofing it materially easier.
Reverse DNS resolves to 172.67.130.241, 104.21.3.164, which usually names the hosting provider.
Who runs DNS and mail for thispersondoesnotexist.com?
DNS is operated by Cloudflare rather than self-hosted name servers.
Mail exchangers point at hosts that do not match any major provider, which usually means self-hosted or niche-provider mail.
The domain publishes AAAA records and accepts connections over IPv6.
Can thispersondoesnotexist.com be spoofed in email?
No DMARC record is published, so there is no instruction telling receiving servers what to do with mail that fails authentication. In practice that means forged mail from this domain is likely to be delivered.
No CAA records are published, so any certificate authority may issue a certificate for this domain.
The zone is not DNSSEC-signed. That is still the norm for most domains, but it means DNS answers cannot be cryptographically verified.
What does robots.txt allow?
No robots.txt was served. Crawlers treat a missing file as permission to crawl
everything, so this is an open crawl policy by default rather than a blocked one.
What structured data does the homepage publish?
No JSON-LD or microdata was found on the homepage.
What does thispersondoesnotexist.com load from third parties?
The homepage pulls resources from 1 third-party host (fonts.googleapis.com). Each one sees the visitor IP and user agent on every page load.
No cookies are set on first load.
Does thispersondoesnotexist.com settle on one address?
Plain HTTP redirects to HTTPS, so visitors who type the bare address still land on the secure version.
Both thispersondoesnotexist.com and www.thispersondoesnotexist.com answer with 200 and neither redirects to the other. Search engines therefore see two complete copies of the site, and link equity is split between them unless a canonical tag resolves it.
How easily can thispersondoesnotexist.com be crawled?
No readable sitemap was found, so crawlers have to discover every page by following links.
A deliberately invalid URL correctly returns HTTP 404, so missing pages will not be indexed.
What tracking does thispersondoesnotexist.com run?
No analytics or advertising trackers were detected on the homepage of thispersondoesnotexist.com, which is unusual for a commercial site.
How does thispersondoesnotexist.com look when shared?
No Open Graph or Twitter Card tags are present. Links shared to social platforms will fall back to whatever the platform can scrape, usually just a bare URL.
How are images, fonts and scripts handled?
1 image on the homepage, 0 of them lazy-loaded (0%).
All image references use JPEG, PNG or GIF. WebP or AVIF typically cut image weight substantially at the same visual quality.
No srcset attributes are used, so every device is served the same image size regardless of screen.
Fonts are loaded from Google Fonts, which means every page view also contacts Google. Self-hosting removes that dependency.
The page pulls 1 external stylesheet and 1 external script, with 1 carrying defer or async.
Responses carry Cloudflare edge headers, so content is served from a CDN rather than straight from the origin.
Is thispersondoesnotexist.com accessible and current?
The page uses 0 landmark elements and 0 ARIA attributes.
No skip-to-content link was found, which keyboard users rely on to bypass navigation.
Can search engines index thispersondoesnotexist.com?
Nothing on the homepage prevents indexing: no noindex is set in the robots meta tag or the X-Robots-Tag header.
No canonical URL is declared, which leaves duplicate addresses of this page to be resolved by the search engine.
The homepage carries 1 internal and 0 external links across 0 outside hosts.
Visible text is only 2.8% of the HTML, which indicates the page is assembled in the browser rather than served as content.
How is thispersondoesnotexist.com delivered?
The HTML is served with Cache-Control: no-store, no-cache, must-revalidate.
HTTP/3 is advertised via alt-svc, so modern browsers will upgrade to QUIC after the first visit.
No favicon is declared in the markup.
Frequently asked questions
Does thispersondoesnotexist.com set the usual HTTP security headers?
It sets 0 of 6. The ones not present are: HSTS, Content Security Policy, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy.
Does thispersondoesnotexist.com allow AI crawlers?
No robots.txt is served, so nothing is disallowed and AI crawlers are free to read the site.
What is thispersondoesnotexist.com built with?
The homepage exposes these fingerprints: Cloudflare. A site behind a CDN or rendered server-side may use more than it reveals.
Where does this data come from?
Every figure was measured by our own server on 5 October 2026: DNS lookups, one HTTPS request to the homepage, a TLS handshake and a request for robots.txt. No third-party SEO API is involved.
Is any of this traffic or authority data?
No. Traffic, authority and ranking figures cannot be measured by inspecting a domain, only modelled. Everything here is a direct observation.
I own thispersondoesnotexist.com and want this page removed.
Ask through the contact page on this site, from an address at the domain, and the report will be taken down. It only ever shows what the domain already serves publicly.
Analysed 5 October 2026.
Analyse another domain →