calendly.com
Domduck has read calendly.com on 6 days across 5 sources, since 2 August 2026. The domain was registered in 2013. Its robots.txt blocks 1 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- 14 September 2026 (2026-09-14)
- The certificate moved from Google Trust Services to Let's Encrypt between 31 August 2026 and 14 September 2026.
- robots.txt started returning HTTP 304 between 31 August 2026 and 14 September 2026, from 200.
- The certificate was renewed between 31 August 2026 and 14 September 2026 and is valid to 3 December 2026.
- 31 August 2026 (2026-08-31)
- DNSSEC was enabled between 17 August 2026 and 31 August 2026.
- robots.txt started returning HTTP 200 between 17 August 2026 and 31 August 2026, from 304.
- 17 August 2026 (2026-08-17)
- DNSSEC was disabled between 3 August 2026 and 17 August 2026.
- The certificate moved from Let's Encrypt to Google Trust Services between 3 August 2026 and 17 August 2026.
- robots.txt started returning HTTP 304 between 3 August 2026 and 17 August 2026, from 200.
- The certificate was renewed between 3 August 2026 and 17 August 2026 and is valid to 3 November 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
Serves llms.txtNo 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 calendly.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
- Let's Encrypt
- Valid
- Yes
- Expires
- 2026-12-03
- Protocol
- TLSv1.3
- Names covered
- 4
- A records
- 2
- AAAA records
- 2
- Mail exchangers
- 5
- Nameservers
- hope.ns.cloudflare.com, roan.ns.cloudflare.com
- DMARC policy
- quarantine
- Registered
- 2013-02-26
- Registrar
- GoDaddy.com, LLC
- Registry status
- client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
How calendly.com compares to other .com domains
Questions
- Does calendly.com block GPTBot?
- No. calendly.com's robots.txt does not disallow GPTBot, though it does not name the agent either.
- Does calendly.com publish an llms.txt file?
- Yes. calendly.com serves an llms.txt file.
- When was calendly.com registered?
- 26 February 2013, through GoDaddy.com, LLC.
- Who issues calendly.com's certificate?
- Let's Encrypt.
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 calendly.com.