✓ Independen — bukan situs pemerintah ✓ Setiap langkah dicocokkan dengan portal resmi ✓ Kami tidak pernah meminta NIK, OTP, atau kata sandi Anda

privacy.com — domain analysis

privacy.com is a live website built on Webflow, registered in 1996, served from San Francisco, United States. It has a valid HTTPS certificate, 3 of 6 common security headers.

Searched as: “privacy .com br”, “privacy .com”.

200HTTP status
359msResponse time
1,312Words on the homepage
3/6Security headers set

What is privacy.com about?

The words appearing most often on the homepage, excluding common filler, are
a rough indication of subject matter rather than a description of the business:

  • privacy ×43
  • card ×28
  • cards ×20
  • information ×9
  • credit ×9
  • virtual ×8
  • secure ×7
  • data ×7
  • security ×6
  • online ×6

Does privacy.com publish the usual trust pages?

Found: about, privacy, terms. Not found at the usual addresses:
contact.

These were checked at conventional paths only, so a site using different URLs may
publish them elsewhere.

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

Measured against the 463 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 58% of them
(median 453ms)
Security headers More than 78% of them
Domain age Older than 83% of them

Related domains in this index

Analysed domains built on a similar stack:

Other analysed domains served from the same country:

When was privacy.com registered?

privacy.com was registered on 3 February 1996, which makes it about 30 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 NameCheap, Inc..

Registration runs until 4 February 2027.

The domain carries 1 registry lock, which blocks unauthorised transfer or deletion.

Registered 3 February 1996
Expires 4 February 2027
Registrar NameCheap, Inc.
Registry status client transfer prohibited

Where is privacy.com hosted?

The first address resolves to infrastructure in San Francisco, United States.

The network is operated by Webflow, Inc (AS209242 Cloudflare London, LLC).

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 privacy.com running on?

privacy.com exposes 2 identifiable technologies: Webflow, 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.

  • Webflow
  • Cloudflare

How does the homepage respond?

The server answered with HTTP 200 over
HTTPS.

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

The HTML weighs 84KB, which is ordinary for a homepage.

The HTML is compressed with gzip.

Server header cloudflare
Compression gzip
Page size 86,233 bytes
Declared language en
Mobile viewport declared

What does the homepage say about itself?

The title is 51 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.

There are 2 H1 headings. One is conventional; several dilute the signal about what the page is primarily about.

All 41 images on the homepage have alt attributes.

Title Privacy.com Virtual Cards – Secure, Temporary Cards (51 chars)
Meta description — none — (0 chars)
H1 Privacy and security built into your payments (2 on the page)
Canonical not set
Open Graph title not set
Headings / images 12 H2s, 41 images (0 without alt text)

Is privacy.com served over a valid certificate?

The HTTPS certificate is issued by Google Trust Services and is
valid until 2027-01-13, which is 56 days from the date of this check. It covers
1 hostname.

  • privacy.com

The certificate has 56 days left to run.

It covers 1 hostname, so it was issued for this site specifically.

Which security headers does it set?

3 of 6 are set (Content Security Policy, X-Content-Type-Options, X-Frame-Options). Absent: HSTS, Referrer-Policy, Permissions-Policy.

Without HSTS, a browser that has never visited before will try HTTP first, which is the window a network attacker needs.

Header Set Value
HSTS no —
Content Security Policy yes frame-ancestors 'self'
X-Content-Type-Options yes nosniff
X-Frame-Options yes SAMEORIGIN
Referrer-Policy no —
Permissions-Policy no —

How is DNS configured for privacy.com?

IP addresses 198.202.211.1
Reverse DNS 198.202.211.1
Name servers ns-1478.awsdns-56.org, ns-1714.awsdns-22.co.uk, ns-862.awsdns-43.net, ns-91.awsdns-11.com
Mail (MX) aspmx.l.google.com (pri 1), alt3.aspmx.l.google.com (pri 10), alt4.aspmx.l.google.com (pri 10), alt1.aspmx.l.google.com (pri 5), alt2.aspmx.l.google.com (pri 5)
SPF v=spf1 a mx include:spf.mtasv.net include:customeriomail.com include:_spf.google.com include:mail.zendesk.com ~all
TXT records 3

privacy.com resolves to a single address, so there is no DNS-level redundancy.

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 198.202.211.1, which usually names the hosting provider.

