facebook.com is a live website, registered in 1997, served from Frankfurt am Main, Germany. It has a valid HTTPS certificate, 5 of 6 common security headers.
Does facebook.com publish the usual trust pages?
All four of the pages a established business normally publishes were found:
about, contact, privacy and terms.
These were checked at conventional paths only, so a site using different URLs may
publish them elsewhere.
How does facebook.com compare with other domains analysed here?
Measured against the 77 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 42% of them (median 496ms) |
|---|---|
| Security headers | More than 94% of them |
| Domain age | Older than 79% of them |
Related domains in this index
Other analysed domains served from the same country:
When was facebook.com registered?
facebook.com was registered on 29 March 1997, which makes it about 29 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 RegistrarSafe, LLC.
Registration runs until 30 March 2034.
The domain carries 6 registry locks, which blocks unauthorised transfer or deletion.
| Registered | 29 March 1997 |
|---|---|
| Expires | 30 March 2034 |
| Registrar | RegistrarSafe, LLC |
| Registry status | client delete prohibited, client transfer prohibited, client update prohibited, server delete prohibited, server transfer prohibited, server update prohibited |
Where is facebook.com hosted?
The first address resolves to infrastructure in Frankfurt am Main, Germany.
The network is operated by Facebook, Inc. (AS32934 Facebook, 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 facebook.com running on?
No platform, framework or analytics fingerprints were found in the homepage markup of facebook.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 200 over
HTTPS.
At 585ms to first byte this response is unremarkable for a homepage measured from a single European location.
The HTML weighs 448KB, which is ordinary for a homepage.
The HTML is compressed with gzip.
| Server header | not disclosed |
|---|---|
| Compression | gzip |
| Page size | 458,686 bytes |
| Declared language | en |
| Mobile viewport | not declared |
What does the homepage say about itself?
The title is only 8 characters, which is short enough that it probably is not describing the page so much as naming it.
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.
| Title | Facebook (8 chars) |
|---|---|
| Meta description | — none — (0 chars) |
| H1 | — none — (0 on the page) |
| Canonical | https://www.facebook.com/ |
| Open Graph title | not set |
| Headings / images | 0 H2s, 0 images (0 without alt text) |
Is facebook.com served over a valid certificate?
The HTTPS certificate is issued by DigiCert Inc and is
valid until 2026-10-12, which is 7 days from the date of this check. It covers
11 hostnames.
- *.facebook.com
- *.facebook.net
- *.fbcdn.net
- *.fbsbx.com
- *.m.facebook.com
- *.messenger.com
- *.xx.fbcdn.net
- *.xy.fbcdn.net
- *.xz.fbcdn.net
- facebook.com
- messenger.com
The certificate expires in 7 days. If renewal is not automated this is close enough to be worth checking today.
Which security headers does it set?
5 of 6 are set (HSTS, Content Security Policy, X-Content-Type-Options, X-Frame-Options, Permissions-Policy). Absent: Referrer-Policy.
| Header | Set | Value |
|---|---|---|
| HSTS | yes | max-age=15552000; preload |
| Content Security Policy | yes | default-src blob: 'self' https://*.fbsbx.com *.facebook.com *.fbcdn.net *.facebook.net *.whatsapp.com *.whatsapp.net;scr |
| X-Content-Type-Options | yes | nosniff |
| X-Frame-Options | yes | DENY |
| Referrer-Policy | no | — |
| Permissions-Policy | yes | accelerometer=(), attribution-reporting=(self), autoplay=(), bluetooth=(), browsing-topics=(self), camera=(self "https:/ |
How is DNS configured for facebook.com?
| IP addresses | 157.240.0.35, 2a03:2880:f177:185:face:b00c::25de |
|---|---|
| Reverse DNS | edge-star-mini-shv-02-fra3.facebook.com, edge-star-mini6-shv-02-fra3.facebook.com |
| Name servers | a.ns.facebook.com, d.ns.facebook.com, b.ns.facebook.com, c.ns.facebook.com |
| Mail (MX) | smtpin.vvv.facebook.com (pri 10) |
| SPF | v=spf1 redirect=_spf.facebook.com |
| TXT records | 7 |
facebook.com resolves to 2 addresses, which indicates load balancing or a CDN rather than a single origin server.
Mail is handled by 1 exchanger.
An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.
Reverse DNS resolves to edge-star-mini-shv-02-fra3.facebook.com, edge-star-mini6-shv-02-fra3.facebook.com, which usually names the hosting provider.
Who runs DNS and mail for facebook.com?
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 facebook.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 1 named authority (issue digicert.com; account=271b0beda0771d006aa3a6c11b05187d456d6c239b46cb5241196095b09c92af), 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 else does facebook.com publish?
A security.txt file is published, giving security researchers a documented way to report vulnerabilities. Very few sites bother.
An ads.txt file is published with 6 entries, which means the site sells programmatic advertising and has declared who may resell its inventory.
What does robots.txt allow?
robots.txt is 35,223 bytes and names
36 user-agent groups.
It disallows all crawlers from the site root.
No sitemap is declared in robots.txt.
AI crawler policy
| Crawler | Policy |
|---|---|
| gptbot | allowed |
| claudebot | allowed |
| perplexitybot | allowed |
| google-extended | allowed |
| applebot-extended | allowed |
robots.txt disallows all general crawlers from the site root, which is an explicit decision to stay out of search results.
No sitemap is declared in robots.txt, so crawlers must discover pages by following links.
Named AI crawlers are explicitly allowed (gptbot, claudebot, perplexitybot, google-extended, applebot-extended).
What structured data does the homepage publish?
No JSON-LD or microdata was found on the homepage.
What does facebook.com load from third parties?
The homepage pulls resources from 1 third-party host (static.xx.fbcdn.net). Each one sees the visitor IP and user agent on every page load.
2 cookies are set before any interaction (fr, sb).
The page links or refers to X/Twitter, Facebook, Instagram, YouTube.
| Cookie | Secure | HttpOnly | SameSite |
|---|---|---|---|
| fr | yes | yes | none/unset |
| sb | yes | yes | none/unset |
Does facebook.com settle on one address?
Plain HTTP redirects to HTTPS, so visitors who type the bare address still land on the secure version.
Both facebook.com and www.facebook.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 facebook.com be crawled?
No readable sitemap was found, so crawlers have to discover every page by following links.
A deliberately invalid URL returns HTTP 200 rather than 404. That is a soft 404: every mistyped or stale link becomes an indexable page, which inflates the site with duplicates.
What tracking does facebook.com run?
No analytics or advertising trackers were detected on the homepage of facebook.com, which is unusual for a commercial site.
How does facebook.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?
The page pulls 2 external stylesheets and 48 external scripts, with 2 carrying defer or async.
Is facebook.com accessible and current?
The page uses 0 landmark elements and 7 ARIA attributes.
There are 4 form inputs but only 3 label elements, so some fields may be unlabelled for screen readers.
No skip-to-content link was found, which keyboard users rely on to bypass navigation.
Can search engines index facebook.com?
Nothing on the homepage prevents indexing: no noindex is set in the robots meta tag or the X-Robots-Tag header.
The homepage carries 28 internal and 0 external links across 0 outside hosts.
Visible text is only 0.1% of the HTML, which indicates the page is assembled in the browser rather than served as content.
How is facebook.com delivered?
The HTML is served with Cache-Control: private, no-cache, no-store, must-revalidate.
HTTP/3 is advertised via alt-svc, so modern browsers will upgrade to QUIC after the first visit.
The TLS certificate also covers 1 subdomain: m.facebook.com.
- m.facebook.com
Frequently asked questions
Does facebook.com set the usual HTTP security headers?
It sets 5 of 6. The ones not present are: Referrer-Policy.
Does facebook.com allow AI crawlers?
robots.txt names no AI crawler specifically, so they fall under the wildcard rule, which does not disallow them.
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 facebook.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 →