fb.com
Domduck has read fb.com on 6 days across 5 sources, since 2 August 2026. The domain was registered in 1990. Its robots.txt blocks 8 of the 8 AI crawlers Domduck tracks.
Last checked .
Charts appear once there are seven days of readings.
blocked
What changed
6 days of readings- 28 September 2026 (2026-09-28)
- The certificate was renewed between 14 September 2026 and 28 September 2026 and is valid to 4 October 2026.
- 14 September 2026 (2026-09-14)
- Mail routing changed between 31 August 2026 and 14 September 2026, from mxa-00082601.gslb.pphosted.com, mxb-00082601.gslb.pphosted.com to mx0a-00082601.pphosted.com, mx0b-00082601.pphosted.com, mxa-00082601.gslb.pphosted.com, mxb-00082601.gslb.pphosted.com.
- The certificate was renewed between 31 August 2026 and 14 September 2026 and is valid to 21 September 2026.
- 31 August 2026 (2026-08-31)
- The certificate was renewed between 17 August 2026 and 31 August 2026 and is valid to 7 September 2026.
- 17 August 2026 (2026-08-17)
- The certificate was renewed between 3 August 2026 and 17 August 2026 and is valid to 24 August 2026.
Popularity rank
72 days, lower is betterPosition in the Tranco list, a research ranking of the million most popular domains averaged over thirty days so a single day’s traffic spike cannot move it.
AI crawler policy
No llms.txt · Catch-all blocks every crawlerNo ChatGPT browsing or training
No ChatGPT search surface
No Claude retrieval
No Perplexity citation
Out of Gemini and AI Overviews grounding, Search ranking unaffected
Out of Apple Intelligence training
Out of most open training corpora
Out of TikTok and Doubao
Read from fb.com/robots.txt. “Not named” means the file says nothing about that agent, which is not the same as allowing it: a catch-all rule added later blocks it without anyone deciding to.
What the domain itself says
read directly, not from a vendor- Issuer
- DigiCert Inc
- Valid
- Yes
- Expires
- 2026-10-04
- Protocol
- TLSv1.3
- Names covered
- 2
- A records
- 1
- AAAA records
- 1
- Mail exchangers
- 4
- Nameservers
- a.ns.facebook.com, b.ns.facebook.com, c.ns.facebook.com, d.ns.facebook.com
- DMARC policy
- reject
- Registered
- 1990-05-22
- Registrar
- RegistrarSafe, LLC
- Registry status
- client delete prohibited, client transfer prohibited, client update prohibited, server delete prohibited, server transfer prohibited, server update prohibited
How fb.com compares to other .com domains
Questions
- Does fb.com block GPTBot?
- Yes. fb.com's robots.txt disallows GPTBot by name.
- Does fb.com publish an llms.txt file?
- No. Domduck found no llms.txt at fb.com.
- When was fb.com registered?
- 22 May 1990, through RegistrarSafe, LLC.
- Who issues fb.com's certificate?
- DigiCert Inc.
How this page is made
Every number on this page is a measurement Domduck took itself or read from a public source, on a stated date. Nothing here is written by a language model. Where a value has not changed, no sentence is generated about it.
First reading . 5 sources, 6 days with at least one reading. The popularity rank comes from the Tranco list; the registration record from RDAP, which ICANN requires registries to publish. The certificate, the DNS records and the crawler policy are read by Domduck directly from fb.com.