Who runs DNS and mail for privacy.com?

DNS is operated by Amazon Route 53 rather than self-hosted name servers.

Mail is handled by Google Workspace.

No AAAA records are published, so the site is reachable over IPv4 only.

What else is worth noting about privacy.com?

3 of 7 externally hosted scripts carry no subresource integrity hash. If one of those hosts were compromised, the replacement script would run with full access to the page.

1 email address appears in the homepage markup, where address-harvesting crawlers will find it.

Can privacy.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.

CAA records restrict certificate issuance to 6 named authorities (issue digicert.com, issue letsencrypt.org, issue pki.goog; cansignhttpexchanges=yes, issuewild amazon.com), so no other CA should be able to issue 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 384 bytes and names
1 user-agent group.

It does not blanket-disallow general crawlers.

No sitemap is declared in robots.txt.

AI crawler policy

robots.txt names no AI crawlers specifically, so they fall under whatever rule
applies to User-agent: *.

What structured data does the homepage publish?

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

What does privacy.com load from third parties?

The homepage pulls resources from 4 third-party hosts (app.optibase.io, cdn.jsdelivr.net, cdn.prod.website-files.com, d3e54v103j8qbb.cloudfront.net). Each one sees the visitor IP and user agent on every page load.

1 cookie is set before any interaction (_cfuvid).

1 resource is referenced over plain HTTP on an HTTPS page, which browsers block or flag as mixed content.

The page links or refers to X/Twitter.

Cookie Secure HttpOnly SameSite
_cfuvid yes yes none

Does privacy.com settle on one address?

Plain HTTP redirects to HTTPS, so visitors who type the bare address still land on the secure version.

Both privacy.com and www.privacy.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 privacy.com be crawled?

A sitemap is served at https://privacy.com/sitemap.xml listing 440 entries.

The most recent lastmod date is 2026-10-28.

A deliberately invalid URL correctly returns HTTP 404, so missing pages will not be indexed.

What tracking does privacy.com run?

No analytics or advertising trackers were detected on the homepage of privacy.com, which is unusual for a commercial site.

How does privacy.com look when shared?

All five social preview tags are present, so links shared to social platforms and chat apps will render with a title, description and image.

How are images, fonts and scripts handled?

41 images on the homepage, 41 of them lazy-loaded (100%).

Modern image formats are in use (1 WebP/AVIF references).

The page pulls 2 external stylesheets and 7 external scripts, 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 privacy.com accessible and current?

The page uses 6 landmark elements and 14 ARIA attributes.

No skip-to-content link was found, which keyboard users rely on to bypass navigation.

Can search engines index privacy.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 57 internal and 16 external links across 9 outside hosts.

Visible text makes up 9.7% of the HTML.

The heading outline skips 1 level, which breaks the document structure screen readers navigate by.

How is privacy.com delivered?

No Cache-Control header is sent for the HTML, so caching behaviour is left to browser defaults.

HTTP/3 is advertised via alt-svc, so modern browsers will upgrade to QUIC after the first visit.

Frequently asked questions

What is privacy .com?

People who search for “privacy .com” are looking for the website at privacy.com. privacy.com is a live website built on Webflow, registered in 1996, served from San Francisco, United States. It has a valid HTTPS certificate, 3 of 6 common security headers.

Does privacy.com set the usual HTTP security headers?

It sets 3 of 6. The ones not present are: HSTS, Referrer-Policy, Permissions-Policy.

Does privacy.com allow AI crawlers?

robots.txt names no AI crawler specifically, so they fall under the wildcard rule, which does not disallow them.

What is privacy.com built with?

The homepage exposes these fingerprints: Webflow, 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 18 November 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 privacy.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 18 November 2026.
Analyse another domain →

⚠ Tetap waspada

Urus adalah panduan independen, bukan situs pemerintah. Lakukan prosesnya hanya di portal resmi. Tidak ada instansi resmi yang meminta OTP, NIK, kata sandi, atau PIN Anda lewat telepon, pesan, atau "bantuan" — jangan pernah memberikannya.

Urus adalah panduan independen dan tidak berafiliasi dengan instansi pemerintah mana pun. Biaya, tautan, dan langkah dapat berubah — selalu konfirmasi di portal resmi sebelum bertindak. Ini informasi umum, bukan nasihat hukum atau keuangan.