Skip to content

people.com — domain analysis

TweetSharePinShare0 Shares people.com blocks automated analysis, answering with Cloudflare mitigation instead of its homepage. Its certificate, DNS and registration records are still readable and are reported below. This…

1 min read
Share Facebook X Pinterest WhatsApp
Tweet
Share
Pin
Share
0 Shares

people.com blocks automated analysis, answering with Cloudflare mitigation instead of its homepage. Its certificate, DNS and registration records are still readable and are reported below.

This site blocks automated analysis.
It answered our request with Cloudflare mitigation rather than its
homepage, so nothing below is derived from its actual content — doing so would describe
the bot wall, not the site. The certificate and robots.txt data are still accurate,
because those are served to everyone.

403HTTP status
108msResponse time
0Words on the homepage
0/6Security headers set

How does people.com compare with other domains analysed here?

Measured against the 76 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 443ms)
Domain age Older than 93% 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.

Other analysed domains served from the same country:

When was people.com registered?

people.com was registered on 2 June 1994, which makes it about 32 years old.

A registration this old means the domain has been renewed repeatedly, which costs money every year and is not something abandoned or disposable projects tend to do.

The registrar of record is MarkMonitor Inc..

Registration runs until 1 June 2027.

The domain carries 6 registry locks, which blocks unauthorised transfer or deletion.

Registered 2 June 1994
Expires 1 June 2027
Registrar MarkMonitor Inc.
Registry status client delete prohibited, client transfer prohibited, client update prohibited, server delete prohibited, server transfer prohibited, server update prohibited

Where is people.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 people.com running on?

No platform, framework or analytics fingerprints were found in the homepage markup of people.com. That usually means hand-written HTML, an uncommon stack, or a page assembled entirely at the edge.

No recognisable platform, framework or analytics fingerprints were found in the homepage markup.

How does the homepage respond?

The server answered with HTTP 403 over
HTTPS.

At 108ms to first byte this response is fast for a homepage measured from a single European location.

The HTML alone is 664KB before images, stylesheets or scripts are counted, which is heavy for a document that browsers must parse before anything renders.

The HTML is compressed with gzip.

Server header cloudflare
Compression gzip
Page size 680,317 bytes
Declared language not declared
Mobile viewport not declared

What does the homepage say about itself?

The homepage has no title element at all, which leaves search engines to invent one from the page content.

There is no meta description, so the snippet shown in search results is assembled by the search engine from whatever text it considers relevant.

No H1 heading was found, so the page offers no single top-level statement of what it is.

No viewport meta tag is declared, so mobile browsers will render the page at desktop width and scale it down.

The html element declares no lang attribute, which removes a signal both screen readers and translation tools rely on.

Title — none — (0 chars)
Meta description — none — (0 chars)
H1 — none — (0 on the page)
Canonical not set
Open Graph title not set
Headings / images 0 H2s, 0 images (0 without alt text)

Is people.com served over a valid certificate?

The HTTPS certificate is issued by Let's Encrypt and is
valid until 2026-11-12, which is 38 days from the date of this check. It covers
2 hostnames.

  • *.people.com
  • people.com

The certificate has 38 days left to run.

It covers 2 hostnames, so it was issued for this site specifically.

Let's Encrypt certificates are free and run on 90-day terms, so this site is almost certainly renewing automatically.

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.

Header Set Value

How is DNS configured for people.com?

IP addresses 172.66.1.220, 162.159.141.224, 2606:4700:7::1d8, 2a06:98c1:58::1d8
Reverse DNS 172.66.1.220, 162.159.141.224
Name servers blue.foundationdns.com, blue.foundationdns.net, blue.foundationdns.org
Mail (MX) alt1.aspmx.l.google.com (pri 5), alt2.aspmx.l.google.com (pri 5), aspmx.l.google.com (pri 1), alt3.aspmx.l.google.com (pri 10), alt4.aspmx.l.google.com (pri 10)
SPF v=spf1 include:_spfti1.timeinc.com include:_spfti2.timeinc.com include:spf.mandrillapp.com include:_spf.google.com include:mail.zendesk.com include:amazonses.com ~all
TXT records 22

people.com resolves to 4 addresses, which indicates load balancing or a CDN rather than a single origin server.

Mail is handled by 5 exchangers.

An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.

Reverse DNS resolves to 172.66.1.220, 162.159.141.224, which usually names the hosting provider.

Can people.com be spoofed in email?

DMARC is set to reject, the strictest setting: mail that fails authentication is refused outright. This is the configuration that actually stops domain spoofing.

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?

robots.txt is 3,457 bytes and names
78 user-agent groups.

It does not blanket-disallow general crawlers.

Sitemaps declared:

  • https://people.com/sitemap.xml
  • https://people.com/google-news-sitemap.xml

AI crawler policy

Crawler Policy
gptbot allowed
claudebot allowed
perplexitybot blocked
google-extended allowed
ccbot allowed
applebot-extended allowed
bytespider allowed
anthropic-ai allowed

2 sitemaps are declared in robots.txt, which gives crawlers a direct list of URLs.

AI crawler policy is selective: perplexitybot blocked, gptbot, claudebot, google-extended, ccbot, applebot-extended, bytespider, anthropic-ai allowed.

What structured data does the homepage publish?

No JSON-LD or microdata was found on the homepage.

Frequently asked questions

Does people.com allow AI crawlers?

No — robots.txt blocks perplexitybot.

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 people.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 →

Tweet
Share
Pin
Share
0 Shares

You Might Also Like

Newsletter

Get the Buzz First

Celebrity and influencer news straight to your inbox — no spam, just the good stuff.

Get the daily celebrity buzz in your inbox.

Join thousands who never miss a headline. Unsubscribe any time.